Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- 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
- CONNECT_OPTIONS 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
- 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
Scheduling capacity licensing reports
By default, NetBackup triggers nbdeployutil to run on a specified schedule to incrementally gather data, and to generate capacity licensing reports for the past 90 days.
Incremental reporting uses the following four parameters:
FREQUENCY_IN_DAYS: The frequency at which nbdeployutil is run.
MASTER_SERVERS: A comma-separated list of the master servers.
PARENTDIR: The gather and report folder location.
PURGE_INTERVAL: The number of days for which the folders that contain the gathered data are retained in the incremental directory.
To use the default values, See Use Case I: Use default values for parameters.
To use the custom values, See Use Case II: Use custom values for parameters.
The location where the data and reports are generated 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 following directories contain the most current capacity licensing report:
On Windows: Install_Dir\NetBackup\var\global\incremental
On UNIX: /usr/openv/var/global/incremental
The older reports are placed in the archive folder. If you want to see how the capacity usage has changed over time, you can view the older reports. Delete the reports or delete the folder if you no longer require the reports. It is recommended that you retain 90 days of reporting data. You can retain data older than 90 days depending on your requirement.
Each time nbdeployutil is triggered, the information is gathered for the following duration: from the last successful run to the latest run of nbdeployutil. For the first run, the duration of the report is as per the frequency specified in the configuration file (default value is 7 days). The report duration is always for the last 90 days based on the availability of the gathered data. Any data prior to 90 days is not considered in the report.
The nbdeployutilconfig.txt file is not required when using the default parameters. nbdeployutil uses the following default values:
FREQUENCY_IN_DAYS=7
MASTER_SERVERS=local_server
PARENTDIR=folder_name
For Windows: Install_Dir\NetBackup\var\global\incremental
For UNIX: /usr/openv/var/global/incremental
PURGE_INTERVAL=180 (number of days).
Edit the nbdeployutilconfig.txt file.
To use custom values in the nbdeployutilconfig.txt file
- Based on your operating system, copy the nbdeployutilconfig.txt file to the following location:
For Windows: Install_Dir\NetBackup\var\global
For UNIX: /usr/openv/var/global
- Open and edit nbdeployutilconfig.txt to change the parameters and then save the file.
FREQUENCY_IN_DAYS=number_of_days
Based on the frequency you set here, nbdeployutil gathers the data and generates the report.
Minimum value: 1 day.
By default, the frequency value in the configuration file is set as 7 days to capture optimum capacity usage data.
If there is no value in this parameter, nbdeployutil uses the default value.
If you specify the frequency as 0, incremental reporting is disabled and no licensing information is captured.
If you delete the parameter, nbdeployutil uses the default value.
MASTER_SERVERS=server_names
nbdeployutil gathers the information for each master server list and generates the report.
If there is no value in this parameter, nbdeployutil uses the default value.
If you delete the parameter, nbdeployutil uses the default value.
Examples of server names:
MASTER_SERVERS=newserver,oldserver
MASTER_SERVERS=newserver,oldserver.domain.com
MASTER_SERVERS=myserver1.somedomain.com,newserver.domain.com
PARENTDIR=folder_name_with_path
To change the gather and report location, edit this parameter.
If there is no value in this parameter, nbdeployutil uses the default value.
If you delete the parameter, nbdeployutil uses the default value.
PURGE_INTERVAL=number_of_days
Gathered data that does not fit into the purge_interval value is deleted automatically.
If there is no value in this parameter, nbdeployutil uses the default value.
If you delete the parameter, nbdeployutil uses the default value.
If you specify a value less than 90 days, nbdeployutil uses 90 days as the value for the parameter. Data that is older than 180 days is purged.
Data to be purged = current date - purge_interval.
Minimum value = 90 days.
If nbdeployutil fails to gather data and generate the report for your environment, refer to the logs to understand when the task failed and the reason for the failure.
To change the directory of the gathered data and licensing report
- If you have older gathered data and licensing reports, copy the complete directory to the new location.
- Edit
nbdeployutilconfig.txtand change the location of the gathered data and licensing report in the PARENTDIR=folder_name field.
To use the previously successful gathered data for generating a capacity licensing report
- Copy the gather folder that was generated after previous run of nbdeployutil to the following location:
On Windows: Install_Dir\NetBackup\var\global\incremental
On UNIX: /usr/openv/var/global/incremental
- Create the gather_end.json file inside the copied folder and add the following text:
{"success":0}
The next incremental run considers the data inside the copied folder to generate a capacity licensing report.
Note:
You must delete any other gather folders inside the copied folder to avoid gaps for the period in which data is gathered. The missing data is automatically generated during the next incremental run.
To create a custom interval report using existing gathered data
- To create a report for a time interval that is different than the default interval of 90 days, run the following command:
On Windows:
nbdeployutil.exe --capacity --incremental --report --inc-settings "<Install_Dir>\netbackup\var\global\nbdeployutilconfig.txt" --hoursago <custom-time-interval>
On UNIX:
nbdeployutil.exe --capacity --incremental --report --inc-settings "/usr/openv/var/global/nbdeployutilconfig.txt" --hoursago <custom-time-interval>
The number of hours specified in --hoursago must be less than the purge-interval that is specified in the nbdeployutilconfig.txt file.
Note:
nbdeployutil uses existing gathered data to generate the custom interval report. You are not required to use the --gather command.