Link to home
Create AccountLog in
Avatar of compdigit44
compdigit44

asked on

Best Way to move a VMDK between VM's

I have a old VM which we will call OLD and an updated one called NEW. OLD has three VMDK files attached to it that I need to move into the folder of the NEW VM.

I know vmkfstool -i is the recommend way to move /clone a VM.

Questions.
1) Can you use this command to clone a VMDK is the source VM is in another cluster?
2)  What is the backup option to using vmkfstool -i to clone the VMDK is you do not have enough space to depulate teh VMDK fiel and only want to copy it?
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of compdigit44
compdigit44

ASKER

Stupid question...

I have never used the vmkfstool -i command to move / clone a vmdk from one datastore /cluster to anther. I have only done this on vmdk that share the same datastore. What changes would I need to make to the syntax
is the host connected to both datastores ?
NO it is not
Here is the problem I have two VMs which we will call OLD and NEW and NEW is going to be replace  OLD with the same name. When we deploy VMs we renamed the old one in the display to OLD-OLD then Deploy the new template as OLD so all of the files are named correctly then updated the display name to OLD-NEW. I cannot move the VM to the same datasore since the VMs folders have the same name.

The 3 VMDK files I have to move range in size from 100GB - 450GB. What is the best way to do this
YES vRanger moving from an old Windows 2003 server version 5.2 to WIndows 2012 R2 version 7.1.1
I am confused??? Use what oh great one????  :-)
Use you backup product, to backup and restore to the location you require.
But the VMDK attached to the old VM has reference images and would issue just deleting them I believe unless I am totally missing something here which is most likly
VM has reference images ?

what are these ? please expand.

So Backup the VM OLD, and Restore the VM OLD VMDKs, to the new host and cluster, and datastore NEW Folder.

This will restore all 3 VMDKs files to the new folder, with the existing VM configuration, add these VMDKs to the VM New, and then complete a storage vMotion, and this will rename all the files (VMDKs) etc.

Can this be done?

Otherwise you will have to

1. CLONE OLD to a new VM (temp).

2. Then use vMotion to move between hosts.