Please enter search query.
Search <book_title>...
Veritas NetBackup™ Device Configuration Guide
Last Published:
2018-02-16
Product(s):
NetBackup (8.1.1, 8.1)
- 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
Attaching devices to a Windows system
The following procedure describes a general method for attaching devices to a Windows computer. The Microsoft Windows device applications available on the server that you use in these steps may differ depending on your Windows operating system.
To attach devices to a Windows system
- Use the appropriate Windows application to obtain information on any currently attached SCSI devices.
- If you attach a new robotic library or drive to a NetBackup media server, follow the vendor's instructions for attaching the device.
Shut down the server and physically attach the supported device. Ensure that SCSI targets and termination settings are consistent with adapter card and peripheral vendor recommendations.
- Reboot the server and answer the prompts for adapter card peripheral configuration options. Watch the display to ensure that the adapter card recognizes the attached peripherals.
- If you add drives, install the tape drivers and use the appropriate Windows application to verify that the drive was recognized.