Should -ctk.vmdk (changed block tracking) files be copied with a cloned disk?

[cdecker]

I need to move a VM across a slow connection. It was thin provisioned, and changed block traking was turned on. Two virtual disks.

So I cloned the disks to 2gbsparse and tar / compressed them to a .tgz file.

I intend to use vmkfstools to bring back the thin provisioned disks from the 2gbsparse ones on the other end.

Should I bring over the *-ctk.vmdk files and install with the machine?

Or should I turn off CBT before going through this process?

[cdecker]

I am posting what I discovered regarding my question.

When I used vmkfstools to clone the moved disks from 2gbsparse to thin provisioned disks, the -ctk.vmdk files were created at that time.

So the answer to my question would appear to be: When moving disk(s) using vmkfstools to clone them at the destination side, there is no need to move the -ctk.vmdk files with them. vmkfstools will create new -ctk.vmdk files in the destination location.

The rest of the files (.vmx, etc) were also moved with these disks, and the VM was simply added to the inventory on the destination host, and it booted and is working fine.

Hope this helps anyone with the same question in the future.

[prettyby77]

Thanks!  This did help.