Move VMDK files to different datastores using vSphere web client-阿里云开发者社区

开发者社区> 云计算> 正文

Move VMDK files to different datastores using vSphere web client

简介:

With VMware vSphere 5.5 it’s 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.

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

Before moving the disks, look at the current SQL Server configuration through Server Manager > Disks (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.

movevmdk02


Looking at the VM Hardware configuration in vSphere Web Client, disks to move are currently located in the datastore named ts421_lun01_raid5.

movevmdk03


Procedure

To proceed with move, from vSphere Web Client right click the virtual machine to migrate VMDK files then select Migrate option.

movevmdk04


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

movevmdk05


Since we need to move only some specific disks, click Advanced button.

movevmdk06


For each disk to move, click in Storage field the datastore parameter to change then select Browse.

movevmdk07


Select the correct destination datastore then click OK.

movevmdk08


You can change the Disk format during move as well by clicking the current format (Same format as source) and selecting the new format (i.e. Thick Provision Eager Zeroed).

movevmdk09


When Storage and Disk format parameters have been set, click Next to continue.

movevmdk10


Review selections then click Finish to start migration.

movevmdk11


The Recent Tasks panel shows the migration ongoing status.

movevmdk12


When process completes successfully, the green check is shown.

movevmdk13


Checking the VMDKs location, the files are now stored to datastores previously set.

movevmdk14


Looking at the SQL Server Disks configuration, nothing has changed and no service interruption has been experienced.

movevmdk15

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 in one shot. Not bad, isn’t it?

本文转自学海无涯博客51CTO博客,原文链接http://blog.51cto.com/549687/1825997如需转载请自行联系原作者


520feng2007

版权声明:本文内容由阿里云实名注册用户自发贡献,版权归原作者所有,阿里云开发者社区不拥有其著作权,亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容,填写侵权投诉表单进行举报,一经查实,本社区将立刻删除涉嫌侵权内容。

分享:
云计算
使用钉钉扫一扫加入圈子
+ 订阅

时时分享云计算技术内容,助您降低 IT 成本,提升运维效率,使您更专注于核心业务创新。

其他文章