 So I thought it'd be useful to run through another feature that's available in vCloud Director 5.1 and that's snapshots So they're similar to vSphere snapshots, which we're probably all familiar with But with a couple of differences the main difference being that snapshots are no longer multiple chains deep So with vCloud Director 5.1 You can only take a single snapshot and revert to that snapshot or take another snapshot which would overwrite it So that's something to bear in mind when utilizing snapshots. However, they're still extremely useful for de-risking deployments So you can recover from failure very quickly Another thing to note is that there are two different types of snapshot in vCloud Director There is a vApp snapshot which will take a snapshot of all the running VMs inside the inside the vApp including metadata so things like ownership permissions or metadata associated with a vApp startup times those kind of things So for this demonstration, I'm actually going to look at not entire vApp snapshots, but I'm actually going to just do a single vApp Sorry a single snapshot of a running virtual machine so if we log on to the virtual machine and and create a file So if we just first of all list the root directory and And then we create a file And then we list that again You can see that we've now created a file called snapshot and I'm now going to go into vCloud Director Right-click on the virtual machine and create snapshot Similar options that we you'll be used to with vSphere and the first is to snapshot the memory So that would allow the virtual machine to remain online when the snapshot has finished restoring And the second option is to create the file system. So to make sure that anything That needs to be written to the file system to make it consistent Is is written so that we don't cause a kernel panic for example So I'm going to click okay. Now it does take a few minutes for the for the snapshot to complete taking so I Will pause the video and and come back when it's finished completing Once the snapshots completed if we head back over to the virtual machine console And we do something very fairly radical Which is to remove the root partition and If we let that come on run for a couple of minutes effectively what it's going to do is wipe the core operating system from the virtual machine If I now reset this virtual machine this will just take a couple of minutes to to complete What you'll see happen is the operating system try to read the files from the root disk and It won't be able to do that and it will kernel panic. So this virtual machine is effectively trash now Now in order to roll back because we took the snapshot earlier We can right-click on the virtual machine and revert to snapshot Confirm that you want to do that Now what this is going to do is effectively reload the the point-in-time snapshot that we took earlier It only takes about 20 seconds to do this and I'm actually going to leave the video running Whilst this process happens just so you can see how quick it is to restore or recover service After making a fairly serious Change and there we go We can see that the virtual machine has come up in the exact state It was when we took the snapshot so all the information that was stored in RAM on the virtual machine has also been captured You can see the last commands that we ran at the shell And you can also see just to confirm it that the file that we created before doing the snapshot is is still there So that's the cloud director 5.1 snapshots. Thank you very much