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 VMware agent
The following section is applicable for NetBackup master server 8.1 or later and NetBackup client 8.1 or later.
Accurate licensing for virtual machine (VM) is specific to a VMware policy. This type of licensing 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 files and policies. The following rules are applied to guarantee data size accuracy:
If the data size backed up by the policyis greater than the sum of other two policies, the data size of is counted.
If the data size backed up by the policiesand are greater than the , the data size of and is counted.
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 uncounted policies are displayed with 0 data size in the FEDS table generated by the nbdeployutil utility.
System administrators can use the following ways to verify the data size reported by accurate licensing.
If all disks are included in the backup, verify the size of the ESX datastore.
If a specific disk is excluded during the backup, verify its size on the guest operating system (OS) of the virtual machine.
VMware virtual machine (VM) is backed up by VADP policy (all drives Included) and the NetBackup client installed inside the guest is backing non filesystem workloads (using 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. There is only one row displayed corresponding to the VADP backup for the virtual machine (VM).
As VADP supports single file restore, file system backup using agent inside the guest is charged separately and corresponding rows are displayed in the nbdeployutil report. nbdeployutil uses the virtual machine (VM) DNS name to correlate backup entries corresponding to VADP and agent backup. If the virtual machine (VM) DNS name is not recorded as part of the VADP backup, this correlation does not work. A virtual machine (VM) backup must have all drives included. If drives are excluded as part of the VADP backup, the agent backup is charged separately.