VolServ
®
Overview
VolServ Version 5.2
November 2003
6-01001-01 Rev A
Trademark Notice
AMASS, DataMgr, EMASS, FileServ, and VolServ are either trademarks or registered
trademarks of ADIC, Advanced Digital Information Corporation. DAS is a trademark of
Grau, an ADIC subsidiary. All other product names and identifications are trademarks or
registered trademarks of their respective manufacturers.
Copyright Notice
© 1996-2003 ADIC®. All rights reserved. This document is the property of ADIC. No part
of this document may be reproduced, transmitted, transcribed, stored in a retrieval system,
or translated into any language or computer language in any form or by any means,
electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without the
express written permission of:
ADIC USA
Tel.: +1 303-705-3900
Fax: +1-303-792-2465
ATAC: 1-800-827-3822
http://www.adic.com
ADIC Europe
ZAC des Basses Auges
1, rue Alfred de Vigny
78112 Fourqueux, France
Tel.: +33.1.3087.5300
Fax: +33.1.3087.5301
ADIC Germany Beteiligungs
GmbH, KG
Eschenstraße 3
D-89558 Böhmenkirch, Germany
Tel:+00.800.9999.3822
U.S. Government Rights Restricted
Use, duplication, or disclosure of either the software or documentation is subject to
restrictions set forth by the U.S. Government in FAR 52.227-19(c)(2) and subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 52.2277013 and/or in similar or following clauses in the FAR, DoD, or NASA FAR Supplement.
Technical Assistance
ADIC Technical Assistance Center:
• In the USA and Canada, call 1-800-827-3822.
• Outside the USA and Canada, call 303-874-0188 or toll-free 00800-9999-3822.
• Send e-mail to: support@adic.com.
Documentation
Although the material contained herein has been carefully reviewed, ADIC does not
warrant it to be free of errors or omissions. We reserve the right to make corrections,
updates, revisions, or changes to the information contained herein.
• Send e-mail to: techdocs@adic.com
READER COMMENT FORM
ADIC includes this Form in an effort to provide the best possible documentation to our
customers. Please take a few moments to mail or FAX your response to:
ADIC USA
Tel.: +1 303-705-3900
Fax: +1-303-792-2465
ATAC: 1-800-827-3822
http://www.adic.com
ADIC Europe
ZAC des Basses Auges
1, rue Alfred de Vigny
78112 Fourqueux, France
Tel.: +33.1.3087.5300
Fax: +33.1.3087.5301
ADIC Germany Beteiligungs
GmbH, KG
Eschenstraße 3
D-89558 Böhmenkirch, Germany
Tel:+00.800.9999.3822
Question Circle One
Information was complete. Agree Disagree
Information was easy to find. Agree Disagree
Information was easy to follow. Agree Disagree
Is there anything you especially like or dislike about the organization, presentation,
or writing in this manual?_______________________________________________
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
___________________________________________________________________
Book Title Document Number
Customer Name Telephone
E-mail Address
Company Name
Address
City, State, Zip
NOTES
Command Reference
Preface
Purpose of This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3
Who Should Read This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3
How This Book is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3
Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-4
Introduction 1
Media Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3
Conforms to Industry Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4
Storage Area Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5
Computer Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5
Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5
Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6
Media Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6
Label Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7
Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8
Required Personnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9
System Administrator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9
Library Operator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10
Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11
GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11
Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11
API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11
VolServ Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-12
VolServ Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-12
6-01001-01 Rev A Contents i
Command Reference
Library Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-15
System Log Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-17
Message Logging Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-18
Client Application Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-20
Client Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-21
Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-23
Query Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-23
How VolServ Works 2
Centralized Media Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3
MediaClass Grouping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
Membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
Media Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
Associated Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
Drive Pool Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
Logical Grouping of Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7
Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7
Membership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8
Media and Drive Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8
Technical Support 3
Phone Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
Training . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
Solutions Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4
ii Contents 6-01001-01 Rev A
Command Reference
Online Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4
Using the Reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6
Contact Publications Department . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6
Secured Web Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6
6-01001-01 Rev A Contents iii
Command Reference
iv Contents 6-01001-01 Rev A
Preface
Purpose of This Book . . . . . . . . . . . . . . . . . . . . . . .P-3
Who Should Read This Book. . . . . . . . . . . . . . . . .P-3
How This Book is Organized . . . . . . . . . . . . . . . .P-3
Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .P-4
P
Preface
VolServ Overview
NOTES
P-2 Preface 6-01001-01 Rev A
VolServ Overview
Preface
Purpose of This Book
Who Should Read This Book
How This Book is Organized
This book provides an introduction or high-level summary of
VolServ, which manages media and volumes contained within
both automated and manual libraries.
This book is written for prospective customers as well as the
system administrator who will be using and maintaining
VolServ.
This book contains the following chapters:
Chapter 1: Introduction — Describes the storage area
network, connectivity, personnel tasks, and operations
performed with VolServ.
Chapter 2: How VolServ Works — Describes centralized
media management and database maintenance.
Chapter 3: Technical Support — Technical support available
to you.
Glossary — Defines terms.
6-01001-01 Rev A Preface P-3
VolServ Overview
Conventions
The conventions used throughout the VolServ technical books
are listed below:
Convention Example
Screen text, file names, program names, and
commands are in Courier font.
The root prompt is shown as a number
symbol.
What you should type in is shown in Courier
bold font.
Site-specific variables are in a Times italics
font.
A backward slash ( \ ) denotes the input is
continued onto the next line; the printed page
is just not wide enough to accommodate the
line.
Pressing <Return> after each command is
assumed.
Request to add a new volume:
Volume group will be “20”
Volume position will be “A123”.
# su root
vsarchiveqry
tar -xvf tapedevicename
#
remsh nodename -n dd if=/dev \
/tapedevicename/bs=20b | tar xvfb \
- 20
(You should type the entire command witho ut
the backward slash.)
A menu name with an arrow refers to a
sequence of menus.
P-4 Preface 6-01001-01 Rev A
Config-->MediaType-->Redefine
NOTES
Preface
VolServ Overview
6-01001-01 Rev A Preface P-5
VolServ Overview
NOTES
P-6 Preface 6-01001-01 Rev A
Media Management . . . . . . . . . . . . . . . . . . . . . . . .1-3
Conforms to Industry Standards . . . . . . . . . . 1-4
Storage Area Network . . . . . . . . . . . . . . . . . . . . . . 1-5
Computer Platform. . . . . . . . . . . . . . . . . . . . . .1-5
1
Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5
Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6
Label Printers. . . . . . . . . . . . . . . . . . . . . . . . . . .1-7
Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
Required Personnel. . . . . . . . . . . . . . . . . . . . . . . . . 1-9
System Administrator Tasks . . . . . . . . . . . . . .1-9
Library Operator Tasks . . . . . . . . . . . . . . . . . 1-10
Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11
GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11
API. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11
VolServ Operations. . . . . . . . . . . . . . . . . . . . . . . . 1-12
VolServ Console . . . . . . . . . . . . . . . . . . . . . . . 1-12
Library Console. . . . . . . . . . . . . . . . . . . . . . . . 1-15
System Log Console . . . . . . . . . . . . . . . . . . . . 1-17
Client Application Tasks . . . . . . . . . . . . . . . . . . . 1-20
Client Commands. . . . . . . . . . . . . . . . . . . . . .1-21
Introduction
Introduction
VolServ Overview
Roadmap
Topic
Refer To
Chapter
Introduction 1
How VolServ works 2
Technical support available to you 3
Glossary
1-2 Introduction 6-01001-01 Rev A
VolServ Overview
Media Management
The VolServ system is a combination of hardware and software
components that provide for UNIX-based hierarchal media
management. This architecture allows you to combine various
modules to satisfy differing data storage requirements.
Depending on the configuration you select, your system storage
capability can range from one to over 100 terabytes.
VolServ provides:
• Centralized management of storage media.
• Control of storage media architectures.
• Automation of mounting and dismounting media into
recording devices.
• Management services for media and drives for multiple
media types and multiple drive types.
VolServ controls and tracks the movement of all media under its
control. This includes media movement within robotic libraries,
media movement to and from storage bins, and media
movement to and from recording devices.
Introduction
VolServ also provides automatic media migration between
different libraries to ensure transparent movement of media
between all levels of storage. The source and destination
libraries must support the same media types as the media
undergoing migration. In addition, these libraries must be
associated with the MediaClass groups to which the media
belong. Source and destination libraries can be either robotic or
manual. An example of migration between libraries is when
media moves from a robotic library to a manual library because
the robotic library is full.
6-01001-01 Rev A Introduction 1-3
VolServ Overview
Conforms to Industry Standards
Because VolServ conforms to the concepts of the Institute of
Electrical and Electronics Engineers (IEEE) Mass Storage
Reference Model, it can readily adapt to future innovations in
media storage architecture.
Currently, VolServ supports a large range of configurations
from networks of workstations to large supercomputers. It is
flexible enough to interface with several types of file serving
software and services a wide variety of robotic and manual
libraries.
1-4 Introduction 6-01001-01 Rev A
VolServ Overview
Storage Area Network
The storage area network consists of a UNIX server, storage
libraries, drives, and label printers as shown in the illustration
below:
VolServ
Server
Label
Printer
Library
Drives
Library
Library
Consoles
Introduction
Computer Platform
Libraries
The computer platform is the host computer for VolServ, and is
currently implemented on Solaris and IRIX platforms.
Storage libraries provide the location for the media, as well as
the structures to support the storage drives. A mass storage
system often includes a combination of robotic and manual
libraries that house several media types. A robot or an operator
delivers the media to the storage drives. A library recognizes
media by external barcode labels or by location.
6-01001-01 Rev A Introduction 1-5
VolServ Overview
Drives
The client application uses drives to store and to retrieve data
from selected media. VolServ allocates drives for the client
application to use and controls the movement of media into and
out of the drives. The client application controls the Read/Write
activities and the release of the media from the drive after the
data is processed.
The client application provides the VolServ system with a
media name or Media Class group and a drive or a drive pool.
The system completes the activity and notifies the client
application when a media is mounted or moved.
Media Types VolServ supports the types of media listed in the table below.
For a current list, contact your VolServ sales representative.
• 4 mm tapes
• 8 mm tapes
• 3480 tapes
• 3490 tapes
• 3490E tapes
• 9840 tapes
• Advanced Intelligent Tape (AIT)
• Digital Linear Tape (DLT) including CTIII and CTIV
• D-2, D-3 digital tapes
• DTF, DTF-2 tapes
• LTO (linear tape-open technology) tapes
• MO5.25 magneto optical
1-6 Introduction 6-01001-01 Rev A
• NCTP (next compatible tape product) tapes
• RF5.25 optical
• ST-120 tapes
VolServ Overview
Label Printers
VolServ uses barcode labels to organize media in the various
libraries. All robotic libraries include a machine-readable
barcode scanner. Each media must have an acceptable barcode
label when it enters the system. VolServ can operate with
preprinted labels or it can use the label making facilities of the
software and an attached barcode label printer.
Media can also use a human-readable label that is separate from
the barcode to provide the correct row, column, shelf, and bin.
These labels can be preprinted or made on an attached label
printer.
Introduction
6-01001-01 Rev A Introduction 1-7
VolServ Overview
Connectivity
Network connectivity depends only on the UNIX platform that
VolServ is installed on—Sun or SGI.
VolServ supports connectivity over the following
industry-standard interfaces:
•DECNet
• Ethernet
• Fiber Distributed Data Interface (FDDI)
• HYPERchannel
• UltraNet
1-8 Introduction 6-01001-01 Rev A
VolServ Overview
Required Personnel
Because the VolServ system virtually runs itself, only the two
positions below are required to manage it:
• System administrator
• Library operator
Tip
The same person can perform both positions.
VolServ supports the division of GUI commands according to
the responsibilities of these positions—system administrator
and library operator. Separate access for these two types of
personnel is maintained through the use of a login identifier
(ID).
• The system administrator login ID provides access to all
VolServ functions.
• However, the operator login ID allows access only to a
subset of these commands.
Introduction
System Administrator Tasks
6-01001-01 Rev A Introduction 1-9
The system administrator’ s role is to configure, install, upgrade,
process, and secure the entire VolServ system. Specifically, this
individual defines the system administrator and client
applications during initial software installation. The system
administrator also defines client privileges based on your site’s
needs.
System administrators work directly with VolServ through the
GUI. The GUI provides access for configuration,
reconfiguration, library management, media management,
resource allocation, and daily maintenance operations for the
volume server system.
VolServ Overview
Library Operator Tasks
The library operator’s role is to be responsible for library
operations that require human intervention. This person
interfaces with each library console to perform all
library-specific requests. The number of library operator
positions is determined by the number of libraries that are
installed with your mass storage system and the extent of media
movement. Operator tasks are generally routine and are usually
in response to a client program’s request.
1-10 Introduction 6-01001-01 Rev A
VolServ Overview
Tools
GUI
VolServ uses the following components to manage media in
supported libraries:
• Graphical User Interface (GUI).
• Command Line Interface (CLI).
• Application Program Interface (API).
The VolServ System Administrator GUI runs under the
OSF/Motif™ window manager. You can access the GUI:
• Directly from the VolServ console.
• Remotely via a network. Remote access requires the remote
computer to support the X-windows system and a window
manager.
The UNIX shell used to initiate the GUI must be configured
with certain environment variables. These environment
variables are established through the software installation script
and are listed in the Installing VolServ book.
Introduction
Commands
API
6-01001-01 Rev A Introduction 1-11
Commands are received through a layered Ethernet interface
that allow multiple clients to share the same interface.
The API interfaces directly with the client application software.
VolServ Overview
VolServ Operations
VolServ Console
The graphical operations are functionally grouped and accessed
through the following consoles:
Console Page
VolServ Console 1-12
Library Console 1-15
System Log Console 1-17
The VolServ console provides access to volume server logical
operations and administrative functions.
VolServ
Console
Label
Printer
Library
Consoles
Library
Library
This console is generated when it is requested by a system
administrator. Access is controlled through the use of
passwords. Multiple VolServ consoles can be used
simultaneously by system administrators.
1-12 Introduction 6-01001-01 Rev A
VolServ Overview
Note
VolServ must be installed, but does not have to be running for
the VolServ console to be initiated.
The VolServ console is grouped into the following functional
categories:
• Media Operations
• Administration
• Configure
• Queries/Reports
These categories are also provided to the client interface with
the exception of Lock Drive, Connect Enterprise,
Disconnect Enterprise and Noop, which is an interface
ping and is effectively satisfied by the presence of the screen.
Introduction
The following table shows the specific commands available
through the VolServ console:
6-01001-01 Rev A Introduction 1-13
VolServ Overview
VolServ Console Commands
Media Operations Administration Configure Queries & Reports
Import Cancel Archive * Intransit Media
Export Reprioritize MediaClass * Archive
Checkin Vary Drive Arc. MediaClass * Drive
Checkout Vary Archive Drive Pool * Request
Mount Vary Arc. Comp. Define Label Pattern Drive Pool
Dismount Change Arc. Mode Delete Label Pattern MediaClass
Manual Eject Reprint Media
Define Drive Media Location
Labels
Clear Eject Unlock Drive Delete Drive Mount
Reclassify Associate Drive Media
Move Disassociate Drive Media Type
Define Media Type Connect
Redefine Media
Type
* Create, Modify, and Delete
Detailed descriptions of all commands are included in the
Command Reference book.
1-14 Introduction 6-01001-01 Rev A
VolServ Overview
Library Console
A library console is used to execute media movement
commands and to manage the media stored within an individual
library.
VolServ
Console
Library
Label
Printer
Library
Consoles
Library
A volume server system has as many library consoles as
configured libraries, because each library has its own library
console. This console is primarily used by a library operator.
VolServ creates and displays library console windows when the
system is brought up. When the operator configures the system,
each library console is assigned by VolServ and is displayed on
the workstation designated by the System Administrator. An
example of the library operator's console is shown below.
Introduction
6-01001-01 Rev A Introduction 1-15
VolServ Overview
After the VolServ system is operational, changes to a library
system can be made using the reconfiguration functions through
the VolServ console. When the configuration is updated,
VolServ automatically regenerates and displays a new library
console for the altered library system. This feature allows
reconfiguration to affect only the library system for which the
actual changes occur.
Library console functionality is specialized for each type of
library architecture. The functions needed to operate each type
of library system cause the library to differ between supported
library architectures. The following table depicts the
information provided on each console type:
Robotic Library Manual Library
Library Tower Shelf Stage
Enter Enter Enter Enter
Eject Eject Eject Eject
Audit Audit Mount Mount
Dismount Dismount
Audit Audit
Reprint Labels
Enter command provides a variety of conditions for entry
The
including a move, import, check in, and migration. Thus,
auxiliary screens are provided to allow the operator to establish
acceptable defaults if the standard default needs changed, to
determine the conditions under which the operator wants an
enter to fail, and to determine salient characteristics about the
proposed media class including fill level, and so on.
1-16 Introduction 6-01001-01 Rev A
VolServ Overview
The audit command is more powerful than the one given to
the client because the library operator can exercise the audit of
not only the entire library, but also of a subdivision of the
library. The operational concept assumes most media
discrepancies are resolved by the operators. The selectable
audit is a powerful tool to reconcile suspected inconsistencies
in the data base.
Introduction
System Log Console
A system logging console is provided to display the system
messages.
VolServ
Console
Label
Printer
Library
Library
Library
Consoles
System logging consoles are generated automatically by
VolServ. The displayed message levels are defined by the
system administrator during initial system configuration.
System messages, generated during system operations, provide
information about events occurring within the volume server
system. System logging consoles should be monitored or
checked periodically by a system administrator for notices or
errors that may occur.
6-01001-01 Rev A Introduction 1-17
VolServ Overview
Message Logging Levels
When a given logging level is set, all messages at the selected
level or higher display. The logging consists of seven levels of
Unix-like messages. System logs can be directed to operator
consoles and/or one or more files. VolServ Error Messages
documents all messages in levels 0 through 6. This manual
includes a description of the event causing the message to
occur, and a description of what action should be taken, if any.
The following table shows the levels of a system logging
console:
0 Emergency Indicates the volume server system is terminating abnormally.
1 Alert Requires immediate human intervention to continue normal
processing.
2 Critical Requires timely human intervention to prevent a situation from
becoming worse.
3 Error Conditions that need human intervention to avoid becoming a
problem.
4 Warning Requires no immediate human intervention at this time , but could
potentially develop into a problem.
5 Notice Message indicating a normal VolServ software system operation.
6 Inform Messages resulting from normal VolServ software system
operations.
In addition to the seven levels, additional lower level software
maintenance level messages exist. These maintenance le vels are
disabled during normal operations because of the potential
degradation of system performance. They can be readily
activated for software or operations tracing.
1-18 Introduction 6-01001-01 Rev A
VolServ Overview
Maintenance levels include detailed logging to debug software
problems, a trace capability invoked each time a software
function is called, data base message logging, and logging of all
interface traffic whether generated through the RPC interface or
the IPC interface.
Introduction
6-01001-01 Rev A Introduction 1-19
VolServ Overview
Client Application Tasks
VolServ is designed to support two types of users:
• Operational personnel who interface through a GUI. Such
as, system administrators and library operators.
• Client applications.
Operational personnel and client systems perform different
roles and require correspondingly different interfaces with
VolServ. Many capabilities are offered over both interfaces to
support the application of the volume server system to a wide
variety of roles and missions as discussed in the introduction.
VolServ provides a control and status interface to a client
application over a network. VolServ is connected to client
program computers through an Ethernet or Fiber Distributed
Data Interface (FDDI) connection and uses standard protocols.
This connection allows multiple client systems to share a
volume server system.
A client system is a hardware and software package performing
data management services for the client's own use or as an
intermediary to other client programs. VolServ provides a
high-level client interface to relieve the client system of the
need to know the underlying storage architecture.
Multiple client systems may interact with VolServ through the
programmatic interface. This communication link between a
client program and VolServ is available using standard
protocols over a Local Area Network (LAN).
1-20 Introduction 6-01001-01 Rev A
VolServ Overview
The client interface can be implemented as an application
program or as a modification to an operating system. The
commands sent by an application program are structured to pass
the required information to the volume server. One volume
server can simultaneously perform similar services for several
client applications.
Operating systems may be designed or modified to include file
management functions. If the operating system provides file
management, a user would not use an application program to
access the volume server system. The VolServ interface would
be included as part of the operating system. Application
programs issue commands through the operating system that
access the volume server transparently.
Introduction
Client Commands
A client application generates volume server requests through a
programmatic interpretation of the selected operations.
Selection can be tailored by authorizing and developing the
command interface for all or any subset of the total client
command capabilities provided by the volume server.
VolServ accepts a command, takes appropriate action, and
returns status for the client commands shown in the following
table:
6-01001-01 Rev A Introduction 1-21
VolServ Overview
.
Client Commands
Media Operations Administrative Configuration Query and Vary
Mount Audit Connect Library query
Dismount Archive vary Createarcmc Connect query
Checkin Drive vary Create class Drive pool query
Checkout Cancel Create pool Drive query
Import Lock Deletearcmc Intransit query
Export Unlock Delete class Media class query
Clear eject Reprioritize Delete pool Media query
Move Noop Disconnect Media type query
Reclassify Modify class Query mount
Modifyarcmc Request query
Modify pool
Detailed descriptions of all commands are included in the
Command Reference book.
The client application can vary a library or a drive online,
offline, or in diagnostic mode. This capability is primarily used
by client applications with dedicated drives or libraries as part
of volume server systems. A client application that runs a vary
command can place the drive or library in a new state without
requiring attendance by the system administrator.
Moreover , a client application can request an
audit of an entire
library.
• If the library is robotic, the audit is initiated as soon as
resources (a robot) can support it based on the priority given
to the audit.
1-22 Introduction 6-01001-01 Rev A
VolServ Overview
• Howe ver, if the library is manual, the volume server prints a
list of media in the library and highlights <Audit> on the
Library Manager console for the manual library to request
the library operator to verify the audit. If the audit is for an
ADIC/GRA U DataShelf library , the media list provides ro w ,
column, shelf, and bin for each media.
Introduction
Configuration Commands
A client application has three sets of configuration commands
available to support media management functions. These
configuration functions can also be accomplished by the system
operator. The client application can exercise full control of the
mount strategy by:
• Establishing specific MediaClass groupings.
• Assigning those MediaClass groups to specific library.
• Establishing client-specific drive pools.
The client application has the freedom to modify or to delete
those same classes and pools.
Query Commands The client application also has a large set of query commands
that allow investigation of key elements of the databases when
needed.
query commands provide options that allow the client to
Most
obtain only the basic information about the object of the query.
In addition, they provide an option to request detailed
information.
6-01001-01 Rev A Introduction 1-23
VolServ Overview
For example, a Media Class Query can be initiated with a
query option reporting on either a single selected MediaClass
group or on all MediaClass groups. This same query can either
provide information about the MediaClass group or provide
additional data about each media in the class such as
Manufacturer/Batch, last dismount, current library, action state,
and so on.
1-24 Introduction 6-01001-01 Rev A
NOTES
VolServ Overview
Introduction
6-01001-01 Rev A Introduction 1-25
VolServ Overview
NOTES
1-26 Introduction 6-01001-01 Rev A
Centralized Media Management . . . . . . . . . . . . .2-3
MediaClass Grouping . . . . . . . . . . . . . . . . . . . 2-4
Media Migration . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Drive Pool Configuration . . . . . . . . . . . . . . . . 2-6
Media and Drive Mounting. . . . . . . . . . . . . . . 2-8
2
How VolServ
Works
How VolServ
Works
VolServ Overview
Roadmap
Topic
Refer To
Chapter
Introduction 1
How VolServ works 2
Technical support available to you 3
Glossary
2-2 How VolServ Works 6-01001-01 Rev A
VolServ Overview
Centralized Media Management
VolServ allows you to manage all the libraries for all your users
from one central point of command. To accomplish this task,
the software provides industry-standard interfaces to the client
and offers a number of capabilities to help you receive
maximum benefits from your mass storage resources.
After a client application requests media to be mounted,
VolServ performs the following steps:
Step 1. VolServ searches its internal database to locate the
volume.
Step 2. VolServ then determines which drive nearest to the
media’s location is free.
VolServ finds the volume and issues commands to
either a system operator or a robot, depending on
whether the volume is stored in a manual library or a
robotic library, to mount the media in a drive.
If the volume is stored in a manual library, VolServ
tells you its exact location. In addition, it tells you
where to mount the volume. If the cassette is in a
robotic library, VolServ tells the robot the exact
location of the volume and the appropriate drive in
which to mount it. This process is completely
transparent to the user.
How VolServ
Works
Step 3. Status is returned to the client application. The status
confirms that the media is mounted and reports the
drive identifier on which the media resides. This
process is transparent to the application user and the
client application is free to perform other work while
the mount request is processed.
6-01001-01 Rev A How VolServ Works 2-3
VolServ Overview
MediaClass Grouping
MediaClass grouping is a media management tool that
segregates media into classes. You can base MediaClass
groupings on client control and security needs. Therefore, your
accountants can have their own MediaClass grouping, the
geophysicists can have their own, and management another.
You can also use MediaClass groupings to effect preferred
placement and, thus, optimize mount activities. You can assign
these groupings to span any libraries containing the same media
type. When the MediaClass grouping is set up to span two or
more libraries, media can freely move between these libraries,
mounts can be serviced when the media is in one library and the
drive in another, and media migration can be activated.
Membership Membership in a MediaClass grouping is exclusive. A media
can belong to only one of these groupings. MediaClass
groupings are restricted to one type of media. For example, a
D-2 small media cannot enter a MediaClass grouping that
contains D-2 large media. Media initially enter a grouping when
they are imported into the VolServ system. You can establish a
default MediaClass grouping to simplify media import into
robotic libraries using the autoimport capability. You can also
enter the Media-Class grouping by using the Import command.
Media Migration
Media migration moves media from one library to another
based on parameters that you specify. For example, VolServ
knows when the least recently used media in a robotic library
should be migrated to a manual library. You can migrate media
between robotic libraries to keep your critical data in a faster or
more conveniently located robotic library. Media can even be
migrated from one manual to another manual library . Therefore,
VolServ media migration allows you to create a hierarchy of
libraries according to the way you need to do business.
2-4 How VolServ Works 6-01001-01 Rev A
VolServ Overview
Scenario The system administrator is responsible for setting up a media
migration hierarchy for libraries containing the same media
type. In this scenario, the hierarchy is composed of two
libraries, one robotic and one manual, that contain the same
media type. The robotic library holds scratch media, which is
media that is not yet dedicated for a specific purpose. The
scratch media is converted to a user-assigned MediaClass
grouping before it begins to record data. The media remains in
the robotic library for a period of time during which it
undergoes several mounts. When the system reaches a media
threshold, the least-recently used media in the MediaClass
grouping is marked for migration to the manual library. The
manual library maintains the media for any amount of time you
determine. It can, however, be recalled from the manual library
for use in the robotic library whenever your requirements
dictate. When you no longer need the data on the media, you
can export it from the VolServ system.
Other uses of media migration include the following:
How VolServ
Works
• Migration from one robotic library to another robotic
library.
• Migration from one manual library to another manual
library.
• Migration to balance the load between two similar libraries
with several clients.
• Migration to ensure that when a media is added to the
MediaClass grouping, it triggers the removal of another
media.
Associated Parameters
To ensure organized data management, each MediaClass
grouping has associated parameters that you specify. These
parameters include capacity, high threshold, and low threshold.
6-01001-01 Rev A How VolServ Works 2-5
VolServ Overview
The capacity parameter specifies the maximum number of
media in each MediaClass grouping within the system. The
high threshold percentage parameter can be any integer value
between 0 and 100, inclusive. This parameter triggers the
migration process. The low threshold percentage parameter can
also be any integer value between 0 and 100, inclusive. This
parameter specifies the minimum number of media maintained
in the system.
You set the high threshold and low threshold parameters as
percentages of the capacity of the MediaClass groups.
Therefore, you do not need to recalculate these parameters
when the capacity of the MediaClass group changes. The sum
of the capacities of the various MediaClass groups can exceed
the capacity of the library.
When the high threshold is reached, you receive a notification
message. If migration does not occur, you continue to receive
notification messages as new media enter the MediaClass
grouping. At capacity, no additional media can be assigned to
the grouping until some of the media are removed or migrated.
When migration occurs automatically, VolServ determines how
many media to remove to reach the low threshold parameter.
Drive Pool Configuration
VolServ can mount requests for a specific drive, and it allows
you to configure drive pools to manage multiple media mounts
for optimum system performance. VolServ dynamically
allocates drives based on need. If the closest drive is in use, our
software queues the mount to the next most con venient dri v e. In
addition, our software continually scans your libraries to find
the most efficient drive mounting solution. You can even
request a specific drive to be used.
2-6 How VolServ Works 6-01001-01 Rev A
VolServ Overview
Logical Grouping of Drives
A drive pool is a logical grouping of drives associated with one
or more compatible libraries. You can base your drive pools on
client control and security needs. You can also organize them to
support preferred media placement of an entire MediaClass
grouping to optimize mount activities. Although EMASS offers
the standard volume server capability to mount on a
client-specified drive, a drive pool frequently offers more rapid
media mounting even when media migrates from one library to
another.
Scenario For this example, the drive pool organization is for a system
configuration that has two libraries, each with four drives and
two clients accessing the system. Although only four drive
pools are described, you could construct more drive pools.
Drive pool 1 contains all four dri ves in library A. The adv antage
you obtain by including all the drives in a library in one drive
pool is that it enables the immediate mounting of a media when
a drive becomes available. If the mount is queued, it is a
candidate for the first available drive.
Drive pool 2 has two drives in each library, which is ideal if
MediaClass groupings are also in both libraries. To improve the
system operation, the client could include all drives in one
library and some drives in the other . In this situation, the limit of
two may be selected to ensure that Client B never takes all the
resources in Library A.
How VolServ
Works
Drive pool 3 has two drives in Library A. The drive pool could
be a second pool for Client A or for Client B. For example,
Client A may use drive pool 1 for data capture. Then Client A
may use drive pool 3 for data playback that is not as critical and
ensure playback operations never take all the resources.
6-01001-01 Rev A How VolServ Works 2-7
VolServ Overview
Drive pool 4 currently has only one drive. This situation occurs
for several re asons. Drives can be added or subtracted from a
pool. Therefore, a temporary state is established where drives
are added or the pool is eliminated. Alternately, a client may
have committed to request all mounts by drive pool, but this
function is of lower priority and, therefore, has only one drive.
Finally, drive 8 does not belong to any drive pools. This drive
can be mounted by requesting the specific drive.
Membership VolServ provides the capability to group drives to assist you in
managing the mount and dismount of media. Drives are
physically connected to one or two clients and are associated
with one robotic or manual library . VolServ allows you to select
a single drive for any given mount activity. However, the
EMASS logical grouping of drives complements this capability
by allowing VolServ to select the most appropriate drive.
Membership in a drive pool is non exclusive. A drive is not
required to belong to a drive pool. You can use the drive by
selecting it in any Mount command. A drive belonging to one
drive pool can be assigned to one or several additional pools.
Note, however, that drive pools are restricted to the types of
media handled by the library.
Media and Drive Mounting
VolServ mounts a selected media on any acceptable drive
quickly and efficiently. However, VolServ allows you to select
media and a drive in any of the following ways:
2-8 How VolServ Works 6-01001-01 Rev A
Option Description
VolServ Overview
Media
Specific Media The client wants any one of several media
mounted. One and only one media is
mounted with this command. VolServ locates
and mounts the media on the nearest
available open drive (if given a choice) or on
the requested drive. The system queues the
command if either the media or drive is busy.
MediaClass Grouping The client wants any media in the MediaClass
mounted. This option is especially useful for
mounting a scratch tape for recording.
VolSer v locates an available mount with the
least robotic movement (and operator
involvement).
Drive Specific Drive The client identifies one and only one driv e for
the mount. If the drive is busy, the mount
queues independent of av ailab le media. If the
drive is av ailabl e and in a diff erent library from
the media, a media movement is required to
move the media to the drive. VolServ controls
each step of the mount, including requests to
the library operator to move the media, if
required.
How VolServ
Works
Drive Pool The client identifies any drive in a drive pool
acceptable for mount. The drive pool can
have from one to ’n’ drives, which can be
located in one or more libraries. V olServ looks
for an open drive in the requested pool that
satisfies the mount with the least media
movement.
Drive Pool with
Exclusions
The client identifies a drive pool, b ut excludes
certain drives. With the exception of the
excluded drives, VolServ treats the mount as
a drive pool mount.
6-01001-01 Rev A How VolServ Works 2-9
VolServ Overview
NOTES
2-10 How VolServ Works 6-01001-01 Rev A
Phone Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
Training. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Solutions Group . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Books. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4
Online Books . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Related Publications . . . . . . . . . . . . . . . . . . . . .3-6
Contact Publications Department. . . . . . . . . . 3-6
Secured Web Site. . . . . . . . . . . . . . . . . . . . . . . . 3-6
3
Technical
Support
Technical Support
VolServ Overview
Roadmap
Topic
Introduction 1
How VolServ works 2
Technical support available to y ou 3
Glossary
Refer To
Chapter
3-2 Technical Support 6-01001-01 Rev A
VolServ Overview
Phone Support
Training
Depending on how you purchased technical support, telephone
support is provided either through your reseller or directly
through ADIC.
The ADIC Technical Assistance Center in Denver, Colorado
provides world-wide service and support.
• In the USA and Canada, call 1-800-827-3822.
• Outside the USA and Canada, call 303-874-0188 or toll-free
00800-9999-3822.
• Send e-mail to: support@adic.com
The training organization in Denver provides hands-on
instruction for ADIC products.
For a list of classes, call 303-792-9700 between 8 a.m. and 5
p.m. Mountain time.
Solutions Group
6-01001-01 Rev A Technical Support 3-3
The ADIC Integrated Storage Solutions group can provide
solutions and services customized for your site’s requirements.
These solution include:
• Analyzing requirements.
• Designing, configuring, and tuning your system.
• Customizing hardware and software solutions.
For more information, call 303-792-9700 between 8 a.m. and 5
p.m. Mountain time.
Technical Support
VolServ Overview
Books
The books described below are part of the technical
documentation set, and are shipped on CD along with the
VolServ software:
Overview
Provides an ov erview of VolServ . Co ntains a
glossary.
Installing VolServ
Describes server requirements, installation
instructions, troubleshooting procedures,
and configuration parameters.
Using the VolServ GUI
Describes how to perform system
administrative tasks using th e graphical user
interface.
API Guide
Provides a list of API functions.
Administrative Tasks
Describes how to perform system
administrative tasks using VolServ
commands.
Command Reference
Contains a list of VolServ comman ds
Error Messages
Provides corrective action f or system log
errors.
Quick Reference Card
Summarizes commands.
Online Books
The documentation CD contains VolServ book files and
requires the Adobe® Acrobat® Reader to view the
accompanying electronic documentation. The Reader allows
you to view and navigate the electronic documentation files yet
preserves the page design and graphics from the printed books.
Using the Reader After downloading the Reader and VolServ books from the CD
onto a server, you can:
• Resize the Reader’s viewing window to suit your needs.
3-4 Technical Support 6-01001-01 Rev A
VolServ Overview
• Insert your own bookmarks in the VolServ books as a quick
reference to important or frequently needed VolServ
information.
• Print one page, a sequence of pages, or the entire VolServ
book.
Benefits Online access to VolServ books provide the following benefits
to our customers:
• Up-to-date: Because books must be printed at least a month
in advance of the scheduled software release date, delayed
information frequently cannot be included. CDs, however,
can accommodate last minute information because
production lead time is lessened. As a general statement,
assume that the electronic version is more current than the
printed version.
• Relevant: Online information is more applicable for our
customers’ needs because system administrators—the
audience for our books—are probably already sitting in
front of and using a computer to operate VolServ.
• Fast and Easy: Online information is fast and easy to
navigate using hypertext links (cross-references, tables of
contents, and indexes) and the Reader’s search feature.
6-01001-01 Rev A Technical Support 3-5
Technical Support
VolServ Overview
Related Publications
Related Publications Description
“Release Notes” For each version of VolServ, the “Release Notes” contain:
“Product Alerts” Informs customers of technical problems and solutions.
“Product Bulletins” Conveys technical information—not problems—to
The publications described in the table below are created and
distributed on an as-needed basis.
• Summary of enhancements
• Describes:
- Fixed problems
- Known problems
- Installation and configuration issue.
•Lists:
- Operating system patches
- System requirements
customers.
Contact Publications Department
Secured Web Site
To make corrections or to comment on VolServ publications,
please contact Software Technical Publications at our e-mail
address: techdocs@adic.com.
To receive access to the secured site on our home page
containing technical product information (Release Notes,
Product Alerts, Product Bulletins, FAQs), visit
http://partners.adic.com/ and follow the password request
procedure. In return, ADIC will send you instructions and a
password.
3-6 Technical Support 6-01001-01 Rev A
NOTES
VolServ Overview
6-01001-01 Rev A Technical Support 3-7
Technical Support
VolServ Overview
3-8 Technical Support 6-01001-01 Rev A
archive
Glossary
Note
The terms in this Glossary are used
throughout the ADIC UNIX software
documentation. Product-specific terms are
noted.
A
AIT
Advanced Intelligent Tape.
API
Application Programming Interface. The
API consists of functions, iterators,
symbolic names, type definitions, and
data structures. Using the API provides
the programmer with the ability to
directly manipulate file system metadata
(such as,
appended files
Files that span media. The files are on
more than one piece of media, possibly,
on more than one library.
namespace) and media.
Generally used to denote a file that is
stored on lower cost media than a hard
disk. The goal for implementing data
archiving is to conserve online storage
space. Contrast with backup.
B
backup
A file that has been backed up means that
a copy of the file exists in another
location. If the original file is lost, the
backup file is used. Having a backup file
protects you against loss or damage of
the original data. Contrast with archive.
barcode
An array of spaces and vertical bars in
varying widths in a machine-readable
pattern. Tape media is identified by
barcode rather than a physical home
storage slot.
6-01001-01 Rev A GL-1
Glossary
VolServ Ov erview
C
client
Program running on a workstation
requests the services provided by a
network server. Part of a client/server
architecture.
D
DataClass group
Migration directories with the same
associated data class parameters are in
the same DataClass grouping. A
FileServ-specific term.
dead space
Random space that remains on a volume
after files have been deleted.
E
Ethernet
A networking system designed to
connect computers that are releatively
close together (physically in the same
department). The specification has been
defined by IEEE Standard 802.3. Other
software, such as TCP/IP, runs on top of
Ethernet to provide high-level
networking services to applications.
F
FCB
File Control Block. A kernel file system
memory resident data structure
containing information about a file
including metadata.
™
DLT
Digital Linear Tape.
drive pool
A logical grouping of drives that pro vide
drive sharing capability between clients.
A FileServ-specific term.
drives
A physical device used to read and write
data on media.
GL-2 Glossary 6-01001-01 Rev A
FDDI
Fiber Distributed Data Interface A
high-speed fiber-optic local area network
that is based on the token ring standard.
file
A collection of related data, such as:
•Text
•Tables
• Digitized audio and visual records
VolServ Overview
FileServ
FileServ acts as an online storage node
for specific libraries by managing online
user data and providing quick response to
client requests for data. When data is not
required for active processing, FileServ
migrates it to magnetic tape to maintain
free disk space.
™
G
GUI
Graphical User Interface. The human
juncture between an end user and a
software product. It contains a series of
pictorial menus that lead a user in a task
accomplished usually with a mouse,
instead of a keyboard.
H
HSM
Hierarchical Storage Management. A
data management strategy where data is
migrated to storage in either a layered or
serial method based on a set of policies.
A paradigm that often controls this
migration is frequency of access. For
example, the least frequently accessed
files are first migrated onto fast magnetic
tape which are later stored on slower
optical platters. The goal for
implementing an HSM strategy is to
provide clients with increased space on
existing disk drives. See also FileServ™.
I
IP address
Central to TCP/IP communication is the
IP address that allows devices to talk to
each other. The IP address is a device’s
logical network address consisting of a
four-byte number separated by full stops,
such as 128.8.14.92.
IPI
Intelligent Peripheral Interface. A
high-performance, general-purpose
parallel peripheral interface. The intent
of the IPI is to isolate the host, both
hardware and software, from changes in
peripherals by providing a “function
generic” command set to allow the
connection of multiple types of
peripherals (disks, printers, and tapes.)
Glossary
6-01001-01 Rev A Glossary GL-3
VolServ Ov erview
L
label
A tag affixed to media used for
identification. For example, a barcode
label is used by a robotic device to insure
the robot is moving the proper media. A
shelf label with human-readable
information has the same purpose.
library
A storage device for data containing one
or more drives. Usually, media is loaded
by a robotic (automated) picker. See also
and standalone drives.
M
mailbox
An opening on the front of a library
where media is loaded into the library
and unloaded to the outside world,
without opening the actual library. This
protects the inside of the library from
dust and dirt. Also known as a mailslot.
media
A storage object that, when mounted in a
drive, is used for read and write
operations. Media types include:
•Tape
• Optical
•CD
migration
The planned movement of data from one
library—and possibly from one type of
media—to another.
N
NFS
Network File System. Originally
developed by Sun Microsystems, it has
become the de facto standard for file
sharing between UNIX systems. NFS
was designed to be a distributed file
service that is operating
system-independent and machine-typeindependent. Consequently, any
computer system can supply files to
many different computer types. NFS uses
the Remote Procedure Call (RPC)
mechanism to perform tasks, read results,
and access remote files.
GL-4 Glossary 6-01001-01 Rev A
VolServ Overview
NIS
Network Information Service. Created
by Sun to make NFS easier to use. NIS
centralizes user and group name
databases for an entire domain. (A
domain consists of a master server, slave
servers, and clients.) NIS allows the
domain to be administered as if it were a
single system. NIS centralizes many of
the local network configuration
functions. NIS used to be called Yellow
Pages (YP).
O
optical
Types of optical platters are described
below:
• MO (Magneto Optical) is rewritable
optical. It uses both magnets and lasers
to write and read data on a plastic disc
having a magnetic layer. Data is
written when the laser beam heats bits
on the disc’s magnetic layer that are
then magnetically polarized by the
drive’s magnet.
• CCW (Continuous Composite Writes)
use the erasable (MO) method to write
files onto a disc but then locks the f iles
to the media with software.
• LIMDOW (Light Intensity Modulation
Direct OverWrite) speeds up the
process of writing to MO discs.
LIMDOW discs have one memory
layer instead of two and consequently
require only one pass to write instead
of two.
R
RAID
Redundant Array of Independent Disks.
Technique for using a group of disk
drives to improve performance, data
availability, or both.
RPC
Remote Procedure Call. Process that
supplies a program a set of procedures
that can be called remotely.
• Ablative™ is an IBM term for the
technology used to make WORM
media. Lasers burn the write into the
media thus ensuring that the media is
Write-Once Ready-Many (WORM).
6-01001-01 Rev A Glossary GL-5
Glossary
VolServ Ov erview
S
SCSI Fast/Wide
Small Computer System Interface. An
intelligent bus-level device interface.
Refers to a combination of Fast transfer
rate (10 MB per second) with a two-byte
wide (68 pins) connector, which results
in 20 MB/sec data transfer rate.
server
Programs running on a network server
provide computing or data services to a
client. Part of a client/server architecture.
slot
Referred to as a bin in some libraries. The
physical home storage slot where a single
piece of media resides. In standalone
drives, the slot is the same as the drive,
but in all other libraries that is not true.
Storage Area Network
A storage area network (SAN) is a
dedicated high-speed network over
which a variety of applications access
data on tape or optical storage systems.
T
TCP/IP
Transmission Control Protocol/Internet
Protocol. Runs on top of Ethernet to
provide high-level networking services
to applications. See also IP address.
thrashing
Unnecessary movement of the library’s
robotics. For example, retrieving disc 1,
then disc 6, then 1, then 6. Thrashing
causes access delays and premature
hardware failure.
SMP
Symmetric Multiprocessing. Making
efficient use of multiple processors
within a computer.
standalone drives
A storage device for data containing a
single drive. Usually, media is loaded
manually in a standalone drive. See also
library.
GL-6 Glossary 6-01001-01 Rev A
truncate
Remove the file data blocks from disk,
leaving the inodes on disk. Only files that
remain unchanged since the last storage
to media can have their data blocks
truncated from disk. A FileServ-specific
term.
U
VolServ Overview
UNIX
A computer operating system that runs
on workstations, servers, mainframes,
and supercomputers.
™
V
VolServ
Manages media and volumes contained
within both automated and manual
libraries.
™
W
Windows NT
An operating system with two
versions—one for workstations and one
for servers. Windows NT is designed to
run on a network. Each application runs
in its own little window on-screen.
Windows NT replaces the historically
standard command line interface with
pictures.
™
6-01001-01 Rev A Glossary GL-7
Glossary
VolServ Ov erview
NOTES
GL-8 Glossary 6-01001-01 Rev A
Adiministrative Tasks
A
Adobe Acrobat Reader. . . . . . . . . . . . 3-4
API. . . . . . . . . . . . . . . . . . . . . 1-11, GL-1
Appended Files . . . . . . . . . . . . . . . .GL-1
Archive. . . . . . . . . . . . . . . . . . . . . . .GL-1
Audience for Book. . . . . . . . . . . . . . . P-3
Audit . . . . . . . . . . . . . . . . . . . . . . . . 1-22
B
Backup . . . . . . . . . . . . . . . . . . . . . . .GL-1
Barcode . . . . . . . . . . . . . . . . . . . . . .GL-1
Bin . . . . . . . . . . . . . . . . . . . . . . . . . . GL-6
book
documentation set . . . . . . . . . . . . 3-4
Books
all titles in set. . . . . . . . . . . . . . . . 3-4
online . . . . . . . . . . . . . . . . . . . . . . 3-4
C
Client . . . . . . . . . . . . . . . . . . . . . . . . GL-2
Client Application Tasks . . . . . . . . . 1-20
Commands . . . . . . . . . . . . . . . . . . . . 1-11
configuration . . . . . . . . . . . . . . . 1-23
for clients . . . . . . . . . . . . . . . . . . 1-21
query . . . . . . . . . . . . . . . . . . . . . 1-23
via VolServ console. . . . . . . . . . 1-13
Connectivity. . . . . . . . . . . . . . . . . . . . 1-8
Console
library. . . . . . . . . . . . . . . . . . . . . 1-15
system log . . . . . . . . . . . . . . . . . 1-17
VolServ . . . . . . . . . . . . . . . . . . . 1-12
Conventions in Book . . . . . . . . . . . . . P-4
D
DataClass Group
definition. . . . . . . . . . . . . . . . . . GL-2
Dead Space . . . . . . . . . . . . . . . . . . . GL-2
DLT . . . . . . . . . . . . . . . . . . . . . . . . GL-2
Documentation Set . . . . . . . . . . . . . . . 3-4
Drive. . . . . . . . . . . . . . . . . . . . .1-6, GL-2
mounting options . . . . . . . . . . . . . 2-8
Drive Pool. . . . . . . . . . . . . . . . . 1-23, 2-6
definition. . . . . . . . . . . . . . . . . . GL-2
E
Error Messages . . . . . . . . . . . . . . . . . 1-17
logging levels . . . . . . . . . . . . . . . 1-18
Ethernet. . . . . . . . . . . . . . . . . . . . . . GL-2
F
Fiber Distributed Data Interface
definition. . . . . . . . . . . . . . . . . . GL-2
File . . . . . . . . . . . . . . . . . . . . . . . . . GL-2
appended. . . . . . . . . . . . . . . . . . GL-1
G
GUI. . . . . . . . . . . . . . . . . . . . .1-11, GL-3
H
HSM . . . . . . . . . . . . . . . . . . . . . . . . GL-3
I
IEEE . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Intelligent Peripheral Interface
definition. . . . . . . . . . . . . . . . . . GL-3
IP Address. . . . . . . . . . . . . . . . . . . . GL-3
IRIX . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
6-01001-01 Rev A Index INX-1
Adiministrative Tasks
L
Label . . . . . . . . . . . . . . . . . . . . . . . .GL-4
Label Printers. . . . . . . . . . . . . . . . . . . 1-7
Library . . . . . . . . . . . . . . . . . . . 1-5, GL-4
Library Console . . . . . . . . . . . . . . . . 1-15
Library Operator
tasks . . . . . . . . . . . . . . . . . . . . . . 1-10
Login ID. . . . . . . . . . . . . . . . . . . . . . . 1-9
M
Mailbox . . . . . . . . . . . . . . . . . . . . . .GL-4
Mailslot . . . . . . . . . . . . . . . . . . . . . . GL-6
Media . . . . . . . . . . . . . . . . . . . . . . . .GL-4
management. . . . . . . . . . . . . .1-3, 2-3
migration . . . . . . . . . . . . . . . .1-3, 2-4
mounting options . . . . . . . . . . . . . 2-8
optical. . . . . . . . . . . . . . . . . . . . .GL-5
supported types . . . . . . . . . . . . . . 1-6
MediaClass. . . . . . . . . 1-3, 1-23, 2-4, 2-5
Messages . . . . . . . . . . . . . . . . . . . . . 1-17
logging levels. . . . . . . . . . . . . . . 1-18
Migration . . . . . . . . . . . . . . . . . . . . . GL-4
N
NFS . . . . . . . . . . . . . . . . . . . . . . . . . GL-4
NIS. . . . . . . . . . . . . . . . . . . . . . . . . .GL-5
O
P
Personnel Required . . . . . . . . . . . . . . .1-9
publications
product alerts. . . . . . . . . . . . . . . . .3-6
product bulletins . . . . . . . . . . . . . .3-6
release notes . . . . . . . . . . . . . . . . .3-6
Publications Dept
email address. . . . . . . . . . . . . . . . .3-6
Purpose of Book . . . . . . . . . . . . . . . . .P-3
R
Reader . . . . . . . . . . . . . . . . . . . . . . . . .3-4
RPC . . . . . . . . . . . . . . . . . . . . . . . . . GL-5
S
SCSI . . . . . . . . . . . . . . . . . . . . . . . . GL-6
Server . . . . . . . . . . . . . . . . . . . . . . . GL-6
Slot . . . . . . . . . . . . . . . . . . . . . . . . . GL-6
SMP. . . . . . . . . . . . . . . . . . . . . . . . . GL-6
Solaris . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Solutions Group. . . . . . . . . . . . . . . . . .3-3
Standalone Drives . . . . . . . . . . . . . . GL-6
Storage Area Network. . . . . . . . . . . . .1-5
Support
technical . . . . . . . . . . . . . . . . . . . .3-3
System Administrator
tasks. . . . . . . . . . . . . . . . . . . . . . . .1-9
System Log Console . . . . . . . . . . . . .1-17
Online Books . . . . . . . . . . . . . . . . . . . 3-4
Operations . . . . . . . . . . . . . . . . . . . . 1-12
Optical
media . . . . . . . . . . . . . . . . . . . . . GL-5
T
Tasks
client applications . . . . . . . . . . . .1-20
library operator . . . . . . . . . . . . . .1-10
system administrator . . . . . . . . . . .1-9
INX-2 Index 6-01001-01 Rev A
TCP/IP . . . . . . . . . . . . . . . . . . . . . . . GL-6
Technical Support . . . . . . . . . . . . . . . 3-3
email address . . . . . . . . . . . . . . . . 3-3
Thrashing . . . . . . . . . . . . . . . . . . . . .GL-6
Tools . . . . . . . . . . . . . . . . . . . . . . . . 1-11
Training . . . . . . . . . . . . . . . . . . . . . . . 3-3
U
UNIX . . . . . . . . . . . . . . . . . . . . . . . . GL-7
V
VolServ
console . . . . . . . . . . . . . . . . . . . . 1-12
defined . . . . . . . . . . . . . . . . . . . . . 1-3
operations. . . . . . . . . . . . . . . . . . 1-12
W
Web
secured site. . . . . . . . . . . . . . . . . . 3-6
Adiministrative Tasks
6-01001-01 Rev A Index INX-3
Adiministrative Tasks
INX-4 Index 6-01001-01 Rev A
Loading...