Netapp SMB3, failed to flush change tracking data

[Erwin Linker]

Hello,

We are using SMB3 shares from a Netapp. When we back-up a VM what is running from the SMB share we get the following message:
*Failed to flush change tracking data. Using full scan incremental run*.
I saw a articel to solve this by adding the SMB3 server to Veeam, but i don't see a option to add a Netapp. (https://www.veeam.com/kb1934)

Has anybody got a idea how to solve this? Can i add the SMB shares from a Netapp to Veeam?

Regards, Erwin

[foggy]

Erwin, VMs stored on non-Windows SMB3 shares can be backed up without CBT only. Adding SMB3 share is only required for CBT data, for regular backup/replication jobs adding the share is not needed.

[Erwin Linker]

Thanks for the replay.

What i read the veeam articels i read that CBT is used for a faster back-up (correct me if i am wrong). So the impact of disabling the CBT function is that the back-up take some more time?
Or are there more consequences for disabling this function.

[foggy]

Correct, CBT (changed block tracking) allows to avoid full scan of VM during each incremental backup cycle, but quickly get a changed blocks set to transfer. Without CBT, Veeam B&R reads entire VM data to define what it needs to backup (what has changed since the previous job run), which requires more time.