Veeam Copy Files to NFS and then again back to VMFS

[peste]

Hello there,

is it the usual behaviour, when I copy the files/folder (with Veeam File Copy) of a VM onto an NFS datastore (I migrate VMs between two not directly connected clusters), that VMWare shows it as thick (already copied on the NFS datastore, with the datastore browser), so it´s only one .vmdk. And the NFS datastore itself (a Synology NAS) shows it as thin (an -flat.vmdk and a .vmdk). Was this conversion correct? Can I use this thin disk without problems on a new VMFS datastore? Or is it better to inflate it after the copying. Just a question for understanding. I´m having a license and I don´t use any free or community version.

I´m a bit confused.

Thanks,
Stefan

[soncscy]

Hey Stefan,

A quick google search suggests this is more a VMware issue, not a Veeam issue:

https://communities.vmware.com/thread/324807

I think such questions are better for VMware and I'd recommend try to reproduce this outside of Veeam.

[peste]

Ok, thanks.