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 selecting media in robots
- About selecting media in standalone drives
- About Tape I/O commands on UNIX
The top of the Summary tab shows the basis for the report information. Examine the section marked Analyzed to verify the gathered data.
The Analyzed section displays the following information:
The master servers that are included in the report.
The date range for catalog data.
The number of clients and policies that are included in the catalog output.
If the client and the policy counts are low, the report may be based on the data that was gathered with narrower, non-default values. The analyzer gathers 90 days of catalog data for all clients by default.
The Input Directory column displays the path to the gathered data. Within the Input Directory is the
nbdeployutil-gather-timestamp.log file. If non-default values were used in the collection of catalog data, the log file displays this information.
For the agents that support accurate licensing the Overlap column summarizes the charged sizes for all overlapping policies. These are policies for which the Overlap keyword appears in the Accuracy column, per master server. The overlap is calculated only for the same policy type. For example, if both an and a policy back up an Exchange database, accurate licensing does not consider this policy as an overlap.
If data is reported using catalog image headers, the information is displayed in the Possible Overlap column.