{"id":9152,"date":"2014-06-02T07:01:17","date_gmt":"2014-06-02T06:01:17","guid":{"rendered":"http:\/\/nolabnoparty.com\/?p=9152"},"modified":"2023-07-16T11:22:04","modified_gmt":"2023-07-16T09:22:04","slug":"move-vmdk-files-different-datastores","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/move-vmdk-files-different-datastores\/","title":{"rendered":"Move VMDK files to different datastores"},"content":{"rendered":"

\"movevmdk01\"<\/p>\n

With VMware vSphere 5.5 it\u2019s possible to move VMDK files to different datastores leaving the VM powered on<\/strong> with no service interruption using the Storage vMotion feature.<\/p>\n

A scenario where disks location has to be reconfigured occurs when a SQL Server is configured with Data, Logs and TempDB stored on same LUN<\/strong> with Lazy Zeroed VMDK format<\/strong>. To improve its performance, moving the VMDk files in dedicated LUNs it's a possible configuration to consider.<\/p>\n

Since SQL Server on VMware best practices suggest to create dedicated LUNs<\/strong> for Data, Transaction Log and TempDB creating VMDK files with Thick Provision Eager Zeroed format<\/strong>, the process needs to move some virtual disks to different datastores.<\/p>\n

Before moving the disks, look at the current SQL Server<\/strong> configuration through Server Manager > Disks<\/strong> (Windows 2012 in this example) because the disk number is not the same as assigned by VMware. In the example disks to move are identified by the numbers 1, 4, 5 > Log, TempDB and Data.<\/p>\n

\"movevmdk02\"<\/p>\n

Looking at the VM Hardware<\/strong> configuration in vSphere Web Client, disks to move are currently located in the datastore named ts421_lun01_raid5<\/em>.<\/p>\n

\"movevmdk03\"<\/p>\n

 <\/p>\n

Procedure<\/h2>\n

To proceed with move, from vSphere Web Client<\/strong> right click the virtual machine to migrate VMDK files then select Migrate<\/strong> option.<\/p>\n

\"movevmdk04\"<\/p>\n

To hot move VMDKs to different datastores without service interruption, VMware vSphere 5.5 has a feature called Storage vMotion<\/strong>. Select Change datastore<\/strong> option then click Next<\/strong>.<\/p>\n

\"movevmdk05\"<\/p>\n

Since we need to move only some specific disks, click Advanced<\/strong> button.<\/p>\n

\"movevmdk06\"<\/p>\n

For each disk to move, click in Storage<\/strong> field the datastore parameter to change then select Browse<\/strong>.<\/p>\n

\"movevmdk07\"<\/p>\n

Select the correct destination datastore then click OK<\/strong>.<\/p>\n

\"movevmdk08\"<\/p>\n

You can change the Disk format<\/strong> during move as well by clicking the current format (Same format as source) and selecting the new format (i.e. Thick Provision Eager Zeroed).<\/p>\n

\"movevmdk09\"<\/p>\n

When Storage and Disk format<\/strong> parameters have been set, click Next<\/strong> to continue.<\/p>\n

\"movevmdk10\"<\/p>\n

Review selections then click Finish<\/strong> to start migration.<\/p>\n

\"movevmdk11\"<\/p>\n

The Recent Tasks<\/strong> panel shows the migration ongoing status.<\/p>\n

\"movevmdk12\"<\/p>\n

When process completes<\/strong> successfully, the green check is shown.<\/p>\n

\"movevmdk13\"<\/p>\n

Checking the VMDKs location<\/strong>, the files are now stored to datastores previously set.<\/p>\n

\"movevmdk14\"<\/p>\n

Looking at the SQL Server<\/strong> Disks configuration, nothing has changed and no service interruption has been experienced.<\/p>\n

\"movevmdk15\"<\/p>\n

Storage vMotion is a great feature useful to optimize systems maintenance allowing the migration of VMDK files to different datastores and with different disk formats<\/strong> in one shot. Not bad, isn't it?<\/p>\n

\"firma\"<\/p>\n","protected":false},"excerpt":{"rendered":"

With VMware vSphere 5.5 it\u2019s possible to move VMDK files to different datastores leaving the VM powered on with no service interruption using the Storage vMotion feature. A scenario where disks location has to be reconfigured occurs when a SQL Server is configured with Data, Logs and TempDB stored on same LUN with Lazy Zeroed VMDK format. To improve its performance, moving the VMDk files in dedicated LUNs it's a possible configuration to consider.<\/p>\n","protected":false},"author":3,"featured_media":9137,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,2701],"tags":[885,954,718,952,953],"class_list":["post-9152","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-vsphere-en","tag-datastore","tag-move-en","tag-sql-en","tag-storage-vmotion-en","tag-vmdk-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/9152","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=9152"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/9152\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/9137"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=9152"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=9152"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=9152"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}