Thin Provisioned VMDK backup - reading as thick disk

[itdirector]

I am evaluating Veeam Backup & Replication 6.0.0.153.

Testing on 1 VM running on vSphere 5. 900GB thin provisioned with 63.2GB used.

Yesterday : Backup job : Full backup : default settings: The job details stated VM Size: 900GB (63.2GB used) : It backed up in 20 minutes, with the job progress details showing it only processes 64GB of data.

Today: I created a snapshot of the VM in vSphere, reverted back to the snapshot, then deleted all snapshots: in vSphere, it shows that it is thin provisioned : Backup job : Full backup : default settings : The job details state VM size: 900GB (63.2GB used) : it is taking over 300 minutes to backup, with the job progress details showing it processed 900GB of data.

We obvisouly wan the scenario from yesterday to work again. Is it because we did a snapshot (note: as stated, all snapshots have been deleted prior to the Veeam backup).

Any help would be appreciated

[tsightler]

So reverting snapshots cause some known issue with the reliability of CBT information. Because of this we likely failed back to "snap and scan" where we basically don't use CBT because it can't be trusted and instead scan the entire disk looking for changes. This should be "self correct" on the next run of the job.