I made the following discovery:
I tested with on vmdk-file with following parameters:
vmdk-file (thin): size 3,36 GB of 20 GB,
Guest OS shows 2,6 GB
Copy time from Datastore1 to Datastore2 with Datastore Browser: ~ 24 secounds
I maked an 1 GB testfile in the guest-vm. After this step the vmdk-file has this parameters
vmdk-file (thin): size 5,35 GB of 20 GB,
Guest OS shows 3,6 GB
Copy time from Datastore1 to Datastore2 with Datastore Browser: ~ 35 secounds
After i deleted the testfile:
vmdk-file (thin): size 5,35 GB of 20 GB,
Guest OS shows 2,7 GB
Copy time from Datastore1 to Datastore2 with Datastore Browser: ~ 35 secounds
I converted the vmdk-file in thick:
vmdk-file (thin): size 20 GB of 20 GB,
Guest OS shows 2,7 GB
Copy time from Datastore1 to Datastore2 with Datastore Browser: ~ 1:56 minutes
Another test with an other vmdk-file:
vmdk-file (thick): size 5 GB,
Guest OS shows: 1,6 GB
Copy time from Datastore1 to Datastore2 with Datastore Browser: ~ 34 secounds
I converted the vmdk in to thin format:
vmdk-file (thick): size 2 of 5 GB,
Guest OS shows: 1,6 GB
Copy time from Datastore1 to Datastore2 with Datastore Browser: ~ 54 secounds
I converted the vmdk back to thick format:
vmdk-file (thick): size 5 GB,
Guest OS shows: 1,6 GB
Copy time from Datastore1 to Datastore2 with Datastore Browser: ~ 34 secounds
This is strange. But i think it means, that the Browser only copy the real data and 'cp/mv' the hole file.
Why a converted file (thin -> thick) increase the copy time is serious.