Veritas NetBackup™ Device Configuration Guide
- Introducing device configuration
- Section I. Operating systems
- AIX
- Before you begin configuring NetBackup on AIX
- RS/6000 AIX adapter number conventions
- About AIX persistent naming support
- About configuring robotic control device files in AIX
- About device files for SAN Clients on AIX
- About configuring tape drive device files in AIX
- About choosing a tape driver on AIX
- About non-QIC tape drives on AIX
- About extended-file marks for drives
- About fast-tape positioning (locate-block) on AIX
- About no rewind device files on AIX
- Creating AIX no rewind device files for tape drives
- Using multiple tape densities on AIX
- About SPC-2 SCSI reserve on AIX
- Disabling SPC-2 SCSI reserve in AIX
- About Sony AIT drives on AIX
- AIX command summary
- HP-UX
- Before you begin configuring NetBackup on HP-UX
- About robotic control on HP-UX
- About HP-UX device addressing schemes
- HP-UX tape drive device file requirements for NetBackup
- About device drivers and files for HP-UX persistent DSFs
- About configuring persistent DSFs
- About HP-UX legacy device drivers and files
- Creating device files for SAN Clients on HP-UX
- About configuring legacy device files
- About SPC-2 SCSI reserve on HP-UX
- Disabling SPC-2 SCSI reserve in HP-UX
- About disabling the HP-UX EMS Tape Device Monitor for a SAN
- HP-UX command summary
- Linux
- Before you begin on Linux
- About the required Linux SCSI drivers
- Verifying the Linux drivers
- About configuring robot and drive control for Linux
- Verifying the device configuration on Linux
- About SAN clients on Linux
- About SCSI persistent bindings for Linux
- About Emulex HBAs
- Utilities to test SCSI devices
- Linux command summary
- Solaris
- Before you begin on Solaris
- About the NetBackup sg driver
- Determining if the NetBackup sg driver is installed
- Special configuration for the Oracle StorEdge Network Foundation HBA driver
- About binding Fibre Channel HBA drivers
- Configuring Solaris 10 x86 for multiple drive paths
- Installing/reinstalling the sg and the st drivers
- Configuring 6 GB and larger SAS HBAs in Solaris
- Preventing Solaris driver unloading
- About Solaris robotic controls
- About Solaris tape drive device files
- Configuring Solaris SAN clients to recognize FT media servers
- Uninstalling the sg driver on Solaris
- Solaris command summary
- Windows
- AIX
- Section II. Robotic storage devices
- Robot overview
- Oracle StorageTek ACSLS robots
- About Oracle StorageTek ACSLS robots
- Sample ACSLS configurations
- Media requests for an ACS robot
- About configuring ACS drives
- Configuring shared ACS drives
- Adding tapes to ACS robots
- About removing tapes from ACS robots
- Robot inventory operations on ACS robots
- NetBackup robotic control, communication, and logging
- ACS robotic test utility
- Changing your ACS robotic configuration
- ACS configurations supported
- Oracle StorageTek ACSLS firewall configuration
- Device configuration examples
Upgrading NetBackup to use HP-UX persistent DSFs
Use the following procedure to configure an existing NetBackup environment to use persistent DSFs after you upgrade a media server to HP-UX 11i v3.
The following procedure also removes the legacy paths from the NetBackup device configuration. To save the legacy paths, you can use the NetBackup tpconfig utility to disable the old paths but retain them in the device configuration.
If you run the NetBackup Device Configuration Wizard before you perform this change, NetBackup adds the new DSF paths to the device configuration. However, the legacy paths remain configured as alternate paths.
To change a NetBackup media server to use the new DSFs
- Add the following entry to the /usr/openv/volmgr/vm.conf file (the syntax must be as specified in all capital letters):
AUTO_PATH_CORRECTION=YES
The AUTO_PATH_CORRECTION entry directs NetBackup to scan for device paths when the ltid device daemon starts.
- After adding the entry to the vm.conf file and with no current jobs running on the media server, run the following command:
/usr/openv/volmgr/bin/stopltid
- Wait a few minutes for the service to stop, then restart ltid by running the following command:
/usr/openv/volmgr/bin/ltid
Upon start-up, ltid scans for device paths, adds the new DSFs, and then purges the legacy DSFs from your NetBackup configuration for the media server.
After ltid starts, only the new persistent DSF paths should be configured in NetBackup.
- After the services are started and device paths updated, you can (but do not have to) remove the AUTO_PATH_CORRECTION=YES entry from the vm.conf file.