Thank you, that worked great. I did discover one modification that saves on the housekeeping. Create the VM without a hard drive. Then copy the VMDK file directly into that VM directory and then add it to the VM.
I have my VMs set up on thin provision, I see yours was thick. When you attached the old hard drive to the new vm you created, it ghosted out the ability to change the size. Are you able to do this with thin provision? If not is it able to be converted back once you bring it up?
Great! what if you want to "copy this VM" to a different network? Do I just take the files and put them on the new host? also, does this move take the network setting or only the HDD?
I just copy the entire folder, after shutting down the instance to another folder(s). If the working VM fails, just rename it for further work and copy the original folder back. What I'd like is a way to script the entire process... shutdown the working OS at midnight, copy the entire folder to another location after deleting or renaming the prior back, complete the backup and then restart the original VM.
Thanks for your comment and question...technically not the same cloning method as what is found on vCenter, within ESXi it is simply a workaround method.
Thanks Emilio for your video. I tried your way. However, it did not work for me. The copied disk file in the new folder did not appear in the folder when I browser it to add existing disk, where I got stuck. on ESXi 6.5.
Thanks for the video and good explanation. However I am wondering why you only copied across the .vmdk files and not the entire vm folder including the entire vm. Using the vSphere Standalone Converter you can do the same and resize WIN hard disk at the same time and switch thick to thin provisioning as you like. What you explain works but as always there are other possible paths one can take. Keep the good work up.
Copy Virtual Disk Description Copy the disk, either a datastore path or a URL referring to the virtual disk Datastore: [datastore1] abc/abc.vmdk State Failed - Unable to access file [datastore1]abc/abc.vmdk since it is locked Errors Please help me!
I have a thin-provisioned vmdk. Won't it become thick during a copy? That's especially important when cloning _potentially_ large machines that haven't grown yet, but have provisioning that would exceed the available space if we go thick. Would using command line allow us to go low-level on this operation, avoiding the management front end's smarting off?
Why not using copy of the whole vm folder... than selecting "register existing VM" and answer "I copied it" whan vsphere asks you where you've got it from? This way whole virtual HW is copied and it actually is a clone. You cloned only the disk.
hey, thanks for your comment. The vmdk files are browsable across current versions of ESXi, including 6.5. What do you see when you browse the datastore?
I'm unable to use this. My ESXI interface does not seem to be allowing copy or download options. When I hit copy it creates a 559Byte file of what should be 29GB. Same thing when I download. VM was powered off while attempting this.
Thanks, really appreciate your comment! Feel free to check out my channel for some other great tech videos that you may find helpful. ua-cam.com/users/digitalbytecomputing
This is not a proper Vmware cloning, more a copy of an existing VM. Title is misleading as the copied VM will share the same hostname and IP address as the source.
This is such a bullshit "issue" to bring up. It's a non-issue at all. You can set all of that on your first boot. It really shouldn't be the hypervisor's burden to edit the contents of the vmdk anyway, even if it is not content-agnostic. Theoretically, the internal structure of partitions on the virtual disk could be damaged by a virus and require careful restoration. No automatic operations should be applied outside the admin control in such a scenario. The virtualization dev team has enough on their hands. Consider this an image copy between identical machines: all you need to do, you can do in minutes, otherwise you have no business being a systems administrator.
Thank you, that worked great. I did discover one modification that saves on the housekeeping. Create the VM without a hard drive. Then copy the VMDK file directly into that VM directory and then add it to the VM.
Thanks for this information. What about converting from Thick to Thin during the process?
Exactly what I needed. Just enough details and perfect pace!
Thanks, if the original vm was an activated win server, the copy asks for activation ?
I have my VMs set up on thin provision, I see yours was thick. When you attached the old hard drive to the new vm you created, it ghosted out the ability to change the size. Are you able to do this with thin provision? If not is it able to be converted back once you bring it up?
Emilio Aguero is the best trainer have seen. He pretty don't keep you in the dark. Thanks for making me
Great! what if you want to "copy this VM" to a different network? Do I just take the files and put them on the new host? also, does this move take the network setting or only the HDD?
have any particular video or idea in how to clone or move a vmware machine from a exsi server to another VM exsi server...?
I just copy the entire folder, after shutting down the instance to another folder(s). If the working VM fails, just rename it for further work and copy the original folder back. What I'd like is a way to script the entire process... shutdown the working OS at midnight, copy the entire folder to another location after deleting or renaming the prior back, complete the backup and then restart the original VM.
So how about copy the disk to NFS or iSCSI, would it work like that as well?
Thank you Emilio, It was very helpful.
I have a question, is it true if we want to backup a VM, we just download vmdk and vmx files only?
What about snapshots that you could have made?
are you saying a paid esxi version will have cloning?
Thanks for your comment and question...technically not the same cloning method as what is found on vCenter, within ESXi it is simply a workaround method.
Is there a way to do it, without shutting down the virtual machine?
Hi @Emilio Aguero,
Could you please create a video about how to migrate VM machine from Exsi 6.7 to another 6.7 without using vshere or vmotion.
Thanks for the suggestion, will look into that
How to clone if I already started creating snapshots and wanted to pick the latest snapshot?
IF the vmdk has 10 snapshots, how can I do it ?
Thanks Emilio for your video. I tried your way. However, it did not work for me. The copied disk file in the new folder did not appear in the folder when I browser it to add existing disk, where I got stuck. on ESXi 6.5.
You need to copy the vmk descriptor file with the vmdk. The file is like 7kb and it has the vmdk extension.
Thanks for the video and good explanation. However I am wondering why you only copied across the .vmdk files and not the entire vm folder including the entire vm. Using the vSphere Standalone Converter you can do the same and resize WIN hard disk at the same time and switch thick to thin provisioning as you like. What you explain works but as always there are other possible paths one can take. Keep the good work up.
Simple and effective explanation, great job @Emilio Aguero.
Glad you liked it!
I have done it exactly like in the video but the new VM isn't booting.
Good you said "I absolutely love it!"
thanks for you comment :)
Thanks for very good short cut.
You're welcome
Copy Virtual Disk
Description
Copy the disk, either a datastore path or a URL referring to the virtual disk
Datastore:
[datastore1] abc/abc.vmdk
State
Failed - Unable to access file [datastore1]abc/abc.vmdk since it is locked
Errors
Please help me!
Facing the same issue, did you get it resolved?
Thank you very much. It was very helpful. Simple and straight forward.
Thanks for this information. been looking to do this for days
Thanks for your comment, glad you found it helpful!
I have a thin-provisioned vmdk. Won't it become thick during a copy? That's especially important when cloning _potentially_ large machines that haven't grown yet, but have provisioning that would exceed the available space if we go thick. Would using command line allow us to go low-level on this operation, avoiding the management front end's smarting off?
Why not using copy of the whole vm folder... than selecting "register existing VM" and answer "I copied it" whan vsphere asks you where you've got it from? This way whole virtual HW is copied and it actually is a clone. You cloned only the disk.
very helpful video, thank you so much for sharing your knowledge!!!
Glad it was helpful!
Nope, total failure. The new vmdk file doesn't appear when browsing for it to add it as an existing drive in ESXi 6.5.
hey, thanks for your comment. The vmdk files are browsable across current versions of ESXi, including 6.5. What do you see when you browse the datastore?
Easy peasy, thank you sir!
Thanks for the comment, glad you found it helpful!
Thanks
Nicely done, thank you.
Great tip! Thank you!
Thanks for your comment, glad you found it helpful!
I'm unable to use this. My ESXI interface does not seem to be allowing copy or download options. When I hit copy it creates a 559Byte file of what should be 29GB. Same thing when I download. VM was powered off while attempting this.
i have the same bullshit
i'm too. Solution is enable ssh in ESXi and copy vmdk using WinSCP
i found if you copy the whole folder it's in, instead of just the file, it will work right.
Nice Tutorial!
Thanks!
Perfect! Worked great!
Thanks for your comment, glad you found it helpful!
loads of thanks, it was useful.
You're welcome!
maybe create the VM first before transfering the disk;
Or use VMware converter. Easiest way and free!
Thank you Sir !
Glad you found it helpful! Thanks for watching.
Very nice, thanks!
Thank you too!
Bloody goddamn legend mate
thansk heaps
Thanks.
Thanks for your comment, appreciate it!
nice, thanks
Thanks
Thank you ;)
You're welcome!
Well done
Thanks, really appreciate your comment!
Feel free to check out my channel for some other great tech videos that you may find helpful. ua-cam.com/users/digitalbytecomputing
Thank you........
Thanks for your comment, glad you found it helpful!
This is not a proper Vmware cloning, more a copy of an existing VM. Title is misleading as the copied VM will share the same hostname and IP address as the source.
Hi Thierry, thanks for your comment. This is what a VM clone is. What are you trying to achieve? Happy to help.
@@TechWithEmilio I know right? There really is no difference. Copy and clone essentially have the same meaning
Hostname and IP is dependent on the VM, so yes of course. Sysprep the VM if you're using windows if you want to do this
This is such a bullshit "issue" to bring up. It's a non-issue at all. You can set all of that on your first boot. It really shouldn't be the hypervisor's burden to edit the contents of the vmdk anyway, even if it is not content-agnostic. Theoretically, the internal structure of partitions on the virtual disk could be damaged by a virus and require careful restoration. No automatic operations should be applied outside the admin control in such a scenario. The virtualization dev team has enough on their hands. Consider this an image copy between identical machines: all you need to do, you can do in minutes, otherwise you have no business being a systems administrator.
Nice
Thanks for your comment, appreciate it!