Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- About NetBackup licensing models
- nbdeployutil utility options
- Creating and viewing the licensing report
- After creating a traditional licensing report
- After creating a capacity licensing report
- Reconciling the capacity licensing report results
- 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 Tape I/O commands on UNIX
NetBackup for VMware Agent
The NetBackup for VMware agent reports data using accurate licensing. After a backup is complete using the VMware policy type, the agent captures the size of data that the policy protects. The data is reported to the master server.
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 following list contains all the selections in the
tab of the VMware policy type. The options are used to exclude certain virtual disks from virtual machine backup.: This type of backup includes data in all disks of a virtual machine.
: This type of backup includes all data that is not on the boot disk of a virtual machine.
: This type of backup only includes data in the boot disk of a virtual machine.
: This type of backup includes all data that is not on the custom attribute defined on the virtual server.
: This types of backup includes all data that is not on the selected disk controllers. You can add multiple disk controllers in the exclusion list by the connection type and controller ID.
The nbdeployutil utility reports actual data usage by calculating the accurate data size using the related backup files and policies. The following rules are executed to guarantee data size accuracy:
If the data size backed up by the policy
is greater than the sum of other two policies, the data size of is counted.If the data size backed up by the policies
and 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 primary VM identifiers include:
VM hostname
VM display name
VM BIOS UUID
VM DNS Name
VM instance UUID
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 correctness of the data size reported by accurate licensing.
To verify the correctness of data size reported by accurate licensing
If all disks are included in the backup, verify size on ESX datastore.
If a specific disk is excluded during the backup, verify the size by logging on to the guest operating system (OS) of the virtual machine and use commands to get the size of selected disk.
When backup agent fails to post licensing information to database, one of following error messages is displayed in the activity monitor:
WRN: Posting to feds failed. status: 5930
The message indicates that the backup agent encountered an authorization issue, with a certificate expired or nbwebsvc account password expired.
WRN: Posting to feds failed. status: 26
The message indicates backup agent encountered a service offline issue, with the service NetBackup web console not running.
For more information, see the Veritas NetBackup Status Codes Reference Guide.