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
NetBackup for Nutanix-AHV agent
Note:
The following section is applicable for NetBackup master server 8.3 or later and NetBackup client 8.3 or later.
The front-end data size that is reported for Nutanix Acropolis Hypervisor is the consumed storage size. You can verify the consumed storage size on the Nutanix AHV console by navigating to Storage column. The Storage column displays the consumed storage size as compared to the total allocated storage size.
under theAccurate licensing for Nutanix-AHV virtual machine (VM) collects the total number of Front-End Terabytes (FETBs) protected by NetBackup.
The nbdeployutil utility reports actual data usage by calculating the accurate data size using the related backup VM size and policies. The following rules are applied to guarantee data size accuracy:
If identical policies are taken, the policy with higher size is counted.
If different policies use the same virtual machine (VM) identifiers, they are detected as identical policies.
The Nutanix-AHV VM can be backed up using BigData policy and by Hypervisor policy (all drives Included). If the same VM is backed up using both BigData and Hypervisor policies, you are charged once for the VM backup using Hypervisor policy.
Note:
File system backup using the agent inside the Nutanix-AHV VM is charged separately and corresponding separate rows are displayed in the nbdeployutil report.