Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and usage reporting
- How capacity licensing works
- Creating and viewing the licensing report
- Reviewing a capacity licensing report
- Reconciling the capacity licensing report results
- Reviewing a traditional licensing report
- Reviewing an NEVC licensing report
- Additional configuration
- About dynamic host name and IP addressing
- About busy file processing on UNIX clients
- About the Shared Storage Option
- DELETE About configuring the Shared Storage Option in NetBackup
- Viewing SSO summary reports
- About the vm.conf configuration file
- Holds Management
- Menu user interfaces on UNIX
- About the tpconfig device configuration utility
- About the NetBackup Disk Configuration Utility
- Reference topics
- Host name rules
- About reading backup images with nbtar or tar32.exe
- Factors that affect backup time
- NetBackup notify scripts
- Media and device management best practices
- About TapeAlert
- About tape drive cleaning
- How NetBackup reserves drives
- About SCSI persistent reserve
- About the SPC-2 SCSI reserve process
- About checking for data loss
- About checking for tape and driver configuration errors
- How NetBackup selects media
- About Tape I/O commands on UNIX
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:
| Backup Selection:
|
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:
| Backup Selection:
|
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.