Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and usage reporting
- About NetBackup licensing models
- Tools for creating and viewing licensing reports
- Setting the licensing type for scheduled reports
- How capacity licensing works
- How NEVC licensing works
- Scheduling reports for capacity licensing
- Scheduling reports for traditional licensing
- Scheduling reports for NetBackup Enterprise Virtual Client (NEVC) licensing
- Other configuration for incremental reporting
- Troubleshooting failures for usage reporting and incremental reporting
- Manually generating licensing reports
- Creating and viewing the licensing report
- Reviewing a capacity licensing report
- Summary tab
- Client aliases and multiple IP addresses
- Itemization tab
- Clients backed up with multiple streams
- Data backed up by multiple policies
- BigData plug-ins for NetBackup
- NetBackup for Exchange agent
- NetBackup for NDMP agent
- NetBackup for Oracle server agent
- NetBackup for SQL Server agent
- NetBackup for VMware agent
- NetBackup for Hyper-V agent
- NetBackup for RHV agent
- NetBackup for Nutanix-AHV agent
- NAS-Data-Protection policy
- Cloud policy
- NetBackup for Kubernetes
- Windows file system backups
- UNIX file system backups
- Reconciling the capacity licensing report results
- Reviewing a traditional licensing report
- Reviewing an NEVC licensing report
- Using the NetBackup Storage API to get the total backup size information
- 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
- DELETE About reserving or releasing shared devices
- How to share robotic libraries without using the Shared Storage Option
- Shared Storage Option terms and concepts
- DELETE About the Shared Storage Option license
- About Shared Storage Option prerequisites
- About hardware configuration guidelines
- About installing and configuring drivers
- Verifying the connectivity
- DELETE 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 in NetBackup versions 8.0 and earlier
- 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
- 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
- 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
- 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)
- child_end_deployment_notify
- child_start_deployment_notify
- 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_deployment_notify
- parent_end_notify script
- parent_start_deployment_notify
- 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
- Index
Itemization tab
The report's Itemization tab shows the calculated capacity for each client or policy combination. The report flags any conditions that have the potential to over count or to under count capacity. These conditions are identified in the Accuracy and Accuracy Comment columns.
Data that is displayed in the Charged Size column is protected data for a policy. A user can verify that the data is precise by referring to the policy type.
See Eliminate redundant counting of clients.
Overlap scenarios:
Overlap is identified within the same policy type when the accurate licensing method is used. This means that if the same data is backed up more than once by different policies of the same type (within the same client or across clients in the same master server), the overlap is identified.
Once the overlap is identified, the overlap size is displayed in the Overlap Size (KB) column. After identification of the overlap, Charged Size(KB) is updated after reducing the calculated overlap size. The Accuracy column displays OK in such cases. For a policy where the overlap was detected is deducted from charged size, the following message is displayed:
Overlap detected for the policy and deducted from the Charged Size.
If identical policies of the same type exist, the policy with the largest backup size is charged to the user. The Charged Size column displays zero for one of the identical policies.
If a policy is a subset of another policy (consumed policy), the Charged Size column displays zero for the consumed policy. The user is charged for the superset policy.
(NetBackup 8.0 or earlier clients)
When the column displays for a policy, it means that the overlap exists for the given policy. The overlap size is calculated for the policy and is displayed in the column, but is not deducted from charged size.
For example, for the policy on a NetBackup client 7.7.3, if the policy has Compression attribute enabled, the Overlap keyword is displayed in the column. Compressed size is not the correct size (being compressed) and cannot be deducted from the charged size.
The size of databases that a NetBackup database agent protects cannot be determined with certainty. Third party components external to NetBackup (for example, RMAN) govern the composition of database backups.
The third-party component determines the number of backup streams and the contents of each stream. These backups are recorded as user-initiated backup images, or UBAKs. NetBackup does not initiate backup streams, nor does it know each stream's relationship to the underlying database. Therefore the information in the catalog does not provide a single, clear, undisputable figure for the total size.
In these cases, the analyzer calculates an estimation upon which to base follow-on examinations. The analyzer uses the image header information to determine the total terabytes of data that were backed up each day within the date range examined. A day is defined as the 24-hour period from midnight to midnight. The analyzer sums all full and user-initiated backups that started within that period. The day with the largest total volume of protected data during the range that is examined is assumed to be the day when a full backup of the database was performed. This figure that is returned is an estimate of the approximate size of active data under protection for the client and policy.
The catalog has only incremental backups for the range analyzed. That error may indicate that a full backup falls outside the report's range or that a full backup does not exist.
The client's data was sent to NetBackup in compressed form. The actual size cannot be determined with certainty. For all compressed backup images, the analyzer multiplies the final backup image size by a fixed value (the compression ratio). The value of the compression ratio is listed on the Summary tab.
The catalog has only snapshots for the range analyzed. The analyzer requires a backup image of the snapshot to have an accurate figure for the client's protected capacity.
Note:
For Kubernetes workloads, if the snapshots do not exist in a backup, the column condition appears as "Size unavailable".
The size of the clients that are protected by multistream backups is the total of all backup images that are created by all streams.