ACSLS Installation Guide

Automated CartridgeSystem Library

Software

Installation and Configuration Guide

for Solaris

Version 6.0

CRC Update

The information in this document is confidential and proprietary to Storage Technology Corporation and maybe used only under the terms of the product license or nondisclosure agreement. The information in thisdocument, including any associated software program, may not be disclosed, disseminated, or distributed inany manner without the written consent of Storage Technology Corporation.

Limitation on Warranties and Liability

This document neither extends nor creates warranties of any nature, expressed or implied. Storage Technology Corporation cannot accept any responsibility for your use of the information in thisdocument or for your use of any associated software program. Storage Technology Corporation assumes noresponsibility for any data corruption or erasure as a result of the use of the information in this document, or theuse of software programs. You should be careful to ensure that your use of the information complies with allapplicable laws, rules, and regulations of the jurisdictions with respect to which the information is used.

Warning: No part or portion of this document may be reproduced in any manner or in any form without thewritten permission of Storage Technology Corporation.

Restricted Rights

Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in subparagraph (c)(1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227–7013 orsubparagraphs (c) (1) and (2) of the Commercial Computer Software –– Restricted Rights at 48 CFR52.227–19, as applicable.

Trademarks

The following terms are either trademarks or registered trademarks of Storage Technology Corporation:StorageTek�

Nearline�

IBM� is a registered trademark of International Business Machines Corporation.

Other product names mentioned in this manual may be trademarks. They are used for identification purposesonly.

Ninth Edition, August 2001

EC 123273

This edition applies to Version 6.0 of Automated Cartridge System Library Software. Information contained inthis publication is subject to change. Comments concerning the contents of this manual should be directed to:

Storage Technology CorporationManager, Software Information Development, MS 5209One StorageTek DriveLouisville, Colorado 80028–5209

ORE–mail us at: ��

� Copyright Storage Technology Corporation 2001. All Rights Reserved.

iiiAbout this Book

About this Book

ACSLS Software

��

� Install and configure ACSLS 6.0

� Upgrade to ACSLS 6.0 from a previous release of ACSLS

� Install a second disk after you have installed ACSLS

Audience

This book is written for StorageTek or customer personnel whoinstall and configure the Solaris operating system and ACSLS.As the ACSLS installer, you should already know the following:

� UNIX file and directory structure

� How to use UNIX commands and utilities for yourplatform

� UNIX system files

� How to do typical UNIX tasks, such as logging on as ��

9th ed., 313464701

iv ACSLS Installation and Configuration Guide for Solaris

We’d like to know what you think about this book. For thatpurpose, we’ve included a reader’s comment form in the back ofthis book. Please copy the form, fill it out, and mail it to us.

If you prefer, you can e-mail your comments to SoftwareInformation Development directly. Our Internet address is:

��

Be sure to include the document title and number with yourcomments.

Reader’sComments

9th ed., 313464701

v About this Book

About the Software

This book supports ACSLS 6.0.

Note: The StorageTek Customer Resource Center (CRC) on theWorld Wide Web lets you download ACSLS PTFs and softwaresupport for product enhancements such as new drive or librarytypes.

To access ACSLS PTFs and software support forproduct enhancements:

1. Using an Internet browser such as Netscape, go to theStorageTek CRC. The URL is:

��

2. Select the �� link.

3. Fill in the information requested in the form.

You should receive your account ID and password withintwo days.

4. When you receive your account information, go back tothe CRC and select the �� link.

When prompted, fill in your User ID and password.

5. In the �� table under ��, select the red square opposite ! ��.

The �� ! �� "" !�� #��# �� page appears. Select the PTF orsoftware support you want from this page.

xxxxxxxx

9th ed., 313464701

vi ACSLS Installation and Configuration Guide for Solaris

How this Guide is Organized

This book contains the following information:

� Chapter 1. “Pre-installation Preparation”

� Chapter 2. “Installing Solaris”

� Chapter 3. “Installing and Configuring ACSLS”

� Chapter 4. “Completing the ACSLS Installation”

� Appendix A. “Utilities”

� Appendix B. “De-installing a Second Disk”

� Glossary

What’s New in This Guide

This guide contains the following new information for ACSLS 6.0:

� Added procedures for removing group and user IDs,Chapter 3 “Installing and Configuring ACSLS”, page 50

� Auto backup option changes to configuration options tablein Chapter 1 “Pre–installation Preparation”, page 7

� Minor updates to Solaris 7 and 8 installation procedures inChapter 2 “Installing and Configuring Solaris”

9th ed., 313464701

vii About this Book

Conventions for Reader Usability

Conventions are used to shorten and clarify explanations andexamples within this book.

The following typographical conventions are used in this book:

� Bold is used to introduce new or unfamiliar terminology,or it’s used in steps to indicate either an action or adecision the user has to make.

� �� $�� is used to indicate command names,filenames, and literal output by the computer.

� �� is used to indicate literal input tothe computer.

� �� is used to indicate that you mustsubstitute the actual value for a command parameter. Inthe following example, you would substitute your name forthe “username” parameter.

��

� A bar ( | ) is used to separate alternative parameter values.In the example shown below either username orsystemname must be entered.

�� % ��

� Brackets [ ] are used to indicate that a command parameteris optional.

� Ellipses ( ... ) are used to indicate that a command may berepeated multiple times.

� The use of mixed face characters (bold and not bold)indicates that not bold letters may be omitted to formabbreviations. For example, you may simply enter � whenexecuting the ��# command.

Typographic

9th ed., 313464701

viii ACSLS Installation and Configuration Guide for Solaris

Single keystrokes are represented by double brackets � �surrounding the key name. For example, press �ESC� indicatesthat you should press only the escape key.

Combined keystrokes use double brackets and the plus sign (+).The double brackets surround the key names and the plus sign isused to add the second keystroke. For example, press �ALT� +

�C� indicates that you should press the alternate key and the Ckey simultaneously.

The instruction to “press the �ENTER� key” is omitted from mostexamples, definitions, and explanations in this book.

For example, if the instructions asked you to “enter” ��, you would type in �� and press �ENTER�.

However, if the instructions asked you to “type” ��, you would type in �� and you would not press�ENTER�.

The following symbols are used to highlight text in this book.

Warning: Information necessary to keep you from damagingyour hardware or software.

Caution: Information necessary to keep you from corruptingyour data.

Hint: Information that can be used to shorten or simplify yourtask or that may simply be used as a reminder.

Note: Information that may be of special interest to you. Notesare also used to point out exceptions to rules or procedures.

Keys

Enter Command

Symbols

STOP

!

xxxxxxxx

9th ed., 313464701

ix About this Book

Technical Support

Refer to Requesting Help from Software Support for informationabout contacting StorageTek for technical support and forrequesting changes to software products.

Related Documentation

The following publications provide more information aboutACSLS 6.0.

� The ACSLS 6.0 Information CD–ROM, part number313464401, which is automatically shipped with the 6.0program package and provides PDF format of all theACSLS 6.0 publications.

� ACSLS Product Information that is provided in PDFformat on the ACSLS 6.0 Information CD-ROM and onthe StorageTek Customer Resource Center (CRC). See“ACSLS Information on the StorageTek CRC” on pagex for more information.

� ACSLS System Administrator’s Guide, which is providedin PDF format on the ACSLS 6.0 Information CD-ROMand on the CRC. Hardcopy can be ordered by contactingStorageTek at 1–800–436–5554. The hardcopy partnumber is 313464801.

� ACSLS Quick Reference, part number 313465001, which isautomatically shipped with the 6.0 program package.

� ACSLS Messages, which is provided in PDF format on theACSLS 6.0 Information CD-ROM and on the CRC.Hardcopy can be ordered by contacting StorageTek at1–800–436–5554. The hardcopy part number is313464901.

ACSLS 6.0Documentation

9th ed., 313464701

x ACSLS Installation and Configuration Guide for Solaris

In addition to the PDF collection on the ACSLS 6.0 InformationCD–ROM, the StorageTek CRC provides PDF collections forACSLS 6.0. Use the following procedure to access thesecollections on the StorageTek CRC.

To access ACSLS PDF collections on the StorageTekCRC:


��




4. When you receive your account information, go back tothe CRC and select the �� link.


5. In the �� table under&��, select the red square opposite ! ��.

The '�� &�� ! �� "" !�� #�� # �� page appears.Select the link for the PDF file of the ACSLS documentyou want.

ACSLSInformation on the

StorageTek CRC

9th ed., 313464701

xi About this Book

The StorageTek CRC provides PDF file format of many ofStorageTek’s ACS hardware publications. Use the followingprocedure to access these publications on the StorageTek CRC.

To access StorageTek ACS hardware documentationon the StorageTek CRC:


��




4. When you receive your account information, go back tothe CRC and select the link for the hardware productcategory you want (for example, (�� , (��&��)�, or �� ).


5. In the �� table that appears, under &��, selectthe red square opposite the product you want.

On the page that appears, select the link for the PDF file ofthe document you want.

ACS HardwareInformation on the

StorageTek CRC

9th ed., 313464701

xiii Document Effectivity

Document Effectivity

EC Number Date Doc KitNumber

EditionType

Effectivity

123273 May 2001 –––––– NinthEdition

This document applies toAutomated Cartridge SystemLibrary Software (ACSLS),Version 6.0

9th ed., 313464701

xv Contents

Contents

About this Book iii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACSLS Software iii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audience iii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reader’s Comments iv. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About the Software v. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . How this Guide is Organized vi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . What’s New in This Guide vi. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Conventions for Reader Usability vii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Typographic vii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Keys viii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Enter Command viii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Symbols viii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Technical Support ix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Related Documentation ix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ACSLS 6.0 Documentation ix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACSLS Information on the StorageTek CRC x. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ACS Hardware Information on the StorageTek CRC xi. . . . . . . . . . . . . . . . . . . . . . . . . . . .

Document Effectivity xiii. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1. Pre–installation Preparation 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for Solaris Installation 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing for ACSLS Installation 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning ACSLS Configuration Options 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Library Configuration Options 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Where To Go Next? 26. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up the Database 27. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Exporting the Database 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9th ed., 313464701

xvi ACSLS Installation and Configuration Guide for Solaris

Chapter 2. Installing and Configuring Solaris 31. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Solaris 7 Operating System 32. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the Solaris 8 Operating System 41. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3. Installing and Configuring ACSLS 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing Group and User IDs 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying Disk Space 51. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing ACSLS 52. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applying Maintenance to ACSLS 57. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring ACSLS 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Troubleshooting Library Connections 64. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 4. Completing the ACSLS Installation 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuring the Second Disk 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Space Required by ACSLS on the Second Disk 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Partitioning the Second Disk 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating the File Systems 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing ACSLS Second Disk Support 79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restarting ACSLS 81. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Importing the Database 82. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying the Imported Database and Library Configuration 84. . . . . . . . . . . . . . . . . . . . . . . . . Verifying ACSLS Software 87. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Verifying ACSLS 87. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Running ivp.sh to Verify ACSLS 89. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ACSLS Setup for Client Communication 90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Regressing to a Previous Version of ACSLS 90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix A. Utilities 91. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 91. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the ACSLS Database Utilities 92. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . bdb.acsss 93. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . db_export.sh 95. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . db_import.sh 98. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . kill.acsss 101. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . rc.acsss 102. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . sd_mgr.sh 103. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9th ed., 313464701

xvii Contents

Appendix B. De–installing a Second Disk 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . De-installing a Second Disk 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Restarting ACSLS 108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Glossary 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9th ed., 313464701

xix List of Figures

List of Figures

Figure 1. Dual LMU Connection Configuration 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2. Configuration Menu 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 3. Defining Primary Disk Partitions 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 4. Defining Secondary Disk Partitions 39. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 5. Defining Primary Disk Partitions 46. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 6. Defining Secondary Disk Partitions 47. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 7. Format Menu 71. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 8. Partition Menu 72. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 9. Partition Table 73. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 10. Second Disk Partition Table 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 11. Partition Menu 76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9th ed., 313464701

xxi List of Tables

List of Tables

Table 1. Pre-Installation Worksheet 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 2. ACSLS Configuration Options 8. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table 3. Library Configuration Options 25. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

9th ed., 313464701

1 Chapter 1. Pre–installation Preparation

Chapter 1. Pre–installation Preparation

Caution: You must complete the procedures in this chapterbefore installing Solaris or ACSLS.

Overview

This chapter describes how to prepare for installation of theSolaris operating system and for installation and configuration ofACSLS.

This chapter includes:

� Preparing for Solaris Installation

� Preparing for ACSLS Installation

� Planning ACSLS Configuration Options

� Planning Library Configuration Options

� Backing Up the Database

� Exporting the Database

!

9th ed., 313464701

2 ACSLS Installation and Configuration Guide for Solaris

Preparing for Solaris Installation

Before installing Solaris, complete the following steps:

1. Satisfy all requirements specified in Product Information(see “ACSLS Online Information on the StorageTekCRC” on page x) prior to installation of Solaris orACSLS.

2. Install the library hardware according to theStorageTek installation manuals. See “RelatedDocumentation” on page ix.

Caution: If you are installing a SCSI library, you mustconnect the server to the library before installing ACSLS.The �� script installs device drivers and kernelpatches. If the SCSI cable is not connected, the devicedriver installation fails.

3. Install the ACSLS server hardware according to thehardware manufacturer’s instructions.

4. Determine and record information about networkcommunication settings in the Your System Valuescolumn in Table 1. “Pre-Installation Worksheet.”

Caution: Consult your system administrator for assistancein obtaining this information. It is critical that thisinformation is correct in order for ACSLS to run properly.

!

!

9th ed., 313464701


Table 1. Pre-Installation Worksheet

Installation Options Your System Values

� Host Name

� Network Adapter

� Internet Protocol Address

� Name Service

� Network Mask

� Domain Name

� Gateway Address

� Name Server

� Subnets

� System Type

� Software Group

9th ed., 313464701


Preparing for ACSLS Installation

Before you install ACSLS, complete the following steps:

1. Verify that the server system hardware is properlyconfigured, connected, powered on, and ready.

2. If your installation includes a 9300 or 4400 library anda single LMU:

a. Connect the LMU to serial port-b, reserving port-afor a remote service modem.

b. If a modem is not used, connect both serial ports tothe LMU for redundant communications.

3. If your installation includes a 9300 or 4400 library anddual 9330 LMUs:

a. Refer to Serial Parallel Controller User’s Guide(Sun P.N. 800–6573–12) for installation instructionsof the serial parallel controller card and connection ofthe serial patch panel.

b. Attach the serial patch panel to the SBus slot on theserver.

c. From the serial patch panel, run 2 cables to eachLMU (see Figure 1).

........ .. .................................................. ..... ... ............

��

� ��

��

��

Figure 1. Dual LMU Connection Configuration

9th ed., 313464701


4. If your installation includes a SCSI library and:

a single-endedSCSI interface

� Verify proper SCSI cable terminatorattachment.

Make sure that the cable does not exceed2 meters between the server and the SCSIlibrary.

Note: The single-ended configurationallows the LSM to connect to the hostsystem bus. Noises on the system bus cancorrupt data bound for the system disk.Common sources of spurious noise shouldbe avoided, including:

Hot plugging devices on the SCSI bus.

Attaching cables that are not activelyterminated.

Powering down an attached peripheralwhile UNIX is running.

� Verify the proper SCSI target address.

Consult the appropriate SCSI hardwareoperator ’s guide for setting this address onthe LSM.

� Set the 97�� library at SCSI target 0,target 2, or target 5 for a standard Solarisplatform.

Typically, target 1 is reserved for a seconddisk, target 3 is reserved for a boot disk,target 4 is reserved for an external tapedevice, target 6 is reserved for aCD-ROM, and target 7 is reserved for aSCSI controller.

Note: If 1, 3, 4, 6, or 7 are alreadyreserved on your system, use 0, 2, or 5 foryour 97�� library.

a differentialSCSI interface

� Verify proper SCSI cable terminatorattachment.

Make sure the cable does not exceed 20meters.

9th ed., 313464701


5. Make sure that each attached LMU and LSM is fullyconfigured, powered on, and ready.

Note: The configuration script, ��*�� , will failunless all LMUs and LSMs are fully configured, poweredon, and ready.

6. Verify the SCSI library connection by doing thefollowing at the boot PROM environment:

��

�� !" �� # ��

��$��

�� %�� %�� &�' �(��

�� % �� %

�� " ��$��

)�� *+', �� $� �� !"

�� %�� # ��

$�� !" ��

7. Obtain the ACSLS 6.0 CD-ROM.

8. If you intend to use removable media for databasebackup, have a blank cartridge available for yourbackup tape device to complete the configurationprocess.

xxxxxxxx

9th ed., 313464701


Planning ACSLS Configuration Options

Figure 2 shows the Configuration menu. Descriptions of theACSLS configuration options 1 through 5 are found in Table 2.The Valid Selections column shows valid values for the option,with defaults shown in bold. Record the value you will use inthe Your Site’s Selection column for reference when youconfigure ACSLS using the procedures on page 58.

ACSLS feature configuration

Please enter the number followed by Return for yourchoice from the following menu to configure productbehavior in that area.

Press ? followed by the Return key for help.

1: Set CSI tuning variables 2: Set event logging variables 3: Set general product behavior variables 4: Set access control variables 5: Set automatic backup parameters 6: Rebuild Access Control information 7: Exit

Figure 2. Configuration Menu

9th ed., 313464701


Table 2. ACSLS Configuration OptionsConfigurationChoice Group

OptionPrompt

OptionDescription

Type ValidSelections

YourSite’s

Selection

+ �� ,

��

)��

