So in the end the newly added virtual disk will be in the same folder as its new VM. I will then move the whole VM and disks back. Then I will use Storage vMotion to move new VM and disks to a new location, this will bring the VM, existing disks and the new disk (from old VM's datastore) over to new area and give them all the same name as the VM. Then in the new VM, I go to add an existing disk and navigate to the original VM's datastore and add the vmdk - once it is added, I go into the Windows Disk Manager and scan disks for it to appear. Note the path of the vmdk first -then the vmdk will no longer be attached to the VM but will still reside in the VM's folder on its datastore. ![]() If the OS is windows 2008, I remove the Drive in Windows Disk Manager first, then remove in vSphere client. ![]() You can do this as long as there are no snapshots on the VMs. I've often removed virtual disks from one VM and then added to another without shutting either VMs down. Of course I always ensure I have a full backup of the data in case of any corruption. ![]() I do this all the time and then migrate the VM and disks back to original spot. In vSphere 5 you can again migrate the VM and all virtual disk to a different datastore folder and it will rename the virtual disks to be same name as VM and bring the VM and disk together.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |