grauaci - The ADIC/Grau Automated Tape Library through the
grauaci is the Sun QFS and SAM-QFS software interface to the
ADIC/Grau Network-attached library. This interface utilizes
the DAS/ACI 3.10E interface supplied by ADIC. For more
information on DAS/ACI, see the DAS/ACI 3.10E Interfacing
Guide and the DAS Administration Guide. Both manuals are
supplied by ADIC.
Sun assumes that your site has the DAS server configured and
operating with the ADIC/Grau library. In the DAS configura-
tion file for this client, the avc (avoid volume contention)
and the dismount parameters should both be set to true.
The Equipment Identifier field in the mcf file is the full
path name to a parameters file used by grauaci. This file
consists of a list of keyword = value pairs or a keyword
followed by a drivename = value pair. For more information
on the mcf file, see the mcf(4) man page.
All keywords and values, including the following, are case
sensitive and must be entered as shown:
client This is the name of this client as defined in the
DAS configuration file. This is a required param-
server This is the hostname of the server running the DAS
server code. This is a required parameter.
acidrive There is one acidrive line for every drive
assigned to this client. Following the acidrive
keyword is a drivename = path, string that is as
drivename The drive name as configured in the DAS
path The path name to the device. This name
must match the Equipment Identifier of
an entry in the mcf file.
Device and Network Interfaces grauaci(7)
If the library contains different media types, then there
must be a separate media changer for each of the media
types. Each media changer must have a unique client name in
the DAS configuration, a unique library catalog and a unique
The following example shows sample parameters files and mcf
entries for a ADIC/Grau library supporting DLT tape and HP
optical drives. The catalog files are placed in the default
directory, which is /var/opt/SUNWsamfs/catalog.
# This is file: /etc/opt/SUNWsamfs/gr50
client = grau50
server = DAS-server
# the name "drive1" is from the DAS configuration file
acidrive drive1 = /dev/rmt/0cbn # a comment
# the name "drive2" is from the DAS configuration file
acidrive drive2 = /dev/rmt/1cbn # a comment
# This is file: /etc/opt/SUNWsamfs/gr60
client = grau60
server = DAS-server
# the name "DH03" is from the DAS configuration file
acidrive DH03 = /dev/samst/c1t1u0
The mcf file entries.
# Sample mcf file entries for an ADIC/Grau library - DLT
/etc/opt/SUNWsamfs/gr50 50 gr gr50 - gr50cat
/dev/rmt/0cbn 51 lt gr50 - /dev/samst/c2t5u0
/dev/rmt/1cbn 52 lt gr50 - /dev/samst/c2t6u0
# Sample mcf file entries for an ADIC/Grau library - HP optical
/etc/opt/SUNWsamfs/gr60 60 gr gr60 - gr60cat
/dev/samst/c1t1u0 61 od gr60 -
The physical adding and removing of cartridges in an
ADIC/Grau network-attached library is accomplished using the
DAS utilities. The import(1M) and export(1M) commands
affect only the library catalog. Therefore, importing and
exporting cartridges with the ADIC/Grau network-attached
library consists of the following two-step process:
1) Physically import or export the cartridge using the DAS
2) Virtually update the automated library catalog using the
Sun QFS or SAM-QFS import and export utilities.
The import(1M) command has an optional -v parameter for sup-
plying the VSN to be added. The grauaci interface verifies
that DAS knows about the VSN before updating the catalog
with the new entry. The export(1M) command removes the
entry from the catalog. For more information on importing
and exporting, see the import and export(1M) man pages.
There are several methods for building a catalog for an
ADIC/Grau network-attached library. You should use the
method that best suits your system configuration, and this
is typically determined by the size of the catalog that is
Method 1: Create a catalog with existing VSN entries.
(Please note this method only works for tapes. It does not
work for barcoded optical media.) You can build a catalog
that contains entries for many tapes by using the
build_cat(1M) command. As input to build_cat(1M), you need
to create a file that contains the slot number, VSN, bar-
code, and media type. For example, file input_vsns follows:
0 TAPE01 TAPE01 lt
1 TAPE02 TAPE02 lt
2 TAPE03 TAPE03 lt
The input_vsns file can be used as input to the
build_cat(1M) command, as follows:
build_cat input_vsns /var/opt/SUNWsamfs/grau50cat
Method 2: Create a null catalog and import VSN entries.
You can create an empty catalog and populate it. To create
a catalog that will accommodate 1000 slots, use the
build_cat command, as follows:
build_cat -s 1000 /dev/null /var/opt/SUNWsamfs/catalog/grau50cat
Use the import(1M) command to add VSNs to this catalog, as
import -v TAPE01 50
For ADIC/Grau optical media, it is very important to import
the A side of barcoded optical media. The Sun QFS and SAM-
QFS software queries the ADIC/Grau database to find the bar-
code for the B side and fills in the catalog entry for the B
side appropriately. The A side of optical media in the
ADIC/Grau automated library is the left side of a slot as
you face the slots.
Method 3: Use the default catalog and import VSN entries.
If a catalog path name is not specified in the mcf file, a
default catalog is created in
/var/opt/SUNWsamfs/catalog/family_set_name when the Sun QFS
or SAM-QFS software is initialized. Following initializa-
tion, you must import VSN entries to this catalog. Use the
import(1M) command, as follows:
import -v TAPE01 50
In the preceding import(1M) command, 50 is the Equipment
Identifier of the automated library as specified in the mcf
mcf The configuration file for the Sun
QFS and SAM-QFS software.
The ACI library supplied by ADIC.
build_cat(1M), dump_cat(1M), export(1M), import(1M), sam-