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™ Administrator's Guide, Volume II
  3. NetBackup licensing models and the nbdeployutil utility
  4. Reviewing a capacity licensing report
  5. Data backed up by multiple policies
Veritas NetBackup™ Administrator's Guide, Volume II

Data backed up by multiple policies

The nbdeployutil utility can use overlap detection to ensure that you are not charged for backup select data that is backed up by multiple policies of the same type. For NetBackup 8.1 and later clients, the report includes the names of the duplicate backup selections. The adjustment for any overlapping data is reflected in the Charged Size column of the report.

For example, if you have the following backup policies for policy type Microsoft SQL Server:

Table: Policies

Policy1

Policy2

Backup Selection:

  • "MSSQLSERVER"/"DB1"/ [Size 1.4GB]

  • "MSSQLSERVER"/"DB2"/ [Size 1.4GB]

Backup Selection:

  • "MSSQLSERVER"/"DB2"/ [Size 1.4GB]

  • "MSSQLSERVER"/"DB3"/ [Size 1.4GB]

Here MSSQLSERVER is the name of instance and DB1, DB2, DB3 are the databases. The DB file DB2 is common in both policies Policy1 and Policy2. nbdeployutil detects the overlap and displays in the report.

Table: Sample report columns

Policy Name

Accuracy

Accuracy Comment

Overlap Size (GB)

Duplicate Selection

Total (Readable) Size (GB)

Charged Size (GB)

Policy1

OK

 

0

 

2.8

2.8

Policy2

OK

Overlap detected for the policy and deducted from the Charged Size

1.4

"MSSQLSERVER"/<PLACE_HOLDER>/"DB2"/

2.8

1.4

In case of Availability Group (AG) the <PLACE_HOLDER> contains the AG name.

For a NetBackup client with version 8.0 or earlier, the following report is displayed policy that uses the backup image header method to gather information:

Table: Policies

Policy1: DB_File_Overlap1

Policy2: DB_File_Overlap2

Backup Selection:

  • Instance=INST_R DB file=DB_01 [Size 1.4GB]

  • Instance=INST_R DB file=DB_02 [Size 1.4GB]

Backup Selection:

  • Instance=INST_R DB file=DB_02 [Size 1.4GB]

  • Instance=INST_R DB file=DB_03 [Size 1.4GB]

In this example, the DB file DB_02 is common in both policies DB_File_Overlap1 and DB_File_Overlap2. nbdeployutil detects the overlap and displays in the report. An extract of the report specific to this example is as follows:

Table: Sample report columns

Policy Name

Accuracy

Accuracy Comment

Overlap Size (GB)

Total (Readable) Size (GB)

Charged Size (GB)

DB_File_Overlap1

Database Estimation, Multistream Estimation, OK

DB size estimated via backup summation, Multi-stream backup estimation

0

2.8

2.8

DB_File_Overlap2

Database Estimation, Multistream Estimation, OK

DB size estimated via backup summation, Multi-stream backup estimation, Overlap detected for the policy and deducted from the Charged Size

1.4

2.8

1.4

For policy DB_File_Overlap2 the customer is charged for only DB file DB_03.

Feedback

Was this page helpful?
Previous

NetBackup CloudCatalyst (NetBackup 8.1 and later clients)

Next

BigData plug-ins for NetBackup

Feedback

Was this page helpful?