��

��

�� ,

��

��

��

�� -./

Maximum timesthe CSI willretransmit amessage

Dynamic 5

+ �� ,

��

)��

0�1��

��

��

��

�, ��

��

-+23455/

Maximum timeoutinterval forpending requestsin CSI requestqueue

Dynamic 172800 sec-onds

600 to315360000

seconds

+ �� ,

��

)��

��

��

��

��)�

�� -6/

Minimum timeoutinterval betweenCSI attempts toestablish anetworkconnection

Dynamic 4

+ �� ,

��

)��

��

��

�� ( �

��

��

��

��

��

��

�, ��

��

��

( � ��

� ��

-(�'�/�

CSI acts as a TCPRPC server ((�'�)or not (7!��)

Static TRUE

FALSE

9th ed., 313464701



YourSite’s

Selection

ValidSelections

TypeOptionDescription

OptionPrompt

+ �� ,

��

)��

��

��

��

'&� ��

��

��

��

��

��

�, ��

��

��

'&� ��

� ��

-(�'�/�

CSI acts as a UDPRPC server ((�'�)or not (7!��)

Static TRUE

FALSE

9th ed., 313464701


Table 2. ACSLS Configuration Options

+ �� ,

��

)��

��

��

��

��

��

��

��

��

��

��

��

8!�9!:� �

��;��

,7*&'!�*�!�*

�<(*��!=��&>

-,7*&'!�*�!�*

�<(*��!=��&/�

Selecting the!�9!:� optionmeans that the portmapper shouldalways beinterrogated whenthe CSI is unableto send a messageto a client.Selecting the��;�� optionmeans that the portmapper shouldnever beinterrogated whenthe CSI is unableto send a responseto a client. Thisoption should beselected if clientsdon’t support aport mapper. Thedefault valueIF_DUAL_LAN_NOT_ENABLEDspecifies that theport mappershould beinterrogated onlyif dual LANsupport has notbeen enabled. Ifdual LAN supporthas been enabled,then it is assumedthat clients don’tsupport a portmapper. Choosingthis optionprovides forbackwardcompatibility inthe productbehavior.

Static IF_DUAL_LAN_NOT_ENABLED

ALWAYS

NEVER

9th ed., 313464701



YourSite’s

Selection

ValidSelections


OptionPrompt

3 �� )��

��

)��

��

�)��

��

�� -?/�

Number ofrollover event logfiles; see“SpecifyingOptions for Eventand Statistic Logs”on the followingpages.

Dynamic 9

0–9

3 �� )��

��

)��

��

��

��#

��

��

��

��

��

9��

��#

��

��

��

��

-@! �*A<0��

�� /�

Pathname fordirectorycontaining theevent log

Static $ACS_HOME/log

3 �� )��

��

)��

0�1��

��#

��)�� )��

�� B� ��

C�#��

8D+555

�#��>

-.55/�

Maximum eventlog size (Kb); see“SpecifyingOptions for Eventand Statistic Logs”on the followingpages.

Dynamic 500

32 or more

3 �� )��

��

)��

&��

��

��

-E:FE�FE�

EA�E0�E�/�

Date and timeformat for allACSLS logs andcommand andutility output

Dynamic The E:variable canspecify4–digit yearformats,which is thedefault

9th ed., 313464701



YourSite’s

Selection

ValidSelections


OptionPrompt

G ��

��

��

��)��

)��

��

��#

;��

��

$��

8<��<77>

-<77/�

Specifies ifvolume statisticsare logged.Logging thesestatistics can takeconsiderable diskspace; see“SpecifyingOptions for Eventand Statistic Logs”on the followingpages.

Dynamic OFF

<�

G ��

��

��

��)��

)��

��

��*��

��

�� -?/�

Number ofrollover statisticslog files; see“SpecifyingOptions for Eventand Statistic Logs”on the followingpages.

Dynamic 9

0–9

G ��

��

��

��)��

)��

0�1��

��#

��)��

��*��

�� B� ��

C�#��

8D+555

�#��>

-.55/�

Maximumstatistics log size(Kb); see“SpecifyingOptions for Eventand Statistic Logs”on the followingpages.

Dynamic 500

32K or more

9th ed., 313464701



YourSite’s

Selection

ValidSelections


OptionPrompt

G ��

��

��

��)��

)��

��

��

��

��

��

-;<�,&*�<�(/

Cleaning cartridgeordering forselection and��# ��

display:;<�,&*�<�( orderby �� !�(*'��& orderfrom least to mostused 0<�(* !�! ,(: orderfrom most to leastavailable cleaningcycles

Dynamic VO-LID_SORT

LEAST_USED

MOST_CAPACITY

9th ed., 313464701



YourSite’s

Selection

ValidSelections


OptionPrompt

G ��

��

��

��)��

)��

��

(��

!��

<��

8(�'��7!��>

-(�'�/�

When option is(�'� andtransport indicatescleaning isrequired, ACSLSwill automaticallyclean the transportbefore next mount((�'�) or not(7!��)

Note: You cannotuse the��*��

configurationprogram to enableauto-cleaning fordrives attached toSCSI–attachedLSMs. UsingACSLS, you canonly clean thesedrives by manuallymounting acleaning cartridge.The LSMhardware,however, lets youenableauto–cleaning viathe LSM controlpanel. For moreinformation, seeyour LSMdocumen-

tation.

Dynamic TRUE

FALSE

G ��

��

��

��)��

)��

��#

��)��

��

��

8�'��,&��>

-�'�/�

Initialize ACSLSin �'� or ,&��state

Static RUN

IDLE

9th ed., 313464701



YourSite’s

Selection

ValidSelections


OptionPrompt

G ��

��

��

��)��

)��

��

��

��

��

! ��

��

��

��

��

��

��

��

��

��

-3/�

Number of ACSLSpersistent mountprocesses; see“SpecifyingOptions forACSLS Processes”on the followingpages.

Static 2

1-10

G ��

��

��

��)��

)��

�� H'��:

��

��

8(�'��7!��>

-(�'�/�

(�'� specifies thatACSLS executesqueries as one ormore persistentprocesses. Use thefollowing optionto specify thenumber of querypersistentprocesses; see“SpecifyingOptions forACSLS Processes”on the followingpages.

Static TRUE

FALSE

9th ed., 313464701



YourSite’s

Selection

ValidSelections


OptionPrompt

G ��

��

��

��)��

)��

��

��

�� #

��

�� ! ��

��

��

��

��

��

��

��

��#

��

��

-3/�

Number of ACSLSquery persistentprocesses; see“SpecifyingOptions forACSLS Processes”on the followingpages.

Static 2

1-10

G ��

��

��

��)��

)��

��

�� 1��

��

! ��

��

��

��

��

��

��

0�1��

��

! ��

��

-65/�

Maximum ACSLStransientprocesses; see“SpecifyingOptions forACSLS Processes”on the followingpages.

Static 40

32 and above

G ��

��

��

��)��

)��

��

��

��

��

��#

8(�'��7!��>

-7!��/�

Log automaticmode enters in theevent log ((�'�) ornot (7!��)

Dynamic FALSE

TRUE

9th ed., 313464701



YourSite’s

Selection

ValidSelections


OptionPrompt

G ��

��

��

��)��

)��

��

)��

��

��#

8(�'��7!��>

-7!��/�

Log databasevolume additionsand deletions in theevent log ((�'�) ornot (7!��)

Dynamic FALSE

TRUE

G ��

��

��

��)��

)��

&��

��

��)��

A��

�1��

�� )��

-+/�

Controls thedatabase isolationlevel

See “SpecifyingOptions forIsolation Levels”on the followingpages.

Static 0-3

6 ��

��

��

)��

��

��

��

��

��

��

��

�

��

!��

��

��)� ��

��

8(�'��7!��>

-7!��/�

Enable commandaccess control((�'�) or not(7!��)

Static FALSE

TRUE

6 ��

��

��

)��

&��

��

��

8! ��

�<! ��>

-! ��/�

If no accesscontrol files,enable defaultcommand access(! ��) or not(�<! ��)

Dynamic ACCESS

NOACCESS

9th ed., 313464701



YourSite’s

Selection

ValidSelections


OptionPrompt

6 ��

��

��

)��

0��

��

��

��

��

)��

��

