1. vSphere copies over the non-volatile files that constitute a VM: the configuration file (VMX), VMkernel swap file, log files and snapshots.
2. vSphere starts a ghost or shadow VM on the destination datastore. Since this ghost VM does not yet have a virtual disk (that has not been copied over, yet), it sits idle waiting for its virtual disk.
3. Storage vMotion first creates the destination disk. Then a mirror device --- a new driver that mirrors I/Os between the source and destination --- is inserted into the data path between the VM and the underlying storage.
4. With the I/O mirroring driver in place, vSphere makes a single-pass copy of the virtual disk(s) from the source to the destination. As changes are made to the source, the I/O mirror driver ensures that those changes are also reflected at the destination.
5. When the virtual disk copy is complete, vSphere quickly suspends and resumes in order to transfer control over to the ghost VM created on the destination datastore earlier. This generally happens so quickly that there is no disruption of service, as with vMotion.
6. The files on the source datastore are deleted.
2. vSphere starts a ghost or shadow VM on the destination datastore. Since this ghost VM does not yet have a virtual disk (that has not been copied over, yet), it sits idle waiting for its virtual disk.
3. Storage vMotion first creates the destination disk. Then a mirror device --- a new driver that mirrors I/Os between the source and destination --- is inserted into the data path between the VM and the underlying storage.
4. With the I/O mirroring driver in place, vSphere makes a single-pass copy of the virtual disk(s) from the source to the destination. As changes are made to the source, the I/O mirror driver ensures that those changes are also reflected at the destination.
5. When the virtual disk copy is complete, vSphere quickly suspends and resumes in order to transfer control over to the ghost VM created on the destination datastore earlier. This generally happens so quickly that there is no disruption of service, as with vMotion.
6. The files on the source datastore are deleted.
No comments:
Post a Comment