NAME

sam-remote, sam-clientd, sam-serverd - Describes the StorageTek SAM-Remote interface and daemons

SYNOPSIS

∕opt∕SUNWsamfs∕sbin∕sam-serverd mshmid pshmid equip

∕opt∕SUNWsamfs∕sbin∕sam-clientd mshmid pshmid equip

AVAILABILITY

SUNWsamfs

DESCRIPTION

The StorageTek SAM-Remote client and server software allows automated libraries to be shared among the Solaris systems in an Oracle HSM environment. StorageTek SAM-Remote allows you to configure multiple storage clients that archive and stage files from a centralized optical and∕or tape library. This environment also allows you to make multiple archive copies on various media housed in multiple libraries.

DAEMONS

The StorageTek SAM-Remote daemons, sam-serverd and sam-clientd, control StorageTek SAM-Remote. The sam-robotsd daemon starts the sam-serverd and sam-clientd daemons. The identifiers associated with these daemons are as follows:

mshmid

The identifier of the master shared memory segment created by sam-amld.

pshmid

The identifier of the preview shared memory segment created by sam-amld.

equip

The equipment number of the device.

For more information on the sam-robotsd or sam-amld daemons, see the sam-robotsd (1m) or sam-amld (1m) man pages.

CONFIGURATION

Configuring the StorageTek SAM-Remote client and server software involves adding lines to the mcf file on both the system to be used as the StorageTek SAM-Remote client and on the system to be used as the StorageTek SAM-Remote server.

In addition, a client configuration file must be created on the StorageTek SAM-Remote client, and a server configuration file must be created on the StorageTek SAM-Remote server.

Each entry in mcf file can configure up to ten clients per server. Use more mcf entries to configure more than ten clients.

In the mcf file, the Equipment Type field contains sc to define a StorageTek SAM-Remote client or ss to define a StorageTek SAM-Remote server.

The server configuration file defines the disk buffer characteristics and media to be used for each client. For a client named portland for example: portland media 100 at (000031|000032|000034|000035|000037|000038) endmedia The media definitions must be indented with white space or tab characters. The regex data must be enclosed by parentheses.

For a complete description of the StorageTek SAM-Remote configuration process, see the Oracle HSM Documentation Library.

FILES

mcf: The master configuration file for Oracle HSM, StorageTek QFS, the StorageTek SAM-Remote client, and the StorageTek SAM-Remote server.
∕opt∕SUNWsamfs∕lib∕librmtsam.so: The StorageTek SAM-Remote shared object library.