CBT

Symptoms

When backing up a Hyper-V Virtual Machine running on Windows Hyper-V Server 2016 (Windows 10) or higher AND this Virtual Machine is running on outdated VM configuration version 5.0, then Changed Block Tracking information for this virtual machine cannot be retrieved and entire virtual disks are processed during backup. 

Example of backup log where the problem is observed – both virtual disks are read from start to end instead of reading only changed sectors reported by CBT:

Symptoms

1. You back up a Windows machine,
2. Backup finishes with warning "Volume Tracker has failed to freeze checkpoint. A device attached to the system is not functioning"

Symptoms

You receive an e-mail notification with backup log, containing one or multiple lines with "Volume Tracker has failed to find changes on volume..."

Example:

2018-12-20T09:00:10:378-04:00 10916 I000101F8: Pending operation 173 started: 'Creating partition image'.

 

2018-12-20T09:00:11:190-04:00 10916 I00100000: Volume Tracker has failed to find changes on volume '\\?\Volume{5e2aeab2-ffb3-4dab-8444-54635f6a3367}\'.

You are reporting a typo in the following text:
Simply click the "Send typo report" button to complete the report. You can also include a comment.
CAPTCHA
This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.
1 + 4 =
Solve this simple math problem and enter the result. E.g. for 1+3, enter 4.