Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- 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
- 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 selecting media in robots
- About selecting media in standalone drives
- About Tape I/O commands on UNIX
The report's Itemization tab shows the calculated capacity for each client or policy combination. The report flags any conditions that have the potential to over count or to under count capacity. These conditions are identified in the Accuracy and Accuracy Comment columns.
Data that is displayed in the Charged Size column is protected data for a policy. A user can verify that the data is precise by referring to the policy type.
Overlap is identified within the same policy type when the accurate licensing method is used. This means that if the same data is backed up more than once by different policies of the same type (within the same client or across clients in the same master server), the overlap is identified.
Once the overlap is identified, the overlap size is displayed in the Overlap Size (KB) column. After identification of the overlap, Charged Size(KB) is updated after reducing the calculated overlap size. The Accuracy column displays OK in such cases. For a policy where the overlap was detected is deducted from charged size, the following message is displayed:
Overlap detected for the policy and deducted from the Charged Size.
If identical policies of the same type exist, the policy with the largest backup size is charged to the user. The Charged Size column displays zero for one of the identical policies.
If a policy is a subset of another policy (consumed policy), the Charged Size column displays zero for the consumed policy. The user is charged for the superset policy.
(NetBackup 8.0 or earlier clients)
When thecolumn displays for a policy, it means that the overlap exists for the given policy. The overlap size is calculated for the policy and is displayed in the column, but is not deducted from charged size.
For example, for the Compression attribute enabled, the Overlap keyword is displayed in the column. Compressed size is not the correct size (being compressed) and cannot be deducted from the charged size.policy on a NetBackup client 7.7.3, if the policy has
The size of databases that a NetBackup database agent protects cannot be determined with certainty. Third party components external to NetBackup (for example, RMAN) govern the composition of database backups.
The third-party component determines the number of backup streams and the contents of each stream. These backups are recorded as user-initiated backup images, or UBAKs. NetBackup does not initiate backup streams, nor does it know each stream's relationship to the underlying database. Therefore the information in the catalog does not provide a single, clear, undisputable figure for the total size.
In these cases, the analyzer calculates an estimation upon which to base follow-on examinations. The analyzer uses the image header information to determine the total terabytes of data that were backed up each day within the date range examined. A day is defined as the 24-hour period from midnight to midnight. The analyzer sums all full and user-initiated backups that started within that period. The day with the largest total volume of protected data during the range that is examined is assumed to be the day when a full backup of the database was performed. This figure that is returned is an estimate of the approximate size of active data under protection for the client and policy.
The catalog has only incremental backups for the range analyzed. That error may indicate that a full backup falls outside the report's range or that a full backup does not exist.
The client's data was sent to NetBackup in compressed form. The actual size cannot be determined with certainty. For all compressed backup images, the analyzer multiplies the final backup image size by a fixed value (the compression ratio). The value of the compression ratio is listed on the Summary tab.
The catalog has only snapshots for the range analyzed. The analyzer requires a backup image of the snapshot to have an accurate figure for the client's protected capacity.
The size of the clients that are protected by multistream backups is the total of all backup images that are created by all streams.