Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- Methods to gather and analyze licensing reporting
- 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
- Verify the completeness of the inputs
- Eliminate redundant data due to client aliases and multiple IP addresses
- Examine the Itemization tab for flagged conditions in the Accuracy column
- Verify correct grouping and summation of multistreamed backup images
- Examine the CloudCatalyst (KB) column that displays the volume of data processed using NetBackup CloudCatalyst
- Examine overlap detection by nbdeployutil
- Reconciling the capacity licensing report results
- Additional configuration
- About multiple NetBackup master servers
- About multiple media servers with one master server
- About direct I/O for backups on Windows
- About dynamic host name and IP addressing
- About busy file processing on UNIX clients
- About specifying the locale of the NetBackup installation
- About the Shared Storage Option
- About Shared Storage Option components
- About reserving or releasing shared devices
- How to share robotic libraries without using the Shared Storage Option
- Shared Storage Option terms and concepts
- About the Shared Storage Option license
- About Shared Storage Option prerequisites
- About hardware configuration guidelines
- About installing and configuring drivers
- Verifying the connectivity
- About configuring the Shared Storage Option in NetBackup
- Verifying your Shared Storage Option configuration
- Device Monitor and Shared Storage Option
- Viewing SSO summary reports
- Operating system assistance
- Common configuration issues with Shared Storage Option
- Frequently asked questions about Shared Storage Option
- About the vm.conf configuration file
- ACS_mediatype entry in vm.conf
- ACS_SEL_SOCKET entry in vm.conf
- ACS_CSI_HOSTPORT entry in vm.conf (on UNIX)
- ACS_SSI_HOSTNAME entry in vm.conf
- ACS_SSI_INET_PORT entry in vm.conf (on UNIX)
- ACS_SSI_SOCKET entry in vm.conf
- ACS_TCP_RPCSERVICE / ACS_UDP_RPCSERVICE entry in vm.conf (on UNIX)
- ADJ_LSM entry in vm.conf
- API_BARCODE_RULES entry in vm.conf
- AUTHORIZATION_REQUIRED entry in vm.conf
- AUTO_PATH_CORRECTION entry in vm.conf
- AUTO_UPDATE_ROBOT entry in vm.conf
- AVRD_PEND_DELAY entry in vm.conf
- AVRD_SCAN_DELAY entry in vm.conf
- CLEAN_REQUEST_TIMEOUT entry in vm.conf
- CLIENT_PORT_WINDOW entry in vm.conf
- CLUSTER_NAME entry in vm.conf
- DAS_CLIENT entry in vm.conf
- DAYS_TO_KEEP_LOGS entry in vm.conf
- EMM_RETRY_COUNT entry in vm.conf
- EMM_CONNECT_TIMOUT entry in vm.conf
- EMM_REQUEST_TIMOUT entry in vm.conf
- ENABLE_ROBOT_AUTH entry in vm.conf
- INVENTORY_FILTER entry in vm.conf
- MAP_ID entry in vm.conf
- MAP_CONTINUE_TIMEOUT entry in vm.conf
- MEDIA_ID_BARCODE_CHARS entry in vm.conf
- MEDIA_ID_PREFIX entry in vm.conf
- MM_SERVER_NAME entry in vm.conf
- PREFERRED_GROUP entry in vm.conf
- PREVENT_MEDIA_REMOVAL entry in vm.conf
- RANDOM_PORTS entry in vm.conf
- REQUIRED_INTERFACE entry in vm.conf
- SERVER entry in vm.conf in NetBackup versions 8.0 and earlier
- SSO_DA_REREGISTER_INTERVAL entry in vm.conf
- SSO_DA_RETRY_TIMEOUT entry in vm.conf
- SSO_HOST_NAME entry in vm.conf
- TLH_mediatype entry in vm.conf
- TLM_mediatype entry in vm.conf
- VERBOSE entry in vm.conf
- Example vm.conf file
- How to access media and devices on other hosts
- Host name precedence in the vm.conf file
- Holds Management
- Menu user interfaces on UNIX
- About menu user interfaces
- About the tpconfig device configuration utility
- About the tpconfig utility menu
- Starting the tpconfig device configuration utility
- Adding robots
- Adding drives
- Updating a robot configuration
- Updating a drive configuration
- Deleting a robot
- Deleting a drive
- Configuring drive paths
- Configuring host credentials
- Displaying and writing the device configuration
- 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
- Methods for determining the NetBackup transfer rate
- NetBackup notify scripts
- backup_notify script
- backup_exit_notify script
- bpstart_notify script (UNIX clients)
- bpstart_notify.bat script (Windows clients)
- bpend_notify script (UNIX clients)
- bpend_notify.bat script (Windows clients)
- bpend_notify_busy script (UNIX clients)
- diskfull_notify script
- drive_mount_notify script (on UNIX)
- drive_unmount_notify script (on UNIX)
- mail_dr_info script
- media_deassign_notify script
- nbmail.cmd script (on Windows)
- parent_end_notify script
- parent_start_notify script
- pending_request_notify script
- restore_notify script
- session_notify script
- session_start_notify script
- shared_drive_notify script
- userreq_notify script
- Media and device management best practices
- About TapeAlert
- About tape drive cleaning
- How NetBackup selects drives
- How NetBackup reserves drives
- About SCSI persistent reserve
- About the SPC-2 SCSI reserve process
- About SCSI reserve requirements
- About SCSI reserve limitations
- About SCSI reservation logging
- About SCSI reserve operating system limitations on Windows
- About checking for data loss
- About checking for tape and driver configuration errors
- About configuring SCSI reserve
- How NetBackup selects media
- Volume pool and volume group examples
- Media formats
- Media and device management processes
- 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.