8(�'��7!��>

-7!��/�

Log command andvolume !��&�� messagesin event log ((�'�)or (7!��)

Dynamic FALSE

TRUE

. ��

��

��

��

9�� #��

��

��# ��

��

��

�� I

8# �� >�

Allows you tochange the defaultautomatic backupschedule, which isset to do a backupevery day atmidnight.Note: Automaticbackups andmanual backupsneed not be doneon the same day.

Dynamic � or �

If you respond�, you arefurtherprompted forthe day andthe time youwant to haveautomaticbackups.

. ��

��

��

��

��

��

��

��

�� ,�0

��)��

��

A��

�1��

-4/�

You select theperiod of time thatyou will retainbackups on localdisk. You canselect a periodbetween 4 and 30days. See “Settingthe RetentionPeriod” on thefollowing pages.

Dynamic Between 4and 30

9th ed., 313464701


Specifying Options for Event and Statistics Logs

The ��*�� configuration program lets you specifyoptions for file size and number of rollover files for the event log(��*�)�� ) and the volume statistics log(��*�� ) as follows:

� You can specify the number of rollover log files to“journal” entries when the base log file reaches maximumsize. If you specify 0, ACSLS creates only one base logfile with no rollover files. You must manually manage thisbase log file, which has no maximum size. If you specify0 rollover log files and also specify a maximum size forthe volume statistics log, ACSLS logs warning messagesin the event log if the log file exceeds the specifiedmaximum size.

Alternatively, you can specify 1 to 9 rollover log files.Rollover log files provide a history to ensure that youcapture all log entries and can more easily locate specificlog entries. For example, if you specify 2 rollover files forvolume statistics logging, when the ��*�� (base) file reaches maximum size, ACSLS renames it tothe first rollover file ()��5�� ), then starts a new��*�� file. When the ��*�� fileagain reaches maximum size, ACSLS renames the)��5�� file to )��+�� , renames��*�� to )��5�� , and starts a new��*�� file. When all rollover files containdata and another rollover occurs, the highest numberedrollover file will be discarded.

� You can specify the maximum log file size; this maximumapplies to both the base log and rollover log files. If youspecify rollover log files, you can typically specify asmaller maximum file size (that applies to both base logand rollover files) than the maximum file size you wouldspecify for a base log only, which must be large enough tocontain enough meaningful entries.

9th ed., 313464701


Specifying Options for ACSLS Processes

Note that the Solaris system limit on processes per user is thelimit for the total number of the following processes:

� ACSLS system persistent

� CSI (1)

� ACSLS transient (specified via ��*�� )

� ACSLS query persistent (specified via ��*�� )

� ACSLS mount persistent (specified via ��*�� )

For the ACSLS transient, query persistent, and mount persistentprocess options, StorageTek recommends that you accept thedefault value at initial configuration, then change the value asrequired. Increasing this value may improve performance.

Warning: With a minimum server platform configuration,higher than 10 query persistent processes could use up systemresources and not allow ACSLS to start up.

If the total number of all the processes listed above exceeds theSolaris system limit on processes per user, ACSLS may fail tostart. If this happens, either increase the system limit onprocesses per user or lower one or more of the values for theACSLS process options that you can specify via ��*�� .

STOP

9th ed., 313464701


Specifying Options for Isolation Levels

The isolation level is used to define the degree of concurrencyamong processes that attempt to access the same rowssimultaneously in Informix Database. The database isolationlevel affects read concurrency when rows are retrieved from thedatabase as in queries and volume reports. The database serveruses shared locks to support different levels of isolation amongprocesses attempting to access data. The update or delete processalways acquires an exclusive lock on the row that is beingmodified. The level of isolation does not interfere with rows thatare being updated or deleted. If another process attempts toupdate or delete rows that are being read with an isolation levelof Repeatable Read, that process is denied access to those rows.

0 – Dirty ReadProvides zero isolation. Dirty Read is appropriate for statictables that are used for queries. With a Dirty Read isolationlevel, a query might return a phantom row, which is anuncommitted row that was inserted or modified within atransaction that has subsequently rolled back. No otherisolation level allows access to a phantom row. Dirty Readis the only isolation level available to databases that do nothave transactions.

1 – Committed Read (default isolation level)Guarantees that every retrieved row is committed in thetable at the time that the row is retrieved. Even so, no locksare acquired. After one process retrieves a row because nolock is held on the row, another process can acquire anexclusive lock on the same row and modify or delete datain the row. Committed Read is the default level of isolationin a database with logging that is not ANSI compliant.

9th ed., 313464701


2 – Cursor StabilityAcquires a shared lock on the selected row. Anotherprocess can also acquire a shared lock on the same row, butno process can acquire an exclusive lock to modify data inthe row. When you fetch another row or close the cursor,the database server releases the shared lock. If you set theisolation level to Cursor Stability, but you are not using atransaction, the Cursor Stability isolation level acts like theCommitted Read isolation level. Locks are acquired whenthe isolation level is set to Cursor Stability outside atransaction, but they are released immediately at the end ofthe statement that reads the row.

3 – Repeatable ReadAcquires a shared lock on every row that is selected duringthe transaction. Another process can also acquire a sharedlock on a selected row, but no other process can modifyany selected row during your transaction or insert a rowthat meets the search criteria of your query during yourtransaction. If you repeat the query during the transaction,you reread the same information. The shared locks arereleased only when the transaction commits or rolls back.Repeatable Read is the default isolation level in anANSI–compliant database.

9th ed., 313464701


Setting the Retention Period

The retention period is the period of time for which you retainbackups. You should note that ACSLS 6.0 changes the backupmanagement from previous ACSLS releases. In previousreleases, ACSLS deleted transaction log files at the time of abackup and reclaimed the space used for log files. In ACSLS6.0, transaction log files are retained with each backup,increasing the space needed in the backup partition. Whenchoosing a retention period, consider the following conditionsspecific to your site:

� The size and activity of your library

� The number of automatic and manual backups performedin a given period of time

Notes:

� When you run a manual backup with the bdb.acsssutility, an automatic backup to local disk is alsodone, thereby increasing the number of backups inthe backup partition.

� The retention period should be greater than theinterval between backups. For example, if you have aretention period of four days, you should takeautomated or manual backups at least three times aweek, with no more than three days betweenbackups.

� The period of time for which you would like to retainbackups and transaction log files, keeping in mind thatlong retention periods increase the space needed in thebackup partition.

� The size of your backup partition

For example, if you have a large library, a lot of library activity,frequent backups, a small partition size, and your retentionperiod is set to the maximum, your backup partition is likely tofill up. If your backup partition is full, the Informix databasewill be unable to offload transaction logs, and all database and

xxxxxxxx

9th ed., 313464701


ACSLS activity will wait until space on the backup partition isfreed up. (You are issued a warning message when the backuppartition reaches 85% full.) In this scenario, you may want to setyour retention period to a shorter period of time. In general, theretention period should be set to an acceptable period of time forretaining backups, but without the risk of filling up the backuppartition.

9th ed., 313464701


Planning Library Configuration Options

Descriptions of library configuration options are found in Table3. The Valid Selections column shows valid values for theoption, with defaults shown in bold. Record the value you willuse in the Your Site’s Selection column for reference when youconfigure ACSLS using the procedures on page 58.

Table 3. Library Configuration Options

Option Prompt Option Description Valid Selections Your Site’s Selection

�� ! � ��

��

Specifies the numberof ACSs in the libraryconfiguration.

A number between 1and 127

��

�� ! �

��

Number ofconnections to eachACS. This promptappears for eachconfigured ACS. Youmust specify at leastone connection perACS.

A number between 1and 16, typically 1 or 2

(1 for SCSI devices)

&�)�� " ! �

�� )��

Full path name of thedevice attached to aport. This optionappears for each portin the library.

Recommended pathnames:

Solaris platform:

��)��#�

��)��#�

��)��

(� can be 0 to 15)

9th ed., 313464701


Where To Go Next?

The remainder of this chapter contains procedures to completepre-installation preparation. These procedures include:

� Backing Up the Database

� Exporting the Database

Complete these procedures only if you are upgrading from aprevious version of ACSLS. If you are doing a new installationof ACSLS, skip this section and go to Chapter 2.

9th ed., 313464701


Backing Up the Database

Hint: Doing a backup prior to upgrading or switching platformsis for disaster recovery in the event that there is a need to returnto the current state.

You will need two blank tapes, one for this backup procedureand one for the export procedure following it.

The following procedure describes how to shut down ACSLSand back up your existing database to tape.

To back up the database:

1. Open a command tool and log in as ��.

2. From the cmd_proc window, idle ACSLS.

��

Wait for the following message before you proceed.

��)�� #��

3. Open another command tool and log in as ��.

4. Shut down ACSLS.

��

5. Load a blank cartridge into the drive.

6. To back up the database, enter

$�$��

7. Remove the cartridge from the drive after the programfinishes.

Caution: You will lose files if you remove the cartridgebefore the program finishes. Write protect the cartridgeand clearly mark it to identify the contents as the backedup database.

!

9th ed., 313464701


Exporting the Database

This section describes how to migrate the database table data ofa previous version of ACSLS to ACSLS 6.0. See ACSLSProduct Information for information about which previousversions of ACSLS are upgradable to 6.0. The ��*�1��utility creates an ASCII representation of the database on tape.It is used by ��*�� at the time of an upgrade to transferexisting data instead of auditing a library.

The procedures outlined below are for exporting the database totape for default tape devices.

Hint: Refer to Appendix A for instructions on exporting thedatabase to disk.

Warning: You must use the ��*�1�� and ��*��utilities if you are upgrading to ACSLS 6.0. Refer to Appendix A “Utilities” for more information about using theseutilities.

1. From a command tool log in as ��.

2. From the ��*�� window, idle ACSLS:

��


4. Shut down ACSLS:

��

5. Shut down the database:

�$-�� &�� (�� .�/�0 ��

��1�

�$-�� &�� (�� .�2

6. Insert a blank tape into the default tape device.

STOP

9th ed., 313464701


7. Start the ��*�1�� utility:

�$-3��

As it executes, the utility displays output indicatingsuccessful table data being exported.

8. Remove the cartridge from the drive only when theprogram completes and the prompt re-appears.

Caution: You will lose files if you remove the cartridgebefore the program completes the backup. Write protectthe cartridge and clearly mark it to identify the contents asthe exported database.

!

9th ed., 313464701

31 Chapter 2. Installing and Configuring Solaris

Chapter 2. Installing and Configuring Solaris

ACSLS 6.0 supports Solaris 7 and 8. StorageTek does notsupport down level versions of the operating system. Thischapter describes separate procedures for configuring Solaris 7and Solaris 8 for ACSLS.

� To install Solaris 7, go to page 32

� To install Solaris 8, go to page 41

Hint: Solaris 7 works in 64-bit support. Solaris 8 works only in32- bit support.

Warning: Before installing Solaris, you must complete Chapter1 “Pre-installation Preparation.”STOP

9th ed., 313464701


Installing the Solaris 7 Operating System

Hint: While installing the Solaris operating system, refer toTable 1. “Pre-Installation Worksheet” on page 3 for the networkcommunication settings recorded during pre-installationpreparation.

To install the Solaris 7 operating system:

1. Boot your system from the CD–ROM containing theSolaris operating system:

a. Press �STOP�+A.

b. Insert the Solaris CD-ROM into the CD-ROM drive.

c. From the �� prompt, enter

$��

Press �ENTER�.

Note: If you have configured the SCSI/Ethernet card onan Ultra 10 and you are not using the second Ethernetconnection, then disregard the message, “home1: linkdown”.

Hint: The �� ,�� will appear first.During the installation process, this console providesmessages indicating what the system is doing.

2. Select Language and Locale options, and press ��.

Within five minutes the �� ,�� screen displays.

3. Press �� twice to get to the A�� screen.

4. Enter the Host Name for your system and press ��.

5. Answer :� to the prompt �� :�� andpress ��.

xxxxxxxx

9th ed., 313464701


6. Does your system have multiple networked Ethernetcontroller systems?

YES At the prompt, specify which network adapter(usually ��5 for a SPARC 5 or ��5 for an Ultra10) is the system’s primary network interface.Press ��.

Go to Step 7.

NO Go to Step 7.

7. Enter your IP address and press ��.

8. Confirm the A�� , ��I, and ,� ��in the �� ,�� screen, and press ��.

9. Select the type of name server used in your system inthe �� )�� screen, and press ��.

Note: Do not select the �,�J or �,� services unless yoursystem administrator can configure these services correctly.

Note: If either �,�J or �,� is selected, a number ofdifferent prompts appear. Respond to these promptsappropriately.

10. Confirm the �� )�� in the ��,�� screen, and press ��.

11. Select #� in �� screen.

Enter your netmask and press ��.

12. Select :� or �� in the �� screen.

If you selected :�, the �� screen appears. Enteryour Netmask and press ��.

13. Specify your timezone type in the (�� K�� screen andclick ��.

xxxxxxxx

xxxxxxxx

9th ed., 313464701


14. Enter the current date and time in the &�� (��screen and press ��.

15. Press �� on the �� ,�� screen.

The �� ,��)� ,�� screendisplays.

16. The first �� ,��)� ,�� screendescribes the differences between an initial installationand a Solaris upgrade.

17. Press ,��.

18. The second �� ,��)� ,��screen describes what occurs during an initial install.Press ��.

19. Press �� on the !�� )��screen.

