Task 1: Migrate VM files from Local Storage to Shared Storage.
Here I went through and made sure I have completed this. This was previously done in the last lab.
Task 2: Create a Virtual Switch and a VMkernal Port Group for vSphere vMotion Migration
For this task we need to create a vitchural switch, much like the ones we have created previously is past labs. The only difference is clicking the vSphere vMotion network.
Task 3: Perform a vSphere vMotion Migration of a Virtual Machine on a Shared Datastore.
Once we have powered off all of the VMs we have, the first step will is to change some of the settings. For this, we will make sure the network adapters are set to production. Which in my case its “production2” and then the cd/DVD drive is unselected and on the “client device.” We will do this to all three VM’s.
At this point, we need to do the same on the 2nd ESXi that we will be using. In my case, it’s my 3rd ESXi host.
Once we have done that we need to go into the cabinet VM Ammbers01-3 and type in ipconfig to make sure this is on the correct network.
Once this is done, i will continually ping the DC01
Back in the console, we will the Migrate this VM into the Third ESXi. As seen below.
Then there is a slight wait to migrate it over, but once it is done, it should look like below.
Now, this has been done we can go back to the VM and see if it dropped any packages in the migration.
Like I said it took a while, so we have a large number of pings sitting there, but it migrated over without dropping any packets which are good.
The next step is to migrate to another VM and transfer over both the “compute resources” and storage. As seen below.
Task 5: Prepare for the Next Lab
So for this, we will migrate all the VMS back, this will take some time. In this time I managed to go to go on to the next lab and leave it migrating. This worked, but I forgot to get any screenshots of this, as I understand home about nine at night.