Task 1: Unregister a VM from VSCA Inventory
Here we still have a VM that is currently migrating, as I said it took over 6 hours. So I went ahead and started another lab. But here we will then remove Ambers01-4 from the inventory.
And as you can see from below it has been removed from the inventory.
But when we went and searched for the files, these are still here. These are still called “hot-clone” for some reason. But because these files get deleted in this lab I’m not going to change the name.
Task 2: Register a VM in the vCentre Server Inventory
So from here, we will “register the VM”, here we made a VM from the “hot clones” files. We also changed the name to Ambers05
Task 3: Unregister and Delete a VM from the Disk
For this, we will look at the summery of the VM itself before we delete it off.
The next this to do is to “Delete from disk” as seen below.
And then we will go back and check to see if the files have in fact been deleted. Which there is no record of “hot-clone” or “ambers05”.
Task 4: Take a snapshot of a VM
For this, we will “launch the remote consol” for the VM
While we do not have the file iometer.txt, I have created a text file
Once we have created this, we need to delete this and put it in the recycle bin. Then we will clean out the recycle bin.
Back in the Vsphere console, we will then create a Snapshot of the VM without the iometer file that we have just deleted. As seen below.
Now this is completed we need to create the cpubusy file
Now, this is created we then need to simulate the deletion of this file and then clean out the recycle bin like the previous pic.
We will then navigate back to the Vsphere console and make another snapshot of the current state of the VM that is without the “iometer or the cpubusy” file.
After this, we will then create another snapshot and then navigate to snapshots ass seen below.
Task 5: Revert to a snapshot.
For this, we will click on the icon in the left-hand corner and revert to the snapshot “Without iometer or cpubusy”. as seen below.
Once this is complete we will then go into the console and look at the “c” drive to check that the created files are not there.
Now we need to revert back to the “with cpubusy” snapshot. for this we will also cheak that the created files are still not there.
Task 6: Delete an individual Snapshot.
For this we are going to be deleing the snapshot called “without iometer or cpubusy” as seen below.
Task 7: Use the “Delete all” Function in the Snapshot Manager
As seen below we are going to use the “delete all” function to delete all of the unneeded snapshots.