Earlier today I was asked if it were possible to move a specific vdisk from one datastore to another. This prompted me to write the post below. However at the time, I completely missed the fact that by using the advanced options in Storage vMotion, we can chose a specific disk to migrate rather than migrating the whole virtual machine. So I’ve altered the post a little bit and instead of using the procedure below to migrate the disk to another datastore, this post will focus on how we can disconnect vdisks from one virtual machine, move to another datastore, and connect it to a completely different virtual machine.
There are times when we need to perform certain virtual machine tasks such as moving vdisk between virtual machines. This could be for many reasons, but the one thing that’s for sure, is that with virtual machines, this process is really easy, somewhat safe, and can be done by any junior admin.
Simply follow the procedure below and you should have no issues. Just make sure to have backups of your virtual machines and make sure you pay close attention when disconnecting the vdisks because you can easily delete disk if not careful.
Here’s a virtual machine that has 2 disks
- Remove from virtual machine
- Remove from virtual machine and delete files from disk (permanently deletes the disk)
Make sure to chose the first option: Remove from virtual machine
Next, we’ll need to move the disconnected disk from the source datastore to the destination. To do so, we need to browse the source datastore and located the disconnected disk (vShield Manager_1.vmdk)
We then need to click on the Move button (3) and select the proper datastore we want to move to. Just a quick tip, I’ve created the vShield Manager folder at the root of the datastore before I started the move.
- Create a new virtual disk
- Use an existing virtual disk (Reuse a previously configured virtual disk)
- Raw Device Mapping
For this particular post we’ll be focusing on option 2, Use an existing virtual disk