Migrating data stores using storage vmotion

With storage vMotion, you can migrate virtual machines and their disk files from one data store to another while the virtual machine is running. When migrating through storage vmotion, you can place the virtual machine and all of its disks in the same location, or choose a separate location for the virtual machine configuration files and for each virtual disk. It is important to note, however, that ESXi hosts are not changed when migrating virtual machines through storage vmotion, and that the host that the virtual machine is running must have a license that includes storage vmotion (the virtual machine must be in shared storage accessible by the host). Storage vmotion Migrating virtual machines are as follows:

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/53/D3/wKiom1RxiaKBqiG_AADOwBVUnjA948.jpg "title=" Qq20141123132955.png "alt=" Wkiom1rxiakbqig_aadowbvunja948.jpg "/>

When migrating a virtual machine through storage vmotion, there is no memory cloning, only simple data cloning, so at the beginning of the storage vmotion, there is no host to participate, but simple files are cloned between different storage devices. VMware Storage vmotion allows the disk of a virtual machine to be relocated to a different data storage location in a completely transparent manner while keeping the virtual machine in a running state without downtime. Before moving the virtual machine's disk files, Storage vmotion moves the virtual machine's home directory to the new location. The home directory contains metadata information about the virtual machine, such as configuration files, replacement files, and log files. It will then "self-vmotion" to the new VM Master location. After the home directory migration is complete, the disk is moved. First, Storage vmotion create a "sub-disk" For each virtual machine disk that you want to migrate. After the migration operation is started, all disk writes go to this "sub-disk." Second, copy the "parent" or the original virtual disk from the old storage device to the new storage device. Then, the child disk that is capturing the write operation is re-established with the newly copied parent disk. Finally, the sub-disks are consolidated into the new parent disk, and the ESX hosts now go back to the parent disk location. The process of switching the primary directory box to disk migration, creating sub-disks and parent disks, rebuilding parent-child relationships, and consolidating sub-disks will be completed in less than two seconds, making the application user unaware of the speed.

When migrating with storage vmotion, you can convert your virtual machine disks from thick provisioning to thin provisioning or from thin provisioning to thick provisioning, and you can upgrade data stores without virtual machine downtime. You can also move the virtual machine away from the storage device to maintain and reconfigure the storage device. You can also use storage vmotion to manually reassign a virtual machine or virtual disk to a different storage volume to balance capacity or improve performance.

Virtual machines and their hosts must meet resource and configuration requirements to migrate virtual machine disks through storage vmotion. The basic requirements to meet include storage requirements and network requirements.

• Storage requirements: The host running the virtual machine must be able to access the source data store and the destination data store. There are three types of FC san, ISCSI san, NFS nas that support shared storage, as long as the ESX host can access both the source and destination storage. and storage vmotion supports the online migration of virtual machines from ESX local storage to shared storage, and vice versa.

• Network requirements: Because it is just migrating data between two stores on an ESX host, you need to vmkernel the network.

The steps to migrate a data store using storage vmotion are as follows.

Step 1 A virtual machine that is running on Windows 7 virtual machines, and VMware Tools is installed and activated correctly on the virtual machine, right-click the virtual machine and choose the Migrate option from the shortcut menu that pops up.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/53/D1/wKioL1Rxii_wG4JiAAB4hAwy_eg519.jpg "title=" Qq20141123133714.png "alt=" Wkiol1rxii_wg4jiaab4hawy_eg519.jpg "/>

Step 2 We prefer to determine the virtual machine to migrate, that is, Windows 7 to be migrated, before the migration, it is running on the iSCSI1 storage, we want to migrate it to iSCSI2 is the storage,

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/53/D1/wKioL1Rxij6TW2aAAAE4KJmZyE8556.jpg "title=" Qq20141123133859.png "alt=" Wkiol1rxij6tw2aaaae4kjmzye8556.jpg "/>

Step 3 The Migration Wizard pops up, selecting change data store in the type of migration to move the storage of the virtual machine to another datastore. Click the Next button,

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/53/D1/wKioL1Rxik3yGtyJAAHyZb_fNn8196.jpg "title=" Qq20141123134128.png "alt=" wkiol1rxik3ygtyjaahyzb_fnn8196.jpg "/> Step 4 Select the target datastore and verify that the compatibility is validated successfully. In select Virtual Disk format, select the migrated disk format ("Thin provisioning" is the number of uses, "thick format" immediately allocates virtual machine space on the storage) or choose the same as the original format,

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M01/53/D1/wKioL1RximDj9KP_AAMdGKtr9Js960.jpg "title=" Qq20141123134207.png "alt=" wkiol1rximdj9kp_aamdgktr9js960.jpg "/> Step 5 View current settings, click the Back button if you want to modify it, or click the Finish button Start Storage vMotion,

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M02/53/D1/wKioL1RxiobCmlFoAAGMeeQbevA879.jpg "title=" Qq20141123134237.png "alt=" wkiol1rxiobcmlfoaagmeeqbeva879.jpg "/> View storage vmotion migration Progress, which takes time to be related to the size of the virtual machine disk. During the migration process, the virtual machine app is not interrupted, and you can use the ping command to detect if the virtual machine is interrupted during the migration.

650) this.width=650; "src=" Http://s3.51cto.com/wyfs02/M00/53/D3/wKiom1Rxih2Sk27JAAegsrHLVCo241.jpg "title=" Qq20141123134412.png "alt=" Wkiom1rxih2sk27jaaegsrhlvco241.jpg "/>

This article is from the "Zhong blog" blog, make sure to keep this source http://capfzgs.blog.51cto.com/7729146/1583470

Migrating data stores using storage vmotion