20. Press �� on �� screen.

21. Select �� '�� #�� in the �� screen, and press ��B�.

The ��B� �� screen appears displaying the�� window.

Note: Steps 22 through 25 refer to customization of the�� window in the ��B� �� screen.

xxxxxxxx

9th ed., 313464701


Hint: In the �� window, an item is selected when the square preceding it iscompletely blacked out. Some items may already beselected by the system. Make sure that you do not deselectthese items by clicking on items already blacked out.

Deselected Partial Selected Selected

22. Scroll down and locate <�F�� 0�� in the�� window. Click onceto select the 0�� .

23. Continue scrolling down and locate <��9��;�� G in the �� window. Click twice to fully select that option.

24. Continue to scroll down through the main directory to�� .

a. Click on the triangular arrow ( �� )in the left margin of �� to expand the subdirectory.

b. Select � �� <�.

c. Click on the triangular arrow ( �� )in the left margin of �� to close the subdirectory.

25. Press <C to exit the ��B� �� screen.

26. Press <C on the warning box.

27. Press �� when the �� screendisplays.

The �� &�� screen displays.

9th ed., 313464701


28. If the boot disk is displayed in the !)�� &��window, select it, then press the single-right-arrowbutton to move it to the “Selected disks” column.

29. Press �� on the �� &�� screen.

The ��)� &�� screen displays.

30. Press �� for a new installation and/or tooverwrite current file systems and unnamed filesystems. (Press ��)�� to preserve existing dataduring an upgrade installation.)

31. Press 0�� #�� in the !��# ��#��7�� #��I screen.

32. Press ��B� in the 7�� #�� &�� #��screen to define disk partitions for ACSLS.

The ��B� &�� screen displays.

9th ed., 313464701


33. Define two disk partitions for the database.

Note: The product is designed for ACSLS to reside in��1��. If you install ACSLS in another directory,every command you enter that uses ��1�� must bechanged to that directory. However, ��1�� muststill exist because the database installs all its files in thatdirectory.

Enter the values specified in bold in Figure 3 to defineprimary disk partitions for the database:

� Assign the mount point for each of the eightpartitions in the left column.

� Assign the size for each slice in the right columnexcept for ��1��.

Do not make �� any smaller than 50 MB.

Swap space must be no smaller than 300 MB.

The size of �� must be at least 700 MB.

��1�� must be at least:

550 MB for a 2.1 GB disk

800 MB for a 9 GB or larger disk

For information about determining the size of yourprimary and secondary disks, see ACSLS ProductInformation, “Determining Disk Size Requirements”.

� Assign ��1�� last. Assign��1�� the amount displayed in 7��after entering all other values. You should have noless than:


6 GB for a 9 GB disk

~25 GB for a 27 GB disk

xxxxxxxx

9th ed., 313464701


0 / .4 5�

1

2

3

4

5

6

7

/44 5�

24 5�

24 5�

644 5�

�1��

�(��

7(��

73��7��

7��

7��

73��7$��

Capacity: disk size

Allocated: ��MB or GBFree: ��MB or GB

Disk: c0t0d0

Based on disk size

Based on disk size

Based on disk size

Figure 3. Defining Primary Disk Partitions

Enter the values specified in bold in Figure 4 to definesecondary disk partitions for the database.

� Assign 256 MB to ��*�� for all disk sizes.

� ��*�� should be at least:

~1.7 GB for a 2.1 GB disk

~8.7 GB for a 9 GB disk


9th ed., 313464701


0 ��*�� 0.8 5�

1

Capacity: disk size


��*��

2 �)��

Disk: c0t1d0

Based on disk size

Based on disk size

Figure 4. Defining Secondary Disk Partitions

34. Press <C after you have filled out the ��B� &��screen.

The 7�� #�� &�� #�� screen appears.

35. Are the file systems and disk layout correct in the 7��#�� &�� #�� screen?

YES Press �� to accept the layout displayed.

NO Press ��B� to change the file system orlayout information.

36. Press �� in the 0�� 7�� #��Iscreen.

37. Verify that the �� screen displays theconfiguration that you want and press =� ��,��.

38. Press !�� in the next screen.

The installation process takes from 30 minutes to 2 hoursdepending on the speed of the CD–ROM drive. Thesystem activities can be monitored by following themessages in the �� ,�� and by the,�� " �� screen,which shows the progress with a sliding bar.

9th ed., 313464701


39. When the installation is complete, the system rebootsand prompts for a password. Enter a password.Reenter the same password at the prompt to verify.

The system then returns to the login prompt.

40. Log in as ��.

41. Press � to the question &� #�� F��)�� I

42. In a command tool, enter

9��

43. Remove and store the CD–ROM.

Complete the installation by editing the �� file to addthe name of the host(s) and the IP address(es).

44. Change directories to the /etc directory.

�� 7��

45. Edit the �� file: add the name of each client and theIP address of each client to the end of the file.

46. At the system prompt enter �% � to verify thefollowing:

� The total KB space available is at least 550000 forthe ��1�� file system for the database. ��1�� will contain the contents of theinstallation media. See Step 33 for suggested sizes of��1�� for different disk sizes.

� The total space available for ��1�� is atleast 400000 KB for the database. See Step 33 forsuggested sizes of ��1�� for different disksizes.

9th ed., 313464701


Installing the Solaris 8 Operating System

Hint: While installing the Solaris operating system, refer toTable 1. “Pre-Installation Worksheet” on page 3 for the networkcommunication settings recorded during pre-installationpreparation.

To install the Solaris 8 operating system:

1. Boot your system from the CD–ROM containing theSolaris operating system:

a. Press �STOP�+A.

b. Insert the Solaris CD-ROM (�� 4 ��)into the CD-ROM drive.

c. From the �� prompt, enter

$��

Press �ENTER�.

Note: If you have configured the SCSI/Ethernet card onan Ultra 10 and you are not using the second Ethernetconnection, then disregard the message, “home1: linkdown”.

Hint: The �� ,�� will appear first.During the installation process, this console providesmessages indicating what the system is doing.

2. Select Language and Locale options.

Within five minutes the �� ,�� screen displays.

3. In the �� )��# screen, select #� andthen ��.

4. In the &A � screen, select �� and ��.

5. In the ��# �� ,�� screen, select ��5and then ��.

xxxxxxxx

9th ed., 313464701


6. In the A�� screen, enter the Host Name for yoursystem and press ��.

7. Enter your IP address and press ��.

8. Select �� to enable IPv6 and press ��.

9. Confirm the A�� , ��I, and ,� ��in the �� ,�� screen, and press ��.

10. Select �� for �� # ��# and press ��. Then confirm security information.

11. Select the type of name server used in your system inthe �� )�� screen, and press ��.

Note: Do not select the �,�J or �,� services unless yoursystem administrator can configure these services correctly.

Note: If either �,�J or �,� is selected, a number ofdifferent prompts appear. Respond to these promptsappropriately.

12. Confirm the �� )�� in the ��,�� screen, and press ��.

13. Select #� in �� screen.

Enter your netmask and press ��.

14. Select :� or �� in the �� screen.

If you selected :�, the �� screen appears. Enteryour Netmask and press ��.

15. Specify your timezone type in the (�� K�� screen andclick ��.

16. Enter the current date and time in the &�� (��screen and press ��.

xxxxxxxx

xxxxxxxx

9th ed., 313464701


17. Press �� on the �� ,�� screen.

The �� ,��)� ,�� screendisplays.

18. The first �� ,��)� ,�� screendescribes the differences between an initial installationand a Solaris upgrade. Press ,��.

19. The second �� ,��)� ,��screen describes what occurs during an initial install.Press ��.

20. Select your regions in the �� $�� screen and press ��.

21. Select �� '�� #�� in the �� screen.

22. Deselect �� ,�� L6 =�� to enable 32 bit support. The box is light when it isdeselected.

23. Press ��B�.

The ��B� �� screen appears displaying the�� window.

Hint: In the �� window, an item is selected when the square preceding it iscompletely blacked out. Some items may already beselected by the system. Make sure that you do not deselectthese items by clicking on items already blacked out.

Deselected Partial Selected Selected

24. Scroll down and locate <�F�� 0�� in the�� window. Click onceto select the 0�� .

9th ed., 313464701


25. Continue scrolling down and locate <��9��;�� G in the �� window. Click twice to fully select that option.

26. Continue to scroll down through the main directory to�� .

a. Click on the triangular arrow ( �� )in the left margin of �� to expand the subdirectory.

b. Select � �� <�.

c. Click on the triangular arrow ( �� )in the left margin of �� to close the subdirectory.

27. Press <C to exit the ��B� �� screen.

28. Press �� when the �� screendisplays.

The �� &�� screen displays.

29. If the boot disk is displayed in the !)�� &��window, select it, then press the single-right-arrowbutton to move it to the “Selected disks” column.

30. Press �� on the �� &�� screen.

The ��)� &��I screen displays.

31. Press �� for a new installation and/or tooverwrite current file systems and unnamed filesystems. (Press ��)�� to preserve existing dataduring an upgrade installation.)

32. Press 0�� #�� in the !��# ��#��7�� #��I screen.

33. Press ��B� in the 7�� #�� &�� #��screen to define disk partitions for ACSLS.

The ��B� &�� screen displays.

9th ed., 313464701


34. Define two disk partitions for the database.

Note: The product is designed for ACSLS to reside in��1��. If you install ACSLS in another directory,every command you enter that uses ��1�� must bechanged to that directory. However, ��1�� muststill exist because the database installs all its files in thatdirectory.

Enter the values specified in bold in Figure 3 to defineprimary disk partitions for the database:

� Assign the mount point for each of the eightpartitions in the left column.

� Assign the size for each slice in the right columnexcept for ��1��.

Do not make �� any smaller than 50 MB.

Swap space must be no smaller than 300 MB.

The size of �� must be at least 700 MB.

��1�� must be at least:


800 MB for a 9 GB or larger disk

For information about determining the size of yourprimary and secondary disks, see ACSLS ProductInformation, “Determining Disk Size Requirements”.

� Assign ��1�� last. Assign��1�� the amount displayed in 7��after entering all other values. You should have noless than:


6 GB for a 9 GB disk

~25 GB for a 27 GB disk

xxxxxxxx

9th ed., 313464701


0 / .4 5�

1

2

3

4

5

6

7

/44 5�

24 5�

24 5�

644 5�

�1��

�(��

7(��

73��7��

7��

7��

73��7$��

Capacity: disk size


Disk: c0t0d0

Based on disk size

Based on disk size

Based on disk size

Figure 5. Defining Primary Disk Partitions

Enter the values specified in bold in Figure 4 to definesecondary disk partitions for the database.

� Assign 256 MB to ��*�� for all disk sizes.

� ��*�� should be at least:

~1.7 GB for a 2.1 GB disk



9th ed., 313464701


0 ��*�� 0.8 5�

1

Capacity: disk size


��*��

2 �)��

Disk: c0t1d0

Based on disk size

Based on disk size

Figure 6. Defining Secondary Disk Partitions

35. Press <C after you have filled out the ��B� &��screen.

The 7�� #�� &�� #�� screen appears.

36. Are the file systems and disk layout correct in the 7��#�� &�� #�� screen?

YES Press �� to accept the layout displayed.

NO Press ��B� to change the file system orlayout information.

37. Press �� in the 0�� 7�� #��Iscreen.

38. Verify that the �� screen displays theconfiguration that you want and press =� ��,��.

39. Press !�� in the next screen.

The installation process takes from 30 minutes to 2 hoursdepending on the speed of the CD–ROM drive. Thesystem activities can be monitored by following themessages in the �� ,�� and by the,�� " �� screen,which shows the progress with a sliding bar.

9th ed., 313464701


40. When the installation is complete, the system rebootsand prompts for a password. Enter a password.Reenter the same password at the prompt to verify.

The system then returns to the login prompt.


42. Press � to the question &� #�� F��)�� I

43. In a command tool, enter

9��

44. Remove and store the CD–ROM.

Complete the installation by editing the �� file to addthe name of the host(s) and the IP address(es).

45. Change directories to the /etc directory.

�� 7��

46. Edit the �� file: add the name of each client and theIP address of each client to the end of the file.


� The total KB space available is at least 550000 forthe ��1�� file system for the database. ��1�� will contain the contents of theinstallation media. See Step 33 for suggested sizes of��1�� for different disk sizes.

� The total space available for ��1�� is atleast 400000 KB for the database. See Step 34 forsuggested sizes of ��1�� for different disksizes.

9th ed., 313464701

49 Chapter 3. Installing and Configuring ACSLS

Chapter 3. Installing and ConfiguringACSLS

Warning: Before installing ACSLS 6.0, you must:

1. Export the database, if this is an upgrade installation (seeChapter 1)

2. Install and configure Solaris (see Chapter 2)

Note: StorageTek does not support ACSLS 6.0 running onunsupported versions of the operating system. ACSLS 6.0supports Solaris 7 and 8 only.

3. Do the following before installing ACSLS if you areupgrading from ACSLS 5.3, 5.3.2 or 5.4 and you alreadyhad Solaris 7or 8 installed:

Remove group and user IDs on page 50 from the ��directories.

STOP

xxxxxxxx

9th ed., 313464701


Overview

This chapter describes how to install and configure ACSLS on aSolaris platform. It includes:

� Removing group and user IDs

� Verifying disk space

� Installing ACSLS

� Configuring ACSLS

� Troubleshooting Library Connections

Removing Group and User IDs

Before you install ACSLS 6.0, you must remove certain groupand user IDs if you are upgrading from ACSLS 5.3, 5.3.2, or 5.4and you already had Solaris 7 or 8 installed.

To remove the IDs:

1. Log in as root.

2. Bring up the Administration Tool by entering:

��

An interactive window displays.

3. From the menu select Browse –> Users

4. Check for the value 11 under the '�� ,& column.Scroll down if necessary.

5. If you find 11 and you decide to delete, select Edit –> Delete.

6. From the menu select Browse –> Groups.

9th ed., 313464701


7. Check for the value 106 under the Group ID column.Scroll down if necessary.

8. If you find the value 106 and you decide to delete, selectEdit –> Delete.

9. From the menu select File –> Exit to exit the tool.

10. Reboot the server.

11. Go to “Verifying Disk Space” on page 51.

Verifying Disk Space

Before installing ACSLS, verify that the hard disk waspartitioned appropriately when the operating system wasinstalled and configured.

To verify disk partitions:


� The total KB space available for the ��1��file system, where ACSLS will reside, is at least:

550000 KB for a 2.1 GB disk

800000 KB for a 9 GB disk


� The total KB space available for ��1�� isat least:

400000 KB for a 2.1 GB disk



9th ed., 313464701


Installing ACSLS

To install ACSLS:


2. Is this a new installation?

YES Go to Step 9.

NO Make sure you exported the database in Chapter 1.

Complete Steps 3, 4, 5, 6, and 7 below.

Then continue with Step 9.

3. Deinstall second disk support:

See Appendix A of this book for instructions.

4. Shut down ACSLS and the database:

�� 8from a cmd_proc)�� (from a command tool)

