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
Before you begin configuring NetBackup on Windows
Observe the following points when performing the configurations described in this chapter:
Verify that NetBackup supports your server platform and devices. Download the NetBackup hardware and operating system compatibility lists:
For NetBackup to recognize and communicate with connected devices and for device discovery to discover devices, NetBackup issues SCSI pass-through commands to the devices in a configuration.
A tape driver must exist for each tape device. Attached devices appear in the registry.
Use the Microsoft Windows device applications to verify that the devices are configured correctly. The device applications available on your server may differ depending on your Windows operating system. Make sure that Windows detects the devices on the SAN before you configure the NetBackup Shared Storage Option.
If you have multiple devices connected to a fibre bridge, Windows may only see one LUN. This will normally be the device with the lowest-ordered LUN.
This limitation occurs because of the default install settings for the device driver for some fibre channel HBAs. See your vendor documentation to verify the settings.
Information about how to configure API robot control over a LAN is available
See the "ADIC Automated Media Library (AML)" topic in this guide.
See the "IBM Automated Tape Library (ATL)" topic in this guide.
See the "Sun StorageTek ACSLS robots" topic in this guide.
After configuring the hardware, add the drives and robots to NetBackup.