1 / 12

Understanding vRanger Pro 4.5: The Impact of CBT and ABM on Backup Performance

This guide explores how Change Block Tracking (CBT) and Application Based Management (ABM) optimize backup processes in vRanger Pro 4.5. We delve into the differences in block scanning for full and incremental backups, highlighting the efficiency gained by utilizing CBT and ABM together. Key concepts include the handling of active, unallocated, zero, and deleted blocks during the backup process, the elimination of unnecessary data reads, and the strategies for both initial and incremental backups. Enhance your understanding of vRanger's performance enhancements for effective data protection.

erasto
Télécharger la présentation

Understanding vRanger Pro 4.5: The Impact of CBT and ABM on Backup Performance

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. vRanger Pro 4.5 CBT and ABM

  2. Image-Based Backup: Activities Impacting Performance • 1: Scanning • 3: Writing 2: Reading 0 0 0 0 0

  3. How CBT and ABM work together A typical disk layout, before 1st backup 0 0 0 0 Active Block Unallocated Block 0 Zero Block 0 Changed Block Deleted Data

  4. Fulls: without CBT or ABM • All blocks must be scanned and read • Unallocated and zero blocks are both read as zeros • vRanger engine removes all “whitespace” on writes Scan and Read Write 0 0 0 0 0 0 0 Active Block Unallocated Block 0 0 Zero Block 0 Changed Block Deleted Data

  5. Fulls: with CBT • Does not scan unallocated blocks • Zeros and deleted blocks are scanned and read • vRangerengine removes “whitespace” on writes Scan and Read Write 0 0 0 0 0 0 0 0 0 0 Active Block Unallocated Block 0 0 0 0 Zero Block 0 Changed Block Deleted Data

  6. Fulls: with ABM • Does not scan zero nor deleted blocks • Unallocated blocks are scanned and read • vRanger engine removes un-allocated “whitespace” Scan and Read Write Active Block Unallocated Block Zero Block 0 Changed Block Deleted Data

  7. Fulls: with Both ABM and CBT • Scans the minimum set of blocks: no zero nor unallocated whitespace, no deleted blocks Write Scan and Read Active Block Unallocated Block Zero Block 0 Changed Block Deleted Data

  8. How CBT and ABM work together A typical disk layout, after 1st backup 0 0 0 Active Block Unallocated Block 0 Zero Block 0 Changed Block Deleted Data

  9. Incrementals: without ABM or CBT • All blocks are scanned • Only changed blocks are read • vRanger engine removes “whitespace” Scan and Read Write 0 0 0 Active Block Unallocated Block 0 Zero Block 0 Changed Block Deleted Data

  10. Incrementals: with CBT • Changed blocks are “presented” to vRanger by vSphere API • No scanning necessary • Only changed blocks are read and written From vStorage API Read and Write Active Block Unallocated Block Zero Block 0 Changed Block Deleted Data

  11. Incrementals: with ABM • Active blocks are presented to vRanger by Windows NTFS • Scanning includes only active and unallocated blocks (zero and inactive blocks are not included in the scan) • Only changed, active blocks are read and written Scanned Read and Written Active Block Unallocated Block Zero Block 0 Changed Block Deleted Data

  12. Incrementals: Both ABM and CBT together • No scanning • Only active and changed blocks are read and written From vStorage API Read and Written Active Block Unallocated Block Zero Block 0 Changed Block Deleted Data

More Related