Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- About NetBackup licensing models
- Tools for creating licensing reports
- How capacity licensing works
- How capacity licensing detects overlap when multiple policies protect data
- Backup policies and agents that support accurate licensing
- Requirements before gathering data for multiple master servers
- Scheduling capacity licensing reports
- 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
- NetBackup CloudCatalyst (NetBackup 8.1 and later clients)
- 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
- Windows file system backups
- UNIX file system backups
- Reconciling the capacity licensing report results
- Reviewing a traditional 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
- 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)
- 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
Creating and viewing the licensing report
After gather data for the licensing report, use the --report - - traditional or the - - capacity option to generate the licensing report. You can create a report for any of the following:
A single master server.
Several master servers.
A specific subset of clients. For example, a report that contains capacity usage for business unit billing.
The - -gather --capacity command is run for master server cayce.rm.com:
C:\Program Files\Veritas\NetBackup\bin\admincmd>nbdeployutil.exe --gather --capacity NetBackup Deployment Utility, version 8.1.x Gathering license deployment information... Discovered master server cayce.rm.com Master Server: cayce.rm.com Domain Type (NIS, NISPLUS, WINDOWS, vx, unixpwd, ldap):WINDOWS Domain Name: rm.com User Name:Administrator Password: Output for master server at: C:\Program Files\Veritas\netbackup\var\global\reports\ 20160527_140620_cayce.rm.com Gather DONE
To create a capacity report based on the data gathered, the utility tells you what command you need to run:
To create a report for this master server, run the following:
nbdeployutil.exe --report --capacity
"C:\Program Files\Veritas\netbackup\var\global\reports\
20160527_140620_cayce.rm.com"
C:\Program Files\Veritas\NetBackup\bin\admincmd>nbdeployutil.exe
--report --capacity
"C:\Program Files\Veritas\netbackup\var\global\report\
20160527_140620_cayce.rm.com"
NetBackup Deployment Utility, version 8.1.x
Analyzing license deployment ...
Following directories were given, but do not exist:
C:\Program Files\Veritas\netbackup\var\global\report\
20160527_140620_
cayce.rm.com
The utility generates a log file named nbdeployutil-report-timestamp.log during the analysis and the report generating operation. By default, the log file is created in the directory where the gathered data resides.
This example assumes that you have gathered the respective master server's data in directories master1dir, master2dir, master3dir. These directories all reside within a parent directory named EMEA-domains. The output (report and log file) is saved to the EMEA-domains directory.
# nbdeployutil --report --parentdir=EMEA-domains
This variation creates a report for a smaller set of master servers and specifies a different directory for the output.
# mkdir UK-masters # nbdeployutil --report EMEA-domains/master1dir EMEA-domains/master2dir --output=UK-masters
The utility can be used to examine a specific set of clients in detail.
Example: Gather data for a subset of clients for a time frame different than the default.
nbdeployutil.exe --gather --output BusinessUnitFinance --start "11/01/10 06:00:00" --end "11/02/10 01:00:00" --clients marybl2g1,marybl7g1 --verbose
To create a report for these clients, run the following:
nbdeployutil.exe --report "BusinessUnitFinance\20101102_155246_marybl2g1"