If you are upgrading from ACSLS 5.3 or 5.3.2, enter thefollowing command:

�$-��

If you are upgrading from ACSLS 5.4, enter the followingcommand:

�$-��

5. Enter the following:

�� 73��7��

If you installed ACSLS in another directory other than/export/home, cd to that directory.

9th ed., 313464701


6. Remove ACSLS files and database files:

If you are upgrading from ACSLS 5.3 or 5.3.2:

� Enter: � ��% �&��

� cd to ��1�� and enter: � ��% ��

If you are upgrading from ACSLS 5.4:

� Enter: � ��% �&�� $��

� cd to ��1�� and enter: � ��% ��$��

If you are upgrading from 5.3, 5.3.2, or 5.4:

� cd to ��*�� and remove alldirectories there

7. Reboot by entering:

�$��


9. Insert the ACSLS 6.0 CD-ROM.

Note: If the Solaris operating system CD or the SolarisCDE CD is still in the drive, enter 9�� . Removethe CD and store it.

10. In a terminal window or at the system prompt, enter

�� 7�� 7�� 47�� 4

xxxxxxxx

9th ed., 313464701


11. To initiate the installation shell script, enter

�7��

If shared memory settings have not been defined, you areprompted to allow the script to set shared memory andreboot the server:

(�� )�� #

�� ! �� &��

�� # �� )��

�� )��I 8# �� >�

Respond � to the prompt.

The server reboots.

When the server comes back, log in as �� and restartinstall.sh.The shell script completes processing in ten to twentyminutes.

12. If you installed Solaris 8, you may get this message:

�� +.6?� 9�� .4 ��# ��

�� " #��

��

Ignore the message if you installed Solaris 8 with 32–bitsupport and proceed with the ACSLS installation.

13. Enter � or � at the prompt to install ACSLS in thedefault directory ��1��.Use the default directory ��1�� or enter thedirectory where you want ACSLS installed.

Note: If you install ACSLS in a directory other than��1��, every command you enter that uses��1�� must be changed to that directory.

xxxxxxxx

9th ed., 313464701


14. Press �ENTER� to accept the default directory��1�� for database backups.

Caution: During this time the CD drive may appear idle,without sound or flashing lights. DO NOT remove theCD from the drive until the installation is complete.

15. Respond � or � to the prompt for automatic startup onreboot.

&� #�� #�� #��

�� M �� # ��

! ��I 8# �� >

Building the mchanger Driver (Steps 16 and 17)

16. Respond (y or n) to the prompt for installing a SCSIdevice driver for SCSI libraries.

&� #�� )�� )��

�� , ��I 8# �� >�

YES The following message displays:

�� , ��)��8> ��

�� # �� )��

�� 8�1�� 6 . L> �� ,

��)�� 5 �� +.

Notes:

� On most Solaris machines, target-7 is not a validdevice address because target-7 is reserved forthe SCSI initiator on the host-bus adapter.

� If you are not sure what numbers to enter in thisStep, follow the procedure in Step 6 of thesection “Preparing for ACSLS Installation” inChapter 1.

Continue with Step 17.

NO Go to Step 19.

!

9th ed., 313464701


17. Respond (y or n) to the prompt after the specified SCSIdevice numbers display.

, �� I 8# �� >�

18. You see the following message:

�� +.5+� :��

�� # �� '�,N

�� O�� 1��! ��P

��*� ��Q

You can enable second disk support after you complete theprocedures in this chapter. See Chapter 4 for steps onenabling second disk. See Appendix B for steps ondisabling second disk support.

19. Respond � or � to the prompt for adding a modem.

9�� #��

��)��#�I 8# �� >�

StorageTek recommends that you attach a modem.

20. Enter � to the following prompt for rebooting:

,� ��

#�� I 8# �� >�

Warning: You must reboot for kernel changes to takeplace and in order to configure and run ACSLS.


22. Enter

9��

23. Remove and store the ACSLS 6.0 CD-ROM.

Warning: Installation is not complete at this point.Complete this chapter and Chapter 4 to ensure that allnecessary procedures are done prior to running ACSLS.

STOP

STOP

9th ed., 313464701


Applying Maintenance to ACSLS

Before you configure ACSLS, please check the StorageTek CRCweb page to see whether there is any maintenance for thisrelease. If there is any maintenance, please download it andapply the most current PUTs, SPEs, or PTFs.

To apply the maintenance, refer to the installation instructions inthe associated PUT or SPE or PTF document included with thePUT CD–ROM, or the document associated with themaintenance tar file on the StorageTek Customer ResourceCenter (CRC) web page.

9th ed., 313464701


Configuring ACSLS

To configure ACSLS:

1. Exit from the desktop.


3. At the password prompt, press �ENTER�.

4. Shut down ACSLS if it is running.

��

Note: If subsequent system messages indicate that the PIDfile does not exist, this means that ACSLS was notrunning.

5. To run the configuration script, enter

��-��%��

The ! �� screen appears.

Note: The configuration script, ��*�� , will failunless all LMU’s, LSM’s, and transports are fullyconfigured, powered on, and ready.

6. Do you want to custom configure ACSLS?

YES Go through each item of the menu, selecting options 1 through 6, and enter the variable informa-tion referring to Table 2. on page 8.

NO Go to Step 7.

7. Select 2 to exit the menu and continue theconfiguration process.The script displays progress messages during databasecreation. This takes about five minutes.

xxxxxxxx

xxxxxxxx

9th ed., 313464701


8. Enter � at the following prompt:

�� # ��I 8#��>�

9. Do you want to reconfigure the library?

YES Enter � at the following prompt:

��# ��)�� 1��

�)��M ��I 8# �� >�

and continue with Step 10.

NO Enter � at the following prompt:

��# ��)�� 1��

�)��M ��I 8# �� >�

and continue with Step 14.

10. Enter the number of ACSs that will be supported atyour site. (See Table 3, “Library ConfigurationOptions.”)

�� ! � ��

You must answer at least : to this prompt. Hardware mustbe installed to support one or more ACSs.

11. Enter the number of connections to your ACS.

�� ! � R��

12. Enter the device name for each connection. (See Table3, “Library Configuration Options.”)

&�)�� " ! �R�M ��)�� R��

&�)�� " ! � R5M ��)�� R5� 7�(7��

&�)�� " ! � R5M ��)�� R+� 7�(7��$

Example device names for 4400 or 9300 libraries

&�)�� " ! � R+M ��)�� R5� 7�(7 ��0

Example device name for SCSI library

9th ed., 313464701


Note: The device name is assigned during ACSLSinstallation when the SCSI device number is entered.

13. The installation script verifies that each defined portcommunicates with an LMU or SCSI LSM.

If communication is verified, you see messages similar tothe following:

��

��)��##� � �� 0' ��

��)�� ++

��)�� . � �� 0 �(C

?265 ��)�� +?.5

If communication is not verified, you see messages similarto the following before the program exits:

��

��)��#� � �� 0'

��)�� . � �� 0� �(C

?265 ��)�� +?.5

��

� �� # �� # ��

�� # ��

��# � �� 1��

Refer to the section “Troubleshooting LibraryConnections” at the end of this chapter and followprocedures there.

xxxxxxxx

9th ed., 313464701


Note: If you are using 9840 10– or 20–drive panels, youmust have Compatibility Level 12 LMU microcodeinstalled. If you have Compatibility Level 11 and 12 orCompatibility 6 LMUs, you receive the followingmessage:

��

��)��#� � �� 0' ��

��)�� ++

��)��#� � �� 0' ��

��)�� +3

! �� )�� 1�� "+3

��# ��

(��

�� +5"��)� �� 35"��)� ��

�� # �� # 6"��)� ��

��#I 8# �� >

If you respond #, the old panel files will be used. If yourespond �, the configuration routine will exit with themessage:

(� ��)� �� M ��

��)��"+3 �� # ��

Note: If you are running Compatibility Level 6 on a 4430LMU, you must upgrade your library hardware to include a 9330LMU.

14. Enter � at the following prompt to build/verify thelibrary configuration.

(�� #��

�� # ��

=�� M �� #��

��# � ��# �� M ��

��#��

=��;��# ��# �� I

8# �� >�

xxxxxxxx

xxxxxxxx

9th ed., 313464701


15. Have you previously configured the system?

YES Enter � at the following prompt:

��# ��)�� 1��

�)��M ��I 8# �� >�

As the script builds the library configuration, itdisplays the following message for each panel ineach LSM.

! � R �M ��0 R ��M �!�� R ��M ��

The script also generates a library configurationreport and appends it to the following file:

��1��! �� *��

NO Continue with Step 16.

16. Respond (� or �) when the system asks whether toconfigure client system interfaces.

�� #�� I

8# �� >�

YES The following message displays:

�, �� (,<� (!=��

+> <��!� �, ��

3> <� �� , !��# ��

&� #�� , ��

�� 8�>�

If �, the following message appears:

�� <��!� �, 8�>�

ONC/RPC is always selected.

NO Continue with Step 17.

9th ed., 313464701


17. Are you backing up the database to tape (forreconfiguring ACSLS only)?

Hint: At this point in the configuration, StorageTekrecommends that you back up the database to a tape thatcan be stored offsite and used, if needed, for disasterrecovery of the database.

YES Insert a blank tape when the following messagedisplays:

��

,��

�� ('��

The database backup procedure ��automatically executes and captures theconfiguration data to enable database journaling.

When the database backup is completed, thefollowing message displays:

&�� # ��

NO Press �CTRL�+ C and refer to �� on page93 in Appendix A to back up the database to diskfile. This completes this procedure.

Caution: The tape drive may appear idle during thebackup. It may not make any sounds or flash any lightsduring this time. DO NOT remove the tape from the driveuntil you see the following success message indicating thebackup is complete:

&�� # ��

Warning: Interrupting the backup process beforecompletion will cause a corrupted backup file or tape.

18. Remove the tape and store it in a safe place.

Warning: Installation is not complete at this point. Completethis chapter and Chapter 4 to ensure that all necessaryprocedures are done prior to running ACSLS.

!

STOP

STOP

9th ed., 313464701


Troubleshooting Library Connections

This section describes how to troubleshoot both serial libraryconnections and SCSI library connections. You must first havecompleted the ACSLS installation and configuration describedearlier in this chapter.

To troubleshoot connections with serial libraries(4400, 9300, 9740):

1. Make sure the library is powered on and functionaland the subsystems are properly connected with theappropriate cables.

2. Change directories:

�� 73��7�� 7�&��7��7$��

3. Enter:

��

4. Is the library communicating?

YES Rerun the configuration program (Step 5 in“Configuring ACSLS”).

NO Go to Step 5 below.

5. Observe the error that is returned from ��.

6. Is an error returned?

YES Continue with Step 7.

NO The problem points to a hardware condition such asfaulty cable connections or a faulty LMU. Checkall connections. Then rerun the configurationprogram (Step 5 in “Configuring ACSLS”).

9th ed., 313464701


7. If �� failed with a permission error, you getoutput such as:

<��8> �� )��#�

�� D +GM ��

��)��#� � �� 0'

This error message indicates that permissions need to bechanged on the low level tty device.

8. Find the actual device node by looking at the symboliclink to your tty device:

�� 7�(7�� 7$

Example output from an Ultra 10:

��""""""" ��

��)��S+�M5��S+M+��S+��S+6M655555��

Example output from a SPARC 5:

��)��BS5M+55555��

