Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- Methods to gather and analyze licensing reporting
- 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
- Verify the completeness of the inputs
- Eliminate redundant data due to client aliases and multiple IP addresses
- Examine the Itemization tab for flagged conditions in the Accuracy column
- Verify correct grouping and summation of multistreamed backup images
- Examine the CloudCatalyst (KB) column that displays the volume of data processed using NetBackup CloudCatalyst
- Examine overlap detection by nbdeployutil
- Reconciling the capacity licensing report results
- 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)
- 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
NetBackup for NDMP Agent
The NetBackup for Network Data Management Protocol (NDMP) Agent reports data using the accurate licensing method when capacity licensing is used. After the backup is complete using the policy for Network Attached Systems (NAS), the captures the size of data that the policy protects. The data is reported to the master server.
Accurate licensing for NDMP is specific to an policy type. This type of licensing collects the front-end data size (FEDS) based on the backup selections that are defined in the backup policy types.
Following are some of the directives, wildcard characters, and path names that are available as backup selections in the NDMP workload.
Directives
The directive provides a method to include all file systems and volumes on an filer in an backup policy. You can exclude specific volumes from an backup selection if you do not want to back up every volume on an filer. Use the directive for this purpose.
The directive is used when is enabled, otherwise it is ignored. In this mode, the following can occur:
The backup splits into separate streams in backup selections wherever the directive occurs.
All file paths between directives belong to the same stream.
The start of the defines the end of previous the stream.
The last stream in the backup selection list is terminated by the end of the backup selection list.
Wildcard character
A regular expression that contains the wildcard character is used to match the NDMP backup selection for all volumes or folders present on the filer. However, regular expression matching cannot be used for files and is not supported for NDMP workloads.
If a filer has three volumes /VolumeA , /VolumeABC, and /VolumeDEF, and each volume contains folders with the name prefix Folder, then the following selections are valid:
/Volume* matches all the volumes that are prefixed with Volume that exist on the filer
/VolumeA/Folder* matches all the folders that are prefixed with Folder in VolumeA that exist on the filer
A regular expression that contains the wildcard character is used to match the NDMP backup selection for all volumes or folders present on the filer. However, regular expression matching cannot be used for files and is not supported for workloads.
If a filer has three volumes /VolumeA , /VolumeB, and /VolumeC, and each volume contains three folders Folder1, Folder2, and Folder3, then the following selections are valid:
/Volume? matches all the volumes present on the NDMP filer with prefix Volume that have any single character after that.
/VolumeA/Folder? matches all the folders with prefix Folder in VolumeA and have any single character after that.
A regular expression that contains the wildcard character is used to match the backup selection for alphanumeric pattern matching. A regular expression that contains the wildcard cannot be used for files and is not supported for workloads.
/fs[1-9] matches all paths that begin with the literal characters /fs and end with any single numeric character from 1 through 9.
For example, /fs1, /fs2, and so on up to /fs9 match the specified pattern /fs[1-9]. However, /fs0 and /fsa do not match the specified pattern.
/vol/ndmp[0-9] matches any volume name that begins with /vol/ndmp and ends with a single numeric character 0 through 9.
/vol/ndmp[0-9][0-9] matches any volume name that begins with /vol/ndmp and ends with the two-digit numeric characters 00 through 99.
/vol/ndmp[0-9][0-9][0-9] matches any volume name that begins with /vol/ndmp and ends with the three-digit numeric characters 000 through 999.
Pathname
/volumeA matches all of the files or folders in the VolumeA that present on the filer.
/volume/FolderA matches all of the files in the folderA that present on the filer.
/volume/FolderA/FileA matches the file FileA only that presents on the filer.
The reports actual data usage without overlap by calculating the accurate data size using the related backup files and policies. The following rules are applied to guarantee data size accuracy:
If the data size backed up by a policy with directive is greater than the sum of other policies, the data size of directive is counted.
If identical policies are taken, then the policy with the higher size is counted.
The uncounted policies are displayed with 0 data size in the report.
If the data size backed up by policy P1 is consumed in another policy, P2, then only the data size of policy P2 is counted.
If the data size is overlapped in multiple policies, then it is counted only once.
System administrators can use the following methods to verify the correctness of the data size that is reported by accurate licensing.
To verify the size of volumes with filer, log on to filer and run the following command:
volume show -fields size,used,available,percent-used.
Alternatively, the administrator can mount the volume of the filer (provided that the NFS protocol is enabled for that volume) on any UNIX-based client and run the following commands:
o du -sh o ls - lh
When backup agent fails to post licensing information to database, one of the following error messages is displayed in the activity monitor:
The message indicates that the backup agent is encountered an authorization issue, with a certificate expired or account password expired.
The message indicates that the backup agent is encountered a service offline issue, with the service NetBackup web console not running.
For more information, see the NetBackup Status Codes Reference Guide.