VMware Cloud Community
TECH198
Hot Shot
Hot Shot
Jump to solution

ESXI copy is different size

i used vmkfstools to convert VM to ESXi, and it converted ok. However, i then  made a copy, So i copied from Datastore to new folder, but the copy is a different size..

 

When I SSH into server, I do see the -flat.vmdk as well... can i just ignore this ?

 

Original is :9.98Gig

Copy is: 9.64Gig

Reply
0 Kudos
1 Solution

Accepted Solutions
IRIX201110141
Champion
Champion
Jump to solution

You should use "vmkfstools " for copying around your VMDKs and not "cp".

vmkfstools-i /path/to/source.vmdk /my/new/folder/copy/target.vmdk

One benefit would be that both files (descriptor and flat) are covered and when using "-d thin" as additional option the target would be a thin provisioning vmdk.

 

Regards,
Joerg

View solution in original post

Reply
0 Kudos
3 Replies
a_p_
Leadership
Leadership
Jump to solution

Virtual disks in ESXi always consist of two .vmdk files, a small descriptor file, and a data (flat/delta/sesparse) file. The datastore browser just displays these two files as one. Viewing the files from the command line, or by using e.g. WinSCP shows the files.

Regarding the file sizes: How did you copy the virtual disk? It's actually vmkfstools which should be used, since it is VMFS aware, and supports features like thin provisioning.  The "cp" command should be avoided, and WinSCP is also not thin provisioning aware.

What does the command ls -lisa show for the source, and target files?

André

Reply
0 Kudos
IRIX201110141
Champion
Champion
Jump to solution

You should use "vmkfstools " for copying around your VMDKs and not "cp".

vmkfstools-i /path/to/source.vmdk /my/new/folder/copy/target.vmdk

One benefit would be that both files (descriptor and flat) are covered and when using "-d thin" as additional option the target would be a thin provisioning vmdk.

 

Regards,
Joerg

Reply
0 Kudos
TECH198
Hot Shot
Hot Shot
Jump to solution

88342558 10103560 -rw------- 1 root root 64424509440 Sep 2 06:31 Windows_10_x64-disk1-flat.vmdk

88342559 4 -rw------- 1 root root 516 Sep 2 06:31 Windows_10_x64-disk1.vmdk

I copied via data browser. But when converting vm (originally came from VMWare Fusion) to esxi i used vmkfstools with -i option.

vmkfstools -i Windows-10-64-Professional-disk1.vmdk.fusion Windows-10-64-Professional-disk1.vmdk

 

However, being in the same root, i moved to new folder via datastore /Windows10/. .... .vmdk, then created a backup  outside of folder . as origional.

Was the mistake i should have created copy ssh ?

Reply
0 Kudos