9. Change permissions on the device node so it is rw forall users:

�� 888 7�(��7��

following the path down to the device node.

10. To avoid future problems related to port permissions,you should disable the specific ACSLS ports fromaccess by any other applications. One specificapplication you should disable is the Solaris portmonitor.

To disable the ports � and � from the Solaris port monitor,log in as �� and enter:

� �� ;� ��

� �� ;� �� $

9th ed., 313464701


To troubleshoot connections with SCSI libraries (97xxand L–series):

1. Check for the following:

� The library is powered on and functional.

� The subsystems are properly connected with theappropriate cables.

� The library interface matches the controller interfacein terms of single-ended vs differential signaldefinitions.

� The bus is properly terminated at the library end witha compatible (single-ended or differential) SCSIterminator.

2. Run ��.

3. Is the library communicating?

YES Rerun the configuration program (Step 5 in“Configuring ACSLS”).

NO Go to Step 4 below.

4. Verify the hardware connection using the PROMmonitor utility:

a. Enter the PROM monitor by pressing the Stop key + a.

b. At the �� prompt, enter the command:

��$<��<��

This command displays the target number, the devicetype, make and model of each SCSI-attached device.A valid response might return something like thefollowing:

(�� .

'�� 5 ��)�� &�)�� (#�� 4 �(C �255

9th ed., 313464701


c. Was a valid response returned for the STK library?

YES Reboot the system and go to Step 5 below.

NO Verify the library hardware including theSCSI target ID defined on the library device.

Make sure all cables and terminators areproperly connected.

Reset the library and wait until the IPL hascompleted. Then repeat Step 4.

9th ed., 313464701


5. Remove and rebuild the SCSI device driver:

a. Switch user to ��.

b. Issue the following commands to remove the existingdrivers:

� -��( ��

� 7�( ��=

Then reboot the system.

c. Log in as �� and rebuild the mchanger devicedriver:

�� # �� 1��! ��.

)�� *��*��.

>�� # ��%� �� (�� '?

�� 1�� 1��

��$<��<��

'% �� 1�� # ��

�� @&��%�� &��A ��

�� *��

If your troubleshooting efforts fail, contact StorageTekSoftware Support for assistance.

9th ed., 313464701

69 Chapter 4. Completing the ACSLS Installation

Chapter 4. Completing the ACSLS Installation

Warning: Before completing the ACSLS installation, you mustcomplete Chapter 1 “Pre-Installation Preparation,” Chapter 2“Installing Solaris,” and Chapter 3 “Installing and ConfiguringACSLS.”

Overview

This chapter describes the steps necessary to complete theACSLS installation. They include:

� Configuring the Second Disk

� Importing the Database (for upgrade installations only)

� Verifying the Imported Database and LibraryConfiguration

� Verifying ACSLS Software

STOP

9th ed., 313464701


Configuring the Second Disk

Note: If you have already partitioned the second disk when youinstalled the operating system in Chapter 2, skip this section andgo to page 79, “Installing ACSLS Second Disk Support”.

If you did not partition the second disk when you installed theoperating system in Chapter 2, or you are installing a newsecond disk, complete this section.

Second disk is used to contain the transaction logs in order toassure recoverability to the most recent transaction, even in theevent of primary disk failure. The storage requirements forsecond disk can be met with 256 MB in Partition 0 and theremainder in Partition 1.

In this procedure, you create two partitions.

To partition the second disk:

1. Is ACSLS running?


NO Go to Step 7.

2. Open a terminal or a command tool and log in as��.


��


5. Shut down ACSLS.

��

6. Shut down the database.

�$-��

xxxxxxxx

Space Required byACSLS on the

Second Disk

Partitioning theSecond Disk

9th ed., 313464701



8. Open a terminal window. At the prompt, enter

%��

The system prompts you to select a disk. On a SPARC orUltra system, the second disk is typically c0t1d0.

9. Enter the number of the second disk (typically menunumber 1).

The Format Menu displays, shown in Figure 7.

" ��

" �� 8��> � �� #��

" �� 8��> � ��

" ��

" �� #B� ��

" �� )� ��

" ��

" �� #�

" ��

" ��

" �� # ��

" �)� ��

" �� )��M �� )��

" �� 4"�� )��

��

�#��

��

��

��

��

��

��#B�

��

��

)��#

�)�

��#

)��

��

7<�0!( 0��'�

Figure 7. Format Menu

10. Enter �� from the Format Menu.

The Partition Menu displays, shown in Figure 8.

9th ed., 313464701


5

+

3

G

6

.

L

2

��

��#

��

��

��

��

" �� T5U ��

" �� T+U ��

" �� T3U ��

" �� TGU ��

" �� T6U ��

" �� T.U ��

" �� TLU ��

" �� T2U ��

" ��

" ��# � ��

" ��

" ��# ��

" ��

�!�(,(,<� 0��'�

Figure 8. Partition Menu

11. Enter �� to display the disk partitions.

The Current Partition Table displays, shown in Figure 9.

9th ed., 313464701


Current partition table (original):

Part

01234567

Tag

unassignedunassignedunassignedunassignedunassignedunassignedunassignedunassigned

Flag

wmwmwmwmwmwmwmwm

Cylinders

0-20350000000

Size

1002.09MB0000000

Blocks

(2036/0/0)(0/0/0)(0/0/0)(0/0/0)(0/0/0)(0/0/0)(0/0/0)(0/0/0)

Total disk cylinders available: 2036+2 (reserved cylinders)

Figure 9. Partition Table

Note: The values in your partition table might differ from thoseshown, depending on the size of your disk and whether you havepreviously partitioned it.

Warning: Modifying an existing partition will destroy any datain that partition.

12. Enter 4 to change the 0 partition.

The partition 0 table is displayed. Enter the values shown.

a. �� -�� /�

Accept either the default �� or enter ��to bring up a list of available id tags.

b. �� -��/� 1

c. �� #� -5/� 4

d. �� B� -5�M 5�M 555��/� 0.8

13. Enter �� to confirm changes made to partition 0.

xxxxxxxx

STOP

9th ed., 313464701


14. Note the number of cylinders in partition 0.

Subtract the number of cylinders in partition 0 from thetotal number of disk cylinders. This number will be usedin Step 15.

15. Enter : to change partition 1.

The partition 1 table is displayed. Enter the values shown.

a. �� -�� /�

Accept the default.

b. �� -��/� 1

c. �� #� -5/�

To determine this value, add 1 to the highestnumbered cylinder in partition 0. For example, ifpartition 0 contains cylinders 5".35, enter .0:

d. �� B� -5�M 5�M 555��/�

Enter the amount displayed in 7�� (see Chapter 2,page 38).

16. Enter �� to confirm the changes entered.

The display should now look like the configuration shownin Figure 10.

The remaining partitions should all be unassigned withstarting cylinder of 0 and partition size of 0.

9th ed., 313464701


Current partition table (original):

Part

01234567

Tag

unassignedunassignedunassignedunassignedunassignedunassignedunassignedunassigned

Flag

wmwmwmwmwmwmwmwm

Cylinders

0-520521–2035000000

Size

256MB17xxMB000000

Blocks

(520/0/0)(1515/0/0)(0/0/0)(0/0/0)(0/0/0)(0/0/0)(0/0/0)(0/0/0)

Total disk cylinders available: 2036 + 2 reserved cylinders

Figure 10. Second Disk Partition Table

Note: On your display, �� should appear on size0 entries.

17. Enter B to display the partition menu.

The �� 0�� appears, shown in Figure 11.

xxxxxxxx

9th ed., 313464701


5

+

3

G

6

.

L

2

��

��#

��

��

��

��

" �� T5U ��

" �� T+U ��

" �� T3U ��

" �� TGU ��

" �� T6U ��

" �� T.U ��

" �� TLU ��

" �� T2U ��

" ��

" ��# � ��

" ��

" ��# ��

" ��

�!�(,(,<� 0��'�

Figure 11. Partition Menu

18. Enter ��$� from the partition menu to update thedisk with the new partitions.

19. Enter � at the ��# �� M ��Iprompt.

20. From the partition prompt, enter �CTRL�+D to exit.

9th ed., 313464701


In this procedure, you create the file systems on the disk you justpartitioned.

To create file systems:

1. At the prompt, enter � to construct a new filesystem.

2. At the system prompt, enter

�1%� 7�(7��7��

where �� is cntndns0, and cntndn matches the diskyou just installed.

For example,

�1%� 7�(7��7�4�:�4�4

The system may display:

��)��5�+�55 �� *��

3. To have second disk file systems automatically mountedon boot up, use an editor (such as )� or ��1��) toedit the ��)�� file to define the mount points.Note that each field is separated by tabs.

Add entries to the file such as the following two entries:

��)��5�+�5+ ��)��5�+�5+

��*�� + #� "

��)��5�+�55 ��)��5�+�55

��*�� + #� "

4. Verify that there is a directory for your mount point��*�� by entering

�� 7��-��

If the directory does not exist, create one by entering

�� 7��-��

or enter an optional directory name.

Creating the FileSystems

9th ed., 313464701


5. Make sure that the second disk is mounted:

�� 7��-��

or enter the optional directory name specified in theprevious step.

6. Make a directory for the backup portion of the seconddisk.

�� 7��-��7$��

This directory is the default directory for the backupportion of the second disk. You may create anotherdirectory name for second disk backups.

7. Make sure the second disk backup is mounted on thedirectory specified in the previous step.

�� 7��-��7$��

9th ed., 313464701


To install second disk support:

1. Is ACSLS running?


NO Go to Step 6.



��

4. Shut down ACSLS.

��


�$-��


7. Change directories.

�� 73��7�� 7�&��7��

8. Run the second disk utility.

�7��- ��

9. Choose : to install second disk:

+� ,��

10. When you are prompted for the directory for seconddisk support, press �ENTER� to accept the default of��*�� if you used ��*�� as the mountpoint in your )�� entry (see “Creating the FileSystems” on page 77). If you used an optional directory

Installing ACSLSSecond Disk

Support

9th ed., 313464701


name instead of /second_disk on page 77, enter thatname.

11. When you are prompted for the second disk directoryfor database backups, press �ENTER� to accept thedefault of ��*�� if you used��*�� as the mount point in your)�� entry (see “Creating the File Systems” on page77). If you used an optional directory name instead of/second_disk/backup on page 77, enter that name.

12. When you see the �� &�� menu, select /to exit the system.

You should see a message about doing a mandatory backupand a prompt to insert a database backup tape.

13. Insert the tape if you need to and wait for the backupto complete.

14. When the prompt returns, log out.

9th ed., 313464701


To restart ACSLS:


2. In a terminal window or at the shell prompt, enter

�$��

Note: If the �� option wasenabled during ACSLS installation, ACSLS is initiatedautomatically when the server system is rebooted. If this isthe case, go to Step 3.



��

It takes a few seconds to start the database and return to theshell prompt.

5. When the shell prompt returns, log out.

6. Log back in as �� to use the ACSLS software.

Restarting ACSLS

xxxxxxxx

9th ed., 313464701


Importing the Database

If this is a new installation and an existing database was notexported, skip this section and go to “Verifying ACSLSSoftware” on page 87.

This section describes how to import and recreate the ACSLSdatabase that you exported in Chapter 1 using the ��*�1��utility.

Hint: The procedures outlined below are for importing thedatabase from the default tape device. Refer to Appendix A“Utilities” for instructions on importing the database from disk.

Caution: To complete the upgrade, use the ��*��utility to import the database you exported with the��*�1�� utility in Chapter 1 of this book. For moreinformation about the ��*�� utility, see Appendix A“Utilities”.

To import the database from tape:

1. Determine whether you are currently the �� user byentering:

��

If the response is not �� in the parenthesis followingthe UID portion of the output, log out by pressing �CTRL� +

�D�, then log back in as ��.

2. Insert the exported database tape that you exported inChapter 1 with the ��*�1�� command into thetape drive.

!

9th ed., 313464701


3. Run the database import utility by entering thefollowing at a UNIX prompt.

�$-� ��

The ��*�� utility displays several messages as itexecutes.

This utility can take up to 15 minutes to complete.

4. Press �CTRL�+C to exit when you see the followingmessage. Do not insert a database backup tape.

��

��)� �1��

,��

