Failback operation not thin provisoning disk

[IanJ]

Hi Guys,

Currently testing failback when not having the original VM.
VM has 3TB of disks which are thin provisioned and only use around 500GB of actual space.

The replica VM is using around 500GB for all disks.

When failing back, the failback process created the VMFS files at the full size (around 3TB).

Just wondering if this is expected behaviour or am I missing something.

The configuration of the VMFS disks show they are thin provisioned so not sure why the failback produced a VMFS at the full size (its like its been thick provisioned).

Additional side effect is the fail back take significantly longer than the replication does in the first place (40 mins to replicate vs hours to failback).

[IanJ]

Just an update.

I noticed after the VM failback had been committed the VMs disk type has changed to Thick Provision Eager Zeroed, which explains why the VMFS is full sized and the why the failback took significantly longer.

[HannesK]

Hello,
the behavior is not expected. User guide says

By default, Veeam Backup & Replication preserves the format of restored VM disks, so that if disks of the VM replica were provisioned as thick, Veeam Backup & Replication will restore the VM with thick disks.

I can only recommend to create a case if things did not go the way as described. And please post the case number for reference.

Best regards,
Hannes

[foggy]

Have you selected "Same as source" during failback?