VMWARE Lab's

VMware Lab 15: Managing Virtual Machines

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.

Removed from inventory; 2.PNG

And as you can see from below it has been removed from the inventory.

Removed from inventory; 3.PNG

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.

VM 4 showes; 4.PNG

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

This slideshow requires JavaScript.

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.

VMFS datastore; 7.PNG

 

The next this to do is to “Delete from disk” as seen below.

This slideshow requires JavaScript.

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”.

files are nolonger there; 10.PNG

Task 4: Take a snapshot of a VM

For this, we will “launch the remote consol” for the VM

Open the VM; 10.PNG

While we do not have the file iometer.txt, I have created a text file

Deleteing the iometer ; 11.PNG

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.

Deleteing the iometer ; 11;a.PNG

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.

This slideshow requires JavaScript.

Now this is completed we need to create the cpubusy file

cpubusy; 13.PNG

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.

cpubusy; 13;a.PNG

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.

This slideshow requires JavaScript.

After this, we will then create another snapshot and then navigate to snapshots ass seen below.

Looking at all the snapshots 15.PNG

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.

This slideshow requires JavaScript.

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.

revereted back ; 17.PNG

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.

This slideshow requires JavaScript.

Task 6: Delete an individual Snapshot.

For this we are going to be deleing the snapshot called “without iometer or cpubusy” as seen below.

This slideshow requires JavaScript.

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.

This slideshow requires JavaScript.

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s