I have a use case where I'm overwrite a .vmdk. I am starting a storage vmotion from an external source into the vcenter. When I attempt the storage vMotion I currently get this:-
Cannot complete the operation because the file or folder ds:///vmfs/volumes/XXXX.vmdk already exists
Is there a way in storage vmotion to specify to overwrite the destination disk rather than fail. If not I will have to explore ways to rename disks.