Error when trying to move the cloudvolumes folder to a different datastore

[jsusls]

Ok so I'm trying to move my App Volumes 2.10 cloudvolumes folder from datastoreA on vcenterA to datastoreB on vcenterB since we are trying to separate our VDI from our Core infrastructure.

We are able to access both vcenters from the web client.

I tried to just copy the cloudvolumes folder from datastoreA to datastoreB and received the following error.

Copy file The object  has already been deleted or has not been completely created

I've seen this error in Veeam before when moving VMs from one datastore to another. The fix is to remove and readd the VM in inventory.

Has anyone else tried to move the cloudvolumes folder?

Any help would be appreciated.

Thanks

[Ray_handels · Accepted solution]

I would never move the folder because there are files that will always be accessed or are not in read/write mode.

I would suggest copying the files from 1 folder to another or maybe add an extra datastore to the Appvolumes manager and let the files (appstacks at least) copy automatically.

[cH1LL1]

But remember if you have thin provisioned the apps volume they may bloat to full size when moving the content. and you don't want that.

So I use vmkfstools for this to ensure app volume remains in thin provisioned from source to destination:

This is the command. (And i think we ran in to an error when running this initially > to get around the error simply copy the volume(S) to a NFS share then copy to destination. )

Example :

/vmfs/volumes/path/cloudvolumes/apps # vmkfstools -i SimplyFile4.vmdk /vmfs/volumes/NFS/SimplyFile4.vmdk -d thin

Destination disk format: VMFS thin-provisioned

Cloning disk 'SimplyFile4.vmdk'...

Clone: 100% done.

Now Copy from NFS volume to VMFS volume and remount.

vmfs/volumes/path/cloudvolumes/apps # vmkfstools -i /vmfs/volumes/NFS\ NFS/SimplyFile4.vmdk  SimplyFile.vmdk -d thin

Destination disk format: VMFS thin-provisioned

Cloning disk '/vmfs/volumes/Synology NFS/SimplyFile4.vmdk'...

Clone: 100% done.

hopefully it helps someone.

[jsusls]

Thanks for the help sorry it took me so long to update been busy. I added the a datastore that both vcenter's could see and was able to copy the cloudvolumes folder.

Thanks again