Discussions specific to the Microsoft Hyper-V hypervisor
Post Reply
Erwin Linker
Service Provider
Posts: 24
Liked: 2 times
Joined: Mar 30, 2016 12:58 pm
Full Name: Erwin Linker
Contact:

Netapp SMB3, failed to flush change tracking data

Post by Erwin Linker » Jun 16, 2016 8:19 am

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
Veeam Software
Posts: 18278
Liked: 1564 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Netapp SMB3, failed to flush change tracking data

Post by foggy » Jun 16, 2016 11:22 am

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
Service Provider
Posts: 24
Liked: 2 times
Joined: Mar 30, 2016 12:58 pm
Full Name: Erwin Linker
Contact:

Re: Netapp SMB3, failed to flush change tracking data

Post by Erwin Linker » Jun 16, 2016 12:51 pm

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
Veeam Software
Posts: 18278
Liked: 1564 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Netapp SMB3, failed to flush change tracking data

Post by foggy » Jun 16, 2016 12:54 pm

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.

Post Reply

Who is online

Users browsing this forum: No registered users and 7 guests