Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. Veritas NetBackup™ for VMware Administrator's Guide
  3. Reduce the size of backups
  4. Block-level backup (BLIB): full vs incremental
Veritas NetBackup™ for VMware Administrator's Guide

Block-level backup (BLIB): full vs incremental

This topic applies to policy configuration for NetBackup for VMware.

When you use the Enable block-level incremental backup option in the policy, NetBackup uses VMware's Changed Block Tracking feature (CBT) to reduce the backup size.

This option reduces the size of full backups as well as the size of incremental backups, as follows.

Table: Block-level backup of the virtual machine: full vs incremental schedule

Type of backup

Optimization that is used in backup

Backup of entire virtual machine, with full schedule

Backs up only the blocks that have changed since the .vmdk was created. Note that the blocks that are not initialized are excluded from the backup.

Backup of entire virtual machine, with incremental schedule

Backs up only the blocks that have changed since the last backup, as follows:

  • For cumulative incrementals, BLIB backs up only the blocks that changed since the last full backup.

  • For differential incrementals, BLIB backs up only the blocks that changed since the previous backup of any kind.

Note:

On incremental backups, the Enable block-level incremental backup option backs up the changed files as well as their metadata.

Note:

VMware CBT may occasionally reset tracking of file changes in the virtual machine, such as after a power failure or hard shutdown. For the next backup, NetBackup reads all the data from the vmdk files and the backup takes longer than expected. If deduplication is enabled, the deduplication rate is lower than expected.

The following VMware article contains more information on CBT:

Changed Block Tracking (CBT) on virtual machines (1020128)

More Information

About reducing the size of VMware backups

Feedback

Was this page helpful?
Previous

About reducing the size of VMware backups

Next

Deleting a vSphere Client snapshot

Feedback

Was this page helpful?