It is important to know the difference between a "copy" and "move" of data. A copy will always copy every last byte and duplicate it...meaning the more data there is, the longer it takes to duplicate. A move will not touch the actual bytes of data, just the reference to it...but only if the source and target are on the same partition. If data has to cross partition, the move command will then act exactly like the copy command. A move can complete its job in under a second whereas a copy can take hours or days to complete depending on the size of the data to duplicate.
For my situation, the storage was on the same partition in storage so a "copy" from one location to another was not needed...just a very quick move would be sufficient but there is nothing in the GUI that allows "moving" a disk from one machine to another. A vmotion migration would make a copy and then remove the original which would take a LONG time to complete and prone to various issues.
Using PuTTY to SSH into the ESXi host, you can issue commands to move the files VERY quickly if on the same storage system by using the unsupported and not recommended "mv" command. Once the disk(s) are offline'd in the OS and detached in VMware, you can then move the .vmdk files using "mv" and then use "vmfstools" command to rename the files once they reached their final destination.
EDIT: Found this search command for finding all snapshot-related files in your datastore:
Code: Select all
find /vmfs/volumes/ -name *-delta*;find /vmfs/volumes/ -name *-0000*