{"id":19103,"date":"2016-11-21T10:00:04","date_gmt":"2016-11-21T09:00:04","guid":{"rendered":"http:\/\/nolabnoparty.com\/en\/?p=19103"},"modified":"2016-11-21T09:18:41","modified_gmt":"2016-11-21T08:18:41","slug":"moving-vmdk-different-vm-retaining-ntfs-permissions","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/moving-vmdk-different-vm-retaining-ntfs-permissions\/","title":{"rendered":"Moving a vmdk to a different VM retaining NTFS permissions"},"content":{"rendered":"

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

In VMware vSphere you can migrate all vmdk virtual disks<\/strong> to a different datastore retaining Windows NTFS<\/strong> permissions in a very easy way.<\/p>\n

If the current server belong to an AD domain, the migration of the stored data to a new server<\/strong> raises the problem of the applied NTFS permissions. How to retain all the settings?\u00a0<\/p>\n

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

 <\/p>\n

Remove the disk to migrate<\/h2>\n

Before proceeding, ensure to have a full backup of the data<\/strong> in case of any corruption.<\/p>\n

From the Windows Server to process open the Disk Manager<\/strong>, right click the disk to migrate and select Offline<\/strong> option.<\/p>\n

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

The disk is then put in offline mode<\/strong> and no longer accessible from the Windows Server.<\/p>\n

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

Open the vSphere Web Client, select the VM and go to Manage > Settings<\/strong>. In this example the Hard disk 2<\/strong> has to be migrated. Click Edit<\/strong> button.<\/p>\n

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

Expand the\u00a0Hard disk 2<\/strong>\u00a0and click the X<\/strong>\u00a0in the right side to remove the disk<\/strong> from the selected VM. Write down the Disk File<\/strong> name and the location<\/strong>.<\/p>\n

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

Leave Device will be removed<\/strong> and Delete files from datastore<\/strong> options unchecked to keep all the stored data. Click the arrow in the right side to cancel the removal. Click OK<\/strong> to confirm.<\/p>\n

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

The Hard disk 2<\/strong> has been removed from the VM hardware.<\/p>\n

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

The vmdk disk to migrate is no\u00a0longer attached to the VM but still resides<\/strong> in the VM's folder on its datastore.<\/p>\n

 <\/p>\n

Add the migrated disk to the new server<\/h2>\n

From the vSphere Web Client, select the new Windows Server and access the VM Hardware<\/strong> section.<\/p>\n

Now we need to add the previously detached hard disk to the new server. From the\u00a0New device<\/strong> drop down menu, select Existing Hard Disk<\/strong> item and click Add<\/strong>.<\/p>\n

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

From the Select File<\/strong> window, locate and select the disk name to migrate from the old server location folder and click OK<\/strong>.<\/p>\n

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

The New Hard disk<\/strong>\u00a0is added in the new server. Click OK<\/strong> to confirm.<\/p>\n

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

Expand the hard disks installed in the new VM.\u00a0Note\u00a0the new added disk kept\u00a0the old VM name<\/strong> and it is still stored in the old location<\/strong>.<\/p>\n

[ts421_lun01<\/strong>_raid5]w12r2-services\/w12r2_services_1.vmdk
\n[ts421_lun02<\/strong>_raid5]w2k8r2-vproxy01\/w2k8r2-vproxy01_1.vmdk<\/span><\/p><\/blockquote>\n

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

Access the Disk Management<\/strong> of the new Windows Server and run the scan disks task<\/strong>\u00a0to detect the new attached disk. Right click the detected disk and select Online<\/strong> option.<\/p>\n

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

The new disk is online and accessible<\/strong> from the new server.<\/p>\n

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

Checking the NTFS permissions from the new Windows Server, all the NTFS permissions have been retained<\/strong>. Only the shares need to be recreated<\/strong> since the server name has changed.<\/p>\n

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

All stored data are available to users again in a transparent way. The administrators only need to configure the new disk map in AD<\/strong> to point to the shares of the new server.<\/p>\n

 <\/p>\n

Rename the vmdk<\/h2>\n

From the vSphere administration point of view, leaving the configuration like it is could be tricky to manage<\/strong>. You have the new\u00a0server with a disk located in a different datastore with the vmdk that still holds\u00a0the old server name.<\/p>\n

\"movevmdk16\"<\/p>\n

The solution to this matter is called\u00a0Storage vMotion<\/strong>.\u00a0Storage vMotion is a feature of vSphere that allows to move VM and disks<\/strong> to a new location giving to existing disks and the new disk, from the old VM's datastore, the same name<\/strong> as the current VM.<\/p>\n

From vSphere Web Client, right click the VM and select Migrate<\/strong>.<\/p>\n

\"movevmdk17\"<\/p>\n

Select Change storage only<\/strong> option and click Next<\/strong>.<\/p>\n

\"movevmdk18\"<\/p>\n

Select the destination storage<\/strong> and click Next<\/strong>.<\/p>\n

\"movevmdk19\"<\/p>\n

Click Finish<\/strong> to proceed with storage migration. Keep in mind that Storage vMotion can move powered on VMs only if you have vSphere Enterprise Plus<\/strong> edition.<\/p>\n

\"movevmdk20\"<\/p>\n

The VM is being relocated.<\/p>\n

\"movevmdk21\"<\/p>\n

When the process has been completed, also the disk from the old location has been moved to\u00a0the same location<\/strong> as the VM renaming the vmdk<\/strong> with\u00a0the new VM's name.<\/p>\n

\"movevmdk22\"<\/p>\n

If for storage performance<\/strong> reasons you need to migrate the VM and disks back to previous datastore, use Storage vMotion tool once again changing the destination storage.<\/p>\n

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

In VMware vSphere you can migrate all vmdk virtual disks to a different datastore retaining Windows NTFS permissions in a very easy way. If the current server belong to an AD domain, the migration of the stored data to a new server raises the problem of the applied NTFS permissions. How to retain all the settings?\u00a0<\/p>\n","protected":false},"author":3,"featured_media":19104,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"facebook_2879994398731222_17841400390232720":"","mastodon_115463926174894442_115463926174894442":"","linkedin_93tdZWzMZc_93tdZWzMZc":"","bluesky_did:plc:tkabz5kl2rukzdwtuongv3kz_did:plc:tkabz5kl2rukzdwtuongv3kz":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[903,913,919],"tags":[1556,65,1739,953],"class_list":["post-19103","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-vmware-en","category-active-directory-en","category-windows-server-en","tag-migration","tag-ntfs","tag-permissions","tag-vmdk-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/19103","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=19103"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/19103\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/19104"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=19103"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=19103"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=19103"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}