Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- About NetBackup licensing models
- nbdeployutil utility options
- Creating and viewing the licensing report
- After creating a traditional licensing report
- After creating a capacity licensing report
- Reconciling the capacity licensing report results
- 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 Tape I/O commands on UNIX
Determine the effect of multistreamed backups
On the Itemization tab, sort the list by the Accuracy column. Find all backups that list Possible multi-stream backup detected and make a note of the policy name under the Policy Name column. Open the log file that was generated when the nbdeployutil --report command ran. By default, the log file is in the directory where the gathered report is located.
Note:
If OpsCenter generated the report, the log file is found on the OpsCenter server. The email with the report results contains a link to the log file location. The log file name is in the format nbdeployutil-report-timestamp-log
.
In the log file, find the policy name for the policy in question and look at the corresponding MAX value. The excerpt from a log file that is shown highlights the information discussed.
Analyzing backups for policy <policy_name>, client <client_name> Analyzing schedule Full MAX 2010-09-01 14.6 T (multiple backups ) 21.7 G (client_name_1283295642) 09:00:42 1.0 T (client_name_1283295643) 09:00:43 793.1 G (client_name_1283295644) 09:00:45 1.2 T (client_name_1283295645) 09:00:48 1.5 T (client_name_1283295647) 09:00:49
Confirm that this information is correct for the policy. If the information is inaccurate, update the Charged Size column, and add a note to the Enter a Reason here when modifying the Charged Size column that explains the change.