Traditionally, Macrium Reflect has detected changes to the file system by comparing the NTFS Master File Table (MFT) on the source volume, with the MFT of the most recent image in the backup set. While this is method is one of the quickest solutions available, we do not consider it an optimal solution when used in a continuous incremental scenario, especially if multi-GB files are present in the file system.
With our Changed Block Tracker driver enabled, the first incremental/differential image taken since Windows was restarted will be performed using the traditional method. This ensures that any changes to the NTFS file system that may have occurred outside of the current Windows session are recorded into the image file. From this point on, any incremental/differential images that are taken, within the current Windows session, will use our Changed Block Tracker technology.
In additional to numerous performance improvements, starting with version 7.2, MRCBT tracks TRIM events. This events are generated by NTFS when a file is deleted or moved and are used by MRCBT to optimize the image by excluding the relevant blocks from the backup.
When MRCBT is first enabled, it captures an internal NTFS attribute that represents the number of times that the file-system has been restarted. By tracking changes to this value, MRCBT can detect if a volume has been modified in any environment where MRCBT is not operating (e.g. on another computer or operating system).
When MRCBT is enabled and Reflect detects that the Restart attribute correctly sequenced, the subsequent incremental and differential image can be generated by comparing the changed block database (created by MRCBT) on the logical volume with that stored in the previous image in the chain. This is indicated by a blue running-man icon displayed in the Reflect UI (see image below).
If Reflect detects that the Restart attribute is not correctly sequenced, the subsequent incremental or differential image will be generated using the traditional method. This is indicated by a grey running-man icon displayed in the Reflect UI.
A reboot is required after installing Macrium Reflect to enable CBT. You can create images without rebooting but CBT will only be enabled after a restart.
The NTFS Restart attribute is a fundamental component of the NTFS file-system and has been supported by all Linux and Apple operating systems dating back several years.
Due to technical limitations with Windows XP, Macrium Reflect Changed Block Tracker will only work on Windows Vista and higher operation operating systems.
After the first image of the current Windows session an icon will appear on the volume prepared for CBT:
When MRCBT is being used to generate an Incremental or Differential image of the volume will use CBT. You will volume, you will see the following line in the Image log:
Macrium CBT Driver Tools is a small Windows utility to install and monitor the Macrium CBT driver. Macrium CBT Driver Tools provides the user with a visual representation of the changed blocks and of the various performance metrics reported by the kernel mode driver. Macrium Driver Tools can be found here: C:\Program Files\Macrium\Reflect\MrCBTTools.exe
Selecting a drive shows performance metrics and tracked block information for the chosen drive. The darker shades indicate a higher percentage of changed blocks.
Session Start Time
The date and time that MRCBT started monitoring the volume. This value will be reset when the volume is mounted, normally when Windows is restarted.
Number of Writes
The total number of write operations on the volume that MRCBT has monitored since the session started.
Number of Paged Writes
The total number of write operations on the volume, flagged as PAGING_IO, that MRCBT has monitored since the session started.
Number of Tracked Writes
The total number of write operations on the volume that MRCBT has tracked since the session started.
Number of Excluded Writes
The total number of write operations on the volume that MRCBT has excluded, due to already having a record of a change to that disk area, since the session started.
Number of Failed Writes
The total number of write operations on the volume that MRCBT has failed to track since the session started. NOTE: If this value is anything other than zero. Macrium Reflect will fall back to the normal method of generating an incremental backup.
The total length of time that MRCBT has taken to track writes on the volume since the session started.
Average Time Per Tracked Write
The average length of time that MRCBT is taking to track each write operation on the volume since the session started.
Number of Changed Blocks
The total number of changed blocks on the volume since the session started.
Number of Changed Bytes
The total number of changed bytes on the volume since the session started.
$CBT Starting LCN
The first Logical Cluster Number (LCN) of the MRCBT tracking file.
$CBT Ending LCN
The last Logical Cluster Number (LCN) of the MRCBT tracking file.
Bytes Per Logical Cluster
The number of bytes per logical cluster for the volume, as reported by NTFS.
Bytes Per Block
The number of bytes per block, as reported by Macrium Reflect.
Volume Mount $LogFile Restart Count
The total current value of the NTFS $LogFile Restart Count.
|Number of TRIM/UNMAP Bytes||The number oftimes||bytes thatthe volume has||have beenmounted by NTFS this session.||affected by a TRIM or UNMAP event.|
Enabling and disabling CBT
CBT is enabled by default. You can change whether CBT is enabled or disabled by selecting “Enable Changed Block Tracking for Incremental Backups” check-box in the “Advanced Incrementals” page of the “Reflect Defaults” dialog box.
Note: You can enable or disable CBT at any time without affecting your Image sets.
We recommend enabling the Delta Indexes for Incremental Backups option as this will produce the smallest incremental image files in the shortest amount of time. Please see Delta Indexes for Incremental Backups