During this copy, VMware uses changed block tracking to keep account of changes being made to the source datastore. Second, an initial copy of the VMs disk files are copied to the target storage device. In version 3.5 it was given the name Storage vMotion and in version 4 it was given a graphical user interface (GUI).Ĭopying home directory (config, log, swap, snapshots) data of a VM to a destination storage device is the first step in a vMotion. Storage vMotion has been available since version 3 of VMware, but it was a command line utility mostly used for upgrading to VMFS.
While this improved that VM’s performance it did so at the cost of wasted capacity per spindle. The most typical scenario was reacting to VM performance issues on over-utilized VMFS datastores. Storage vMotion was an excellent solution for managing an environment under the rigid constraints of the traditional storage model of tiered back-end storage pools. While a valuable addition to the VMware toolkit, Storage vMotion creates challenges for the storage infrastructure. The motivation to move a VM’s datastore can be to move it to a storage system that can deliver better performance, better reliability or as the VM becomes static, migrate it to a secondary storage system. It is similar in concept to how regular vMotion migrates a VM to another host in a VMware cluster.
VMware’s Storage vMotion is an invaluable tool to enable the migration of a virtual machine’s (VMs) datastore to another storage system.
0 kommentar(er)
