Purpose: How to perform svMotion migration?
Go to VM -> right click on VM and select Migrate VM. This will prompt you a window:-
- Select Migration Type: O Change Host .
O Change Datastore.
O Change Both Host and Datastore.
(But for this change both Datastore and Host , VM must be powered off)
Here we select change Datastore option as this is svMotion migration only and not a host migration.
- Storage: Select Disk format from drop down menu :-
- Same format as source.
- Flat Disk
- Thick provision(Lazy Zero or Eager Zero)
- Thin provision
Then select the destination LUN from available list of LUNs as per the maximum space available.
You can separate Configuration file with the other disk files by clicking on Advanced button and browse the configuration datastore location. Before migration we need to check whether the Compatibility Validation: Succeeded, if the compatibility isn’t validated successfully then this will cause an error and we should not perform that vMotion to that host because it may have compatibility issues.
- vMotion Priority: O High priority.
O Standard priority.
Here we select High priority to make sure that this migration is performed with high priority.
4. Ready to complete.
- VSphere licensing Enterprise plus or enterprise.
- Now vSphere 5 moving a powered ON VM with snapshots is supported.
- Move large MVDK can take a long time depending upon your n/w connection.
- When you migrate storage you have to option to change from –
- Thin to Thick provision
- Thick to Think provision
Migrating VMs with snapshots now in new vSphere:
Now in vSphere 5 we have this feature of migrating storage vMotion with snapshots but it was not there in the earlier version of vSphere 4.x we had to remove the snapshots before migrating VMs into another datastore.