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
Scheduling reports for capacity licensing
By default, NetBackup triggers nbdeployutil to run on a specified schedule to incrementally gather data and to generate licensing reports. For the first run, the duration of the report uses the frequency that is specified in the configuration file.
For capacity licensing, the report duration is always for the last 90 days based on the availability of the gathered data. Any data older than 90 days is not considered in the report. Each time nbdeployutil runs, it gathers information for the time between the latest run of nbdeployutil and the previous successful run.
The current capacity licensing report resides in the following directory:
On Windows: install_path\NetBackup\var\global\incremental
On UNIX: /usr/openv/var/global/incremental
It contains the following files:
The generated report for the latest nbdeployutil result.
Folders containing incrementally gathered data.
The archive folder that contains the older generated reports.
nbdeployutil log files.
The older reports are placed in the archive folder. Veritas recommends that you retain at least 90 days of reporting data. Data can be kept longer than 90 days, depending on the requirements of your environment. Older reports can help to show how the capacity usage has changed over time. Delete the reports or the folder when they are no longer required.
The nbdeployutilconfig.txt file is not required when you use the default parameters. nbdeployutil uses the following default values for capacity licensing:
FREQUENCY_IN_DAYS=7
MASTER_SERVERS=local_server
PARENTDIR=folder_name
For Windows: install_path\NetBackup\var\global\incremental
For UNIX: /usr/openv/var/global/incremental
PURGE_INTERVAL=120 (number of days)
MACHINE_TYPE_REQUERY_INTERVAL = 90 (number of days)
If the file nbdeployutilconfig.txt is not present, create a file using the following format:
[NBDEPLOYUTIL_INCREMENTAL] MASTER_SERVERS=<server_names> FREQUENCY_IN_DAYS=7 PARENTDIR=<folder_name_with_path> PURGE_INTERVAL=120 MACHINE_TYPE_REQUERY_INTERVAL=90
To use custom values for the licensing report
- Copy the nbdeployutilconfig.txt file to the following location:
For Windows: install_path\NetBackup\var\global
For UNIX: /usr/openv/var/global
- Open the nbdeployutilconfig.txt file.
- Edit the
FREQUENCY_IN_DAYSvalue to reflect how often you want the report to be created.Default (recommended)
7
Minimum
1
Value of 0
Disables the incremental reporting and no licensing information is captured.
Parameter deleted
nbdeployutil uses the default value.
- Edit the
MASTER_SERVERSvalue to include a comma-separated list of the master servers you want to include in the report.Note:
Veritas Usage Insights requires that master servers be at NetBackup 8.1.2 or later.
No value
nbdeployutil uses the default value.
Parameter deleted
nbdeployutil uses the default value.
For example:
MASTER_SERVERS=newserver, oldserver
MASTER_SERVERS=newserver, oldserver.domain.com
MASTER_SERVERS=myserver1.somedomain.com, newserver.domain.com
- Edit the
PARENTDIRvalue to include the full path for location where the data is gathered and reported.No value
nbdeployutil uses the default value.
Parameter deleted
nbdeployutil uses the default value.
- Edit the
PURGE_INTERVALto indicate the interval (in days) for how often you want to delete the report data. Data that is older than 120 days is automatically purged.Default
120
Minimum
90
No value
nbdeployutil uses the default value.
Parameter deleted
nbdeployutil uses the default value.
- Edit the
MACHINE_TYPE_REQUERY_INTERVALto indicate how often to scan physical clients for updates to the machine type.Default
90
Minimum
1
No value
nbdeployutil uses the default value.
Parameter deleted
nbdeployutil uses the default value.