Management

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 787 other subscribers

Social

  • LinkedIn
  • RSS Feed for Posts
  • Twitter
  • StumbleUpon

[Solved] Veeam: :: Failed to flush change tracking data, using full scan to determine changes.

This week a customer of us had out of the blue, an error in Veeam Backup & Replication.

Error :

<Date> ::
Failed to flush change tracking data, using full scan to determine changes.

Solution:

In our case we needed to reset the HvVmChangeTracking

More info:

http://helpcenter.veeam.com/backup/80/hyperv/changed_block_tracking.html

In some cases, CBT data may get corrupted — as a result, Veeam Backup & Replication will fail to process VMs with changed block tracking. To reset CBT data for individual VMs or specific VHD/VHDX files, you can use the Reset-HvVmChangeTrackingPowerShell cmdlet.  To learn more, see the Veeam PowerShell reference guide at http://www.veeam.com/documentation-guides-datasheets.html.

http://helpcenter.veeam.com/backup/80/powershell/reset-hvvmchangetracking.html

Reset-HvVmChangeTracking -Server $server -VhdPath “C:\Users\Public\Hyper-V\Virtual Hard Disks\hv_dns.vhdx”

If ADM01 is hosted on HV01 and ADM02 is hosted on HV02:

Reset-HvVmChangeTracking -Server hv01 -VMName “adm01”

Reset-HvVmChangeTracking -Server hv02 -VMName “adm02”

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.