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.

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?
LVL 21
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
1 yes, this command works at the host and datastore level, so it moves data from one datastore to another.

2. if you do not have enough space for the copy or clone, you do not have enough space, copy will fail.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
compdigit44Author Commented:
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
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
is the host connected to both datastores ?
Protecting & Securing Your Critical Data

Considering 93 percent of companies file for bankruptcy within 12 months of a disaster that blocked access to their data for 10 days or more, planning for the worst is just smart business. Learn how Acronis Backup integrates security at every stage

compdigit44Author Commented:
NO it is not
compdigit44Author Commented:
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
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Backup and Restore product ?
compdigit44Author Commented:
YES vRanger moving from an old Windows 2003 server version 5.2 to WIndows 2012 R2 version 7.1.1
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Could you use this?
compdigit44Author Commented:
I am confused??? Use what oh great one????  :-)
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Use you backup product, to backup and restore to the location you require.
compdigit44Author Commented:
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
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.