I'm using VMware vCenter Server Appliance 220.127.116.11000 Build number 15132721
I get the error Invalid datastore path '[datastore.251] Server2/Server2.vmdk' when cloning a VM from a VMware ESXi 6.7.0 8169922 to a VMware ESXi, 6.7.0 14320388
But I get the same error in other three cases with other vCenter and Esxi environments (also previous builds).
The only common thing is that the cloned vm has more than one hard disk.
You say you get the same error in three other cases. Do you always get the error when you try to create a clone? Could it be a permissions issue?
Yes I always get the error when I try to create a clone in every esxi environment.
I don't think it's a permissions issue...I have no problem with another cloning software and no problem with any vCenter operations (start, stop, snapshot, etc.).
Actions on a VM like starting or stopping are different privileges than those needed for creating a clone. For this you would also need other privileges.
You must have the following privileges to clone a virtual machine:
I added an hard disk succesfully...and the "Invalid datastore path" occurs during the cloning operation (it starts correctly).
The cloning operation goes well if I exclude from the cloning the one of the 2 hard disks that causes the error.
The datastore is in the server raid of the os.
I'm able to clone the vm to another esxi using a different clone utility...it goes well.
Why?But I cannot think about something wrong with the storage, because I have the same problem with 2 other vmware systems.
Hi, were you able to get the solution for this? I am facing the same issue while I try to clone across the hosts which are registered to different vCenter instances. However, in my case the error is pointing to the disk as mentioned in the problem description which happens to be the multi-writer flag enabled which is also skipped during the clone process.
This is still a problem in vSphere 7.0 Update 3. I almost always do cloning using other tools (Ansible usually), but was troubleshooting a different issue today and tried cross-vcenter cloning using the vCenter Ui. Source VM has snapshots, and cloning it using vCenter to a linked vCenter fails with the same "invalid datastore" error.