Installing VolServ® VolServ Version 5.
Trademark Notice AMASS, DataMgr, EMASS, FileServ, and VolServ are either trademarks or registered trademarks of ADIC, Advanced Digital Information Corporation. DAS is a trademark of Grau, an ADIC subsidiary. All other product names and identifications are trademarks or registered trademarks of their respective manufacturers. Copyright Notice © 1996-2001 ADIC®. All rights reserved. This document is the property of ADIC.
READER COMMENT FORM ADIC includes this Form in an effort to provide the best possible documentation to our customers. Please take a few moments to mail or FAX your response to: ADIC Software Documentation 10949 East Peakview Ave. Englewood, CO 80111 FAX: 303-792-2465 E-mail: techdocs@adic.com Question Circle One Information was complete. Agree Disagree Information was easy to find. Agree Disagree Information was easy to follow.
NOTES
Installing VolServ Premise of This License This License sets forth the terms and conditions under which ADIC agrees to grant and Licensee agrees to accept a license to use certain of ADIC’s proprietary software and related documentation. Any software programs or related materials provided by ADIC shall be subject to the terms and conditions of this License. By opening this media package you accept the terms of the following agreement.
Installing VolServ Use Licensee is authorized hereby to use the Software on the Designated Computer(s) only, or on backup equipment if the Designated Computer is inoperative until such time as the Designated Computer is restored to operation and processing on the backup equipment is completed.
Installing VolServ Ownership & Protection ADIC’s Warranty ADIC warrants that it is the owner of the Software and all portions thereof, except for any embedded third party software, and that it has the right to modify the Software and to grant this License for its use. Title to Software The Software and all copies thereof (except for any embedded third party software) are proprietary to ADIC and title thereto remains in ADIC.
Installing VolServ Responsibility Licensee has sole responsibility for use of the program and any information entered, used, or stored thereon. This responsibility includes protection of data from modification, destruction, or disclosure, and for the accuracy and integrity of the results from improper use. ADIC assumes no responsibility for Licensee’s negligence or failure to protect data from modification, destruction, or disclosure not specifically authorized in writing by ADIC.
Installing VolServ Warranty & Servicing Warranty ADIC warrants that for a period of 90 days from installation, the Software will conform to all substantial operational features in ADIC’s current published specifications and will be free of defects which substantially affect performance of the Software. ADIC does not warrant that the Software will meet the Licensee’s requirements or that the operation of the Software will be uninterrupted or error free.
Installing VolServ Disclaimer EXCEPT FOR THE EXPRESS LIMITED WARRANTY STATED ABOVE, ADIC MAKES NO WARRANTIES, EXPRESS OR IMPLIED, FOR THE SOFTWARE, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. Third-Party Warranties No reseller or distributor of the Software who may have participated in offering, demonstrating, promoting or delivering the Software subject to this License makes any warranty whatsoever.
Installing VolServ Upon failure of (1), (2) or (3) above, despite the reasonable efforts of ADIC, Licensee may terminate this License only with respect to the Software adversely affected by such action or claim. Upon such termination, ADIC shall promptly refund to Licensee any License Fees paid and other payments made for the adversely affected Software.
Installing VolServ This License may be terminated by ADIC if the Licensee: • terminates or suspends its business; • becomes subject to any bankruptcy or insolvency proceeding under governmental statute or • becomes insolvent or becomes subject to direct control by a trustee, receiver or similar authority. If this License is terminated by ADIC, ADIC shall have the right to take immediate possession of the Software, Documentation and all copies wherever located, without demand or notice.
Installing VolServ General No Assignment This License is not assignable. None of the Software or Documentation may be sublicensed, assigned or transferred to any other party without ADIC’s prior written consent. Any effort contradictory of this is null and void. Modification This License or any Exhibit thereto can only be modified by a written agreement executed by Licensee and ADIC. Governing Law THIS LICENSE WILL BE GOVERNED BY THE LAWS OF THE STATE OF COLORADO.
Installing VolServ Entirety Licensee acknowledges that it has read this Software License, understands it, and agrees to be bound by its terms and conditions. Further, Licensee agrees that this is the complete and exclusive statement of the agreement between the parties which supersedes all proposals or prior agreements, oral or written and all other communications between the parties relating to the subject matter of this License.
Contents Preface Purpose of This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Who Should Read This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How This Book is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Books . . . . . . . . . . . . . . . . .
Installing VolServ Installation Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5 Extract Files from CD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6 Install VolServ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8 Post Installation Tasks 3 Post Installation Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface Purpose of This Book . . . . . . . . . . . . . . . . . . . . . . .P-3 Who Should Read This Book. . . . . . . . . . . . . . . . .P-3 How This Book is Organized . . . . . . . . . . . . . . . .P-3 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .P-4 Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .P-5 Online Books . . . . . . . . . . . . . . . . . . . . . . . . . . .P-5 Related Publications . . . . . . . . . . . . . . . . . . . . .
Installing VolServ NOTES P-2 Preface 601351 Rev A
Purpose of This Book This book describes how to install VolServ. Who Should Read This Book This book is intended as a reference guide for use by the VolServ installation team and the site system administrator. Use this guide for the installation and setup of a VolServ system.
Installing VolServ Conventions The conventions used throughout the VolServ technical books are listed below: Convention Example Screen text, file names, program names, and commands are in Courier font. Request to add a new volume: Volume group will be “20” Volume position will be “A123”. The root prompt is shown as a number symbol. # su root What you should type in is shown in Courier bold font. vsarchiveqry Site-specific variables are in a Times italics font.
Books The books described below are part of the technical documentation set, and are shipped on CD along with the VolServ software: Overview Provides an overview of VolServ. Contains a glossary. Installing VolServ Describes server requirements, installation instructions, troubleshooting procedures, and configuration parameters. Using the VolServ GUI Describes how to perform system administrative tasks using the graphical user interface.
Installing VolServ Related Publications The publications described in the table below are created and distributed on an as-needed basis. Related Publications “Release Notes” Description For each version of VolServ, the “Release Notes” contain: • Summary of enhancements • Describes: - Fixed problems - Known problems - Installation and configuration issues • Lists: - Operating system patches. - System requirements “Product Alerts” Informs customers of technical problems and solutions.
1 Getting Started Getting Started Prior to Installation . . . . . . . . . . . . . . . . . . . . . . . . 1-3 VolServ Directory Structure . . . . . . . . . . . . . . . . . 1-4 System Parameters Checklist . . . . . . . . . . . . . . . . 1-6 Create VolServ Directories . . . . . . . . . . . . . . . . . . 1-7 Configure UNIX Environment . . . . . . . . . . . . . . . 1-8 Obtain VolServ License Strings . . . . . . . . . . . . . .
Installing VolServ Roadmap Topic Refer To Chapter Prepare to install VolServ 1 Install VolServ 2 Tasks after installing VolServ: • Startup and shutdown scripts 3 • Put Linter engine in PATH • Database maintenance and recovery • Media management Site-specific tasks: • Modifying .
Installing VolServ Prior to Installation The tasks below are presented as guidelines only since the actual steps for your specific site are unique: 1 Refer to Page Task Getting Started Step Install the hardware and connect the storage devices to the network. NOTE: If you are also using FileServ, first install VolServ, then install FileServ. 2 A new installation on an existing system may require the system administrator to do some data manipulation and disk repartitioning.
Installing VolServ VolServ Directory Structure The VS_DIR environment variable is set up in the local .cshrc file by the installation script. During execution of the script, a prompt asks for the name of the directory in which to install VolServ. The default value of VS_DIR is /volserv/volserv but you can enter a different location during execution of the installation script.
Installing VolServ Directory config Contents Getting Started A series of *.config files. Changes to VolServ operating environment can be made by altering entries in the *.config files. For example, the user can elect to add or to remove VolServ capabilities available to the clients or VolServ system administrator by modifying command.config or operator.config files. In most cases, changes made to the *.config files do not take effect until VolServ and the system administrator consoles have been cycled.
Installing VolServ System Parameters Checklist The installation script prompts you for configuration information. Therefore, before running the script, complete the System Parameters Checklist table shown below.
Installing VolServ Create VolServ Directories During the VolServ installation process, you are requested to either: Accept the default directories. • Or, supply directory locations for certain files that assist in database recovery. If you do not want to accept the defaults, create the new directories before beginning the VolServ installation process. The required directories are described below.
Installing VolServ Configure UNIX Environment Step 1. Login as root user. Step 2. Use an editor, such as vi, to add the vsadmin group to the /etc/group file. This file must contain a line entry for each group recognized by the system. The format of each entry is: groupname:password:gid:[user-list] where: Option Description groupname Name of the group. password Encrypted group password or * if no password. gid Group’s numerical identifier within the system; it must be unique.
Installing VolServ Step 3. Use an editor, such as vi, to view the /etc/passwd file. If this file already contains a vsadm entry, no further action is necessary. Otherwise, the user must add a vsadm user definition to the file. This file must contain a line entry for each user recognized by the system. The format of each entry is: where: Option Description username The name of the user. password The encrypted user password or * if no password is used.
Installing VolServ Note Creating shadow files are optional. If you are not creating a shadow file, go to Step 7. Step 4. Change the /etc/shadow file access mode to 600. # chmod 600 /etc/shadow Step 5. Use an editor, such as vi, to view the /etc/shadow file. Make the following vsadm entry: vsadm:::::::: Make sure to enter eight colons after the vsadm string. Step 6. Reset the /etc/shadow file access mode to 400. # chmod 400 /etc/shadow Step 7. Run the passwd command to initialize the vsadm password.
Installing VolServ Step 1. Display the host identification number for the host server. • On SGI, use the following command: Getting Started Obtain VolServ License Strings # sysinfo -s • On Sun, use the following command: # hostid Step 2. Obtain a site license strings by calling the ADIC Technical Assistance Center: • In the USA and Canada, call 1-800-827-3822. • Outside the USA and Canada, call 303-874-0188 or toll-free 00800-9999-3822. • Send e-mail to: support@adic.com.
Installing VolServ NOTES 1-12 Getting Started 601351 Rev A
Distribution Media . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Running the Installation Script . . . . . . . . . . . . 2-3 Installation Summary . . . . . . . . . . . . . . . . . . . . . . 2-5 Extract Files from CD . . . . . . . . . . . . . . . . . . . . . . . 2-6 Install VolServ . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing VolServ Roadmap Topic Refer To Chapter Prepare to install VolServ 1 Install VolServ 2 Tasks after installing VolServ: • Start-up and shutdown scripts 3 • Put Linter engine in PATH • Database maintenance and recovery • Media management Site-specific tasks: • Modifying .
Installing VolServ Distribution Media The VolServ distribution CD contains: • Information describing the release • A script file to perform installation • One or more data files to be installed The installation process involves verifying the header file and loading and executing the installation script file. The script controls the remainder of the installation process. Installing VolServ takes approximately 30 minutes. The following procedure includes the prompts issued by the installation script.
Installing VolServ VolServ parameter files are ASCII text files that can be modified using a text editor. The system administrator can change these parameters to tune the system for site-specific needs. The VolServ administrator environment is created during installation. The exact setup of the environment depends largely upon the intended use of the VolServ system.
Installing VolServ Installation Summary The following steps are required for a successful installation: Step Refer to Page Task 1 Complete the steps in the “Prior to Installation” table. 1-3 2 Extract the files from the CD. 2-6 3 Use the vs_install script to install VolServ onto the UNIX server. 2-8 4 Determine which post installation tasks you need to perform. 3-3 5 Determine which site-specific tasks you need to perform.
Installing VolServ Extract Files from CD Step 1. Place the VolServ CDROM into the CD drive. Step 2. Login to the VolServ host computer as the root user. Step 3. If a windowing environment is used, expand the shell window to a width of 80 columns or more. Step 4. Remote only: Edit the remote host’s /.rhosts file by adding the hostname (of the machine that VolServ is being installed on) to the file. Step 5.
Installing VolServ where: Option platform Description Enter your UNIX server platform type: • Solaris = sol • IRIX 6.2 = sgi6.2 • IRIX 6.5 = sgi6.5 Step 7. To start extracting the VolServ files, press . 601351 Rev A Installation Procedures 2-7 Installation Procedures The VolServ support and executables files are extracted from the installation CD. Extraction time depends on platforms and media type.
Installing VolServ Install VolServ Step 1. At the command line, enter the following command to begin the VolServ install script: # /usr/tmp/volserv/vs_install Step 2. The ADIC copyright license and the date the distribution CD was created displays as shown below: Copyright 1992-2001 by ADIC, Inc. All rights reserved.
Installing VolServ Are you installing from CDROM ( or n)? y Is your intended response ( or n)? y ------------------------------------------------------------------ Enter remote CDROM device path (e.g. /cdrom/volserv)<> Ready to install/update the necessary VolServ files Do you wish to install/update the VolServ files now ( or n)? y Step 4. Either accept the default volserv installation directory or enter a new path. Tip For this example, the default is used.
Installing VolServ Step 5. VolServ checks the available disk space for the specified load directory. If insufficient space is available, an error is returned. The installation script also checks the selected file system to ensure that enough free disk space is available.
Installing VolServ Step 7. If you have a DataShelf, Stage, DataTower, AML, Silo, or SCSI library connected, you are asked about installing those executables as well. Do you wish to install the VolServ DataShelf executables ( or n)? n ------------------------------------------------------------------ Do you wish to install the VolServ Stage executables ( or n)? y Checking disk space in /volserv/volserv… done.
Installing VolServ The “vsadm” user and “vsadmin” group must exist before the installation can continue. You must create them now if you have not already done so. If you are installing from a single-window terminal, you may suspend this install process by using -Z and then resume when ready by using the fg command. Press to continue… ------------------------------------------------------------------ Step 9.
Installing VolServ Step 10. Enter the VolServ license string. If you do not enter it now or want to change the string later use the $VS_DIR/util/change_license utility. For instructions, see “Updating the License String” on page 3-17. Please enter the license strings that were delivered with the VolServ software.
Installing VolServ ------------------------------------------------------------------ Setting VolServ permissions… done. ------------------------------------------------------------------ Step 12. The VolServ database (Linter) is installed under $VS_DIR/linter. The home directory of the linter database is /vsdev/volserv/linter. The LINTER_DIR environment variable will be set to this value. Commencing installation of the VolServ database. Copying Linter RDBMS files to /vsdev/volserv/linter… . . .
Installing VolServ ’Version’ table created ’ArchiveClass’ table created ’InsertArchiveClass ’ created ’DeleteArchiveClass ’ created ’UpdateArchiveClass ’ created ’ArchiveType’ table created . . . ’InsertArchive ’ created ’DeleteArchiveSuite ’ created ’UpdateArchive ’ created Set up of tables for database voldb complete. Step 13. Installation Procedures After all the database tables are entered, VolServ automatically makes an initial checkpoint of the Linter Database. Checkpointing the voldb database .
Installing VolServ Either accept the default path or enter a new pathname. --------------------------------------------------------------------Ready to install the necessary VolServ API files. Do you wish to install/update the VolServ API files now ( or n) ? y -----------------------------------------------------------------When prompted for the installation directory, remember that“/vsapi” is appended to your response.
Installing VolServ Step 16. At the end of the installation, the files installed will be displayed and a copy of the installation configuration will be written to a file. The following software was installed: ADIC VolServ 5.0.0 ADIC VolServ API 5.0.0 Relex, Inc. Linter RDBMS v593 ADIC 5.0 Software Installation Script Complete ------------------------------------------------------------A transcript of this install can be found in /volserv/volserv/logs/install.5.0.0.log# Step 17.
Installing VolServ NOTES 2-18 Installation Procedures 601351 Rev A
Post Installation Topics . . . . . . . . . . . . . . . . . . . . . 3-7 Put Linter in PATH . . . . . . . . . . . . . . . . . . . . . . 3-3 Database Maintenance . . . . . . . . . . . . . . . . . . . 3-4 Database Recovery . . . . . . . . . . . . . . . . . . . . . . 3-6 Media Management . . . . . . . . . . . . . . . . . . . . . 3-6 Site-Specific Topics . . . . . . . . . . . . . . . . . . . . . . . . . 3-7 Modifying the .cshrc File . . . . . . . . . . . . . . . . 3-7 Configuring SCSI Device Nodes. . . . . . . .
Installing VolServ Roadmap Topic Refer To Chapter Prepare to install VolServ 1 Install VolServ 2 Tasks after installing VolServ: • Start-up and shutdown scripts 3 • Put Linter engine in PATH • Database maintenance and recovery • Media management Site-specific tasks: • Modifying .
Installing VolServ Post Installation Topics Setting up the VolServ environment includes the following tasks: Topic Put Linter in PATH Page Put Linter in PATH 3-3 Database Maintenance 3-4 Database Recovery 3-6 Media Management 3-6 VolServ uses a Linter Database to store and track information about the archived files, tape drives, and media managed by VolServ. If Linter goes down, VolServ also terminates. Edit either the .cshrc or .
Installing VolServ Database Maintenance Linter must be active before VolServ initiates. Periodic database maintenance is required to prevent data loss, to improve VolServ performance, and to simplify recovery procedures, if needed. All maintenance operations are established during the initial VolServ installation. However, the VolServ system administrator can modify the backup script to accommodate the specific needs of each site.
Installing VolServ Step 2. Enter the time in the scr_unix.bsl script for “Everyday” and “CWEEKDAY.” Step 3. When you are finished editing, restart the Linter Database and backup process by running the following: # /etc/rc2.d/S90linter This backup script includes the following two device paths that were set up during the database installation: Check Pointing the Database • ARCDEVICE—stores weekly backups. • LHBDEVICE —stores daily backups. A checkpoint is a snapshot of the database.
Installing VolServ Database Recovery All changes to the database can be recovered by the following operations: • Journaling enabled for the Linter Database. • Linter software maintaining a record of every update since the last checkpoint. If the Linter Database ($VS_DIR/linter/db) becomes either corrupt or loses data, you can recover the database from checkpoints, journals, and backups. To restore your database, follow the steps below: Step 1.
Installing VolServ Site-Specific Topics Additional tasks include the following topics: Topic Modifying the .cshrc File Page Modifying the .cshrc File 3-7 Configuring SCSI Device Nodes 3-8 Changing the Configuration File 3-13 Updating the License String 3-17 Configuring Label Printers 3-17 During execution of the VolServ installation script, the .cshrc file for vsadm was created. This file may need to be modified if the shell used is different from the shell the software was installed under.
Installing VolServ Configuring SCSI Device Nodes Note These steps are only required when attaching a SCSI-connected library. If you are attaching a SCSI-connected library, use the following procedures. SGI/IRIX Host Note These instructions do not apply to a SCSI library that is to be controlled via the Scalar DLC network attachment. To configure a SCSI device node to an IRIX host: 3-8 Post Installation Tasks Step 1. Power-down the IRIX machine. Step 2. Connect a properly terminated SCSI library.
Installing VolServ Here is an example of the report from hinv: $ hinv 2 195 MHZ IP30 Processors CPU: MIPS R10000 Processor Chip Revision: 2.7 FPU: MIPS R10010 Floating Point Chip Revision: 0.0 Main memory size: 128 Mbytes Xbow ASIC: Revision 1.3 Instruction cache size: 32 Kbytes Data cache size: 32 Kbytes Secondary unified instruction/data cache size: 1 Mbyte Integral SCSI controller 0: Version QL1040B (rev.
Installing VolServ Step 7. $ ls /dev/scsi sc0d1l0 sc1d2l0 sc0d2l0 sc1d3l0 $ sc2d1l0 sc2d2l0 Enter ls /dev/scsi to display the nodes for all SCSI devices. An example report is: sc2d3l0 sc2d4l0 sc2d5l0 sc2d6l0 sc2d8l0 In this example, the SCSI Device to be entered for configuration of this SCSI library for VolServ is sc2d6l0 where c2 corresponds to Controller 2, d6 corresponds to SCSI ID (Unit) 6, l0 and corresponds to Logical Unit Number (LUN) 0.
Installing VolServ Step 6. Edit the /kernel/drv/sgen.conf file as shown below.
Installing VolServ An OK prompt will appear on the desktop, not in a CDE window. Step 8. Reboot the Solaris host machine using boot -r to force re-configuration of hardware devices. This will create the device node required for the attached library. Be prepared to immediately do another STOP-A sequence as soon as the memory checks starts (this is when you see the cursor spin activity with the characters '\' '-' '/', etc. without moving position). This will abort the boot and return to the OK prompt.
Installing VolServ Configuring for FileServ Step 1. Start VolServ. Step 2. Configure the appropriate libraries. Step 3. Configure all drives and associate them with their appropriate libraries. Step 4. Configure client and operator command authorization. Step 5. Add media to a library. Step 6. Install FileServ. Step 7. The FileServ install script automatically: • Configures the Media Classes. • Performs archive Media Class associations.
Installing VolServ Step 3. Edit the appropriate *.config files. where: *.config File 3-14 Post Installation Tasks Description command.config A list of VolServ commands available to client software. This file is used by VolServ to determine permission of clients to execute these commands. View information contained in this file for more information. console.config Entries that configure the logging system for VolServ. View information contained in this file for more information. console_locations.
Installing VolServ *.config File label_printers.config Printer name and type of the label printers used by VolServ to print or reprint media labels. View information contained in this file for more information. operator.config A list of VolServ commands available to the system administrator. This file is used by VolServ to determine permission of the system administrator to execute these commands. View information contained in this file for more information. printers.
Installing VolServ *.config File 3-16 Post Installation Tasks Description process.config A list of processes that are started up following processes contained in the servers.config file or are terminated before those in servers.config. Information in this file should not be modified unless directed by ADIC technical support. View information contained in this file for more information. servers.config A list of processes that are started up prior to those processes in process.config file.
Installing VolServ Updating the License String After installation, you may need to update a license string or subsystem configuration. The same utilities invoked by the installation script are used to make these updates; therefore, the procedures (after invoking the utilities) follow those shown in the installation script. The utility for updating a license string is $VS_DIR/util/change_license. Step 1. Log in as vsadm. # su - vsadm Step 2.
Installing VolServ # # Intermec Printer: # barcodelabel:\ :lp=/dev/ttyb:sd=/var/spool/lpd:\ :br#9600:ms=evenp: Step 2. If these printers are not attached to the VolServ host machine serial ports A and/or B or if they are attached to parallel ports or a remote machine, the system administrator must set up the /etc/printcap file to define the printers. Step 3. To simplify the printcap file modification, use the names of the label printers as defined in the label_printers.config file.
Installing VolServ Step 1. Login as root. # su root Step 2. Connect the printer data cable to the appropriate port on the back of the VolServ host computer. Step 3. Enter the following: # admintool & Step 4. Select the Serial Port Manager and disable communication to both serial ports. Close the Serial Port Manager. Step 5. Select the Printer Manager. Step 6. Select Edit-->Add Printer-->Add Local Printer option. Make the following entries for “port A.
Installing VolServ 3-20 Post Installation Tasks • Enable Printer Queue: Yes • Accept Print Jobs: Yes Step 8. Close the Printer Manager. Step 9. Close the admintool window.
Installing VolServ NOTES Post Installation Tasks 601351 Rev A Post Installation Tasks 3-21
Installing VolServ 3-22 Post Installation Tasks 601351 Rev A
Index A Adobe Acrobat Reader. . . . . . . . . . . . API . . . . . . . . . . . . . . . . . . . . . . . . . . . Archive Controller hostname . . . . . . . . . . . . . . . . . . . internet address . . . . . . . . . . . . . . P-5 1-7 1-6 1-6 B Book audience . . . . . . . . . . . . . . . . . . . . conventions . . . . . . . . . . . . . . . . . documentation set . . . . . . . . . . . . online . . . . . . . . . . . . . . . . . . . . . . organization . . . . . . . . . . . . . . . . . purpose. . . . . . . . . . . .
Installing VolServ stop. . . . . . . . . . . . . . . . . . . . . . . . 3-3 P Printers barcode label . . . . . . . . . . . . . . . 3-18 seiko shelf label . . . . . . . . . . . . . 3-18 Publications Department. . . . . . . . . . . . . . . . . . P-6 Product Alerts . . . . . . . . . . . . . . . P-6 Product Bulletins . . . . . . . . . . . . . P-6 Release Notes. . . . . . . . . . . . . . . . P-6 S Solaris Utilities admintool . . . . . . . . . . . . . . . . . . 3-18 console_locations.config . . . . . . .
