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
About the capacity licensing model
Capacity licensing is based on the total amount of data that NetBackup protects on the client or agent. When the capacity licensing model is used, NetBackup automatically gathers the information in one of two methods:
By getting the information from the backup image header. If a policy type is not yet supported for the accurate licensing method, this method is used.
By using the accurate licensing method.
NetBackup automatically uses this method if the policy type supports accurate licensing. Each supported policy type uses a unique mechanism at backup time to calculate the size of the data that the policy is protecting. This information is gathered and then stored in the NetBackup database.
The following policy types report data size using accurate licensing:
MS-Windows
Standard
MS-Exchange-Server
MS-SQL-Server
VMware
NDMP
Oracle
BigData
Accurate licensing enables the user to have the following:
Faster performance of the nbdeployutil tool to gather and generate capacity licensing report as NetBackup stores the front-end size of backup data.
Precise Front-end Terabytes (FETBs). If multiple backup copies are created, only the first copy is considered.
Table: NetBackup client versions and supported policy types
NetBackup client version | Supported policy types |
|---|---|
8.0 | MS-Windows, Standard, MS-Exchange-Server, MS-SQL-Server |
8.1 | MS-Windows, Standard, MS-Exchange-Server, MS-SQL-Server, VMware, NDMP, Oracle, BigData (for Hadoop HDFS and Nutanix Acropolis Hypervisor) |
The capacity licensing report includes details about the mechanism that is used based on the policy type. nbdeployutil securely communicates with the master server to gather the protected data sizes and generate reports. The report is generated only for full backups and user-directed backups (including expired backups) for the last 90 days per the license agreement.
All of the clients included in the policy must be updated to NetBackup 8.1 or later when accurate licensing is used. The reporting data for any clients that run older NetBackup versions is not included in the calculation of protected data. For these clients, the capacity licensing numbers are generated using the legacy method of backup image header.
The data size that is reported in the Itemization sheet of the report under Storage Types, for example, Tape, BasicDisk, PureDisk, etc., is the front-end data size that is backed up to that specific storage type and not the storage size that the backup consumes.
Users are charged based on the protected data size. If multiple backup copies are created using a single policy (a copy created and stored on disk, for example), only the first copy is considered for calculation. The other copies are not charged to the user.
If multiple policies of the same type protect the same data, the capacity report identifies the overlap. The user needs to calculate the actual data overlap and then configure the policies considering this overlap. The user can then change the report based on the overlap. The overlap is only applicable to data reported using accurate licensing.
To record protected data, an agent must have a valid certificate (issued by the master server) to securely connect with the master server. If the certificate is not generated and available on the client, the protected data is not recorded using accurate licensing. In this scenario, the data is reported using the backup image header in the capacity licensing report. After the certificate is available and protected data is recorded using accurate licensing, the method of using the backup image header is no longer used.
The user can generate the certificate by using the nbcertcmd command. For more information about this command, refer to the NetBackup Commands Reference Guide.