-A�� ('�� CTRL� + �C� ��

�1��/

9th ed., 313464701


Verifying the Imported Database and Library Configuration

In this procedure you use the ��*�� program to verifythe database and the library configuration.

To verify that the database has been imported:

1. Run the configuration program:

��-��%��

The ! �� screen appears.

2. Enter 6 to skip library ACSLS feature configuration.

At this point, the system generates a series of messagesindicating that the database is being verified.

3. Enter � at the prompt to skip library communicationsoftware configuration.

�� # ��I 8# �� >�

4. Enter � at the prompt to build/verify the libraryconfiguration.

(�� #��

�� # ��

=�� M �� #��

��# � ��# �� M ��

��#��

=��;��# ��# �� I

8# �� >�

9th ed., 313464701


5. Enter � when the following prompt displays:

��# ��)�� 1��

�)��M ��I 8# �� >�

As the script builds the library configuration, it displaysone of following messages for each panel in each LSM.

! � � �M ��0 � ��M �!�� M ��

! � � �M ��0 � ��M �!�� M ��

The script also generates a library configuration report andappends it to the��1��! �� *�� file.

6. Enter � at the prompt to skip CSI configuration.

�� #�� I

8# �� >�

9th ed., 313464701


7. Are you backing up the database to tape or disk?

Tape Insert a blank tape when the following messagedisplays:

��

,��

�� ('��

The database backup procedure ��automatically executes and captures theconfiguration data to enable database journaling.

When the database backup is completed, thefollowing message displays:

&�� # ��

Disk Enter �CTRL� + �C� and refer to �� onpage 93 to back up the database to disk file. Thencontinue with Step 9.

Caution: The tape drive may appear idle during thebackup. It may not make any sounds or flash any lightsduring this time. DO NOT remove the tape from the driveuntil you see the following success message indicating thebackup is complete:

&�� # ��

Warning: Interrupting the backup process beforecompletion will result in corruption of the database.

8. Remove the tape and store it in a safe place.

9. Run �� to start the server.

If the �� option is enabled,ACSLS is initiated automatically when the server systemis rebooted.

The ACSLS is now ready for library operations. You may logout and log back in as ��.

!

STOP

9th ed., 313464701


Verifying ACSLS Software

The IVP (Initial Verification Program) is an exerciser that is used toverify that a newly installed library is fully functional. This step isoptional. It will mount and dismount specified volumes to specifieddrives.

To verify ACSLS, mount and dismount a volume by either:

1. Entering mount and dismount commands from a ��*��(See “Verifying ACSLS”).

2. Running the Initial Verification Program (IVP) (See“Running ivp.sh to Verify ACSLS”).

Mount/dismount a volume to verify ACSLS:


2. Query the server from the ��*�� by entering

�� (�

If messages are displayed indicating that the server is inrecovery mode, wait for a message indicating that theserver is running.

3. If ACSLS is not running, start it by entering

��

4. Do you have at least one volume in an LSM?

YES Continue with the procedure.

NO Enter a volume into an LSM. For moreinformation, see “Operator Tasks” in ACSLS SystemAdministrator ’s Guide and continue with theprocedure.

Verifying ACSLS

9th ed., 313464701


5. Mount a volume by entering:

��

Hint: Use the ��# ��)� command to get the ID of anavailable drive and the ��# (�� command to get theID of a library volume. See “Command Reference” inACSLS System Administrator’s Guide for moreinformation.

6. Did you see a message indicating a successful mount?

A successful mount message is:

0��

YES Procedure is complete.

NO If an error message appears, run this verificationprocedure again, ensuring that you specified avalid, available drive and a library volume. If themount/dismount still fails, call StorageTek forassistance.

7. Dismount the volume by entering:

�� %��

where �� is the volume and �� is the drive youspecified in Step 5.

9th ed., 313464701


Use this procedure to run the IVP program (�)��) to mountand dismount a volume. You specify the volume and drive that�)�� uses in the �)�� file.

Run �)�� to mount/dismount a volume to verifyACSLS:

1. Open a Terminal or a Command tool.

2. Change to the directory that contains the �)�� file.

�� 73��7�� 7�&��7��7��

3. Using any text editor (for example, )� or ��1��),open the �)�� file and enter a drive ID and volumeID in the following format at the bottom of the file:

��

Hint: Use the ��# ��)� command to get the ID of anavailable drive and the ��# (�� command to get theID of a library volume. See “Command Reference” inACSLS System Administrator’s Guide for moreinformation.

4. To start the IVP program, enter

73��7�� 7�&��7��7�(�7�(��

�)�� mounts and dismounts the volume that youspecified in the �)�� file in about 30 seconds.

5. Did you see a message indicating a successful mount?

YES Procedure is complete.

NO If an error message appears, run this verificationprocedure again, ensuring that you specified avalid, available drive and a library volume in the�)�� file. If the mount/dismount still fails, callStorageTek for assistance.

Running ivp.sh toVerify ACSLS

9th ed., 313464701


ACSLS Setup for Client Communication

To set up ACSLS for client communication, you include theclient host name and IP address in �� or in the NISlookup table.

Regressing to a Previous Version of ACSLS

If for whatever reason you need to regress to a previous versionof ACSLS after you install ACSLS 6.0, contact StorageTekSoftware Support. For more information, see Requesting Helpfrom Software Support.

9th ed., 313464701

91 Appendix A. Utilities

Appendix A. Utilities

Overview

This appendix contains general guidelines for using specificACSLS database utilities and descriptions of the library utilitiesmentioned in this book. These include the following:

� bdb.acsss

� db_export.sh

� db_import.sh

� kill.acsss

� rc.acsss

� sd_mgr.sh

9th ed., 313464701


Using the ACSLS Database Utilities

Follow these general guidelines for using the ACSLS databaseutilities:

� You must log in as �� to set up the correct paths andownership to run ACSLS utilities; you cannot � to ��.

� Backups created by �� are primarily for disasterrecovery. To restore the database, use �� asdescribed in the System Administrator’s Guide.

� StorageTek recommends that you use �� tomanually back up the database for disaster recovery after:

� A large number of enters or ejects

� A large number of scratch mounts

� Running ��*��

� Running ��*��

� Any database recovery

� To ensure that you recover an accurate and consistentdatabase, always use the most current database backup.

� ��*�1�� and ��*�� database utilities are forcapturing and recovering database table data andmiscellaneous files for upgrades or OS changes to avoidhaving to run a lengthy audit.

� After you upgrade to a new version of ACSLS, make sureto create a new backup as soon as you have upgraded. Donot recover your database with backups or exports createdwith previous versions.

� Retain all utility event logs. These logs will helpStorageTek resolve any problems.

9th ed., 313464701


bdb.acsss

The �� utility backs up the ACSLS database andmiscellaneous library resource files.

Note: When you run the �� utility, ACSLSautomatically creates a backup on local disk as well.

�� -"� �� % ��/

Hint: If you enter �� with no options, the backuputility defaults to the default tape device attached and configuredto the ACSLS server.

F� �� specifies a UNIX file to contain the ACSLS database. Youmust have write permissions to the file.

F� ��specifies any tape device attached and configured to theACSLS server.

Use the �� utility to manually back up the ACSLSdatabase to tape or to an external network file to create backupsthat can be used, if needed, for disaster recovery of the database.A tape backup, for example, lets you recover the database if bothdisks fail on a two-disk server.

How often you back up the database depends on the amount oflibrary activity. In general, you should back up the databaseoften for frequent changes to library contents or configuration.

xxxxxxxx

Format

Options

Usage

9th ed., 313464701


StorageTek recommends that you use �� to manuallyback up the database to tape after:

� Running ��*�� .

� Importing the database. After you upgrade to a newversion of ACSLS, do not use database backups or exportscreated with previous versions. Make sure, however, tocreate a new backup as soon as you have upgraded.

� A significant number of enters, ejects, scratch mounts, orvolume state changes, such as from scratch to data or fromlocked to unlocked.

� Any database recovery.

9th ed., 313464701


db_export.sh

The ��*�1�� utility exports the ACSLS database tabledata and miscellaneous files in preparation for an upgradeinstallation or a reinstallation of ACSLS.

��*�1�� F� ��

Hint: If you enter ��*�1�� with no options, the exportutility defaults to the default tape device attached and configuredto the ACSLS server.

F� �� specifies a UNIX file to contain a backup of the ACSLSdatabase. You must have write permissions to the file.

Note: If you export the database to a file, the file must reside ina directory above /export/home/ACSSS.

Use the ��*�1�� utility to prepare for a reinstallation ofACSLS or an upgrade installation of ACSLS.

The following examples:

� Describe how to export the database to the default tapedevice attached to the ACSLS server.

� Describe how to export the database to disk file.

Format

Options

xxxxxxxx

Usage

Examples

9th ed., 313464701


To export the ACSLS database to the default tapedevice:


2. From the cmd_proc window, idle ACSLS:

��


4. Shut down ACSLS.

��


