NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and usage reporting
- About NetBackup licensing models
- Tools for creating and viewing licensing reports
- How capacity licensing works
- How NEVC licensing works
- Scheduling reports for capacity licensing
- Scheduling reports for traditional licensing
- Scheduling reports for NetBackup Enterprise Virtual Client (NEVC) licensing
- Other configuration for incremental reporting
- Troubleshooting failures for usage reporting and incremental reporting
- 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
- Data backed up by multiple policies
- BigData plug-ins for NetBackup
- NetBackup for DB2
- NetBackup for Enterprise Vault
- NetBackup for Exchange agent
- NetBackup for FlashBackup
- NetBackup for Hyper-V agent
- NetBackup for Informix
- NetBackup for Kubernetes
- NetBackup for Lotus Notes
- NetBackup for MariaDB Agent
- NetBackup for MySQL Agent
- NetBackup for NDMP agent
- NetBackup for Nutanix-AHV agent
- NetBackup for Oracle accurate licensing
- NetBackup for SharePoint
- NetBackup for SQL Server agent
- NetBackup for RHV agent
- NetBackup for SQLite Agent
- NetBackup for PostgreSQL Agent
- NetBackup for SAP HANA
- NetBackup for SAP MaxDB
- NetBackup for SAP Oracle
- NetBackup for Sybase
- NetBackup for VMware agent
- NAS-Data-Protection policy
- Cloud policy
- Windows file system backups
- UNIX file system backups
- Reconciling the capacity licensing report results
- Reviewing a traditional licensing report
- Reviewing an NEVC licensing report
- Using the NetBackup Storage API to get the total backup size information
- Additional configuration
- About multiple NetBackup primary servers
- About multiple media servers with one primary 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 in NetBackup versions 8.0 and earlier
- 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
- 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
- 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
- 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
- VERBOSE entry in vm.conf
- Example vm.conf file
- 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
- Index
How NetBackup uses host names
A major consideration is the extent to which you qualify host names. In many cases, the short host name of a computer is adequate. If the network environment contains multiple domains, qualify host names to the extent that servers and clients can identify each other in a multi-domain environment.
For example, use a name such as mercury.bdev.null.com or mercury.bdev rather than only mercury.
The following topics discuss how NetBackup stores and uses host names. These topics also address factors to consider when you choose host names.
Note:
(On Windows) Veritas recommends that you do not change the host name of a NetBackup server. You may need to import all previously used media to the server before you can use it under the new host name.
The following table discusses the topics that address how NetBackup stores and uses host names.
Table: How NetBackup stores and uses host names
Topic | Description |
|---|---|
Server and client names on UNIX servers and clients | On both UNIX servers and clients, the SERVER entries in the bp.conf file define the NetBackup servers that are allowed access. The first SERVER entry identifies the primary server. The first SERVER entry indicates the server to which client requests are made. For this reason, the SERVER name must be one by which all clients can connect to the server. If more than one SERVER entry exists, the additional entries identify other NetBackup servers that can initiate scheduled backups on the client. The bp.conf file must have multiple SERVER entries if you configure remote media servers. The NetBackup Request daemon (bprd) and NetBackup Database Manager daemon (bpdbm) do not run on any server other than a primary. When a client makes a list or restore request to the server, the NetBackup client name is used to determine whether to allow the operation. (The client name as specified on the client.) The client name that is used is usually the CLIENT_NAME from the bp.conf file of the client. Or, the client name can be the actual host name of the client if not in the bp.conf file. Alternate client restores can use the name that is specified through the user interface or with a parameter on the bprestore command. For a successful request, the client name must match the name that is specified for the client in the NetBackup configuration on the server. The only exception to this rule is if the server is configured to allow alternate client restores. |
Host names on Windows servers and PC clients | Windows NetBackup servers and clients also have SERVER and CLIENT_NAME settings. On these systems, specify server and client settings in the NetBackup web UI. |
Policy configuration | (On Windows) The configured name for a client is the host name as it's added to a policy. This name is how the client is identified in the NetBackup configuration. (On UNIX) The configured name for a client is the host name as it's added to a policy. This name is how the client is identified in the NetBackup configuration. NetBackup also adds a CLIENT_NAME entry to a UNIX client's bp.conf file when software is first installed on the client. The server uses the client's configured name to connect to the client and start the processes that satisfy client requests. Always use qualified host names to add clients to a policy so that all NetBackup servers can connect to the clients. When a client makes a user backup, archive, or restore request to the NetBackup server, the server uses the peer name of the client. The peer name (identified from its TCP connection) is used to determine the client's configured name. If you add a client to more than one policy, always use the same name in all cases. If the same name is not used, the client cannot view all the files that are backed up on its behalf. In this case, file restores become complicated because both user action and administrator action is required to restore from some of the backups. |
Image catalog | A subdirectory in the image catalog is created for a client when a backup is first created for that client. The subdirectory's name is the client's configured name. Every backup for a client has a separate file in this subdirectory. Each of these backup records contains the host name of the server on which the backup was written. |
Error catalog | NetBackup uses the entries in the error catalog for generating reports. These entries contain the host name of the server that generates the entry and the client's configured name, if applicable. The server host name is normally the server's short host name. (For example, servername instead of servername.null.com.) |
Catalog backup information |
If you include a media server's catalog files in the NetBackup catalog, qualify the host name of the media server in the file path. Qualified names are necessary because they allow the primary server to connect to the media server. |
Many NetBackup user-defined strings must not contain non-US ASCII characters, including the following:
Host name (primary server, media server, Enterprise Media Manager (EMM) server, volume database host, media host, client)
Policy name
Policy keyword (Windows only)
Backup, Archive, and Restore keyword (Windows only)
Storage unit name
Storage unit disk pathname (Windows only)
Robot name
Device name
Schedule name
Media ID
Volume group name
Volume pool name
Media description
Vault policy names
Vault report names
BMR Shared Resource Tree (SRT) name
nbcertcmd command