Changed Block Tracking

In this article

    The changed block tracking (CBT) mechanism allows Veeam Backup for AWS to quickly backup EC2 instances to backup repositories.

    Veeam Backup for AWS uses the CBT mechanism to reduce the amount of data read from processed EBS volumes:

    • During a full backup session, Veeam Backup for AWS reads only written data blocks, while unallocated data blocks are filtered out.
    • During an incremental backup session, Veeam Backup for AWS reads only those data blocks that have changed since the previous backup session.

    To detect unallocated and changed data blocks, CBT relies on EBS Direct APIs.

    1. During the first (full) backup session, Veeam Backup for AWS creates a cloud-native snapshot of an EC2 instance. To do that, Veeam Backup for AWS sends API requests to access the content of the snapshot and to detect unallocated data blocks.
    2. During subsequent sessions, new cloud-native snapshots are created. Veeam Backup for AWS sends API requests to access and to compare the content of the snapshot created during the previous backup session and the snapshot created during the current backup session. This allows Veeam Backup for AWS to detect data blocks that have changed since the previous backup session.

    Limitations for Changed Block Tracking

    Veeam Backup for AWS cannot use CBT for EC2 instances that reside in AWS Regions where EBS Direct APIs are not available.

    If CBT cannot be used, Veeam Backup for AWS reads the whole content of processed EBS volumes and compares it with backed-up data that already exists in the backup repository. In this case, the completion time and cost of incremental backups may occur to grow.

    Related Topics

    CBT Impact on Snapshot Retention