![]() ![]() ![]() If a match is found (which means the block already exists in the backup), the corresponding block is filtered out. ![]() When incremental backup is run, Veeam Backup & Replication opens all backup files in the chain of previous full and incremental backups, reads metadata from these files and compares it with checksums calculated for a VM in its current state. Checksums are stored as metadata to backup files next to VM data. Instead of tracking changed blocks of data, Veeam Backup & Replication filters out unchanged data blocks.ĭuring VM processing, Veeam Backup & Replication consolidates virtual disk content, scans through the VM image and calculates a checksum for every data block. If Veeam Backup & Replication cannot leverage VMware vSphere CBT, it fails over to the Veeam proprietary filtering mechanism. Hello everyone, I am following the Keith Barker CBT nuggets video to create a lab in my local machine. In some situations, Veeam Backup & Replication cannot leverage VMware vSphere CBT, for example, if VMs run an earlier version of virtual hardware. For VMs with virtual disks on NFS datastore, Veeam Backup & Replication uses CBT as well, but cannot leverage CBT on first full run (for more information, see this KB article ). ![]() For VMs with virtual disks in thin format, Veeam Backup & Replication also uses CBT during active full backup sessions to detect unallocated regions of virtual disks and skip them. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |