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
NetBackup for RHV agent
The following section is applicable for NetBackup master server 8.2 or later and NetBackup client 8.2 or later.
The front-end data size that is reported for the Red Hat Virtualization (RHV) is same as consumed storage size. But this data is based on supported file systems. The value is accurate for NTFS, FAT, ext3,ext4 and inaccurate for ReFS, xfs file systems, or encrypted file systems.
Accurate licensing for Red Hat Virtualization (RHV) 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.
This information is applicable for NetBackup master server 8.3 or later and NetBackup client 8.3 or later.
RHV virtual machine (VM) is backed up by a Hypervisor policy (all drives). The NetBackup client that is installed inside the guest is backed up with non-file system workloads (policy types other than Standard/MS-Windows). You are only charged for the virtual machine (VM) backup.
The nbdeployutil report does not display a row for agent backup. Only one row is displayed corresponding to the RHV backup for the virtual machine (VM).
As RHV does not support single file restore, the file system backup with the agent inside the guest is not charged separately. Corresponding rows are not displayed in the nbdeployutil report. The nbdeployutil utility uses the virtual machine (VM) DNS name to correlate backup entries corresponding to RHV and agent backup. If the virtual machine (VM) DNS name is not recorded as part of the RHV backup, this correlation does not work.