Veritas NetBackup™ Device Configuration Guide
- Introducing device configuration
- Section I. Operating systems
- 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 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
- Linux
- 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
Configuring a robot inventory filtering on ACS robots
If you want NetBackup to use only a subset of the volumes under ACS library control, you can filter the volume information from the library. To do so, you use the ACSLS administrative interface to assign the volumes you want to use to a scratch pool or pools. Then you configure NetBackup to use only the volumes in those scratch pools.
A NetBackup robot inventory includes the volumes that exist in the ACS scratch pool. The ACS library software moves each volume from the scratch pool after it is mounted.
A partial inventory also includes those volumes that NetBackup can validate exist in the robotic library, including volumes not in the ACS scratch pool. To prevent losing track of previously mounted volumes, the library reports the complete list of volumes that exist in the robotic library.
The following procedure is an example of how to configure an inventory filter.
To configure an inventory filter (example)
- Use the ACSLS administrative interface (ACSSA) command to create a scratch pool. Assign ID 4 and 0 to 500 as the range for the number of volumes, as follows:
ACSSA> define pool 0 500 4
- Use the ACSLS administrative interface (ACSSA) command to define the volumes in scratch pool 4:
ACSSA> set scratch 4 600000-999999
- On the NetBackup media server from which you invoke the inventory operation, add an INVENTORY_FILTER entry to the vm.conf file. The following is the usage statement:
INVENTORY_FILTER = ACS robot_number BY_ACS_POOL acs_scratch_pool1 [acs_scratch_pool2 ...]
The following define the options and arguments:
robot_number is the number of the robot in NetBackup.
acs_scratch_pool1 is the scratch pool ID as configured in the ACS library software.
acs_scratch_pool2 is a second scratch pool ID (up to 10 scratch pools are allowed).
For example, the following entry forces ACS robot number 0 to query scratch volumes from Oracle StorageTek pool IDs 4 and 5.
INVENTORY_FILTER = ACS 0 BY_ACS_POOL 4 5