vm veeam and nfs cbt required time to backup

[mgambetti]

hi,
we have one vm with veeam, the repository is a cifs nas, and the datastores of vcenter are all nfs (as required by best practice). When i do the incrementals (with cbt enabled correctly) backups of all the vms, i have seen that, from veeam server job statistics, the transferred MBs are equal to the delta since last backup, as expected, BUT the time it takes to complete the job is equal to that of full backups!
it seems to me that veeam is "reading" all the vmdk anyway and transferring only the new blocks...
am i missing something?
thank you.

[Vitaliy S.]

Hello,

it seems to me that veeam is "reading" all the vmdk anyway and transferring only the new blocks...

This is exactly how Veeam's proprietary change tracking engine works if backup job cannot leverage VMware CBT while backing up your VMs. Anyway, what you see is an expected behavior for backing up Veeam backup proxies.

Thanks!

[mgambetti]

soory but i have not understood. i am not using any proxy backup and the cbt is ENABLED on vmware...so why is using the "proprietary" engine?
thank you

[Vitaliy S.]

we have one vm with veeam

It is just a repository server? Do you see a [CBT] tag next to VM virtual disks in the corresponding job log session?

[mgambetti]

vm hardware was still 4.
shame on me not checked berfore.
sorry, thank you for the support.

[Vitaliy S.]

Ok, thanks for coming back and updating the topic.