Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and usage reporting
- About NetBackup licensing models
- Tools for creating and viewing licensing reports
- Setting the licensing type for scheduled 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 Exchange agent
- NetBackup for NDMP agent
- NetBackup for Oracle server agent
- NetBackup for SQL Server agent
- NetBackup for VMware agent
- NetBackup for Hyper-V agent
- NetBackup for RHV agent
- NetBackup for Nutanix-AHV agent
- NAS-Data-Protection policy
- Cloud policy
- NetBackup for Kubernetes
- 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 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
- DELETE About reserving or releasing shared devices
- How to share robotic libraries without using the Shared Storage Option
- Shared Storage Option terms and concepts
- DELETE About the Shared Storage Option license
- About Shared Storage Option prerequisites
- About hardware configuration guidelines
- About installing and configuring drivers
- Verifying the connectivity
- DELETE 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
- 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
- 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
- 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)
- 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
Common configuration issues with Shared Storage Option
If you cannot obtain full functionality after you configure SSO, consider the following:
Verify that the SAN hardware uses current firmware or drivers. Hardware includes hubs, switches, HBAs, and bridges.
Verify that the JNI HBA failover value was set to zero to avoid I/O hangs. This value applies to bridges and HBAs.
Verify that the HBAs with the SCSI-3 protocols are compatible with the operating system drivers.
Verify that your cluster configuration is supported.
For more information about cluster configuration, see the NetBackup Release Notes, available at the following URL:
Verify that all of your Fibre Channel devices support your Fibre Channel topology. For example, in a switched fabric topology, ensure that all devices supported switched fabric.
Verify that Shared Storage Option is licensed on each server. To do so, select Help > License keys from the NetBackup Administration Console on each server. To enable the Shared Storage Option, enter the Shared Storage Option license on each server.
Verify that you configured Shared Storage Option from the master server. You must configure SSO from the master server not from a media server (or SAN media server).
Verify that you configured the same robot control host on every host. Remember that except for ACS robot types, only one host controls the robot.
Verify that you used the Device Configuration Wizard rather than the tpconfig utility to configure Shared Storage Option. The wizard coordinates configuration with all hosts that share the drives. The tpconfig utility may create inconsistent configurations.
Verify that you selected the appropriate device hosts in the Device Configuration Wizard , including the host with robotic control.
Fibre Channel connections to the drives and the robots cause increased complexity in a NetBackup device configuration. On some operating systems, SCSI-to-fibre bridges may result in inconsistencies in the device paths when you restart a host. After a restart of the host, the device configuration should be verified.
Verify that names across all systems that share the drives are consistent.
Test the drive paths on every media server.
Define NetBackup storage units for each media server. Do not select any available media server in the storage units.
Verify that you did not interrupt a data path during a backup. If you do, the NetBackup job fails. It can fail with media write errors or it may hang and have to be terminated manually.
Verify that you do not use Berkeley-style close on the tape path (UNIX or Linux servers only).
On Solaris systems, verify the following:
That you added tape configuration list entries in /kernel/drv/st.conf (if needed).
That you defined configuration entries for expanded targets and LUNs in sg.links and sg.conf files. If you see problems with the entries in the /etc/devlink.tab file (created from sg.links), verify the following:
The first entry uses hexadecimal notation for the target and LUN. The second entry uses decimal notation for the target and LUN.
Use a single tab character between the entries; do not use a space or a space and a tab character.
That you configured the operating system to force load the sg/st/fcaw drivers.
For more information, see the Solaris chapter of the NetBackup Device Configuration Guide, available at the following URL: