|
Objective 1.4 - Implement and Manage Storage VMotion |
|
|
|
Written by Matthijs van den Berg
|
|
Tuesday, 06 January 2009 13:30 |
KNOWLEDGE
- Describe Storage VMotion operation
Storage VMotion moves a running Virtual Machine from one storage pool to another storage pool on one ESX server. During this process the VM keeps on running while all VM (disk) files are being transported to anther LUN. Both the source and destination LUN must be visible to the ESX servers in the farm.
- Explain implementation process for Storage VMotion
Storage VMotion must be done from the commandline of a server. On the particularly server the VMware Remote CLI must be installed. A storage VMotion is always performed from the commandline. Currently (3.5U2) nu official GUI is available.
- Identify Storage VMotion use cases
Storage VMotion can be use in numerous scenarios like:
- The VM must be placed on a LUN to increase free space on this LUN
- The disks of a VM must be places from one LUN to different LUNs to optimize performance
- Understand performance implications for Storage VMotion
Storage VMotion copies all VM files from a LUN to another LUN via the storage HBA/ NIC controller. This puts a heavy load on the connection possibly influencing performance for this and other VMs. Also during the storage VMotion a snapshot of the VM is made. This process also influence VM and ESX host performance.
SKILLS AND ABILITIES
- Implement Storage VMotion based on various use cases
- Migration of all virtual disks to target storage location
svmotion --url=https://myvc.mycorp.com/sdk --username=me --password=secret --datacenter=DC1 --vm='[old_datastore] myvm/myvm.vmx:new_datastore'
- Migration of virtual disks to independent target storage locations
svmotion --datacenter='My DC' --vm='[old_datastore] myvm/myvm.vmx: new_datastore' --disks='[old_datastore] myvm/myvm_1.vmdk: old_datastore, [old_datastore] myvm/myvm_2.vmdk: old_datastore'
TOOLS
|