This chapter describes how to install and set up your OpenVault system. There are two types of OpenVault hosts: the server, with the media library manager (MLM), and remote hosts, with an LCP or DCP, but without the MLM.
Depending on which hosts have drives and libraries physically or logically connected, configurations fall into one of two categories:
Local configuration: all OpenVault-managed drives, libraries, and applications reside on the OpenVault server host.
Local-and-remote configuration: one or more libraries or drives (or both) reside on OpenVault hosts other than the OpenVault server host.
If you have already configured OpenVault and would like to change the configuration, see Chapter 4, “Administering OpenVault”.
See the Release Notes that come with your OpenVault IRIX product for a detailed list of supported drive types, libraries, and the different OS versions that are supported.
On SGI ProPack for Linux systems, see the documentation in /usr/share/doc/openvault-version.
This release of OpenVault supports barcoded tape media only. You must have at least one tape for each drive type; the norm is to load a tape in each available library slot.
Though not required, if you configure OpenVault using a graphics console, resizing and backward scrolling (in xwsh for example) can make setup easier.
You must have a license installed to run the OpenVault server software. Licensing tools must be installed beforehand on the OpenVault server system. IRIX 6.5 has the required License Tools.
To obtain a license, visit the Web site http://www.sgi.com/support/licensing/index.html, or send e-mail to [email protected], with a blank message, to obtain the license template. You may also use the FAX number, +1-650-920-0537, or this postal address:
SGI
1600 Amphitheatre Parkway
Mountain View, CA 94043
Attn: Software Licensing, MS 134
The OpenVault license you received includes instructions on how to install it.
On SGI ProPack for Linux systems, licensing tools are included with the base software.
On IRIX systems, when upgrading from OpenVault 1.4.x or earlier versions to OpenVault 1.5 or later versions, the administrator will notice that the location of OpenVault executables, configuration files, databases, and log files has changed. In OpenVault 1.4.x and earlier releases, all OpenVault files were stored in the /usr/OpenVault directory. In OpenVault 1.5 and later releases, OpenVault files are stored in the /usr/openvault directory and in the /var/opt/openvault directory. OpenVault logs, configuration files, and databases are stored in the /var/opt/openvault directory.
When installing the software to upgrade OpenVault 1.4.x or earlier to OpenVault 1.5 or later, existing OpenVault log, configuration, and database files are copied from /usr/OpenVault to their new location. The upgrade script may also modify some of the new files, to conform to what OpenVault 1.5 expects. The old files are left in /usr/OpenVault. After doing such an upgrade, you should verify that the installation completed successfully, that all necessary files were copied, and that OpenVault functions correctly. At that point, you may want to make a backup copy of /usr/OpenVault, and then remove /usr/OpenVault.
If you have not already installed OpenVault, you can install it using the inst command or the graphical Software Manager on IRIX systems or rpm on SGI ProPack for Linux systems.
For more information about IRIX install programs, see the appropriate man pages.
The default OpenVault product images include the following subsystems on IRIX systems:
OpenVault.sw.core OpenVault core servers
OpenVault.sw.admin OpenVault administrative tools
OpenVault.sw.config OpenVault configuration support scripts
OpenVault.sw.startstop OpenVault scripts for starting and stopping daemons
OpenVault.sw.user OpenVault end-user tools
OpenVault.upgrade OpenVault scripts for upgrades to existing
OpenVault installations
OpenVault.man.manpage OpenVault manual pages
OpenVault.man.relnotes OpenVault release notes
OpenVault.dcp.AIT1 OpenVault DCP for AIT-1 drive
OpenVault.dcp.AIT2 OpenVault DCP for AIT-2 drive
OpenVault.dcp.AIT3 OpenVault DCP for AIT-3 drive
OpenVault.dcp.DLT2000 OpenVault DCP for DLT2000 drive
OpenVault.dcp.DLT4000 OpenVault DCP for DLT4000 drive
OpenVault.dcp.DLT7000 OpenVault DCP for DLT7000 drive
OpenVault.dcp.DLT8000 OpenVault DCP for DLT8000 drive
OpenVault.dcp.IBM3590 OpenVault DCP for IBM 3590 Magstar drive
OpenVault.dcp.IBM3590E OpenVault DCP for IBM 3590E Magstar drive
OpenVault.dcp.SDLT320 OpenVault DCP for SDLT320 drives
OpenVault.dcp.STK9840 OpenVault DCP for STK 9840 and T9840B drives
OpenVault.dcp.STK9940 OpenVault DCP for STK T9940A drive
OpenVault.dcp.STK9940B OpenVault DCP for STK T9940B drive
OpenVault.dcp.SuperDLT1 OpenVault DCP for SuperDLT1 (SDLT220) drive
OpenVault.dcp.Ultrium1 OpenVault DCP for Seagate/IBM/HP LTO
Ultrium Generation 1 drive
OpenVault.dcp.STKredwood OpenVault DCP for STK SD-3 Redwood drive
OpenVault.dcp.STKtimberline OpenVault DCP for STK 9490 Timberline drive
OpenVault.dcp.pseudo OpenVault DCP for the "pseudo" drive
OpenVault.lcp.ADICDAS OpenVault LCP for ADIC DAS interface libraries
OpenVault.lcp.ADICSCSI OpenVault LCP for ADIC SCSI interface libraries
OpenVault.lcp.IBM3494 OpenVault LCP for IBM 3494 libraries
OpenVault.lcp.STK9700 OpenVault LCP for STK SCSI-attached 9700
series libraries
OpenVault.lcp.STKLseries OpenVault LCP for STK SCSI-attached L-series libraries
OpenVault.lcp.STKACSLS OpenVault LCP for STK ACSLS libraries
OpenVault.lcp.pseudo OpenVault LCP for the "pseudo" library
OpenVault.docs.adminguide OpenVault Administrative manual
OpenVault.docs.designdoc OpenVault design documentation
OpenVault.dev.include OpenVault include headers for writing applications
OpenVault.dev.examples OpenVault example application code
OpenVault.dev.libs OpenVault LCP/DCP development libraries |
On SGI ProPack for Linux systems, all of the server software, administrative and user tools, and supported LCPs and DCPs and man pages are included in the openvault-sw package.
Figure 2-1 shows an OpenVault local-only configuration.
This shows the OpenVault IRIX server named ursa, controlling two libraries: an STK-9730, connected at device address /dev/scsi/sc2d3l0, and an STK-9710, connected at device address /dev/scsi/sc3d1l0.
The STK-9730 at /dev/scsi/sc2d3l0 contains two drives:
DLT-7000 at /dev/rmt/tps2d1, physically located as the bottom drive in the library.
DLT-7000 at /dev/rmt/tps2d2, physically located as the top drive in the library.
The STK-9710 at /dev/scsi/sc3d1l0 contains two drives:
DLT-7000 at /dev/rmt/tps3d2, physically located as the bottom drive in the library.
DLT-7000 at /dev/rmt/tps3d3, physically located as the top drive in the library.
Figure 2-2 shows an OpenVault local-and-remote configuration.
In Figure 2-2, ursa is the designated IRIX OpenVault server host, with four libraries:
STK-9730 connected at device address /dev/scsi/sc2d3l0
STK-9710 connected at device address /dev/scsi/sc3d1l0
IBM 3494 connected via an IBM library server running on the host, tsm-ps2
StorageTek WolfCreek silo connected via the ACSLS server host, tsm-sun
The STK-9730 on ursa has the following drives, both of which are connected to the host:
DLT-7000 at /dev/rmt/tps2d1, physically located as the bottom drive in the library.
DLT-7000 connected at address /dev/rmt/tps2d2, physically located as the top drive.
The STK-9710 on ursa has the following drives, both of which are connected to the host:
DLT-7000 at /dev/rmt/tps3d2, physically located as the bottom drive in the library.
DLT-7000 at /dev/rmt/tps3d3, physically located as the top drive.
The IBM 3494 on host ursa has the following drive, connected to the host ursa:
IBM-3590 at /dev/rmt/tps4d6, identified by the IBM Library Server as drive 0
The StorageTek ACSLS-controlled WolfCreek silo has the following drives, all of which are connected to vega, not ursa:
STK-RedWood at /dev/rmt/tps3d1, located physically in LSM 2, Panel 3, as Drive 1
STK-RedWood at /dev/rmt/tps3d3, located physically in LSM 2, Panel 3, as Drive 3
STK-TimberLine at /dev/rmt/tps3d2, located physically in LSM 2, Panel 1, as Drive 1
STK-TimberLine at /dev/rmt/tps3d4, located physically in LSM 2, Panel 1, as Drive 3
Host vega is an OpenVault IRIX client host with one library: STK-9714 connected at device address /dev/scsi/sc7d1l0. The STK-9714 has the following drives, both of which are connected to vega:
DLT-7000 at /dev/rmt/tps7d3, located physically as the bottom drive in the library.
DLT-7000 at /dev/rmt/tps7d2, located physically as the top drive.
Notice that vega has two STK-RedWood drives and two STK-TimberLine drives connected to it, but the library in which these drives reside is not connected to vega.
On SGI ProPack for Linux systems, tape device pathnames have the same format as on IRIX systems (for example, /dev/rmt/tps11d3), but the corresponding SCSI device pathnames use an entirely different format. On SGI ProPack for Linux, SCSI device pathnames reside in subdirectories of /dev/xscsi, and have basenames of ds (for example, /dev/xscsi/pci00.01.0-1/target0/lun0/ds and /dev/xscsi/pci01.00.0/node500104f0004256bb/port1/lun0/ds.)
The general strategy for configuring OpenVault is shown in Table 2-1. The OpenVault configuration tool (ov_admin) allows you to perform many of these steps. The details of each step are explained in the rest of this chapter. Some steps may not be relevant to your specific installation:
Table 2-1. OpenVault Configuration Roadmap
1. | Prepare OpenVault hosts and devices. Install OpenVault license. Collect information and complete worksheets. | This step is required for all OpenVault hosts. |
2. | Configure OpenVault core on the OpenVault server host. | This required step must be performed on the OpenVault server host. |
3. | Configure drives attached to the OpenVault server host. | This step is required for drives connected to the OpenVault server host, and must be performed on the OpenVault server host. |
4. | Configure libraries attached to the OpenVault server host. | This step is required for libraries connected to the OpenVault server host, and must be performed on the OpenVault server host. |
5. | Enable applications on OpenVault server. | This step is required for any applications. |
6. | Enable drives and libraries attached to remote OpenVault client hosts. | If you have remote libraries and drives, perform this step on the server host. |
7. | Enable applications to run on remote OpenVault client hosts. | If you have applications running on remote hosts that request services from OpenVault, perform this step on the server host. |
8. | Configure drives attached to OpenVault client hosts. | If you have drives attached to remote OpenVault client host(s), perform this step on the remote host(s). |
9. | Configure libraries attached to OpenVault client hosts. | If you have libraries attached to remote OpenVault client host(s), perform this step on the remote host(s). |
10. | Import media into OpenVault. | After configuring all libraries, perform this step on the OpenVault server host. |
11. | Custom installation. | If desired. |
This section explains how to prepare OpenVault managed devices for configuration. All drives you configure must be housed in a library, because OpenVault cannot manage standalone drives (that is, drives not housed in a robotic library). Procedure 2-1 describes the steps as preparation before configuring your OpenVault devices and hosts.
Procedure 2-1. Pre-Configuration Preparations
In this procedure, step 4 is required only if you are configuring a IBM 3494 library, and step 5 only if you are configuring a DAS library.
Cable all SCSI drives to appropriate hosts. Always ensure proper SCSI termination.
Cable all SCSI libraries to appropriate hosts.
For each host with an OpenVault controlled drive attached to it, run the following commands as root:
# killall mediad # chkconfig mediad off
Note: The mediad daemon interferes with OpenVault operation; so it is essential that you prevent mediad from accessing OpenVault drives. Refer to the mediad(1M) man page for information on how to prevent mediad from accessing drives. Prepare the IBM 3494 libraries that you are planning to configure:
Note: The IBM-3494 LCP is not currently supported on SGI ProPack for Linux systems. Enable communication between the LCP host and the IBM 3494 server. The IBM 3494 library server runs on the PS/2 system located at the rear of the library. From the graphical administration interface for the library server available on the PS/2, inform the library server of the OpenVault host that will run the LCP for the IBM 3494. Refer to the IBM 3494 Library server documentation for details on how to do this.
On the OpenVault host that will run the LCP for the IBM 3494, prepare the /etc/ibmatl.conf file. If this file does not exist, you must create it. Briefly, this file contains three fields:
libraryname PS/2 hostname LCPhostname
Here libraryname can be any name not already in this file. The PS/2 hostname is the hostname or IP address of the PS/2 system that is running the IBM 3494 library server. The LCPhostname is the hostname of the machine that will run the LCP for the IBM 3494. Refer to the IBM 3494 documentation for details about the /etc/ibmatl.conf file.
Caution: It is critical that you remember libraryname, which is also the OpenVault name for this library. As root, start lmcpd on the IBM 3494 LCP host.
On IRIX systems:
# cd /usr/openvault/clients/lcp/IBM-3494 # ./lmcpd
Prepare the DAS PS/2 system for any ADIC DAS or EMASS Grau library you plan to configure.
Use the following worksheets as an aid to collecting information that is required for configuring an OpenVault system.
Note the vendor, product, and serial number for each drive as you fill out the following worksheets.
Fill out Figure 2-3 with OpenVault server client host information.
Fill out Table 2-2 through Table 2-4 for any ADIC DAS or EMASS GAU libraries that you are configuring.
Table 2-2. Library Worksheets (DAS): Worksheet 1
Item | Value |
Library Device Path | |
DAS Server | |
DAS Client Name | |
Number of Export Areas | |
Number of Import Areas | |
OpenVault Name for Library |
Table 2-3. Library Worksheets (DAS): Worksheet 2
Import Area Name | Open Vault Name |
|
|
|
|
|
|
|
|
Export Area Name | OpenVault Name |
|
|
|
|
|
|
|
|
Fill out the following worksheet for drives in the DAS library:
Fill out Figure 2-4 for drives in a SCSI library.
Fill out Figure 2-5 for drives in an IBM 3494 library.
Fill out Figure 2-6 for drives in an ACSLS library.
Fill out Figure 2-7 and Figure 2-8 for each SCSI library.
Fill out Figure 2-9 and Figure 2-10 for each IBM 3494 library.
Fill out Figure 2-11 and Figure 2-12 for each ACSLS library.
Follow the order outlined to record information on the worksheets:
Acquire the names of the OpenVault server and client hosts. See Figure 2-3.
Generate unique names of the libraries. See Figure 2-7 through Figure 2-11.
Collect information about the attached drives. See Figure 2-4 through Figure 2-6.
Collect information for SCSI-attached libraries. See Figure 2-7 and Figure 2-8.
Collect information for IBM 3494 libraries. See Figure 2-9 and Figure 2-10.
Collect information for ACSLS libraries. See Figure 2-11 and Figure 2-12.
Collect information for ADIC DAS or EMASS Grau libraries. See Table 2-2, Table 2-3, and Table 2-4.
You need to identify all hosts that form your OpenVault system. Identify only one host as the OpenVault server host.
In addition, you need to identify OpenVault client hosts, other than the OpenVault server host. These include any host on which you plan to configure a DCP, LCP, application, or OpenVault administrative commands. Wherever hostnames are required, use the exact output of the hostname command.
Generate unique names for all OpenVault managed libraries. You may choose any naming scheme that suits your site, provided the names remain unique. If you prepared an IBM 3494 as described earlier, you must generate a library name, which must become the OpenVault name.
Determine which drives are attached to each host. On SGI IRIX and Linux systems, you can use the ov_scandev command, which is part of OpenVault. Alternatively, on IRIX systems, you can use the hinv command. Example 2-1 shows the drives in the configuration in Figure 2-2.
Example 2-1. Identifying Drives
The following drives are on hosts ursa and vega:
ursa# hinv | grep Tape Tape drive: unit 1 on SCSI controller 2: DLT Tape drive: unit 2 on SCSI controller 2: DLT Tape drive: unit 2 on SCSI controller 3: DLT Tape drive: unit 3 on SCSI controller 3: DLT Tape drive: unit 6 on SCSI controller 4: IBM Magstar 3590 vega# hinv | grep Tape Tape drive: unit 1 on SCSI controller 3: STK SD3 Tape drive: unit 2 on SCSI controller 3: STK 9490 Tape drive: unit 3 on SCSI controller 3: STK SD3 Tape drive: unit 4 on SCSI controller 3: STK 9490 Tape drive: unit 2 on SCSI controller 7: DLT Tape drive: unit 3 on SCSI controller 7: DLT |
For each OpenVault-managed drive in an OpenVault library, follow these steps in Procedure 2-2:
Procedure 2-2. Collecting Drive Information
Determine to which OpenVault host the drive is physically cabled. Record this information in the drive worksheet. It may be necessary to follow SCSI cabling in order to determine this.
Determine the device path. You can use the ov_scandev command, which is part of OpenVault. See the man page for more information. On IRIX systems, you can also use the hinv command.
The ov_scandev command provides you with drive serial numbers, which can be helpful in resolving path names. Alternatively, you could insert a tape into the drive, unload all other drives that are on the same SCSI bus as this drive, and issue an mt status command.
For example, to determine this information for one of the two STK-SD3 (STK-RedWood) drives connected to vega, insert a cartridge into drive in question, unload the other drives on SCSI controller 3, and issue mt -f /dev/rmt/tps3d1 status and mt -f /dev/rmt/tps3d3 status commands. By process of elimination, you arrive at the required information.
Record the name of the library in which the device is physically housed.
Generate a unique name for this drive and record this name.
Record the physical location of drives in the library. For example, in SCSI libraries it is typical to find drives ordered in a linear fashion, either vertically or horizontally as viewed from the front of the library.
For SCSI libraries, a scheme that describes the location of the drive in relation to the topology of the other drives in the library might suffice. For example, “second drive from bottom” or “third drive from left” are descriptive terms. Typically, StorageTek SCSI libraries order drives from the bottom, EXABYTE SCSI libraries order drives from the top, while some SpectraLogic libraries order drives from left to right.
For drives in an ACSLS controlled robot, a physical description is not appropriate. You need to query ACSLS for more information. A summary of how you can do this is shown below. Refer to the ACSLS administration guide for details.
Log in to the ACSLS server with login acsss.
Run the command cmd_proc.
Issue the command query drive all.
Record the LSM ID, the Panel ID, and the drive # for the relevant drive(s).
ACSSA query drive all 08-28-98 04:49:16 Drive Status Identifier State Status Volume Type 0, 2, 1, 1 online available 9490 0, 2, 1, 3 online available 9490 0, 2, 3, 1 online available SD3 0, 2, 3, 3 online available SD3
The comma-separated tokens are the ACS ID, the LSM ID, the panel ID, and the drive number, respectively.
For drives in an IBM 3494 library, a physical description is also not appropriate. You need to query the IBM 3494 server for more information. A summary of how to do this is shown below. Refer to the IBM 3494 documentation for details.
Note: The IBM-3494 LCP is not currently supported on SGI ProPack for Linux systems. Prepare the OpenVault host to run the LCP for the IBM 3494 as described in “Collecting Information for IBM 3494 Libraries”. As root on IRIX systems, enter these commands:
# cd /usr/openvault/clients/lcp/IBM-3494 # ./mtlib -l libraryname -D
Here libraryname is the name that you generated earlier (in Procedure 2-1) when you prepared the /etc/ibmatl.conf file.
With the configuration in Figure 2-2, the first output field of this mtlib command is a drive number; refer to the IBM 3494 documentation concerning how to map drive numbers to physical locations:
ursa 9# ./mtlib -l ibm3494 -D 0, 00141700 003590B1A00
Record the drive number and physical location in the appropriate worksheets.
For drives in an ADIC DAS or EMASS Grau library, determine locality information similarly.
Follow the steps in Procedure 2-3 to obtain information for SCSI-Attached libraries.
Procedure 2-3. Collecting SCSI-Attached Libary Information
Record the device control path. The ov_scandev command, which is part of OpenVault, can be used to find this information. See the man page for details. Alternatively, on IRIX systems, you can use the hinv command to determine connected SCSI libraries, and use the output of hinv with the scsicontrol command to determine the type of each attached SCSI library, as follows:
# hinv | grep Juke | \ awk '/Juke/ {printf "/dev/scsi/sc%dd%dl0\n", $7, $3}' | \ xargs /usr/sbin/scsicontrol -i /dev/scsi/sc2d3l0: Jukebox STK 9730 1300 /dev/scsi/sc3d1l0: Jukebox STK 9710 1805For each jukebox that hinv displays, issue a scsicontrol inquire command in the following form, where X is the controller number from the hinv output and Y is the unit number from the hinv output:
# scsicontrol -i /dev/scsi/scXdYl0
Repeat the previous step on every host with an OpenVault-controlled SCSI library.
Gather information about drives contained in libraries. For each SCSI library, enter these commands, where LCPtype is the LCP name, for example STK9700:
On IRIX systems:
# cd /usr/openvault/clients/lcp/LCPtype # ./LCP* getlibinfo/lcpcontrolpath| grep DRIVE
On SGI ProPack for Linux systems:
# cd /opt/openvault/clients/lcp/LCPtype # ./LCP* getlibinfo/lcpcontrolpath | grep DRIVE
Here lcpcontrolpath is the /dev/scsi (or /dev/xscsi on SGI ProPack for Linux systems) control path as described in the first step. In the sample local-only configuration on host ursa (shown in Figure 2-2), enter the following commands for the STK-9730 library:
ursa# cd /usr/openvault/clients/lcp/STK9700 ursa# ./LCP* getlibinfo /dev/scsi/sc2d3l0 | grep DRIVE DRIVE 1030 - - first_drive_from_BOTTOM DRIVE 1031 - - second_drive_from_BOTTOM
Use the output information to complete worksheets for SCSI-attached libraries.
Use Procedure 2-4 to collect information for IBM 3494 libraries.
Procedure 2-4. Collecting IBM 3494 Library Information
Record the hostname of the PS/2 system that is running the IBM 3494 server.
Record the drive information. The method for determining drive information is described in “Collecting Information for Attached Drives”.
Use Procedure 2-5 to collect information for ACSLS libraries.
Procedure 2-5. Collecting ACSLS Library Information
Record the hostname of the system running the ACSLS server.
Record the ACS ID of the ACSLS server that you plan to use. Refer to the documentation for the ACSLS server on how to obtain this ID.
Determine the packet version for ACSLS. The packet version is 1 less than the major version number of ACSLS running on the ACSLS server. For example, if you are running ACSLS version 5.1, use 4 as the packet version.
Record the drive information. The method for determining drive information is described in “Collecting Information for Attached Drives”.
Chapter 3, “Cartridge Life Cycle”, introduces the notion of cartridge and drive groups. The OpenVault ov_admin script initially creates one cartridge group named carts, and one drive group named drives.
All media that you import by means of the initial configuration procedure are by default introduced into the carts cartridge group. If you would like to create more cartridge groups, to allow importing different media into different cartridge groups, you may do so by following the instructions provided in Chapter 6, “Reconfiguring OpenVault”. At initial configuration time, be sure to answer no when asked if you want to “Import Media.” The Import Media option is available as part of reconfiguration procedures--after creating the desired cartridge groups, you may import media.
As with cartridge groups, at initial configuration time all drives are introduced into the drives drive group. You may choose to add new drive groups and move drives from one drive group to another at a later time by following instructions provided in Chapter 6, “Reconfiguring OpenVault”.
| Note: When adding new cartridge and drive groups, remember to enable appropriate applications to use these cartridge groups and drive groups. |
If your site requires security, it is recommended that you create an OpenVault password. The ov_admin script asks you to enter an OpenVault password, for authentication of initially configured applications, drives, and libraries. If you want individual libraries, drives, or applications to use passwords other than the default password that you enter during initial setup, see the instructions in the Chapter 6, “Reconfiguring OpenVault”.
The OpenVault setup procedure requires you to identify and provide OpenVault names for libraries and drives, each of which must have a unique OpenVault name. The ov_admin script asks you to enter these names in one or more places. It is important that you enter all OpenVault drive and library names consistently and correctly. The configuration worksheets can help you do this.
If a library or drive is connected to the OpenVault server host, the OpenVault ov_admin script requests the OpenVault name for that physical library or drive. The script offers a generated name as default, which you may override by entering a name you select.
If a library or drive is connected to a remote OpenVault client host, the OpenVault ov_admin script requests an OpenVault name for that physical library/drive in these places:
When you configure the OpenVault server host, you must enable each library/drive by providing its OpenVault name. At such time you have the choice of accepting a name generated by the ov_admin script, or entering a name you select.
When you actually configure the library/drive on the OpenVault client host, the script asks you for the OpenVault library/drive name that you entered when you enabled the library/drive on the OpenVault server host.
Be sure to enter the same OpenVault library or drive name in both places!
| Note: It is possible that drives are connected to remote OpenVault clients, but housed in a library connected to the OpenVault server host. In this case, configuration of the library requires entry of all drive names; the ov_admin script cannot offer defaults. If you wrote drive names for this library on your worksheet, then enter those existing names. If you did not write drive names on your worksheet, you must create them. Be sure to record drive names and enter them exactly later in the configuration process. |
Regardless of where a drive is connected, at the time of configuring the library in which a drive is housed, you are asked to enter the OpenVault name of the drive. Be certain to enter the same OpenVault drive name in all three places!
Procedure 2-6 describes the steps required to configure the OpenVault server, following the “Configuration Roadmap”. Depending on the specific configuration at your site, some questions might not apply.
Procedure 2-6. Configuring the Server
You must configure the OpenVault server before any of its components.
Log in to the designated OpenVault server as root.
Ensure that the OpenVault license is installed in the proper file. On IRIX systems, it should be installed in the /var/flexlm/license.dat file. On SGI ProPack for Linux systems, it should be installed in the /etc/flexlm/license.dat file.
Execute the ov_admin script:
# /usr/sbin/ov_admin
The ov_admin script is the main OpenVault configuration tool. It sets up OpenVault based on installed hardware and software, and your input to various questions. If you do not see a choice you want, double check your installation to make sure the items are installed. Where possible, the ov_admin script presents a default, indicated by “[value]:” at the end of line. You may accept this default by pressing the Enter key. Help is available at many prompts by entering a question mark (?).
The ov_admin script goes through the following steps in setting the OpenVault server port:
The script starts by asking for the name of the OpenVault server:
What is the name of the OpenVault Server? [ursa]
Your answer informs ov_admin whether it is executing on the OpenVault server or not. Press Enter if you are configuring the OpenVault server host.
If the OpenVault server is not yet configured, the script asks:
The OpenVault server is not yet configured; would you like to do so now?[Yes]
The script continues:
What port number is OpenVault using? [44444]
The default port number for OpenVault communications is 44444. Press Enter if this is acceptable.
If another application uses port number 44444, or if you prefer to select a different port, enter that port number. Make sure that no other application uses this port on the OpenVault server host.
The script continues:
What default security key would you like to use? [none]
The OpenVault server, LCPs, DCPs, and applications are by default configured without a security key, implying no security. If you enter a security key, the OpenVault server uses it to authenticate new connections from a client (an LCP, DCP, or application). If you have already selected a security key (password), enter it now.
You may choose to configure OpenVault initially without security, which simplifies setup. Later, you can establish OpenVault security passwords by following steps in Chapter 6, “Reconfiguring OpenVault”.
Note: If you have remote OpenVault client hosts, you are prompted for the security key value at the time of configuring remote OpenVault client hosts. It is imperative that you enter the same value that you chose while configuring the OpenVault server. Failure to do so prevents successful configuration of the OpenVault client host. If the configuration was successful, the ov_admin script displays:
The OpenVault server was successfully started.
At this point, the following items have been configured:
The OpenVault core including its catalog and an ovroot process is ready to service connections from OpenVault clients.
A default cartridge group has been created named carts.
A default drive group has been created named drives.
The user mounting application ov_umsh has been enabled on the OpenVault server (this host); see the ov_umsh(1M) man page for information.
The ov_umsh application is eligible to use cartridges in the carts cartridge group, and drives in the drives drive group.
The ov_admin script presents the OpenVault Configuration Menu:
OpenVault Configuration Menu Configuration on Machines Running LCPs and DCPs 1 - Manage LCPs for locally attached Libraries 2 - Manage DCPs for locally attached Drives Configuration on Admin-Enabled Machines 11 - Manage Cartridge Groups 12 - Manage Drive Groups 13 - Import Media Configuration on the OpenVault Server Machine 21 - Manage remote Libraries and LCPs 22 - Manage remote Drives and DCPs 23 - Manage Applications and Admin CLI Tools q - Exit. Which operation would you like to do:
It is recommended that you choose option 2 to proceed with configuration of locally attached drives at this time.
The OpenVault ov_admin script scans hardware to determine which SCSI tape drives are attached to this host. The following menu is displayed when you run the ov_admin script:
OpenVault DCP Configuration Menu
1 - Create a new DCP
r - Return to Main Menu.
q - Exit.
Which operation would you like to do: |
Choose option 1 to proceed.
The OpenVault ov_admin script scans the hardware to determine which SCSI tape drives are attached to this host.
If any drives are present, they are presented for configuration, as in the following example:
OpenVault -- DCP Creation Menu 1 - /dev/rmt/tps4d2 2 - /dev/rmt/tps4d3 3 - /dev/rmt/tps3d2 4 - /dev/rmt/tps3d3 r - Return to Previous Menu. q - Exit. For which Drive would you like to add a DCP:
Check the drive worksheets that you created in “Preparing OpenVault Devices and Hosts”. Choose a drive for which you would like to add a DCP. You can use the following criteria to determine which drive to choose:
It matches one of the “Device Drive Pathnames” on the worksheet and “Hostname Drive is Connected to” is equal to the current hostname.
You need to configure this drive at this time.
The ov_admin script then issues a series of prompts:
Enter a name for the device, or <enter> to use the default name [tape1]
The value entered here is the OpenVault name for the drive. See “Naming Libraries and Drives” for details. The script then prompts:
What instance name would you like to give to this DCP? [[email protected]]
The instance name can be any string. It is used to differentiate between two DCPs that are controlling the same drive. The script then prompts:
What security key would you like to give to this DCP? [none]
The script then prompts:
What polling interval would you like this DCP to use? [30]
The DCP needs to check the status of the drive periodically when the drive is not in use. The "polling interval" is the number of seconds between each of those status checks. The script then prompts:
What directory should hold handles for this DCP? [/var/opt/openvault/clients/handles]
The DCP will be creating and deleting handles which are character special files that applications use to access the drive. The DCP needs a directory where it can store those handles. That directory can be shared with other DCPs but not with anything else.
The configuration parameters you have entered are displayed, and you are asked:
Create the DCP now? [Yes]
If you answer no, you can re-enter the configuration options. If you answer yes, and the DCP could be created, ov_admin displays the following message:
DCP successfully created The following Drive Groups currently exist: drives What Drive Group do you want to use (or create)? [drives]
Press Enter to choose the default, or enter the name of an existing drive group, or enter the name of a drive group to be created. If you enter the name of a drive group to be created, you will be prompted for more information about it. If the DCP was successfully created, the script displays the results, as in the following example:
Drive name : tape1 DCP name : [email protected] DCP type : DLT7000 OpenVault Server host name : ursa OpenVault Server port number: 44444 Security key : none DCP polling interval : 30 Handle creation directory : /var/opt/openvault/clients/handles Drive access path : /dev/rmt/tps2d1 Direct SCSI access path : /dev/scsi/sc2d1l0
At this point, the following items have been configured:
The named drive entry has been added to the OpenVault catalog, and the drive has been added to the specified drives drive group.
An authentication entry has been added to the /var/opt/openvault/server/config/core_keys file.
The drive's configuration file has been created (/var/opt/openvault/clients/dcp/dname/instname/config, where dname is the name chosen for this drive and instname is the instance name chosen).
To configure locally attached libraries, choose option 1 from the OpenVault Configuration Menu. This includes SCSI-attached libraries and network-attached libraries that you wish to configure. The ov_admin script prompts you:
OpenVault LCP Configuration Menu
1 - Create a new SCSI LCP
2 - Create a new network LCP
r - Return to Main Menu.
q - Exit. |
This section describes how to configure SCSI libraries.
Choose option 1 from the menu above. The ov_admin script then examines the hardware for attached libraries, and presents a list of SCSI-Attached libraries, as in this example:
OpenVault -- SCSI LCP Creation Menu 1 - /dev/scsi/sc4d3l0 2 - /dev/scsi/sc3d1l0 r - Return to Previous Menu. q - Exit. For which SCSI library would you like to add a LCP:
This prompt offers you the choice of configuring the library(s) at the address(es) shown. Choose the library you want to configure, based on the SCSI library worksheets that you created in “Preparing OpenVault Devices and Hosts”. The ov_admin script then prompts:
Enter a name for the device, or <enter> to use the default name [lib1]
The name entered here is the OpenVault name for the drive. See “Naming Libraries and Drives” for details.
The following prompt appears:
What instance name would you like to give to this LCP? [[email protected]]
The name can be any string. It is used to differentiate between two LCPs that are controlling the same library.
The following prompts appear:
What security key would you like to give to this LCP? [none]
What polling interval would you like this LCP to use? [30]
The LCP needs to check the status of the library occasionally. The "polling interval" is the number of seconds between each of those status checks.
The ov_admin script then displays a message similar to this one:
Configuring STK-9700 at /dev/scsi/sc4d3l0 to be "lib1"
This is followed by a prompt, similar to this one:
What is the default shape of the slots in the library? [DLT]
The ov_slottype command can be used to list the allowable slot types. The ov_admin script now prompts you to configure all of the drives contained in the library. The script queries the device to determine information about drives housed in this library. This device query might take some time, especially if the host has just been rebooted, if the device has just been power-cycled, or if the main door to the library has just been closed.
At this point, you see output similar to the following, repeated for each drive:
For the drive at location dlocation, enter a drive name for the element address daddr
dlocation is a text description of the drive's location, and daddr is the drive's “slot” address (the slot number that the SCSI robot uses to address the drive).
You must enter the OpenVault name for the drive at the given physical location within the SCSI library.
Refer to the SCSI library worksheet for this library to determine the OpenVault name of this drive.
You need to match the description string dlocation with the column labeled “Description of Drive's Physical Location within Library.” Although your description may not exactly match the description provided by the ov_admin script, choose the one that has the same meaning.
Tip: It is critical to the proper functioning of OpenVault that all drive names match up. If you have not already recorded a drive name on your worksheet, enter the correct name now. If you are running ov_admin in a scrolling window, scroll up to where you configured this drive, and use the name that was entered there. The daddr (the drive's slot address) is offered as a guide to the expert user. If you are familiar with the SCSI library's addressing scheme, you may choose to use this as an unambiguous reference to the drive's physical location within the library.
If you do not want OpenVault to manage this drive, press Enter.
The ov_admin script bypasses configuring the drive into the library; so OpenVault never mounts into this drive.
Note: If this drive is connected to a remote OpenVault client system, enter the name from your worksheet to configure this drive. If you have not yet recorded a name for this drive, select a unique drive name to enter at the prompt, and record this name on the worksheet. You will be required to enter this name when you later configure drives on the remote OpenVault client system to which the drive is attached.
After you enter the names or bypass, output similar to the following is displayed:
LCP Configuration Parameters: Library name : lib1 LCP name : [email protected] LCP type : STK-9700 OpenVault Server host name : ursa OpenVault Server port number: 44444 Security key : none LCP polling interval : 30 Number of drives : 2 Direct SCSI access path : /dev/scsi/sc2d3l0 Default cartridge shape : DLT Drives in the Library Drive Name Drive Address ---------- ------------- drive1 500 drive2 501 Create the LCP now? [Yes]The final line prompts you for confirmation:
If you are satisfied with the SCSI library configuration summary shown above, enter Y.
If you want to change one or more parameters, enter N and you can change the values.
Upon confirmation, the ov_admin script proceeds to configure the SCSI library:
LCP successfully created
At this point, the following items have been configured:
The named library entry has been added to the OpenVault catalog.
An authentication entry has been added to the /var/opt/openvault/server/config/core_keys file.
The library's configuration file is created (/var/opt/openvault/clients/lcp/lname/linst/config, where lname is the name chosen for this library and linst is the instance name for the library.).
Choose the Create a New Network LCP option from the OpenVault LCP Configuration Menu if you want to configure an IBM 3494 library. If you have software for the IBM 3494 LCP installed, then the ov_admin script displays the following menu:
OpenVault -- Network LCP Creation Menu
1 - IBM-3494
2 - STK-ACSLS
3 - ADIC-DAS
r - Return to Previous Menu.
q - Exit.
Which type of network LCP would you like to add: |
Choose option 1 to configure an IBM 3494 LCP.
The following prompt is displayed:
Enter a name for the device, or <enter> to use the default name [lib1]
The ov_admin script proposes a default name for the library, libN where N is 1 in this example.
Consult the IBM 3494 library worksheets you created in “Preparing OpenVault Devices and Hosts”. If you have multiple IBM 3494 libraries to be configured, select one of them.
If you have not yet chosen a name, or can accept the default name, press Enter. (When the library is being configured on an OpenVault client, the ov_admin script does not propose a default library name, but instead asks you to enter the name.)
If you have chosen another name for this library, enter it at the prompt.
The ov_admin script issues the following prompts:
What instance name would you like to give to this LCP? [[email protected]] What security key would you like to give to this LCP? [none] What polling interval would you like this LCP to use? [30]
The ov_admin script configures the LCP, and you see output similar to the following:
Configuring IBM-3494 to be "ibm3494"
You are then prompted for the hostname or TCP/IP address for the PS/2 that is running the IBM Library Server for this library:
What is the hostname or TCP/IP address of the PS/2 inside the library?
The ov_admin script queries the device to get information about drives housed in this library. This device query might take a while, especially if the host has just been rebooted, if the device has just been power-cycled, or if the main door to the library has just been closed. Soon you see output like this:
Acquiring drive information from library (may take a while) ...
After querying information about contained drives, the ov_admin script asks you to enter the OpenVault name for each drive in this library, one after the other.
For the drive at location “-” Enter a drive name for the element address daddr: 3590
Here daddr is the drive's address as reported by the IBM 3494 Library server, usually a number starting from 0. Enter the OpenVault name for the drive at the given address. Refer to the IBM 3494 library worksheet to determine the OpenVault name for this drive. You must match drive address daddr with the column “Drive Number as Described by mtlib Command.” See “Collecting Information for Attached Drives”, for details on how to run the mtlib command.
Tip: It is critical to the proper functioning of OpenVault that all drive names match up. If you have not already recorded a drive name on your worksheet, enter the correct name now. If you are running setup in a scrolling window, scroll up to where you configured this drive, and use the name that was entered there. If you do not want OpenVault to manage this drive, press Enter. The script bypasses configuring the drive in the library; so OpenVault does not mount cartridges in this drive.
Note: If this drive is connected to a remote OpenVault client system, enter the name from your worksheet to configure this drive. If you have not yet recorded a name for this drive, select a unique drive name to enter at the prompt, and record this name on the worksheet. You will be required to enter this name when you later configure drives on the remote OpenVault client system to which the drive is attached.
The script prompts you for OpenVault names for each drive housed in the library. After you enter names of all drives (or bypass) you see output similar to the following:
LCP Configuration Parameters: Library name : ibm3494 LCP name : [email protected] LCP type : IBM-3494 OpenVault Server host name : ursa OpenVault Server port number : 44444 Security key : none LCP polling interval : 30 Number of drives : 2 TCP/IP Address of the Library: tsm-ps2 Drives in the Library Drive Name Drive Address ---------- ------------- 3590 0 Create the LCP now? [Yes]
To configure a StorageTek ACSLS library, choose the Create a new network LCP option from the OpenVault LCP Configuration Menu.
If you have LCP software for the StorageTek ACSLS installed on an OpenVault host, the ov_admin script offers the option of configuring this library. The following is an example of the Network LCP Creation Menu:
OpenVault -- Network LCP Creation Menu
1 - IBM-3494
2 - STK-ACSLS
3 - ADIC-DAS
r - Return to Previous Menu.
q - Exit.
Which type of network LCP would you like to add: |
Choose option 2 to configure an STK-ACSLS library. You are then prompted:
Enter a name for the device, or <enter> to use the default name [lib1]
The name entered here is the OpenVault name for the library. See “Naming Libraries and Drives” for details.
The next prompt displays:
What instance name would you like to give to this LCP? [[email protected]]
The name can be any string. It is used to differentiate between two LCPs that are controlling the same library.
The following prompts appear:
What security key would you like to give to this LCP? [none]
What polling interval would you like this LCP to use? [30]
The LCP needs to check the status of the library occasionally. The "polling interval" is the number of seconds between each of those status checks.
The ov_admin script then displays:
Configuring STK-ACSLS to be "lib1"
You are then prompted for the host name of the ACSLS server for this library:
What is the host name of the ACSLS server? []
After entering this host name, enter the version number of the ACSLS interface. Identify the version of ACSLS installed on the ACSLS server, subtract 1 from this number, and enter that value. See “Collecting Information for ACSLS Libraries ”, for details.
What is the version number of the ACSLS interface? [4]
Next enter the ID of the ACS that you are using for this LCP. Refer to the vendor's library documentation for information about obtaining the ACS ID.
What is the ACS ID of ACS? [0]
The ov_admin script queries the device to determine information about drives housed in this library. This device query might take a while, especially if the host has just been rebooted, if the device has just been power-cycled, or if the main door to the library has just been closed.
Upon querying the information about contained drives, the ov_admin script asks you to enter the OpenVault name for each drive in this library, one after the other.
For the drive at location “ACSid 0, LSMid 2, Panelid 1,Driveid1” Enter a drive name for the element address "0,2,1,1": timberline1
The location string displayed is the ACS ID, LSM ID, Panel ID, and Drive number for the drive. See “Collecting Information for Attached Drives”, for steps to obtain information for drives in an ACSLS library. Consult the ACSLS library worksheet for this library and select the drive entry with the corresponding ACS ID, LSM ID, Panel ID, and Drive number.
Enter the OpenVault name you selected.
Tip: It is critical to the proper functioning of OpenVault that all drive names match up. If you have not already recorded a drive name on your worksheet, enter the correct name now. If you are running ov_admin in a scrolling window, scroll up to where you configured this drive, and use the name that was entered there. If you do not want OpenVault to manage this drive, press Enter. The script bypasses configuring the drive in the library; so OpenVault does not mount cartridges in this drive.
Note: If this drive is connected to a remote OpenVault client system, enter the name from your worksheet to configure this drive. If you have not yet recorded a name for this drive, select a unique drive name to enter at the prompt, and modify your worksheet. You will be required to enter this name when you later configure drives on the remote OpenVault client system to which the drive is attached. The script prompts you for OpenVault names for each drive housed in the library.
After you enter names of all drives (or bypass) you see output similar to the following:
LCP Configuration Parameters: Library name : wolfcreek LCP name : [email protected] LCP type : STK-ACSLS OpenVault Server host name : ursa OpenVault Server port number: 44444 Security key : none LCP polling interval : 30 Number of drives : 2 ACSLS Server Host name : tsm-sun ACSLS Server Version : 4 ACSLS Server ACS ID : 0 Drives in the Library Drive Name Drive Address ---------- ------------- redwood1 0,2,3,1 redwood3 0,2,3,3 timberline1 0,2,1,1 timberline3 0,2,1,3 Create the LCP now? [Yes]The final line prompts you for confirmation. If you are satisfied with the library and drive configuration shown, enter Y. If you want to change one or more parameters, enter N and you can change the configuration values.
Note: The ov_admin script does not allow you to change the name of the library at this time. However, you may do so at a later time by following steps in Chapter 7, “Tertiary Storage Management”. Upon confirmation, the ov_admin script proceeds to configure the library:
LCP successfully created Library lib1 was successfully created.
At this point the following items have been configured:
The named library entry has been added to the OpenVault catalog.
An authentication entry has been added to the /var/opt/openvault/server/config/core_keys file.
The library's configuration file is created (/var/opt/openvault/clients/lcp/lname/linst/config, where lname is the name chosen for this library and linst is the chosen instance name).
This optional configuration step enables the following features:
Administration of the OpenVault server from remote OpenVault clients
LCPs and DCPs that connect to the OpenVault server from OpenVault clients
This step enables remote connections. You must also run the ov_admin script on the remote OpenVault client(s) to configure libraries and drives on client host(s).
It is possible to administer the OpenVault server from a client machine where you have installed the OpenVault administrative commands. To enable that, on the OpenVault host, choose option 23, Manage Applications from the Admin CLI Tools from the OpenVault Configuration Menu. The following menu is displayed:
Manage Applications and Admin CLI Tools Menu
1 - Create a new Application
2 - Delete an Application
3 - Show all existing Applications
4 - Activate another Application Instance for an existing Application
5 - Deactivate an Application Instance
6 - Show all activated Application Instances
7 - Activate a Host to use the Admin CLI Tools
8 - Deactivate a Host from using the Admin CLI Tools
9 - Show all Hosts activated to use the Admin CLI Tools
r - Return to Main Menu.
q - Exit.
Which operation would you like to do: |
Choose option 7 to activate a host to use the Administrative Command Line Tools. The ov_admin script then prompts:
For which Remote Host do you want to activate Admin CLI Tools? [] |
To identify remote client hostnames, consult the host worksheet that you generated in “Preparing OpenVault Devices and Hosts”.
Option 21, Manage Remote Libraries and LCPs on the OpenVault Configuration Menu, enables LCPs that connect to the OpenVault server from OpenVault clients. When this option is chosen, ov_admin presents the following menu:
Manage remote Libraries and LCPs Menu
1 - Create a new Library
2 - Delete a Library
3 - Show all existing Libraries
4 - Activate another LCP for an existing Library
5 - Deactivate a LCP
6 - Show all activated LCPs
r - Return to Main Menu.
q - Exit.
Which operation would you like to do: |
Choose option 1 to create a new library. You are prompted:
Enter the name of the Library you want to create []
If you chose a name for this library in the configuration worksheet, enter that name.
The ov_admin script then displays the following prompts and messages:
Library 9714 was successfully created Do you want to activate a LCP for this Library? [Yes] Enter the name of the Host where the LCP for Library "9714" will run [vega] Enter the LCP's instance name [[email protected]] What security key will the LCP use [none] The LCP "[email protected]" for Library "9714" was successfully activated on "vega". Press enter to continue...
Repeat this process for all remote libraries you want to configure.
Tip: Use the worksheets to record the names you select. You will be asked to enter them again when configuring the library or drives on a remote OpenVault client host. After this, the ov_admin script prompts for remote libraries.
To configure the OpenVault server host for remote drives, choose option 22, Manage Remote Drives and DCPs from the OpenVault Configuration Menu. The following menu is displayed:
Manage remote Drives and DCPs Menu
1 - Create a new Drive
2 - Delete a Drive
3 - Show all existing Drives
4 - Activate another DCP for an existing Drive
5 - Deactivate a DCP
6 - Show all activated DCPs
r - Return to Main Menu.
q - Exit.
Which operation would you like to do: |
Choose option 1 to create a new remote drive. You are then prompted:
Enter the name of the Drive you want to create []
If you chose a name for this library in the configuration worksheet, enter that name.
The following prompt appears:
The following Drive Groups currently exist: drives What Drive Group do you want to use (or create)? [drives]Press Enter to choose the default, or enter the name of an existing drive group, or enter the name of a drive group to be created. If you enter the name of a drive group to be created, you are prompted for more information about it.
The following prompts and messages appear:
Drive drive1 was successfully created. Do you want to activate a DCP for this Drive? [Yes] Enter the name of the Host where the DCP for Drive "9714-top-dlt" will run [vega] Enter the DCP's instance name [[email protected]] What security key will the DCP use [none] The DCP "[email protected]" for Drive "9714-top-dlt" was successfully activated on Host "vega". Press enter to continue...
After you configure locally attached drives and libraries, the script asks to import tapes that were discovered in the newly configured libraries. If you have libraries on remote OpenVault client hosts, wait until those libraries are configured, then invoke the import function as described in the section “Importing Media”. If you do not have any remote libraries, you may import media right away.
After configuring the OpenVault server, it is time to configure remote OpenVault clients, in any order. Consult the host worksheet that you generated in “Preparing OpenVault Devices and Hosts”, for the list of OpenVault client hosts.
To configure an OpenVault client host, follow these steps:
Log in to the remote host as root.
Start the ov_admin script:
# /usr/sbin/ov_admin
The ov_admin script outlines the general configuration strategy:
OpenVault Configuration The general strategy for setting up OpenVault is to 1) configure the OpenVault server 2) configure LCP/DCPs on the server machine 3) configure server for local Applications 4) if needed, configure server for remote LCPs, DCPs, and Apps 5) if needed, install and configure LCP/DCPs on remote machines 6) from the server, setup/import media for each libraryThe ov_admin script then determines the name of the OpenVault server host, the OpenVault server port number, and the OpenVault security key that you chose while configuring the OpenVault server.
The script prompts for the name of the OpenVault server host:
What is the name of the OpenVault Server? [vega]
Enter the name. The default presented in this prompt is the hostname of the machine on which you are running ov_admin script.
The script prompts for the port number of the OpenVault server host:
What is the port number OpenVault is using? [44444]
If you chose another port number when you configured the OpenVault server, enter that port number now; otherwise, accept the default.
The script prompts for the security key of the OpenVault server host:
Enter the security key that you chose when you configured the OpenVault server. If you did not select security at that time, accept the default.
What default security key would you like to use? [none]
Note: Specifying the exact values for the OpenVault server's hostname, port number, and security key is critical for proper functioning of all OpenVault components. The ov_admin script then provides the menu options shown Example 2-2:
Example 2-2. OpenVault Configuration Menu Options
OpenVault Configuration Menu Configuration on Machines Running LCPs and DCPs 1 - Manage LCPs for locally attached Libraries 2 - Manage DCPs for locally attached Drives Configuration on Admin-Enabled Machines 11 - Manage Cartridge Groups 12 - Manage Drive Groups 13 - Import Media q - Exit. Which operation would you like to do?Configure all libraries and drives that you plan to attach to this host.
Select the Manage DCPs for Locally Attached Drives option from the OpenVault Configuration Menu to configure drives that are attached to the host. The ov_admin script displays the following menu:
OpenVault DCP Configuration Menu
1 - Create a new DCP
2 - Modify a DCP
3 - Delete a DCP
4 - Start a DCP
5 - Check status of DCPs
6 - Stop a DCP
r - Return to Main Menu.
q - Exit.
Which operation would you like to do: |
Choose option 1 to create a new DCP.
The set of dialogs presented are similar to the dialog when you configure drives on the OpenVault server. The main difference is that the script asks you to enter the OpenVault name for the drive, but does not offer a default name.
Consult your drive worksheet to make certain that the names match. A sample dialog is shown below:
Example 2-3. Drive Configuration on a Client Host
OpenVault -- DCP Creation Menu
1 - /dev/rmt/tps3d1
2 - /dev/rmt/tps3d2
3 - /dev/rmt/tps3d3
4 - /dev/rmt/tps3d4
5 - /dev/rmt/tps7d2
5 - /dev/rmt/tps7d3
r - Return to Previous Menu.
q - Exit.
For which Drive would you like to add a DCP: 1
Enter a name for the device [] redwood1
What instance name would you like to give
to this DCP? [[email protected]]
What security key would you like to give to this DCP? [none]
What polling interval would you like this DCP to use? [30]
What directory should hold handles for this
DCP? [/var/opt/openvault/clients/handles]
Configuring STK-redwood at /dev/rmt/tps3d1 to be "redwood1"
DCP Configuration Parameters:
Drive name : redwood1
DCP name : [email protected]
DCP type : STK-redwood
OpenVault Server host name : ursa
OpenVault Server port number: 44444
Security key : none
DCP polling interval : 30
Handle creation directory : /var/opt/openvault/clients/handles
Drive access path : /dev/rmt/tps3d1
Direct SCSI access path : /dev/scsi/sc3d1l0
Create the DCP now? [Yes]
DCP successfully created
|
The DCP has been started. If you have not already done so, you need to create the Drive and activate the DCP on the OpenVault server so that the DCP can connect to the server.
Choose the Manage LCPs for Locally Attached Libraries option from the ov_admin OpenVault Configuration Menu to configure attached libraries on an OpenVault Client Host.
The script scans the installed hardware and software to determine which libraries are available for configuration. Each detected library is offered for configuration. The set of dialogs presented are similar to the one when you configure libraries on the OpenVault server. The main difference is that the script asks you to enter the OpenVault name for the library, but does not offer a default name.
It is critical that you enter the OpenVault name for each library exactly as you entered it (during server configuration when enabling remote libraries).
Consult your library worksheet to make certain that the names match. A sample dialog for a SCSI-attached library is shown in Example 2-4.
Example 2-4. Library Configuration on a Client Host
OpenVault LCP Configuration Menu 1 - Create a new SCSI LCP 2 - Create a new network LCP r - Return to Main Menu. q - Exit. Which operation would you like to do: 1 OpenVault -- SCSI LCP Creation Menu 1 - /dev/scsi/sc7d1l0 r - Return to Previous Menu. q - Exit. For which SCSI library would you like to add a LCP:1 Enter a name for the device [] 9714 What instance name would you like to give to this LCP? [[email protected]] What security key would you like to give to this LCP? [none] What polling interval would you like this LCP to use? [30] Configuring STK-9700 at /dev/scsi/sc7d1l0 to be "9714" What is the default shape of the slots in the library? [DLT] For the drive at location "first drive from BOTTOM" Enter a drive name for the element address "1030": 9714-bottom-dlt For the drive at location "second drive from BOTTOM", Enter a drive name for the element address "1031": 9714-top-dlt LCP Configuration Parameters: Library name : 9714 LCP name : [email protected] LCP type : STK-9700 OpenVault Server host name : ursa OpenVault Server port number: 44444 Security key : none LCP polling interval : 30 Number of drives : 2 Direct SCSI access path : /dev/scsi/sc7d1l0 Default cartridge shape : DLT Drives in the Library Drive Name Drive Address ----------- ------------- 9714-bottom-dlt 1030 9714-top-dlt 1031 Create the LCP now? [Yes] LCP successfully createdThe LCP has been started. If you have not already done so, you need to create the Library and activate the LCP on the OpenVault server so that the LCP can connect to the server.
The ov_admin script prompts you for OpenVault drive names contained in the library.
Type names exactly as you did when enabling those drives on the OpenVault server. Consult your library worksheet for details. You must match the location description string for each contained drive with the corresponding description string in the library worksheet.
If you have drives in this library that are connected to another host, enter the exact OpenVault name for these drives, even if you have not yet configured the drives on that host. Consult your library worksheet for this library to get this information.
Configuring a non SCSI-attached library on an OpenVault client host follows the same procedure as configuring one on the OpenVault server host.
At this point the library is configured and the LCP is started. To verify current status of the LCP, run the ov_stat command on the OpenVault server.
After you have configured the libraries on the OpenVault server and all OpenVault clients, you need to import media to make it available for application use. Importing media is how the OpenVault server learns about each piece of media. Each tape that applications use must be imported before it can be made available for allocations and mounts. See Chapter 3, “Cartridge Life Cycle”, for more information.
| Caution: If you have media that contain data in a library, or if media are known to certain sensitive applications, take precautions so that other applications do not accidentally modify these media (for example, by defining a cartridge group for the dedicated used by only the one application). Refer to the application's documentation for importing media known to that application only. Failure to do so could lead to data loss. |
It is best to invoke the import media function of the ov_admin script only after you have configured all libraries, including libraries on remote OpenVault client hosts.
The import function is available only on the OpenVault server host.
To import media into a library, you must identify a cartridge group for each cartridge. The ov_admin script imports all media found in a library into the same cartridge group. By default, media are imported into the default cartridge group called carts. If you would like to add more cartridge groups, do so now. To import media using multiple cartridge groups, see Chapter 6, “Reconfiguring OpenVault”.
You must also identify a cartridge type for each cartridge. The ov_admin script assumes that all media in a library is of the same cartridge type. If this is not true, skip automatic import of media and follow the procedures described in Chapter 3, “Cartridge Life Cycle”.
The import function allows you to pre-allocate all media to an application. If you wish to import media that is pre-allocated to other applications, skip automatic import of media and follow the procedures described in Chapter 3, “Cartridge Life Cycle”.
You may import media that is not pre-allocated. If you do, make sure that OpenVault applications know how to import media. For example, the media mounting application ov_umsh provided with OpenVault knows how to allocate media.
To use the import function, enter the /usr/sbin/ov_admin command as root on the OpenVault server host, and select the Import Media option 13, as shown in Example 2-5:
OpenVault Configuration Menu Configuration on Machines Running LCPs and DCPs 1 - Manage LCPs for locally attached Libraries 2 - Manage DCPs for locally attached Drives Configuration on Admin-Enabled Machines 11 - Manage Cartridge Groups 12 - Manage Drive Groups 13 - Import Media Configuration on the OpenVault Server Machine 21 - Manage remote Libraries and LCPs 22 - Manage remote Drives and DCPs 23 - Manage Applications and Admin CLI Tools q - Exit. Which operation would you like to do: 13 Would you like to import media ? [Yes]The ov_admin script checks for all configured libraries containing media to import, and shows each of the libraries individually.
Would you like import media from the library 9710 [Yes]
Accept the default if you are ready to import media in that library; otherwise, enter No.
The script continues:
Would you like to add ALL cartridge to the SAME Cartridge group [Yes]
If you decide to import all cartridges in this library into the same cartridge group, accept the default. Otherwise, enter No to have the script skip importing media from this library.
Known cartridge types are presented for your inspection, including types that might be unavailable. Choose the type that corresponds to the brand name on your cartridges.
Note: Because 3590 cartridges are the same size as 3480 cartridges, they are said to have a 3480 slot type, which is sometimes a source of confusion. Once you select the cartridge type, available cartridge groups are displayed. Enter the cartridge group of which all cartridges in this library should be members.
Cartridge Groups available are: 1. carts Select the Cartridge group for the cartridges in this library:Once you select a cartridge group, the script asks about pre-allocation. If you want to pre-allocate cartridges to an application, accept the default. If not, see “Not Pre-allocating Cartridges”.
Would you like to pre-allocate cartridges to specific application [Yes]
If you answer Yes, you are prompted for an application name, dmf in this example:
Enter name of application for cartridge pre-allocation [ov_umsh] dmf
If the application name you enter does not exist, the ov_admin script creates it for you.
Once the import completes successfully, you see output similar to the following:
Created Application: dmf Cartridge-group-application creation: Application: dmf Group: carts Importing tapes with: Cartridge Type = DLT2000 Cartridge Group = carts Application = dmf This may take a while... Finished importing media from library, 9710
If you do not wish to pre-allocate cartridges, enter No after the following prompt:
Would you like to pre-allocate cartridges to specific application [Yes] |
Cartridges in this library are imported without being pre-allocated to any application. Once the import completes successfully, you see output similar to Example 2-6:
Example 2-6. Importing Media without Pre-allocating Cartridges
Importing tapes with:
Cartridge Type = DLT-7000
Cartridge Group = carts
This may take a while ...
Finished importing media from library, 9730 |
On IRIX systems, it is possible to do a custom installation, which allows you to install only the subsystems that you need. Before doing a custom install, you must determine the types of all OpenVault-managed libraries and drives on all systems.
For drives, see “Determining Attached SCSI Drives”.
For SCSI libraries, see “Determining Attached SCSI Libraries”.
For other libraries, see “Network Libraries”.
Remember to repeat the steps explained in this section for every host with an attached library or drive that is to be managed by OpenVault.
On SGI ProPack for Linux and IRIX systems, you can use the ov_scandev command, which is part of OpenVault to determine the connected SCSI drives. The command display includes vendor name, path to the drive, and drive product name, as shown in Example 2-7. See the man page for more details.
Example 2-7. ov_scandev Drive Output (IRIX)
# ./ov_scandev -D -p vendor,product,serial_number,wwn -l
/dev/rmt/5005076300002d33/lun0/c33p400000
vendor : IBM
product : 03590E11
serial_number : <unknown>
wwn : 5005076300002d33
/dev/rmt/500104f0004395f0/lun0/c33p1
vendor : STK
product : 9840
serial_number : 331000031498
wwn : 500104f0004395f0
/dev/rmt/500104f000425829/lun0/c33p1
vendor : STK
product : 9840
serial_number : 331000030387
wwn : 500104f000425829 |
This sample output is unrelated to Figure 2-1 and Figure 2-2.
On SGI ProPack for Linux and IRIX systems, you can use the ov_scandev command, which is part of OpenVault to determine the connected SCSI libraries. As shown in Example 2-8, the command can display the library vendor name, library product name, and path. See the man page for details.
Example 2-8. ov_scandev Library Output (IRIX)
# ./ov_scandev -L -p vendor,product,serial_number,wwn -l
/dev/scsi/sc21d5l0
vendor : STK
product : 9714
serial_number : <unknown>
wwn : <unknown>
/dev/scsi/5005076300002d33/lun1/c33p400000
vendor : IBM
product : 03590E11
serial_number : <unknown>
wwn : 5005076300002d33 |
This sample output is unrelated to Figure 2-1 and Figure 2-2.
OpenVault supports several network libraries. If you plan to manage this type of library, you must install the appropriate OpenVault.lcp subsystems on IRIX systems. On SGI ProPack for Linux systems, all of the LCPs provided by SGI are included in the openvault-sw package.
For any library that you plan to manage with OpenVault, configure one and exactly one controlling LCP. Because the above-mentioned libraries are not SCSI-attached, you may designate any OpenVault host system to run the LCP. You must install the appropriate OpenVault.lcp subsystem on that chosen system. For simplification, it might be best to designate the OpenVault server as the LCP host for non-SCSI-attached libraries.
| Note: If you unintentionally install the LCP for a network LCP on an OpenVault host, the OpenVault ov_admin menus will present it as an option for installation. Do not select it unless you want to configure it. |
This section offers guidelines for selecting OpenVault components to install on IRIX systems. On SGI ProPack for Linux systems, all OpenVault server commands and executables, administrative tools, LCPs, and DCPs are included in the openvault-sw package; OpenVault sample source for applications and include headers are included in openvault-dev packages.
For OpenVault server hosts:
Required
OpenVault.sw.config OpenVault setup scripts OpenVault.sw.core OpenVault core servers OpenVault.sw.admin OpenVault administrative tools OpenVault.sw.startstop OpenVault scripts to start & stop daemons OpenVault.upgrade.files OpenVault scripts required for upgrading Openvault installationsRecommended
OpenVault.man.manpages OpenVault manual pages OpenVault.man.relnotes OpenVault release notes OpenVault.docs.adminguide OpenVault Administrator's Guide
Optional
OpenVault.sw.user OpenVault end-user tools OpenVault.dev.examples OpenVault sample source for applications OpenVault.dev.include OpenVault app C/C++ include headers
As needed
OpenVault run-time libraries for DCPs OpenVault.dcp.XXXX Appropriate DCP susbsystem OpenVault.lcp.XXXX Appropriate LCP susbsystem
For OpenVault client hosts:
Required
OpenVault.sw.config OpenVault setup scripts OpenVault.upgrade.files OpenVault scripts required for upgrades.
Not recommended
OpenVault.sw.core OpenVault core servers
Recommended
OpenVault.man.manpages OpenVault manual pages OpenVault.man.relnotes OpenVault release notes OpenVault.sw.admin OpenVault administrative tools OpenVault.docs.adminguide OpenVault Administrator's Guide
Optional
OpenVault.sw.user OpenVault end-user tools OpenVault.dev.examples OpenVault sample source for applications OpenVault.dev.include OpenVault app C/C++ include headers
As needed
OpenVault run-time libraries for DCPs OpenVault.dcp.XXXX Appropriate DCP susbsystem OpenVault.lcp.XXXX Appropriate LCP susbsystem OpenVault.sw.startstop OpenVault scripts to start & stop daemons
The OpenVault.sw.startstop and OpenVault.sw.config and OpenVault.upgrade.files subsystems are required on each OpenVault host that contains an OpenVault DCP or LCP.
The installation tool enforces these requirements.