Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- Creating and viewing the licensing report
- Reviewing a capacity licensing report
- Reconciling the capacity licensing report results
- Reviewing a traditional licensing report
- Additional configuration
- About dynamic host name and IP addressing
- About busy file processing on UNIX clients
- About the Shared Storage Option
- About configuring the Shared Storage Option in NetBackup
- Viewing SSO summary reports
- About the vm.conf configuration file
- Holds Management
- Menu user interfaces on UNIX
- About the tpconfig device configuration utility
- 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
- NetBackup notify scripts
- Media and device management best practices
- About TapeAlert
- About tape drive cleaning
- How NetBackup reserves drives
- About SCSI persistent reserve
- About the SPC-2 SCSI reserve process
- About checking for data loss
- About checking for tape and driver configuration errors
- How NetBackup selects media
- About selecting media in robots
- About selecting media in standalone drives
- About Tape I/O commands on UNIX
Manually generating licensing reports
You can manually generate reports for either the capacity or the traditional reporting model. The utility is located in the following directory:
On Windows: Install_dir\NetBackup\bin\admincmd\
On UNIX: /usr/openv/netbackup/bin/admincmd/
The utility generates the report in multiple steps. Data is gathered in the first step, and then analyzed and presented.
Table: Using nbdeployutil to gather and report licensing information
If you want to gather data from one master for other remote master servers, ensure that you have granted the necessary access across all servers:
For back-level master servers, load the engineering binary that is associated with nbdeployutil onto all master servers for which you want to gather information.
Gather the backup size data
The nbdeployutil utility uses the following options to gather data from one or more master servers.
nbdeployutil --gather [--output=DIRECTORY] [--capacity | --traditional] [--hoursago=N] [--start="mm/dd/yyyy HH:MM:SS" [--end="mm/dd/yyyy HH:MM:SS"]] [--clientlist=FILENAME | --clients=HOSTNAME[,...]] [--master=HOSTNAME[,...]] [--log=FILENAME] [--runtimestats] [--nolog] [--bpimagelist=OPTIONS] [--use-bpflist]
Analyze the data and prepare the report
The nbdeployutil utility uses the following options to analyze the gathered data and prepare the report:
nbdeployutil --report <--capacity | --traditional> <directory> ... [--dirlist=FILENAME | --parentdir=DIRECTORY] [--capacity] [--debug-inputs] [--log=FILENAME] [--clientlist=FILENAME | --clients=HOSTNAME[,...]] [--day-boundary=TIME] [--runtimestats] [--nolog] [--overlap-details] [--anonymize | --anonymize -anon-master=SOME_NAME]
For a traditional report, run: nbdeployutil --report --traditional
For a capacity report, run: nbdeployutil --report --capacity
Note: For NetBackup 8.0 and later, this step requires that you provide the web service credentials.
Examine the report and make adjustments.
On the master servers that have NetBackup 8.0 or later, when you manually run nbdeployutil for the gather operation in capacity licensing, you must enter the following credential information for authentication of the NetBackup web management service:
Table: Required credential information
Enter a domain type value from NIS, NISPLUS, WINDOWS, vx, unixpwd, ldap. This value is case-sensitive.
Name of the domain that the master server host belongs to. If the master server does not belong to any domain, enter the name of the master server.
Name of the user that has administrator privileges.
Password of the same user that has administrator privileges. When you enter the password, characters are intentionally not displayed in the command line.
In a multi-master server scenario, you must enter the credentials for all the master servers that are mentioned with the gather command.
The performance of the nbdeployutil utility is dependent on the system running it as well as the size of the NetBackup catalog. The --gather option only executes as quickly as the bpimagelist command can run on 90 days of images. The speed of report generation is dependent on the number of images and fragments. The operating system running the command also affects the utility's performance.
Depending on the environment, the nbdeployutil utility can take from several seconds to several minutes to run the --gather or the --report options.
Veritas posts the most recent information about the nbdeployutil utility on the following website:
For capacity licensing reports for any agents that support the accurate licensing method, use the overlap option to detect any data that NetBackup protects with multiple policies. To enable overlap detection, run the nbdeployutil report with the
Table: Description of overlap detection option
Command line option
This option searches for any duplicate backup selections in policies of the same type. The results are noted in the Duplicate Selections column of the report.
The backup selection data must contain only ASCII or English-only characters. This option displays the actual backup selection data in the report.
If you used scripts to automate data gathering before NetBackup 8.0, these scripts must be updated when you upgrade. The data gathering process requires that you enter the credentials for the NetBackup web service.
In this example, the nbdeployutil utility gathers information for the local master server.
C:\Program Files\Veritas\NetBackup\bin\admincmd>nbdeployutil --gather NetBackup Deployment Utility, version 8.1 Gathering license deployment information... Discovered master server master.example.com Master Server:master.example.com Domain Type (NIS, NISPLUS, WINDOWS, vx, unixpwd, ldap):WINDOWS Domain Name:example.com User Name:Administrator Password: Output for master.example.com at: C:\Program Files\Veritas\NetBackup\var\global\reports\ 20160525_151315_master.example.com Gather DONE Execution time: 9 secs
The utility generates a log file named
nbdeployutil-gather-timestamp.log during the gathering operation. By default, the log file is created in the directory where the gathered data resides.
nbdeployutil --gather --master=sidon.example.com
nbdeployutil --gather --client=dynamo,lettuce,marble2
nbdeployutil --gather --clientlist=filename.txt