Veritas NetBackup™ Device Configuration Guide
- Introducing device configuration
- Section I. Operating systems
- About configuring tape drive device files in AIX
- Creating AIX no rewind device files for tape drives
- About device drivers and files for HP-UX persistent DSFs
- About configuring persistent DSFs
- About HP-UX legacy device drivers and files
- About configuring legacy device files
- Creating legacy SCSI and FCP robotic controls on HP-UX
- About the required Linux SCSI drivers
- About configuring robot and drive control for Linux
- Installing/reinstalling the sg and the st drivers
- About Solaris robotic controls
- About Solaris tape drive device files
- Configuring Solaris SAN clients to recognize FT media servers
- Section II. Robotic storage devices
- Robot overview
- Oracle StorageTek ACSLS robots
- About removing tapes from ACS robots
- Robot inventory operations on ACS robots
- NetBackup robotic control, communication, and logging
- NetBackup robotic control, communication, and logging for UNIX systems
- ACS robotic test utility
- ACS configurations supported
- Device configuration examples
Upgrading NetBackup to use HP-UX persistent DSFs
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):
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:
- Wait a few minutes for the service to stop, then restart ltid by running the following command:
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.