�$-�� %�� &�� (��

3�� .�2

�$-�� &�� (�� .�2

��

6. Insert a blank tape into the default tape device.

7. Start the ��*�1�� utility.

�$-3��

8. Press �� to accept 6.0 as the target release ofACSLS) at the following prompt:

�� ! �� -L5/�

As it executes, the utility displays output indicatingsuccessful table data is being exported.

9. Remove the cartridge from the drive only when you seea message indicating the export is complete.

Caution: You will lose files if you remove the cartridgebefore the program completes. Write protect the cartridgeand clearly mark it to identify the contents as the exporteddatabase.

!

9th ed., 313464701


To export the ACSLS database to a disk file:

Caution: The files created during the export must besaved to some filesystem or other workstation so that theyare not destroyed by the upgrade.



��


4. Shut down ACSLS.

��


�$-�� &�� (�� .�/�0 ��

��1�

�$-�� &�� (�� .�2

6. Start the ��*�1�� utility.

�$-3�� % db_file

The ��*�1�� utility creates two files: ��*�� and��*��. Verify that the ��*�� and��*�� files are in a remote location that will notbe destroyed by the upgrade (i.e., not on the primary disk).

As it executes, the utility displays output indicatingsuccessful table data is being exported.

When the program finishes, you see a message indicatingthe export is complete.

!

9th ed., 313464701


db_import.sh

The ��*�� utility imports the ACSLS database tabledata and the miscellaneous files that you exported when youused the ��*�1�� utility.

��*�� F� ��

F� �� specifies a UNIX file created by db_export.sh.

Use the ��*�� utility to import the ACSLS databasethat you exported using the ��*�1�� utility.

Caution: To ensure that you import accurate and consistentdata, terminate ACSLS before running ��*��.

The following examples:

� Describe how to import the database from the default tapedevice attached to the ACSLS server.

� Describe how to import the database from disk files.

Format

Options

Usage

!

Examples

9th ed., 313464701


To import the ACSLS database from the default tapedevice:



��


4. Shut down ACSLS.

��

5. Insert the export tape into the default tape device.

6. Start the db_import.sh utility.

�$-� ��

7. When you see the prompt about tables being destroyedfrom the ACSLS database, respond � to continue.

8. When the import completes, remove the tape.

9. Run ��*�� to verify the imported database and�� to back up the database.

9th ed., 313464701


To import the ACSLS database from disk file:



��


4. Shut down ACSLS.

��

5. Start the db_import.sh utility.

�$-� �� % db_file

6. When you see the prompt about tables being destroyedfrom the ACSLS database, respond � to continue.

7. Run ��*�� to verify the imported database and�� to back up the database.

9th ed., 313464701


kill.acsss

The �� utility terminates ACSLS.

��

None.

Use the �� utility to terminate ACSLS.

��

Caution: Do not run �� while an ACSLS request is inprogress! You must first idle ACSLS (with the �� command)before you run ��. This allows any outstanding jobsto finish before terminating ACSLS.

Format

Options

Usage

See Also

Notes

!

9th ed., 313464701


rc.acsss

The �� utility starts ACSLS.

�� -��/

��

puts the ACSLM in the idle state.

Use the �� utility to start ACSLS. When you startACSLS, it goes through recovery mode to online state. ACSLSinitialization includes checking its database and “recovering”status of the library volumes and library hardware; thus, the term“recovery mode”.

��

The utility will automatically log in as ��, so you may beprompted to enter the �� password. Only one copy ofACSLS can be running on the server. The utility will notproceed if ACSLS is already running.

Format

Options

Usage

See Also

Notes

9th ed., 313464701


sd_mgr.sh

The �*� �� utility installs or deinstalls second disk support.

�*� ��

None.

Use the �*� �� utility to install or deinstall a second disk.See Chapter 4 or Appendix B.

You can deinstall a second disk to go back to a single–disksystem. You may want to do this to take the second disk offlinefor service or replacement.

Format

Options

Usage

9th ed., 313464701

105 Appendix B. De–installing a Second Disk

Appendix B. De–installing a Second Disk

Overview

De-installing a second disk is usually done when the second diskneeds to be serviced or replaced.

Caution: De-installation of the second disk should be used ifthere is a hardware failure of the second disk. ACSLS will notstart if a hardware failure occurs.

!

9th ed., 313464701


De-installing a Second Disk

To de-install the second disk:

1. If you are not already logged in as �� log in as��.


��

3. Shut down ACSLS.

��


��


6. Change directories.

��

7. Run the second disk utility.

��

This command starts the second disk manager. With thisfunction, you can remove second disk support.

8. Enter � to de-install second disk support when you areprompted for a menu choice.

��

9. Respond � or � when you see the following prompt:

��

��

Select � if your second disk is damaged andnon-functioning.

Select � if your second disk is not damaged.

9th ed., 313464701

107 Appendix B. De–installing a Second Disk

10. When the Second Disk Support menu appears, select 3to exit the menu.

A message and prompt display indicating you must do amandatory backup and to insert a database backup tape.

11. Insert the tape and wait for the backup to complete.

The backup takes several minutes to complete.

12. When the backup is completed, remove the backuptape and store it in a safe place.

13. Log out by selecting �� from the ��menu.

9th ed., 313464701


Restarting ACSLS

To restart ACSLS:



��




��




xxxxxxxx

9th ed., 313464701


Restarting ACSLS

To restart ACSLS:



�$��




��




xxxxxxxx

9th ed., 313464701

109 Glossary

Glossary

ACS—See Automated Cartridge System.

ACSEL—See ACS Event Logger.

ACS Event Logger (ACSEL)—Thesoftware component that receives messagesfrom other ACSLS components and writesthem to an Event Log.

ACS ID—A unique identifier for an ACS.

ACSLH—See ACS Library Handler.

ACS library—A library is composed of oneor more ACSs, attached tape drives, andcartridges residing in the ACSs.

ACS Library Handler (ACSLH)—Thepart of the ACSLM that communicatesdirectly with the LMU.

ACSLM—See ACS Library Manager.

ACS Library Manager (ACSLM)—Thesoftware component that validates androutes library requests and responses.

ACSLS—See ACS Library Software.

ACSLS database—ACSLS databasecontaining information about the locationand status of the tape cartridges. Theinformation includes cell location, scratchstatus, etc.)

ACSLS platform—The server hardware andsoftware that provide the properenvironment for ACSLS.

ACS Library Software (ACSLS)—Manages ACS library contents and controlsACS library hardware to mount anddismount cartridges on ACS cartridgedrives.

ACSLS database—A database used byACSLS to track the library configurationand the locations and IDs of all tapecartridges in the library.

ACSSA— See ACS System Administrator.

ACS System Administrator(ACSSA)—The interface between theCommand Processor and the rest of thesystem.

ADI—Application Data Interchange.

audit—A physical inventory of the contentsof all or part of a library.

Automated Cartridge System(ACS)—The library subsystem consistingof one LMU, and one to 24 LSMs connectedto that LMU.

automated library—See library.

9th ed., 313464701


beginning of tape (BOT)—The location ona tape where written data begins.

BOT— See Beginning of Tape.

CAP—See Cartridge Access Port.

CAP ID—A unique identifier for thelocation of a CAP. A CAP ID consists of theACS ID, the LSM number, and the CAPnumber.

cartridge—A plastic housing containing alength of data recording tape. The tape isthreaded automatically when loaded in atransport. A plastic leader block is attachedto the tape for automatic threading. Thespine of the cartridge can contain anOCR/Bar Code label listing the volume ID.

Cartridge Access Port (CAP)—Abidirectional port built into the door panel ofan LSM, which provides for the manualentry or automatic ejection of tapecartridges.

cartridge drive (CD)—A device containingtwo or four cartridge transports and theirassociated power and pneumatic supplies.

cartridge tape I/O driver—Operatingsystem software which issues commands(e.g., read, write, and rewind) to cartridgesubsystems.

cartridge transport—Anelectromechanical device that moves tapefrom a cartridge over a head that writes andreads data from the tape. A transport isdistinct from the power and pneumaticsources that supply the electricity and air itneeds to function. See cartridge drive.

CCI—See client computing system.

CD—See cartridge drive.

cell—A receptacle in the LSM in which acartridge is stored.

channel—A device that connects the hostand main storage with the input and outputcontrol units.

client applications—Software applicationsthat manage tape cartridge contents. Theyaccess tape cartridges by interacting withACSLS. Any number of client applicationscan be resident on a client system.

client computing system—A computer andan executable image of the operatingsystem.

client software— This software managestape cartridge contents, generates requestsfor cartridges, and transfers data to and fromcartridges. The client software is not part ofACSLS.

Client System Component—Softwarewhich provides an interface between theclient computing system’s operating systemand ACSLS.

Client System Interface (CSI)— Thesoftware component that translates androutes messages between the ACS LibraryManager and the Client System Component.

command area—The bottom area of thecmd_proc interface where you enter requestsand receive response.

command processor (cmd_proc)— Thescreen interface of the ACSSA. cmd_proclets you enter the commands described inChapter 7.

9th ed., 313464701

111 Glossary

control path adapter—A hardware devicewhich converts from a Client ComputingSystem’s control protocol to the controlprotocol of the StorageTek Library ControlSystem.

control unit (CU)—A microprocessor-basedunit logically situated between a channeland up to sixteen cartridge transports. TheCU translates channel commands intotransport commands and sends transportstatus to the channel.

CSE—Customer Services Engineer.

CSC—Client System Component.

CSI—See Client System Interface.

CSI variables—Used to define variousoptions to fine–tune communicationsbetween a CSC and the CSI. You changethese variables in the ��*�� program.

CU—See control unit.

cycle error messages—Messages thatindicate a library or ACSLS failure.

database—A collection of interrelated datarecords. See also ACSLS Database.

data path—The network path that allowsclient applications read/write access to tapecartridges.

data path adapter—A hardware devicewhich translates from a Client ComputingSystem’s data protocol to the data protocolof the StorageTek Control Unit.

display area—The top area of the cmd_procinterface that collects messages regardingthe status of the library.

end of tape (EOT)— The location on a tapewhere written data ends.

EOT— See end of tape.

EPO—Emergency Power Off.

EPROM—See erasable programmable readonly memory.

erasable programmable read-onlymemory (EPROM)—A special memorychip that can be erased and reprogrammed.

Event Log—A file, maintained by theACSEL, that contains messages describinglibrary and ACSLS events.

Event Logger—See ACS Event Logger.

external label identifiers— Asix–character alphanumeric label on theoutside edge of a cartridge used to identify aphysical tape volume. It may consist ofuppercase letters A through Z, numerals 0through 9, and blanks.

full installation—A complete softwareinstallation required for new customer sitesor for existing sites where a new library hasbeen installed.

home location—The cell associated with agiven cartridge.

ID—Identifier or identification.

Informix—The relational database used byACSLS 6.0.

Informix Storage Manager (ISM)—TheInformix database manager, which managesdatabase backups and offloaded transactionlogs.

9th ed., 313464701


Initial Program Load (IPL)—A processthat activates a machine reset, initiates wakeup diagnostics (from EPROMs) and loadsfunctional code.

inline diagnostics— Routines that testcomponents of a subsystem while operatingon a time-sharing basis with the functionalmicrocode in the subsystem component.

in–transit cartridges—Cartridges betweentheir source and destination locations.Cartridges are considered in–transit if theyare in the pass–thru ports, robot hands, orplayground.

I/O—Input/Output.

IPC—Interprocess Communication.

IPL—See Initial Program Load.

ISM—See Informix Storage Manager.

journal—A sequential log of changes madeto the database since the last checkpoint.

LAD— Lock Access Door.

LAN—See local area network.

large CAP (LCAP)—A 40–cartridge CAPwith the storage cells arranged in fourremovable magazines of ten cells each. Themagazines appear as a single column of 40cells to the host software.

LCAP—See large CAP.

LCU—See Library Control Unit.

LED—See Light Emitting Diode.

library—A library is composed of one ormore ACSs, attached tape drives, volumes inthe ACSs, and the ACSLS software thatcontrols and manages the ACSs.

library configuration options—Allowsthe customer to specify the number of ACSsin the library and the connections betweeneach ACS and the server system.

library control component—Softwarewhich controls the mounting anddismounting of cartridges in the ACS.

library control processor—Properlyconfigured computer hardware that, with theaddition of appropriate software, supportsthe operation of the Library ControlSoftware.

library control system—The librarycontrol platform loaded with library controlsoftware (ACSLS).

library control software—The softwarecomponents of ACSLS including the librarycontrol component, the Client SystemInterface and Library Utilities.

Library Control Unit—The portion of theLSM that controls the picking, mounting,dismounting, and replacing of tapecartridges.

library drive—A cartridge transportattached to an LSM that is connected to, andcontrolled by, a client system. Librarydrives interact with the LCU duringautomated tape cartridge mount anddismount operations. Library drives interactwith a client application during tape datatransfer operations. Library drives areindividually addressable by the ACSLM andare individually accessible by clientapplications. See Cartridge Transport.

library errors—Errors that occur becausethe library is offline, has suffered hardwarefailure, is unavailable, etc.

9th ed., 313464701

113 Glossary

Library Management Unit (LMU)—Theportion of an ACS that manages LSM’s,allocates their resources, and communicateswith ACSLS.

Library Storage Module (LSM)—AnACS structure that provides the storage areafor cartridges, cartridge drives, CAPs, andthe robot necessary for moving them.

light emitting diode (LED)—A lightemitting device that uses little energy and isused mainly to indicate on/off conditions.

LMU—See Library Management Unit.

local area network (LAN)—A computernetwork in which any component in thenetwork can access any other component.This is the type of interface between anLMU and attached LSM’s.

LSM—See Library Storage Module.

LSM ID—A unique identifier for an LSM.The LSM ID consists of the ACS ID and theLSM number.

network adapter—Equipment that providesan electrical and logical interface between anetwork and specific attached equipment.

Network Interface (NI)—An interfacebetween the server system and the clientsystems that maintains network connectionsand controls the exchange of messages. TheNI is resident on the server system and eachclient system.

NI—See Network Interface.

OCR—Optical character recognition.

ONC—Open network computing.

Open Systems Interconnection(OSI)—A software architecture model ofthe International Organization forStandardization. The OSI model providesstandards for the interconnection of dataprocessing systems.

OSI— See Open Systems Interconnection.

OSLAN—Open Systems Local AreaNetwork.

Pass–Thru Port (PTP)—Mechanism thatallows a cartridge to be passed from oneLSM to another in a multiple LSM ACS.

PCAP—See priority CAP.

playground—A reserved area of specialcells (within an LSM) used for storingdiagnostic cartridges and cartridges foundin–transit upon power–on and beforeinitialization of the LSM is completed.

pool—A collection of tape cartridges havingone or more similar features or attributes,such as a pool of scratch tapes.

POST—Power–on self–test.

priority CAP (PCAP)—A single–cartridgeCAP used for priority entry and ejection ofcartridges.

processing errors—Errors that result fromprocessing or network communicationfailures.

PROM—Programmable read-only memory.

PTP—See Pass–Thru Port.

RDBMS—Relational database managementsystem.

9th ed., 313464701


redo log files—Backup files used to restorethe ACSLS database.

relational database—A database that isorganized and accessed according torelationships between the data items;relationships are represented by tables.

ROM—Read–only memory.

RPC—Remote Procedure Call.

SCAP—See standard CAP.

scratch—An attribute of a tape cartridge,indicating that it is blank or contains nouseful data.

SCSI—Small computer serial interface.

second disk journaling—Allows for thedatabase’s journal records to be written to asecond disk device, instead of writingrecords to the primary disk. This improvesthe chances of recovery from a disk failure.

server system—The part of the library thatis the residence for ACSLS, now referred toas the Library Control System. The LibraryControl System acts as an interface betweena library and client systems.

server system user—A person who invokesACSLS commands, utilities, or procedureson the server system. Server system usersare generally site and maintenance personnel(for example, library operators, tapelibrarians, system administrators, CSEs, andsystems personnel).

servo—A system that uses feedback tocontrol a process.

silo—A commonly used term for an LSM.See Library Storage Module.

SIMM—Single inline memory module.

SQL—See structured query language.

SRN. See service request number.

SSI—See Storage Server Interface.

SSR—Software Support Representative.

Standard CAP (SCAP)—A 21–cartridgeCAP with the storage cells arranged in threerows of seven fixed cells.

Storage Server Interface (SSI)—Asoftware component, resident on a clientsystem, that translates and routes messagesbetween client applications and the CSI.

structured query language (SQL)—Alanguage used to define, access, and updatedata in a database.

system resource variable—Used to controlthe amount of system resources used byACSLS.

system unit—The Library Control Platform.

tape library management system(TLMS)— A type of client application.

TCP—Transmission Control Protocol.

TLMS—See tape library managementsystem.

TOD—Time of day.

UDP—User Datagram Protocol.

UNIX—An operating system originallydeveloped by Bell Laboratories (now UNIXSystems Laboratories, Inc.) and used by avariety of computer systems.

unsolicited messages—Messages thatindicate an error or notify you when aparticular routine action can be taken.

9th ed., 313464701

115 Glossary

UOC—Usable on codes.

upgrade installation—Performed wheninstalling a new version of ACSLS at anexisting customer site.

user–selectable features and optionsvariables—Used to define varioususer–selectable features and options.

validation errors—Errors that result fromformat and syntax validation performed bycmd_proc.

virtual label—A logical label that can beassigned to a cartridge when its physicallabel is missing or unreadable.

volser—Volume Serial Number.

volume—A tape cartridge.

volume access control—Limits access tovolumes, usually by the client.

volume identifier—A six-character stringthat uniquely identifies a tape cartridge tothe database.

volume serial number (volser)—Asynonym for external label identifier.

WTM—write tape mark.

XDR— External data representation.

ACSLS Installation Guide

Documents

Transcript of ACSLS Installation Guide