Filter
Top Products
ADIC/GRAU DAS and STK ACS Libraries
The ADIC/GRAU DAS Library Device
Chapter 14 663
• Before you configure a Data Protector ADIC/GRAU backup device,
you have to create/update the C:\DAS\ETC\CONFIG file on the DAS
server computer. In this file, a list of all DAS clients has to be defined.
For Data Protector, this means that each Data Protector client with
the DAS Media Agent installed has to be defined.
Each DAS client is identified with a unique client name (no spaces),
for example DATA_PROTECTOR_C1. In this example, the contents
of the C:\DAS\ETC\CONFIG file should look like this:
client client_name = DATA_PROTECTOR_C1,
# hostname = AMU,"client1"
ip_address = 19.18.17.15,
requests = complete,
options = (avc,dismount),
volumes = ((ALL)),
drives = ((ALL)),
inserts = ((ALL)),
ejects = ((ALL)),
scratchpools = ((ALL))
These names have to be configured on each Data Protector DAS
Media Agent client as the omnirc variable DAS_CLIENT. The omnirc
file is either the omnirc (on Windows) on the Data Protector home
directory or the .omnirc file (on UNIX). For example, on the system
with the IP address 19.18.17.15, the appropriate line in the omnirc
file is DAS_CLIENT=DATA_PROTECTOR_C1.
• You have to find out how your GRAU library slot allocation policy has
been configured, either statically and dynamically.
The static policy has a designated slot for each volser while the
dynamic allocation policy assigns the slots randomly. Depending on
the policy that has been set, however, you need to configure Data
Protector accordingly.
If the static allocation policy has been configured, you need to add the
following omnirc variable to your system controlling the robotics of
the library:
OB2_ACIEJECTTOTAL = 0