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_path\NetBackup\bin\admincmd\
On UNIX: /usr/openv/netbackup/bin/admincmd/
You cannot manually generate the NetBackup Enterprise Virtual Client Edition (NEVC) licensing report.
If you use capacity-based licensing, run the following commands:
For gather: --gather --capacity
For reports: --report --capacity
If you use traditional based licensing, run the following commands:
For gather: --gather --traditional
For reports: --report --traditional
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
Step | Action | Description |
|---|---|---|
Step 1 | Complete prerequisites. | 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: See Requirements before gathering data for multiple master servers in capacity licensing. Multiple master servers are only supported in capacity licensing. 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] | |
Step 2 | 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. |
Step 3 | 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
Option | Description |
|---|---|
Domain Type | Enter a domain type value from NIS, NISPLUS, WINDOWS, vx, unixpwd, ldap. This value is case-sensitive. |
Domain Name | 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. |
User name | Name of the user that has administrator privileges. |
Password | Password of the same user that has administrator privileges. When you enter the password, characters are intentionally not displayed in the command line. |
Note:
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.
If you use Flexible licensing, scanning a large number of clients increases the execution time of nbdeployutil run accordingly. The clients that are scanned in the current run (for which the machine type is collected) are not scanned again in the subsequent runs. This reduces the execution time of nbdeployutil.
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 --overlap-details option.
Table: Description of overlap detection option
Command line option | Description |
|---|---|
--overlap-details | 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. Note: 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.
See Providing web service credentials for the capacity licensing report.
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
or
nbdeployutil --gather --clientlist=filename.txt