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
NetBackup for NDMP agent
Accurate licensing for NDMP is specific to anpolicy type. This type of licensing collects the front-end data size (FEDS) based on the backup selections that are defined in the backup policy types.
The nbdeployutil reports actual data usage without overlap by calculating the accurate data size using the related backup files and policies. The following rules are applied to guarantee data size accuracy:
If the data size backed up by a policy withdirective is greater than the sum of other policies, the data size of directive is counted.
If identical policies are taken, then the policy with the higher size is counted.
The uncounted policies are displayed with 0 data size in thereport.
If the data size backed up by policy P1 is consumed in another policy, P2, then only the data size of policy P2 is counted.
If the data size is overlapped in multiple policies, then it is counted only once.
System administrators can use the following methods to verify the correctness of the data size that is reported by accurate licensing.
To verify the size of volumes withfiler, log on to filer and run the following command:
volume show -fields size,used,available,percent-used.
Alternatively, the administrator can mount the volume of thefiler (provided that the NFS protocol is enabled for that volume) on any UNIX-based client and run the following commands:
o du -sh o ls - lh