ADIC Table Top Game FileServ User Manual

Administrative Tasks

FileServ Version 4.3

February, 2001

600716 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

Copyright © 1996-2001 by 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
10949 East Peakview Ave.
Englewood, CO 80111 USA
Phone: [phone]
FAX: [phone]

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 theRights in Technical Data and Computer Software clause at DFARS 52.227­7013 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: [e-mail].

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: [e-mail]

READER COMMENT FORM

ADIC includes this Form in an effort to provide the best possible documentation to our
customers. Please take a few moments to mail or FAX your response to:

ADIC
Software Documentation
10949 East Peakview Ave.
Englewood, CO 80111
FAX: [phone]
E-mail: [e-mail]

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

Contents

Preface

PurposeofThisBook................................................ P-3

WhoShouldReadThisBook ......................................... P-3

HowThisBookisOrganized ......................................... P-3

Conventions ....................................................... P-4

Books ............................................................. P-5

OnlineBooks.................................................... P-5

RelatedPublications ............................................. P-6

ContactPublicationsDepartment .................................. P-6

SecuredWebSite ................................................ P-6

System Tasks 1

InitializeFileServ ....................................................1-3

AccesstheHostServer ............................................1-3

InterfacetoVolServ ...............................................1-4

DrivePools ...................................................1-4

AssociateMediaClasswithLibrary...............................1-5

RegistertheConfiguration .........................................1-6

DefineDataClassGroups ..........................................1-6

AssociateDirectories ..............................................1-7

MediaUnderFileServManagement.................................1-8

CreateMigrationPolicies ..........................................1-9

RoutineProcessing..................................................1-10

600716 Rev A Contents 5

Administrative Tasks

StoreandTruncateFiles ..........................................1-10

DatabaseMaintenance ...........................................1-10

chk_point.pl .................................................1-11

checkDBALL.................................................1-12

keyBuildAll ..................................................1-14

CommandLineMode .........................................1-16

InteractiveMode .............................................1-17

RecoverDatabase.............................................1-19

TrashcanCleanup ...............................................1-20

StartupandShutdown ..............................................1-22

NormalStartup..................................................1-22

RecoveryProcessing .............................................1-23

ContingencyStartup .............................................1-23

NormalShutdown ...............................................1-25

AutomateSoftwareTermination................................1-26

ManagingSystemConfiguration......................................1-27

ModifySystemParameters........................................1-27

GeneralParameters ...........................................1-28

SystemAdministrationParameters .............................1-28

DefaultParameters ...........................................1-36

FileRetentionParameters......................................1-39

VolServ-specificParameters....................................1-40

InstallationParameters ........................................1-41

SoftwareMaintenanceParameters ..............................1-43

MediaStatsParameters........................................1-44

LoggingParameters...........................................1-44

Edit System Parameters .......................................1-46

ReconfigureSystemDevices ......................................1-47

6Contents 600716 Rev A

Administrative Tasks

Edit Devices with fsconfig Command ...........................1-48

AddaLibrary ................................................1-49

Edit Device ..................................................1-50

DeleteaDevice...............................................1-50

GenerateReport ..............................................1-51

ChangeComponentState .........................................1-53

AddandDeleteDrives ...........................................1-55

Fine-tuneParameters................................................1-57

ReallocateDrives ................................................1-57

ModifyTapeUsage ..............................................1-58

Redirect Policy Applications ......................................1-59

Operating Tasks 2

DataClassManagement ..............................................2-3

DataClassGroups ................................................2-4

ManipulateRelations.............................................2-10

AddRelationswithfsaddrelationCommand .....................2-10

FileManagement ...................................................2-22

Pathname.......................................................2-22

Links...........................................................2-22

Spanning .......................................................2-23

Clustering ......................................................2-24

ModifyFileAttributes............................................2-26

GenerateReport .................................................2-28

DataMigration .....................................................2-30

FileCleanup ....................................................2-30

MinimumTimeParameters .......................................2-31

600716 Rev A Contents 7

Administrative Tasks

Policies.........................................................2-31

StoragePolicy ................................................2-32

CleanupPolicy ...............................................2-34

OverflowPolicy ..............................................2-35

StoringandRetrievingData..........................................2-40

StoreFiles ......................................................2-40

CleanUpDatafromDisk .........................................2-42

CleanupbyFileName.........................................2-42

CleanupbyDataClass .........................................2-43

CopySecondaryFiles ............................................2-43

GeneralStorageProcessing .......................................2-44

RetrieveFiles....................................................2-46

RetrieveFilesfromTrashcan ...................................2-48

CleanupTrashcan ............................................2-50

RetrievePartialFiles ..........................................2-51

RetrieveSecondaryFiles.......................................2-52

DelayedDismount...............................................2-52

MediaManagement.................................................2-54

MediaServices ..................................................2-54

MediaClassGroupDefinitions .................................2-55

LoadandUnloadMedia ..........................................2-56

RemoveMedia ...............................................2-57

AddBlankMedia.............................................2-57

RemoveBlankMedia..........................................2-59

FormatMedia ...................................................2-61

Media Duplication ...............................................2-61

CopyMedia..................................................2-62

CopyFiles ...................................................2-63

8Contents 600716 Rev A

Administrative Tasks

MediaStates ....................................................2-63

StorageLimit....................................................2-65

GenerateMediaReports ..........................................2-66

MediaInformation............................................2-66

MediaList ...................................................2-68

Utilities 3

Utilities ............................................................3-3

fspic ............................................................3-3

autostartscripts ..................................................3-3

FileServandAmassAutostart ...................................3-4

dbcheck .........................................................3-4

keybuild.........................................................3-6

Trouble­shooting Tools 4

DataRetrievalFails ..................................................4-3

CommandsthatIDProblems..........................................4-4

DisasterRecovery ................................................4-4

Messages ...........................................................4-5

StatusMessages ..................................................4-5

SyslogMessages..................................................4-6

ExtractSyslogMessages ........................................4-6

LogFileMaintenance ..........................................4-6

SetUpFileServLogging ........................................4-7

RecoverData........................................................4-9

600716 Rev A Contents 9

Administrative Tasks

DumpData ......................................................4-9

RestoreData ....................................................4-11

AuditDatabase..................................................4-17

FileSystemRecovery..........................................4-17

DatabaseMaintenance ........................................4-18

RunningfsauditCommand ....................................4-18

TroubleshootSystemPerformance ....................................4-20

Reports............................................................4-21

DataClassReport ................................................4-21

MediaFragmentationReport......................................4-22

MediaMovementReport .........................................4-23

ResourceQueueReport ..........................................4-24

HistoryReport ..................................................4-25

ComponentStatisticsReport ......................................4-26

HardwareConfigurationReport ...................................4-27

ContactTechnicalSupport ...........................................4-29

Index

10 Contents 600716 Rev A

PurposeofThisBook.......................P-3

WhoShouldReadThisBook.................P-3

HowThisBookisOrganized ................P-3

Preface

P

Conventions...............................P-4

Books.....................................P-5

OnlineBooks...........................P-5

RelatedPublications.....................P-6

ContactPublicationsDepartment..........P-6

SecuredWebSite........................P-6

Preface

Administrative Tasks

NOTES

P-2 Preface 600716 Rev A

Administrative Tasks

Preface

Purpose of This Book

Who Should Read This Book

How This Book is Organized

This book describes the management tasks, utilities, and
troubleshooting tools used in operating FileServ.

This book is written for the system administrator who is
operating and troubleshooting FileServ.

It assumes the administrator has a strong familiarity with:

• UNIX operating systems.

• Applications running in their site environment.

This book contains the following chapters:
Chapter 1: Initial Tasks — Initialize FileServ, configure

interface with VolServ, perform start up and shut down,
configure system parameters, and tune system for better
performance.

Chapter 2: Operating Tasks — Manage: DataClass Groups,
files, migration, data, and media.

Chapter 3: Utilities — Using the FileServ utilities.
Chapter 4: Troubleshooting Tools — Troubleshoot operating

problems.

600716 Rev A Preface P-3

Administrative Tasks

Conventions

The conventions used throughout the FileServ 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 percent sign. % su root
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.

FS0000 03 204773 fsmedinfo
completed: Command Successful.

fsadmret

fsaudit newfilesystem

% remsh nodename -n dd if=/dev \
/tapedevicename/bs=20b | tar xvfb \

-20

(You should type the entire command without
the backward slash.)

A menu name with an arrow refers to a
sequence of menus.

P-4 Preface 600716 Rev A

Edit Policy -> Add Library

Administrative Tasks

Preface

Books

The books described below are part of the technical
documentation set, and are shipped on CD:

FileServ Overview

An overview of FileServ. Contains a
glossary.

Installing FileServ

Describes: server requirements, installation
procedures, configuration parameters, and
tools to troubleshoot install problems.

Error Messages

Summarizes error messages.

Online Books

The documentation CD contains FileServ book files and
Adobe® Acrobat® Reader. The Reader allows you to view and
navigate the online documentation files yet preserves the page
design and graphics from the printed books.

Administrative Tasks

System tasks, operating tasks, FileServ
utilities, and troubleshooting problems.

Command Reference

An alphabetical list of FileServ
commands.

quick reference card

Summarizes commands.

600716 Rev A Preface P-5

Administrative Tasks

Related Publications

Related Publications Description

“Release Notes” For each version of FileServ, 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:

-Fixedproblems.

- Known problems.

- Installation and configuration issues.

• Lists:

- Operating system patches.

- System requirements.

customers.

Contact Publications Department

Secured Web Site

To make corrections or to comment on FileServ publications,
please contact Software Technical Publications at our email
address: [e-mail].

To receive access to the secured site on our home page
containing technical product information, send email to
[e-mail] and include your: name, company, address,
telephone number, fax number, FileServ serial number (or enter
“reseller” if you are not a customer), and your email address. In
return, we will send you instructions and a password.

P-6 Preface 600716 Rev A

GeneralParameters..................1-28

SystemAdministrationParameters....1-28

DefaultParameters..................1-36

1

FileRetentionParameters............1-39

VolServ-specificParameters..........1-40

InstallationParameters...............1-41

SoftwareMaintenanceParameters.....1-43

MediaStatsParameters..............1-44

LoggingParameters.................1-44

Edit System Parameters ..............1-46

ReconfigureSystemDevices.............1-47

Edit Devices with fsconfig Command . . 1-48

AddaLibrary ......................1-49

Edit Device.........................1-50

DeleteaDevice.....................1-50

GenerateReport ....................1-51

ChangeComponentState ...............1-53

AddandDeleteDrives..................1-55

Fine-tuneParameters......................1-57

ReallocateDrives.......................1-57

System Tasks

System Tasks

ModifyTapeUsage.....................1-58

Redirect Policy Applications .............1-59

Administrative Tasks

Roadmap

Topic

Initialize FileServ, configure interface with
VolServ, perform start up and shut down, modify
system configuration, and tune system for better
performance.

Manage: DataClass Groups, files, migration,
data, and media.

Using the FileServ utilities. 3
Troubleshoot operating problems. 4

Refer To

Chapter

1

2

Note

For complete information on the FileServ commands used in
these tasks, refer to the Command Reference book. Status for
the commands used in these tasks is returned to the command
line.

Note

For complete information on the menus used in these tasks,
refer to the Using the FileServ GUI book.

1-2 System Tasks 600716 Rev A

Administrative Tasks

Initialize FileServ

Access the Host Server

Running FileServ for the first time involves the following tasks
listed in the table below:

T ask Page

Access the Host Server 1-3
Interface to VolServ 1-4
Register the Configuration 1-6
Define DataClass Groups 1-6
Associate Directories 1-7
Media Under FileServ Management 1-8
Create Migration Policies 1-9

To access the host where FileServ has been installed to transfer
files to or from the migration directories, use one of the
following methods:

• UNIX Remote Copy Protocol (rcp)

System Tasks

• File Transfer Protocol (FTP) session with put/get

• UNIX copy (cp) with an NFS mounted file system
A remote login (

rlogin)oraremoteshell(rsh) must be used

to issue FileServ commands when not logged into the FileServ
host.

600716 Rev A System Tasks 1-3

Administrative Tasks

Interface to VolServ

After both FileServ and VolServ have been installed and
initially configured, drive pool and association of a MediaClass
group with a library must be established within VolServ for
FileServ communications.

Drive Pools A drive pool is composed of a single drive or group of drives

that have the same capability. Drive pool names used within
FileServ must exist in VolServ before any data transfer
operations can be performed.

A drive pool is assigned a unique name to identify the drives or
system using the drives.

The system administrator can either specify a drive pool name
when adding DataClass group in FileServ, or can use the default
drive pool name found in the system parameter

VS_DEFAULT_DRIVEPOOL. The system administrator can also

limit a set of drives to a set of clients by creating different drive
pools and specifying the names of each drive pool for each
DataClass group associated with those users.

During FileServ installation, a drive pool name is created
containing all drives. The drive pool name is then added to
VolServ. The generated drive pool name is under FileServ’s

VS_DEFAULT_DRIVEPOOL parameter. If this name is not

configured in VolServ, all requests for data operations fail.
Several FileServ commands allow the user to specify a drive

pool using the

-v option. If a drive pool name is specified, it

must either reside or be created within VolServ before any
FileServ commands can be executed.

1-4 System Tasks 600716 Rev A

Administrative Tasks

Associate MediaClass with Library

On SGI systems, there are fifty four MediaClass names. Each
MediaClass has the following form:

FileServID_mediatype_mediaclasstype

There are ten possible values for FileServ ID: F0 through F9.
The following mediaclasstype exist:

• ADDBLANK or ADDBLNK

•CHECKIN

•IMPORT

•DATA

•MIGRATE

•REMOVE
An example of a valid MediaClass name is

F0_D2S_ADDBLANK.
The FileServ installation script creates each of the MediaClass

names as a VolServ MediaClass group. After the FileServ
installation, the VolServ system administrator must associate
the appropriate FileServ default MediaClass names with the
appropriate library.

System Tasks

An example of valid MediaClass names that must be associated
withalibraryareasfollows:

• F0_D2S_ADDBLANK

• F0_D2S_CHECKIN

• F0_D2S_IMPORT

• F0_D2S_DATA

600716 Rev A System Tasks 1-5

Administrative Tasks

• F0_D2S_MIGRATE

• F0_D2S_REMOVE

Register the Configuration

Define DataClass Groups

Before FileServ can operate properly, the physical
configuration of the system must be defined within FileServ.
This procedure is accomplished during or after FileServ
installation.

After installation, the system administrator is responsible for
associating all the drive devices configured in VolServ to
FileServ.

fsconfig command provides hardware component

The
configuration.

Note

For more information on the fsconfig command, refer to
the Command Reference book.

To use FileServ to either migrate or archive data, directories in
various file systems must be associated with sets of parameters
that govern data migration characteristics. The migration
parameter set is known as a DataClass group.

A DataClass group is created and defined through the

fsaddclass command or Define Classes screen.

The DataClass parameters control the following:

• Allocation of media.

• Number of copies of file data that are stored.

• Application of the data storage.

1-6 System Tasks 600716 Rev A

Administrative Tasks

• Truncation policies for files and media types associated
with the DataClass group.

Note

For more information on the fsaddclass command,
refer to the Command Reference book.

System Tasks

Associate Directories

After a DataClass group is defined, it can be associated with
directories in a file system so that files written to that directory
structure have their file data migrated according to the
parameters defined for the DataClass group.

Caution

Never associate the directories that contain the FileServ
executables with a class!

DataClass group association is implemented through the

fsaddrelation command or Define Class/Directory
Relations

screen. Only files written to directories that are
associated with a DataClass group are subject to the migration
policy application of FileServ.

These files are stored using the

Note

Associated directories and files are unavailable when FileServ
is inactive. ADIC recommends that directories that contain
applications or login files not be associated.

fsstore command.

600716 Rev A System Tasks 1-7

Administrative Tasks

Media Under FileServ Management

Before data can be copied from disk to tape, the tape media
must be in place. The media should be properly labeled and
entered into a storage subsystem by a VolServ operator before
entering media into the FileServ database.

The fsmedin -b command is used to add blank media into the
FileServ storage subsystem.

The total quantity can be any number; a default value of 99 is
used if quantity is not specified. The total quantity should be
restricted to a number equal to or less than that entered into an
archive following VolServ installation.

The mediatype name should match the type of assets associated
with the library located at your site. Formatting each tape
requires about 1 minute for DLT and 3590 media, 6 minutes for
D-2S, 15 minutes for D-2M, and 35 minutes for D-2L. Use the
command below to format a tape.

% fsmedin -b -q quantity -t mediatype

If D-2 tape formatting is preferred, time is saved by changing

$FS_HOME/sysparms/fs_sysparm_override file.

the

FS_MAX_ACTIVE_FORMATS parameter has a default

The
value of 1, which means only one tape drive can be used at one

time for formatting. This value can be changed using an editor
to a number equal to the number of tape drives available for
formatting.

1-8 System Tasks 600716 Rev A

Administrative Tasks

Create Migration Policies

Migration policies initiate movement of file data from disk to
tape.

Tip

ADIC recommends that migration policies be applied on a
routine basis. Periodic application of migration policies is best
accomplished through the use of a crontab, to invoke many
routinely executed UNIX commands.

The following types of policy can be run:

• Store data to tape (based on DataClass parameters).

• Remove data from disk (based on disk space)
The

fspolicy -s command is used to invoke the policy to

store data to tape. Eligibility for storage is based on the
DataClass parameters of class.

% fspolicy -s -c class

The fspolicy -t command is used to invoke the policy to
truncatedatafromdiskafterithasbeenstoredtotape.
Eligibility for truncation is per file system filesystem and based
on the file attributes, such as last access date.

System Tasks

% fspolicy -t -y filesystem

600716 Rev A System Tasks 1-9

Administrative Tasks

Routine Processing

Store and Truncate Files

Part of the FileServ system routine processing includes:

Routine Tasks Page

Store and Truncate Files 1-10
Database Maintenance 1-10
Trashcan Cleanup 1-20

Policies for storage and for data truncation are run as part of
routine system processing. The standard method of running
routine operations is to have the operating system
execute the operations. A
registered with the ongoing

root generated crontab is read and

cron process. The application of

cron process

migration and truncation policies is handled as part of this
process. The

cron file contains many routinely executed by

UNIX commands.

Database Maintenance

The database used by FileServ is an intricate part of the
software. Access to the database is controlled through a process
called the Lock Manager. The Lock Manager is started by the
FileServ system administrator. The startup script is called

lm_start and is located in the $FS_HOME/util directory . If

the Lock Manager is not running, FileServ will not start.
To prevent data loss and improve FileServ performance,

periodic database maintenance must be performed.

1-10 System Tasks 600716 Rev A

Administrative Tasks

FileServ database maintenance is part of routine system
processing. FileServ uses a RAIMA database to store and track
information about the files under FileServ. The RAIMA
database is embedded within FileServ and automatically starts
when FileServ starts.

Periodic database maintenance is required to prevent data loss,
improve FileServ software performance, and simplify recovery
procedures if needed.

The following three utilities should be run on a periodic basis:

• $FS_HOME/internal/chk_point/chk_point.pl

• $FS_HOME/util/checkDBALL

• $FS_HOME/util/keyBuildAll

chk_point.pl The

script checkpoints the RAIMA database (database recovery is
faster and more reliable when regular checkpoints are taken).

Checkpointing of the database is not automatically established
during FileServ installation. Therefore, checkpointing must be
placedinthecrontab file by the system administrator and
executed according to parameters of

Also, checkpointing cannot be accomplished without having
Perl installed. Checkpointing should be done during low usage
times.

System Tasks

$FS_HOME/internal/chk_point/chk_point.pl

crontab.

Since checkpointing is a snapshot of the RAIMA database,
taking regular checkpoints makes recovery of the database
faster and more reliable.

600716 Rev A System Tasks 1-11

Administrative Tasks

When the checkpoint script runs, it tars the entire contents of
the FileServ database to a separate file system. After this
process is completed, it zeros out the journal file. If the
journaling file system becomes full, processing stops.
Therefore, it is important to checkpoint the database regularly
through a

cron process.

Checkpointing can be written to the host computer disk or table,
but these files must not be placed under FileServ’s control.

checkDBALL The

database consistency by validating the position of each record
occurrence and checking the integrity of deleted chains. The
consistency check verifies that the member and owner record
types are valid, the membership count is current, and the
doubley linked lists are properly formed.

The script also validates the existence of the key values
associated with each record and the key field in the data files.
For each key in the key file, the script reads the associated
record and checks to ensure that the key’s data field contents
match that stored in the key file. Finally, t he checkDBALL
script performs a timestamp consistency check on the database.

The
host platform crash because FileServ may have been
performing a database transaction when the crash occurred.

$FS_HOME/util/checkDBALL script checks the

checkDBALL database script should always be run after a

1-12 System Tasks 600716 Rev A

Administrative Tasks

The table below shows the suggested database maintenance
intervals for each database utility.

Note

Although the terms “Normal Usage” and “Heavy Usage” in the
table header are somewhat subjective and may have different
definitions at different sites, in general, the
script and keyBuildAll script should be run every 100,000
storage, retrieval, modification, creation, and/or deletion of files
within the FileServ controlled DMAPI file systems.

checkDBALL

System Tasks

Database Maintenance Script

$FS_HOME/internal/chk_point/chk_point.pl
$FS_HOME/util/checkDBALL
$FS_HOME/util/keyBuildAll

Although FileServ must be terminated, the Lock Manager
process must be active, to run the
script may be run by either user

ADIC recommends that the output of the checkDBALL script
be redirected to a temporary file so that an analysis can be
performed after the script completes it’s execution. This is
accomplished as shown below:

# $FS_HOME/util/checkDBAll > temp_file_name

After the script completes it’sexecution, the
file should be analyzed for any er rors.

Normal

Usage

Heavy Usage

Daily Daily
Monthly Bi-weekly
Monthly Bi-weekly

checkDBALL script. The

fsadm or user root.

temp_file_name

600716 Rev A System Tasks 1-13

Administrative Tasks

keyBuildAll The $FS_HOME/util/keyBuildAll script rebuilds all the

key files for the RAIMA database. Rebuilding the file keys is a
two step process that also rebalances the B-tree structure of the
database.

To rebuild the file keys, follow the steps below:

Step 1. Reinitialize the file.
Step 2. Sequentially reads each record is from each data file

record and recreates each key file is from the record
contents.

Database Utilities

Run the

keyBuildAll script if one of the following occurs:

• If any errors were detected by the checkDBALL script.

• Periodically, based on system usage. (check the system
usage in the previous table)

For instructions on file recovery or UNIX to FileServ
comparison, see “Audit Database” on page 4-17.

There are 19 database utilities that allow you to add, modify,
delete and query a specific FileServ table.

The table utilities are:

classdef, classdir, devdb, dirdb, exitinfo,
externmed, fileattr, filecmnt, filecomp,
filexpir, keytest, medbpos, mediadir, transdb,
trashcomp

, and trashname.

activefl, blockpos, cfgdir,

1-14 System Tasks 600716 Rev A

Administrative Tasks

The utilities that operate on specific file systems are:

blockpos, dirdb, fileattr, filecmnt, filecomp

and filexpir.

Note

The one table utility that does not work like the others is the
keytest utility.

All of the utilities, with the exception of

keytest,havetwo

modes:

• Command Line Mode.

• Interactive Mode.

Both modes are described below.
For both Command Line Mode and Interactive Mode, an

additional parameter called the

device key is required before

running the utility. This parameter must be the first parameter
given to the command

Step 1. To determine the

device key, consult the devdb

table. An entry or output from the devdb utility may
look similar to the output shown below:

dvdmhdl :099c17edal7e8fd1

System Tasks

dvdmsz :8
device key :4
dvpath :/test2

Step 2. Assume that you now want to check files on the

/test2 migration file system.

600716 Rev A System Tasks 1-15

Administrative Tasks

First, you check the devdb table for the entry
containing
“device key” associated with

/test2. Notice there is a field called

/test2.This is the

value you will use for device specific table utilities
that are associated with the

/test2 file system.

Command Line Mode

Step 3. To look at the

/test2 and to send the output to a file called
test2.files, enter the following command:

fileattr entries for the files on

# fileattr 4 -ftest2.files

Examine the file at your leisure.

Command line mode queries only the specified table. In most
cases you need to enter only the utility name to call the query.
The utility queries the database for all r ecords in that specific
table. The results appear on the screen, or you can redirect the
results to a file using the standard UNIX redirection command.

Options for most of the utilities are listed below:

Option Description

-ffilename

Note: Do not put
a space between
the

-f and the

filename.

Send all output to the specified filename.

-h Display a help screen

-i Run in interactive mode

1-16 System Tasks 600716 Rev A

Administrative Tasks

Option Description

-k key Query for a specific record key. A working
knowledge of the database internals is often
needed to provide the proper key.

Each table utility has a different requirement
for the key. For additional information, see the
HELP screen.

Interactive Mode To start a utility in Interactive Mode, include the -i option on

the command line. If the

-k key option.

-i option is used, FileServ ignores the

In Interactive Mode, a menu displays with options valid for the
specified utility. The following table describes the available
options.

Options Description

a Add a record. You can add a record to any table.

You will have the opportunity to change every field
and enter the record as you like. In some tables,
key fields are generated automatically and are not
part of the add record process. If you need to
change a key field, this can be done under the
modify process.

System Tasks

d Delete a record. To delete a record, knowledge of

specific keys is required. Queries may need to be
performed in order to determine the specific key
the delete process requires before deleting a
record. Once the record is found, it is displayed for
confirmation before deletion. Be aware that in
some tablesthis will result in more than one
record for deletion.

e End this program.
I Retrieve record by class id.

600716 Rev A System Tasks 1-17

Administrative Tasks

Options Description

i List class ids.
k List class indices.
K Retrieve record by class index.
m Modify a record. Modifying a record requires a

specific key that corresponds to the record to be
modified Once the record is found, any field can
be modified including key fields. Modifying a key
field can result in a duplicate key for the table. In
such cases, the modification will fail.

q Query a table. Each table has different fields that

are used for queries. There is no specific field that
each table is queried on. Some queries allow for a
sub menu, while other table queries have several
fields that can be queried.

r Record count.
S Set output destination.
v View all records.

In addition, there is always an option to query on one or more
unique keys.

When entering an option, you may enter as many options on the
command line as you like. However, only the very first
character is accepted as the command. If that is a space, the
command is in error and nothing is done.

Frequency of Use

How frequency you should use these utilities depend on system
usage. It may be advantageous to make checkpoints more often
when FileServ database activity is heavy. Such activity
includes:

• Addition or deletion of many migration directories.

1-18 System Tasks 600716 Rev A

Administrative Tasks

• Heavy storage, retrieval, modification, creation, or deletion
of files in migration directories.

The advantage to taking extra checkpoints is that recovery from
database corruption is much faster and more reliable. However,
a checkpoint done during heavy system use takes longer and
can create serious performance degradation for FileServ
processes. By weighing these factors, the database system
administrator and the FileServ system administrator must
decide the time of day and frequency for each database
maintenance operation.

No matter how busy a system is, failure to perform database
maintenance on a regular scheduled interval increases the
chances of system downtime and loss of data.

Recover Database If you have total database loss or corruption, a database

recovery will be necessary to recover the files under FileServ.

System Tasks

Step 1. To recover the database, run the

restore.pl

script located under

$FS_HOME/internal/chk_point.

The amount of time required for a recovery depends
on how large the FileServ database is and how large
the journal file is. If the checkpoints are made
often, the recovery process will go quickly.

Step 2. After the restore.pl script completes, as root

type $FS_HOME/util/fs_recover without
parameters.

# su - root
# $FS_HOME/util/fs_recover

600716 Rev A System Tasks 1-19

Administrative Tasks

Run this command only if the archived file systems
are newer than the restored database and the journal
files have been preserved. The restore.pl
commandwill not replacethe old journal,so no other
preparatory work should be needed if the journal file
has been preserved. The journal file is located in

$FS_HOME/journal/fsdbjrnl.

Step 3. On the other hand, if the database was lost, but the

current journal file is available, the database can
be brought up-to-date by running

fs_recover.

Trashcan Cleanup

Another command that must be routinely run is fsclean.The

fsclean command purges the FileServ trashcan information.

Caution

Using the fsclean command eliminates the ability to recover
files from the trashcan with the fsundelete command!

Precautions must be taken when using the

fsclean command.

The trashcan serves as the repository for references to media
data that is deleted from the disk or modified. Each time a file is
modified, its tape copy becomes invalid. An entry is created in
the trashcan for the older version of the file. Also, when files
(containing current file copies on media) are removed (UNIX
rm), the trashcan receives an entry for each removed file.

Because of asynchronous processing, an fsclean performed
immediately after file removal may not completely clean the
media.

1-20 System Tasks 600716 Rev A

Administrative Tasks

Run a fsmedinfo -l report to verify all files deleted from
media. If files still exist, rerun the

Note

Execute the fsundelete command twice to make sure all
your required files have been undeleted.

fsundelete command allows recovery of removed or

The

fsclean command.

modified copies of files as long as an entry exists in the
trashcan. Only the primary copy is recoverable with the

fsundelete command. After fsclean is run for media, all

files on that media referenced in the trashcan are no longer
recoverable with

fsundelete.

System Tasks

600716 Rev A System Tasks 1-21

Administrative Tasks

Startup and Shutdown

Normal Startup

The following startup modes exist for FileServ:

• Normal. A normal termination allows a request to continue
to a known processing state. When a normal termination is
unsuccessful, contact technical support personnel to assist
with the correction. If termination exits with a message that
the system abnormally terminated, contact the technical
support personnel.

• Contingency. A contingency start is only recommended
when a normal start fails.

Both types of startup are described below.

A normal startup is performed following a graceful termination
of FileServ. A normal FileServ startup performs the following
tasks:

• Reinitializes the system parameters.

• Performs command recovery processing using the recovery
processing information retained after termination.

To normally start or terminate FileServ, the system
administrator runs the
must be issued from a login to the host computer.

This command can also be included in a script that is run
automatically at the time of the host computer initialization.
The FileServ command will automatically starts FileServ
each time the server is restarted.

The licensed subsystems must be configured before startup or
FileServ will fail to start.

1-22 System Tasks 600716 Rev A

FileServ command. This command

Administrative Tasks

The following messages display at the command line where the

FileServ command is run to indicate a successful initiation:

FS0338 FileServ: Request accepted
FS0277 FileServ complete: FileServ software is
running

System Tasks

Recovery Processing

Contingency Startup

During FileServ processing, software activity is continually
recorded in recovery processing files. These files are only used
during a normal startup. It is important to always attempt a
normal start after any termination of FileServ.

Caution

If files that are migrated to media are actively being transferred
to disk at the time an abnormal software termination occurs, a
contingency start may corrupt the file data.

A normal start resets the active files to the original state before
starting the transfer. Files that are on media only and are being
retrieved are reset to being on media only. The request that was
active at termination must be reissued by the requestor.

A contingency start is only recommended when a normal start
fails. With the exception of initial startup at installation, never
attempt a contingency start without first attempting to perform a
normal start of FileServ.

Note

A contingency start is used for first-time Initialization of
FileServ. For more information, refer to Installing FileServ.

A contingency start initializes certain log files and internal
directories but does not perform recovery processing.

600716 Rev A System Tasks 1-23

Administrative Tasks

% FileServ -c

The recovery files cannot be used after a contingency start is
issued. If the user needs to save the recovery files for review at
a later time, move these files to another directory. Do not
rename the recovery files because the software deletes all files
found in the recovery file directories.

These activities allow FileServ to return to a known processing
state when a normal start cannot be performed.

Caution

All files in the recovery directoryare deletedduring a
contingency start. To retain files, move all recovery files to a
different directory.

Step 1. Run the FileServ -c command.

FS0290 CAUTION! Contingency startup deletes recovery
processing files.
FS0284 FileServ contingency startup requested.
FS0290 Caution! Contingency startup deletes recovery processing
files:
FS0293

FS0293…
FS0294 Are you sure you wish to continue? (y/<n>):

…

Step 2. Press <RETURN> to cancel the contingency startup

or enter Y for yes.

1-24 System Tasks 600716 Rev A

Administrative Tasks

Normal Shutdown

To ensure an orderly shutdown of FileServ,any processing must
be terminated gracefully.

All components must be shut down in the sequence as follows:

Step 1. Shut down FileServ.
Step 2. Shut down VolServ.
Step 3. Shut down Ingres database software.
Step 1. Run a system-wide broadcast message that states

FileServ will be terminated. Use the UNIX

rwall

command to issue a message similar to the one
below to all hosts and their clients on the network.

FileServ services will be terminated in
n minutes

Step 2. Repeat the broadcast before termination.
Step 3. Run the FileServ -t command. The following

message is returned.

System Tasks

FS0285 Termination requested by user.
FS0294 Are you sure you wish to
continue? (y/<n>):y

Files being actively transferred to media,orfrom
media are completed. File transfer requests awaiting

resources are terminated and a request aborted status
is returned to the user.

All files are closed and cleanup is performed to
ensure that the system is in the proper state to allow
an orderly restart.

600716 Rev A System Tasks 1-25

Administrative Tasks

Any media introduction or removal operations in
progressare interrupted. The requestsresumeand are
completed when a subsequent normal startup is
performed. The configuration states for the storage
library components are not changed during
termination.

Step 4. Perform an orderly system shutdown only after

FileServ has terminated.

Step 5. Enter the following command to make sure that

unwanted processes are not still running:

# ps -elf | grep fs_
# ps -elf | grep fsadm

Automate Software Termination

FileServ terminates if the software is unable to perform a

commit or rollback operation on the database for a resident

FileServ process. Error messages are sent to the system logs and
console to indicate that FileServ is terminating because of a
database software error .When the database software problem is
resolved, bring up FileServ.

1-26 System Tasks 600716 Rev A

Administrative Tasks

Managing System Configuration

Modify System Parameters

For the proper execution of FileServ commands and operations,
the physical storage library configuration must be maintained in
the FileServ system and parameter files. The table below lists
the tasks that the FileServ system administrator can perform on
the system and files.

System Tasks Page

Modify System Parameters 1-27
Reconfigure System Devices 1-47
Change Component State 1-53
Add and Delete Drives 1-55

FileServ employs global parameters that define the system.
These parameters are located in files contained in the

$FS_HOME/

sysparms directory, where $FS_HOME is the

directory where FileServ is installed.
FileServ parameter files can be edited to customize the software

for your specific installation. For instructions, see “Edit System

Parameters” on page 1-46.

System Tasks

The table below lists the configurable parameters:

Configurable System Parameters Page

General Parameters 1-28
System Administration Parameters 1-28
Default Parameters 1-36
File Retention Parameters 1-39
VolServ-specific Parameters 1-40

600716 Rev A System Tasks 1-27

Administrative Tasks

Configurable System Parameters Page

Installation Parameters 1-41
Software Maintenance Parameters 1-43
Media Stats Parameters 1-44
Logging Parameters 1-44

GeneralParameters The fs_sysparm file contains parameters that control general

FileServ activities. The parameters in this file are grouped into
the following categories:

Category Description Page

System Administration Used to tune system performance and media

usage.

FileServ Defaults Used with FileServ commands that allow

default value.

File R etention Used by the file comment keyword search and

file expiration daemons.
Installation Established at the time of system installation. 1-41
Software Maintenance Modified as required for software maintenance. 1-43

System Administration Parameters

The system administration parameters in the table below can be
changed to tune system performance and media usage. FileServ
must be cycled (using the

FileServ -t and FileServ

1-28

1-36

1-39

commands) to pickup changes to these parameters.

Parameter Default Definition

NOMINAL_FILE_SIZE 5000000 Nominal file size in bytes to estimate

how many bytes of user data fit on
the remaining space on the media.

1-28 System Tasks 600716 Rev A

Administrative Tasks

Parameter Default Definition

FILE_LBL_FMT_TAPE adic00000001 Defines the way data labels are

writtentotapedevices.
adic00000001 is ANSI standard and
writes data with tape marks between
the header labels and data, and
between data and trailer labels.
adic00000002 leaves off tape
marks.This is faster, but is not ANSI
standard.

FILE_LBL_FMT_DLT adic00000003 Defines the way data labels are

writtentoRSP-2150devices.
adic00000001 is ANSI standard and
writes data with tape marks between
the header labels and data, and
between data and trailer labels.
adic00000003 leaves off tape
marks.This is faster, but is not ANSI
standard.

System Tasks

FILE_LBL_FMT_RSP adic00000003 Defines the way data labels are

writtentoRSP-2150devices.
adic00000001 is ANSI standard and
writes data with tape marks between
the header labels and data, and
between data and trailer labels.
adic00000003 leaves off tape
marks.This is faster, but is not ANSI
standard.

FILE_LBL_FMT_8590 adic00000003 Defines the way data labels are

writtentoRSP-2150devices.
adic00000001 is ANSI standard and
writes data with tape marks between
the header labels and data, and
between data and trailer labels.
adic00000003 leaves off tape
marks.This is faster, but is not ANSI
standard.

600716 Rev A System Tasks 1-29

Administrative Tasks

Parameter Default Definition

DEFAULT_MEDIA_TYPE DLT Default media type used with

commands with optional media
types.

DEF_MED_SPC_3480 220000000 Default tape length of a 3480

cartridgeinbytes.

DEF_MED_SPC_3490 400000000 Default tape length of a 3490

cartridgeinbytes.

DEF_MED_SPC_3490E 800000000 Default tape length of a 3490E

cartridgeinbytes.

DEF_MED_SPC_D2SM 25000000000 Default tape length of a D-2 small

cassette in bytes.

DEF_MED_SPC_D2MD 75000000000 Default tape length of a D-2 media

cassette in bytes.

DEF_MED_SPC_D2LG 165000000000 Default tape length of a D-2 large

cassette in bytes.

DEF_MED_SPC_CTIII 10000000000 Default tape length of a DLT

cartridgeinbytes.

DEF_MED_SPC_CTIV 20000000000 Default tape length of a DLT

cartridgeinbytes.

FS_EOT_SIZE_RESET_
FACTOR

0.5 Fraction of space available that will
be added to current write position
whenphysicalEnd-Of-Tape(EOT)is
detected for systems utilizing 3490
media. Smaller fractionsshould be
used when fewer mounts and
performance for robotic utilization is
a priority.Higher fractions should be
used when tape utilization is a
priority. Valid range is 0.0 - 1.0. It is
recommended that this value not be
modified prior to contacting
technical support.

1-30 System Tasks 600716 Rev A

Parameter Default Definition

Administrative Tasks

FS_MAX_ACTIVE_
FORMATS

1 Maximum number of drives allowed

to perform tape formatting at one
time.

FS_MAX_ACTIVE_
MEDCHECKS

1 Maximum number of drives allowed

to perform media checking at any
one time.

STORE_LIMIT_NOTICE 1 If FileServ is started up when the

storage used is within this number of
GB from the storage limit, notice is
sent to

FS_OWNER_ID.

FS_CALLOUT_SLEEP_INT 2 A file can be accessed by one

process at a time. This parameter
represents the time to wait (in
seconds) before the next retry if
callouts are suspended because of
a file busy. (For tuning, refer to note
in parameter

MAX_DMON_SUSP_ERRORS.)

MAX_DMON_SUSP_ERRORS 60 two-second

retries

Maximum number of retries in
response to a suspend failure. The
command sleeps between retries for
the number of seconds specified in

FS_CALLOUT_SLEEP_INT. A suspend

failure can occur for a file if:

System Tasks

• The file has already received a

callout.

• The maximum number of

suspends is already reached.

600716 Rev A System Tasks 1-31

Administrative Tasks

Parameter Default Definition

(continued) The FS_CALLOUT_SLEEP_INT and

MAX_DMON_SUSP_ERRORS

parameterscanbetuned,if
recurring failures of multiple copies
of files are noted in the system logs.
This situation can occur in a backup
environment where the primary and
backup copies of large files are both
stored at the same time by issuing
the fspolicy command. The
default can expire on the second
copy of a large file while the first
copy is written to media.

Note: Run fspolicy -w to rebuild
candidate files.

For additional help in tuning these
parameters, call ADIC technical
support.

CONNECT_SLEEP_TIME 1 Time to wait (in seconds) before the

next retry if the IPC Connect request
fails.

CONNECT_RETRIES 120 Number of retries on IPC connection

failure. This is set by the factory and
is changed only by technical support
personnel.

MAX_READS 100 Number of retries on IPC receive

failure. Set the MAX_READS and
MAX_WRITES parameters to the
same number. This is set by the
factory and can be changed only by
technical support personnel.

1-32 System Tasks 600716 Rev A

Administrative Tasks

Parameter Default Definition

MAX_WRITES 100 Number of retries on IPC send

failure. The

MAX_WRITES parameters are set to

MAX_READS and

the same number. This is set by the
factory and is changed only by
technical support personnel.

FS_DB_RETRY_COUNT 3 Number of retries on database

services failure because of
table-busy errors.

DMON_POLL_TIME 10 Time to wait (in 1/100 seconds) on

select poll for events on IPC queue.
This is set by the factory and can be
changed only by technical support
personnel.

System Tasks

MAX_RETRIEVE_RETRY_
COUNT

2 Maximum number of retries for any

retrieve operation. Each retry is
performed on a different file copy.

LOBLK_THRESHOLD 85 Percentage of used disk space

when reached initiates the overflow
utility to reduce the level of used
disk space down to the

HIBLK_THRESHOLD value.

HIBLK_THRESHOLD 84 Minimum level of used disk space

that the overflow utility maintains.

MAX_TAPE_TO_TAPE
_ALLOC_TIME

60 Maximum amount of time (in

minutes) that a Medcopy request
waits for resources. When this
threshold is exceeded, the request
fails. (Valid range is 1 through

10000.)

600716 Rev A System Tasks 1-33

Administrative Tasks

Parameter Default Definition

STARVATION_PERCENT 50 Percent of

MAX_TAPE_TO_TAPE_ALLOC_TI
ME variable in which resources will
be obtained and not released until
all resources have been secured or
the time limit has been exceeded.
(V alid range is 1 through 100.)

FS_NICE_VALUE n If enabled, the FileServ process and

database resident process runs with
this n value. Refer to set priority (2)
for the value range of the system.

To enable, enter a value.
To disable, set the value to “0.”

FS_VS_QUEUE_XXX
_THRESHOLD

variable Storage request threshold value

when surpassed, resource requests
are queued in the FileServ system
instead of the VolServ system. The
Value is 3x the number of drives
located in the system. For each
media type, there is a separate entry
required, e.g.,
FS_VS_QUEUE_D2S_THRESHOLD.If
the value is changed, it is
recommended that the sum of all

FS_VS_QUEUE_xxx_THRES­HOLD values not exceed 100.

FS_THRESHOLD_INC_NUM 5 Threshold increment number

variable. The value for the drive
failure level when an access to a
drive fails.

FS_THRESHOLD_DEC_NUM 1 Threshold decrement number

variable. The value for the drive
failure level when an access to a
drive is successful.

1-34 System Tasks 600716 Rev A

Parameter Default Definition

Administrative Tasks

FS_DRIVE_ERR
_THRESHOLD

20 Threshold value when equalled or

exceeded results in drives being
taken offline.

FS_MAX_FILES_PR_3480 2000 Maximumnumber of files allowed on

a single 3480 cartridge tape.

PERCENT_FULL_TO
_MIGRATE

95 Percentage value used to check

against to determine if media can be
migrated.

File Copy Block Factors device-dependent Size of the following blocks is a

calculated optimum for each device
type.

FS_DISK_BLOCK_FACTOR 10 Number of disk blocks used per

transfer when reading/writing the
disk. Parameter is normally
commented out. Use this parameter
with systems that have limited
memory. System performance is
degraded during file copies. Contact
technical support before activating.

FS_TAPE_BLOCK_FACTOR 1 Number of tape blocks used per

transfer when reading/writing a tape.
Parameter is normally commented
out. Use this parameter with
systems that have limited memory.
System performance is degraded
during file copies. Contact technical
support before activating.

System Tasks

FS_RSP2150_BLOCK
_FACTOR

4 Number of 2150 blocks used per

transfer when reading/writing the

2150. Parameter is normally
commented out. Use this parameter
with systems that have limited
memory. System performance is
degraded during file copies. Contact
technical support before activating

600716 Rev A System Tasks 1-35

Administrative Tasks

Parameter Default Definition

CLEANUP_PROCESSING 100 Number of files processed per

transaction in the fsclean
command. If this value is set higher
than 100, the results can be
memory allocation problems and
increased processing time. 100 is
the recommended value.

FS_PRINTER_PATH /usr/bin/lpr Default printer used for printing

reports from the GUI.

MDM_POSITION_VALIDATION YES Enables validation of the tape

position prior to the first file in a file
set.

Default Parameters The FileServ default parameters are used with FileServ

commands that allow defaults (

fsmodclass). To change a default, modify this file, cycle

fsaddclass and

FileServ, then retry the command.
Review these parameters to verify that the applicable defaults

are site specific. Because the defaults are used when no specific
value is indicated in a command, these defaults are set to values
that are most often used. This allows increased use of the
defaults in the commands. Modify those values that are contrary
to a site’s specific operations. The following example illustrates
the type of issues for which it is beneficial to modify the
FileServ defaults.

1-36 System Tasks 600716 Rev A

Administrative Tasks

If the system administrator does not log on as root, change the
CLASS_USERID to default to the user ID of the user who is
available for mail notification of actions that are required by
FileServ.

Parameter Default Definition

CLASS_USERID fsadm Default userid. Any valid userid can be

used. This is the default for the E-mail
Notify ID.

CLASS_ACCTNUM 12345 Default account number. One to five

alphanumeric characters can be entered.

CLASS_SCODE NONE Default security code. One to four

alphanumeric characters can be entered.

CLASS_SOFTLIMIT 8 Default warning limit for the number of

media in a class. The warning is issued
when the number of media are allocated
to the class. The default number can be
changed when setting up the class.The
number can also be modified for an
existing class with the fsmodclass
command.

CLASS_HARDLIMIT 10 Default hard limit for a class. Additional

media is not allocated for the class when
this limit is reached. The default number
can be changed when setting up the
classbyusingthefsaddclass
command. The number can also be
modified for an existing class with the
fsmodclass command. The classes
value must be greater than the value for
the

CLASS_SOFTLIMIT.

System Tasks

CLASS_MTIME 10 Default minimum time (in minutes) since

a file was last accessed. A file is eligible
for policy application (store or cleanup)
after mintime. The number can also be
modified for an existing class with the
fsmodclass command.

600716 Rev A System Tasks 1-37

Administrative Tasks

Parameter Default Definition

CLASS_DEF_MEDIA_TYPE DLT Default media type (D2S, D2M, D2L,

DLT, 3480, 3490, 3490E, 3590,8590).
Depending on the platform used or a
manual system, modify the default to
media used. The number can also be
modified for an existing class by using
the fsmodclass command.

CLASS_FILE_SPAN N Default flag to allow file spanning media

(Y or N).Thevaluecanalsobemodified
for an existing class by using the

fsmodclass command.

CLASS_FILE_CLUSTER N Default flag to allow file clustering

(Y or N).Thevaluecanalsobemodified
for an existing class by using the

fsmodclass command.

CLASS_MAX_COPIES 2 Maximum number of copies allowed,

including the primary copy. A maximum
number of two copies is allowed for the
current version of FileServ. The number
canalsobemodifiedforanexistingclass
by using the fsmodclass command.

CLASS_DEFAULT_COPIES 1 Total number of copies stored to media

for each file in a class. Must not exceed

CLASS_MAX_COPIES.Thenumber can also

be modified for an existing class by using
the fsmodclass command. The default
can be modified for a file by using the
fschfiat command, although the
number must not exceed

CLASS_MAX_COPIES.

1-38 System Tasks 600716 Rev A

Administrative Tasks

Parameter Default Definition

CLASS_FILE_CLEANUP P Default file cleanup action (I or P). When

a file is stored, cleanup can occur
immediately (I) after storing the file or at
policy application (P). The value can also
be modified for an existing class by using
the fsmodclass command. If the
sysparm value is not set to I or P,
FileServ defaults to P.

CLASS_MEDIA_CLEANUP S Default media cleanup action (C or S).

When media becomes logically blank,
the media can return to the class blank
media pool (C) or to the system blank
media pool (S). The value can also be
modified for an existing class with the
fsmodclass command.Ifthesysparm
value is not set to C or S, FileServ
defaults to C.

FS_EPSON_LABEL_PRINTER Defaultprinterforprinting external media

labels. Specifies the Epson printer that
generates the external top media labels.
To enable, contact technical support.

System Tasks

CLASS_DRIVEPOOL fs_F0drivepool Default drive pool (up to 16 characters).

Usually set to the same value as
VS_DEFAULT_DRIVEPOOL.

File Retention Parameters

The following list shows parameters that are used by the file
comment keyword search and file expiration processes. To
change a value, modify this file, cycle the user interface, then
retry the command.

600716 Rev A System Tasks 1-39

Administrative Tasks

Parameter Default Definition

A file will be retained on the disk based upon the

DEF_FILE_RETION_PERIOD or the
FILE_RETENTION_PERIOD value. The lowest value will

determine a file’s true retention period.

ADVANCE_NOTIFICATION_
PERIOD

DEF_FILE_RETENTION_
PERIOD

FILE_RETENTION_PERIOD 0 Time a file is kept on disk. Valid range is from 0

VolServ-specific Parameters

Parameter Default Definition

FILESERV_ID F0 A two-character unique identifier used to

The following parameters are specific to the VolServ system.
FileServ must be cycled to pick up changes to these parameters.

30 Number of days in advance the DataClass

group manager is notified of the impending
expiration of files located in a DataClass group.
Valid range is from 1 and 32767 days.

0 Time a file is kept on the disk. Valid range is

from 0 to 32767. If value is set to 0, the file will
be kept on disk indefinitely. If a value from 1 to
32767 is used, the file will be retained for the
numberofdaysenteredbeyondthelastaccess
date.

to 32767. If value is set to 0, the file will be kept
indefinitely. If a value from 1 to 32767 is used,
the file will be retained for the number of days
entered beyond the last access date.

differentiate the FileServ systems connected
to the same VolServ host. This identifier is
the prefix for all MediaClass names and drive
pool names.

VS_HOSTNAME XXXXXXX VolServ hostname to be used by this

FileServ system.

1-40 System Tasks 600716 Rev A

Administrative Tasks

Parameter Default Definition

VS_PROGRAM_NUMBER XXXXXXX If enabled, the VolServ program number to

be used by this FileServ system. To disable,
comment out the parameter.

VS_DEF_QUANTITY 99 Default media quantity for entry/exit port

operations. (Range 1-99)

VS_DEFAULT_DRIVEPOOL fs_F0drivepool Default VolServ drive pool used for retrieves.

This drive pool contains all
FileServ-configured drive components.This
drive pool is used for media with no
DataClass group. Defined in terms of

FILESERV_ID.

VS_DIR XXXXXXX This parameter should point to the VolServ

environment for the fspic utility to run
logoffcomps.

System Tasks

Installation Parameters

The following list shows the system parameters that are to be
established at the time of system installation. Use the FileServ
installation script for this purpose.

As a general rule, do not modify these rules unless the system is
completely reinitialized and reinstalled.

Parameter Default Definition

FileServ_LICENSE_STRING FileServ license string.
FS_ADMIN_DAEMON_ID 2 FileServ daemon number (0-3) used for

administrative activities.

FS_DATA_DAEMON_ID 3 FileServ daemon number (0-3) used for

data activities.

600716 Rev A System Tasks 1-41

Administrative Tasks

Parameter Default Definition

FS_DATABASE fsdb FileServ database name (1-20 chars).

The database maintenance scripts use
fsdb as the FileServ database name. If
this parameter is modified, these scripts
must also be modified.

FS_CONSOLE /dev/console Identifies the device path for the FileServ

console.

FS_DEFAULT_SUBSYSTEM V0 Default component ID only for the

fsmedin, fsmedout,andfsqueue

commands when the user does not
specify the subsystem on the command.

These parameters below set (UGO) permissions, owner, and group ID for any files created by
FileServ.

FS_FILE_MODE 511

Decimal value

UGO permissions for files created by
FileServ.

of octal
permissions

777.

FS_FILE_GROUP adicadm Group ID for files created by FileServ.
FS_OPR_GROUP adicopr Group ID for fs operators.
FS_OWNER_ID fsadm Owner ID for FileServ files and database

owner’s userid.

1-42 System Tasks 600716 Rev A

Administrative Tasks

Software Maintenance Parameters

The following list shows parameters that can be modified as
required for software maintenance. FileServ must be cycled to
affect the changes. These parameters are used to enable and
disable different types of message logging. These logs can be
used for debugging purposes. To enable logging, remove the
comment line indicators from the parameter(s) and recycle
FileServ.

Parameter Default Definition

COMMAND_LOGGING y Enables logging of user commands and status

to the fs_hist_21 file.

COMMAND_INFO_DETAIL y Removes the message number, priority, and

request identifier from the status returned to
the user.

COMMAND_EXTRACT_HEADER n If enabled, removes the message number,

priority, and request ID from the command
status back to the user. Does not effect
logging.

FS_TRACE_MASK o Controls generations of trace logs to the

/FS_HOME/tracelogs directories. Set Mask
according to which trace logs generate. Use
individually or in combination.

System Tasks

• k = KRPC messages

• i = IPC messages

• o = no trace logging performed

FS_TRACE_SIZE 8192 Record size limit (in bytes) for recording in the

trace logs.

600716 Rev A System Tasks 1-43

Administrative Tasks

Media Stats Parameters

The following list shows parameters that can be modified as
required, to collect media statistic information for each site.
FileServ must be cycled to pick up changes to these parameters.

Parameter Default Definition

TSC_LOG_MASK e Enables or disables various priorities of the tape

statistic logging. The following values can be used
in any combination:

• e = error priority (always logged)

• h = history priority

Logging Parameters The following list shows parameters that can be modified, as

required, to choose logging levels for each site. FileServ must
be cycled for to affect changes. These parameters are used for
trace logging.

If trace logging is enabled through the FSLOG_OPTIONS
parameter, logs are sent to the trace log files. If trace logging is
disabled, then all trace-level logs are discarded.

Parameter Default Definition

FSLOG_OPTIONS

FS_LOG_LEVEL YYYYYYYYY Controls which dynamic technical support logs are

1-44 System Tasks 600716 Rev A

e Enable the trace logging facility to the

/FS_HOME/syslog/trace directories.

• e = enable trace logging.

• - = no trace information is logged.

sent to the fs_ATAC_11 file.

• NNNNNNNN = OFF levels 12-2 0

• YYYYYYYY = ON levels 12-20

Administrative Tasks

Parameter Default Definition

FS_FACILITY 1 Logging facility used for priority 0-7 messages

directed to the syslog. The configuration for the
syslog is in the
/etc/syslog.conf file. The following facilities can be
used with the FS_FACILITY parameter KEY (used
to direct messages to files):

• 0 = LOG_LOCAL0

• 1 = LOG_LOCAL1

• 2 = LOG_LOCAL2

• 3 = LOG_LOCAL3

• 4 = LOG_LOCAL4

• 5 = LOG_LOCAL5

• 6 = LOG_LOCAL6

• 7 = LOG_LOCAL7
For more information, refer to the man page for

syslog and syslogd.

FS_LOG_OPTIONS pc Log options for priority 0-7 messages that are

directed to the syslog. The following options can be
used in any combination with the FS_LOG_OPTIONS
parameter:

System Tasks

•p=LOG_PID

• c = LOG_CONS

• d = LOG_NDELAY

FS_INT_PERF_LOG Y Performance point logging:

• N= disables logging

• Y= enables logging

600716 Rev A System Tasks 1-45

Administrative Tasks

Parameter Default Definition

FS_LOG_MASK ui The log mask used for priority 0-7 messages that are

directed to the syslog. The FS_LOG_MASK
parameter allows the “setlogmask” function to be
called with modifiable values. These options can be
used for the FS_LOG_MASK parameter, either
individually or with a’u’ appended to it.

•e=LOG_EMERG

• a = LOG_ALERT

• c = LOG_CRIT

• r = LOG_ERR

• w = LOG_WARNING

• n = LOG_NOTICE

• i = LOG_INFO

•d=LOG_DEBUG

• u = LOG_UPTO()
Example:

FS_LOG_MASK=e; implies
setlogmask(LOG_MASK(LOG_EMERG));

FS_LOG_MASK=ur; implies
setlogmask(LOG_UPTO(LOG_ERR));

Edit System Parameters

Configurable system parameters are modified by editing the
FileServ system parameters $

Step 1. Edit the

fs_sysparm file using a text editor and

FS_HOME/fs_sysparm file.

replace the existing value with a valid new value.
Allentries must be in the format:

name=value;with

no blank spaces around the equal (=) sign and each
value terminated with a semicolon (;).

1-46 System Tasks 600716 Rev A

Administrative Tasks

An example for the CLASS_MTIME parameter is
shown below:

rm CLASS_MTIME=10;

Reconfigure SystemDevices

CLASS_MTIME=30;

Step 2. Recycle FileServ by running the command below:

FileServ -t

Upon restart, a service utility is called by various
processes and routines to establish system parameter
values within the FileServ environment. This utility
reads the appropriate parameter file to gather the
parameter name and its value.

Step 3. Restart FileServ as shown below:

FileServ

Although device configuration of the library hardware is
performed during system installation and setup, storage
subsystems or drive components can be added to or removed
from the FileServ system configuration.

System Tasks

Device configuration involves the allocation of device driver
files for all peripherals, including the following:

•Disks

•Libraries

• Tape drives

600716 Rev A System Tasks 1-47

Administrative Tasks

The UNIX device drivers provide the means to reconfigure
devices for the standard peripherals (disks and system console).
To reconfigure these components, refer to the applicable
platform manual.

Edit Devices with fsconfig Command

After installation, the system administrator can add or remove
devices from the configured storage system.

The

fsconfig command provides hardware component

configuration. By specifying the proper options and the
accompanying values, hardware components can be added,
modified, or deleted from the system to reflect the actual
physical configuration.

Note

The fsconfig command does not allow duplicate device
pathnames in the database.

For more information on the
the Command Reference book.

fsconfig command, refer to

The component identifier is a required value to add, modify, or
delete hardware. When adding a new drive or subsystem
component, the component identifier, component type, and
component alias are required values. The component identifier
cannot be modified. When deleting a subsystem, the drives
must be deleted before the subsystem can be deleted.

1-48 System Tasks 600716 Rev A

Administrative Tasks

When adding or deleting a drive to the system, the system
parameter
under $FS_HOME/

FS_VS_QUEUE_XXX_THRESHOLD value located

sysparms directory must be updated for

each media type the drive supports. The entered value is three
times the total number of drives in the system. For example,
three drives exist in a library system, with a fourth drive to be
added. Because the drive supports D-2 media, the system
parameter file shows the following values for

FS_VS_QUEUE_XXX_THRESHOLD:

• FS_VS_QUEUE_D2S_THRESHOLD = 9

• FS_VS_QUEUE_D2M_THRESHOLD = 9

• FS_VS_QUEUE_D2L_THRESHOLD = 9

The value for each supported media type is changed to reflect
the addition of the new drive (3x4 drives). If a drive is deleted
from the system, the value is changed to reflect the deletion of
the drive. If multiple drive types are used, it is recommended
that the sum of all

FS_VS_QUEUE_XXX_THRESHOLD not

exceed 100.

System Tasks

Add a Library Step 1. If a new library is added to your site, add the license

string variable to the VolServ ENVAR file system
parameter file.

Step 2. Add the drives in the new library to the FileServ

system configuration list with the

fsconfig

command.

Step 3. Contact technical support for detailed instructions

for adding or removing storage subsystems and
libraries to your storage system.

600716 Rev A System Tasks 1-49

Administrative Tasks

Edit Device Step 1. Run the fsconfig command with the -a option to

add a new component to the ADIC system.

Step 2. Use the appropriate options, as needed. For option

information, refer to the Command Reference book.

Delete a Device Step 1. Run the fsconfig -h componentID command

with the -d option to delete a device from the
configuration.

Step 2. Use other appropriate options, as needed. For option

information, refer to the Command Reference book.

1-50 System Tasks 600716 Rev A

Administrative Tasks

Generate Report Step 1. Run the fsconfig command.

Use the -h option to show the configuration of all
component.

Or, use the -i option to show the configuration of
a specific component.

Step 2. An example of the generated report is shown below:

% fsconfig

-----------------------------------------------------------­Hardware Configuration Report Fri Jan 29 09:13:49 1999

Component ID: V0

------------------------------------------------------------

Device pathname: N/A

User Alias: VolServ

Component Type: SUBS

Device Type: N/A

Drive ID: 10

Delay Time: 0

------------------------------------------------------------

System Tasks

Hardware Configuration Report Fri Jan 29 09:13:49 1999

Component ID: V0,10

------------------------------------------------------------

Device pathname: /dev/er90/s0

User Alias: ER90_DR1

Component Type: DRIVE

Drive Type: ER90

Drive ID: 10

Delay Time: 0

------------------------------------------------------------

600716 Rev A System Tasks 1-51

Administrative Tasks

Hardware Configuration Report Fri Jan 29 09:13:49 1999

Component ID: V0,11

------------------------------------------------------------

Device pathname: /dev/er90/s1

User Alias: ER90_DR2

Component Type: DRIVE

Drive Type: ER90

Drive ID: 11

Delay Time: 1000

Drive Compatibility

The fsconfig command can configure various drives. The
following list shows the FileServ default drive values and the
various drives each default value supports along with the media
type. When adding a drive, this table should be referenced. The
tape media that came with your system may not include all
these types.

Drive Names Supported Drives Supported Media Media Types

DLT2000 DLT2000 CompacTape Type III CTIII
DLT4000 DLT4000 CompacTape Type III

CompacTape Type IV

DLT7000 DLT7000 CompacTape Type III

CompacTape Type IV

MO5.25 HP2600FX 2.3GB MO disc

2.6GB MO disc

3480 4480 3480 Cartridges 3480

M2483B (Fujitsu) 3480 Cartridges 3480
M2483H (Fujitsu) 3480 Cartridges 3480

CTIII
CTIV
CTIII
CTIV
MO525

1-52 System Tasks 600716 Rev A

Administrative Tasks

Drive Names Supported Drives Supported Media Media Types

3490E 4490E 3490 Cartridges*

3490E Cartridges

M2483N (Fujitsu)

M2483ND (Fujitsu)

8590 8590 8590 Cartridges 8590
* Only blank 3480 media can be written to. On the other hand, 3480 media containing data from

a 18-track drive can only be read.

Change Component State

Component state changes allow for timely maintenance and
diagnostics of a library component. When a library component
is taken from the online (ON) state to the offline state
(OFF), it is not available for usual FileServ operations. After

3490 Cartridges
3490E Cartridges

3490 Cartridges
3490E Cartridges

*

*

3480

3480

3480

the specialized operations are performed, the component must
be returned to the online status.

fschstate command allows the user to report or to

The
change the state of a drive component or storage subsystem.

System Tasks

Note

For more information on the fschstate command, refer to
the Command Reference book.

The

fschstate command can be executed when FileServ is

active or nonactive. Only storage subsystems can be changed if
FileServ or VolServ is inactive.

Drive component changes require both FileServ and VolServ to
be active. Valid states are:

600716 Rev A System Tasks 1-53

Administrative Tasks

• UNAVAIL

• MAINT

•ON

•OFF

• UNKNOWN
Because FileServ and VolServ components work interactively,

changes in the drive components or storage subsystem are
reflected in VolServ.

If a component is taken to either the

maintenance state, FileServ does not attempt any processing

offline or

with that component.
When a component is taken to a

maintenance state, the

maintenance port is enabled and the Ethernet communications
link is disabled; whereas, the

offline state is only a

logical state within FileServ.
After maintenance has been completed, change the component

statebacktothe

online state for the component to be reused

by FileServ.
Using the

fschstate command without any options generates

a report that shows all currently configured library components,
for example, drives, drive identifiers, and VolServ systems. The
report can be limited to a single component by specifying a
component alias.

Step 1. Run the

fschstate command and specify the

component alias of any storage subsystem,
component or drive in the library system.

1-54 System Tasks 600716 Rev A

Administrative Tasks

Step 2. Use the -s option to indicate the required new state

of the component. Valid state entries are: UNAVAIL,
MAINT, ON, OFF,andUNKNOWN.

Step 3. To receive a report on all configured storage

subsystem and drive components in the system, run
the

fschstate command with out options.

System Tasks

Add and Delete Drives

Adding and deleting drives from an Automated Media Library
(AML) requires technical support assistance. The robot inside
the AML requires reteaching and the robotic database will need
to be update with special support equipment used by trained
ADIC technical personnel.

After this is done, the drives can be configured by the system
administrator.

To add a drive, follow the steps below:
Step 1. Performed by ADIC technical support.

• Install drive in AML configuration.

• Teach robot (teaching automatically updates the
robotic database).

•Deletelibrary.

• Create new library.

• Remap the library.

Step 2. Performed by VolServ system administrator.

• Define new tape drive and specify media type.

• Associate new drive with VolServ library being
used by FileServ.

Step 3. Loginasroot user.

600716 Rev A System Tasks 1-55

Administrative Tasks

Step 4. Change directory to $FS_HOME (directory where

FileServ is located).

Step 5. Source FileServ

.cshrc

.

cshrc by entering source

Step 6. Execute the fsvsinstall script by entering run

/util/install/fsvsinstall

and respond to

questions.
The

fsvsinstall script prompts you for the

following information:

• Enter VolServ library used by FileServ software.

• Enter drive identifier to add to FileServ.

• Enter component alias, device pathname, drive
type, and drive delay time for each drive
identifier.

Step 7. Log out as

root and log in as the FileServ system

administrator.

Step 8. Verify the drives have been added to the FileServ

system by entering

fsconfig.

Step 9. Log out as the FileServ system administrator and log

in as the VolServ system administrator.

Step 10. Verify the drives have been added to VolServ by

querying the drive pool used by FileServ.

Step 11. Log out as the VolServ system administrator.

1-56 System Tasks 600716 Rev A

Administrative Tasks

Fine-tune Parameters

Reallocate Drives

The following parameters can be fine-tuned for better system
performance:

Parameter Page

ReallocateDrives 1-57
Modify Tape Usage 1-58
Redirect Policy Applications 1-59

Drive allocation is affected by the following sets parameters:

• Drive deallocation.

The deallocation parameters determine when a drive is
taken offline because of access errors. Drive
deallocation parameters are set by modifying the
appropriate system parameters. The system parameter file,

fs_sysparm, is located in the $FS_HOME/sysparms

directory.

• Delayed dismount.

The delayed dismount parameters determine when media is
dismounted from a drive after a store or retrieve request is
processed. The delayed dismount feature allows
optimization of reallocation of media for another request in
the queue and, thus, can reduce mount/dismount time for
resource requests.

System Tasks

Step 1. Using a text editor, open the

located in the

600716 Rev A System Tasks 1-57

$FS_HOME/sysparms directory.

fs_sysparm file

Administrative Tasks

Step 2. Modify any of the drive parameters identified in the

table below:

Parameters Description

FS_DRIVE_ERR_THRESHOLD Threshold value when

equalled or exceeded results
in drives being taken offline.

FS_THRESHOLD_INC_NUM Threshold increment number

variable. Value for the drive
failure level when an access
to a drive fails.

Modify Tape Usage

FS_THRESHOLD_DEC_NUM

Threshold decrement number
variable. The value for the
drive failure level when
access to a drive is
successful.

Step 3. Save and close the edited file.

The way data is written to tape is m odified by editing the
appropriate system parameters that control:

• Estimated tape length calculations.

• Data block size.
Step 1. Using a text editor, open the

located in the

$FS_HOME/sysparms directory.

fs_sysparm file

Step 2. Modify any of the default tape utilization parameters

identified in the table below:

Parameters Description

NOMINAL_FILE_SIZE Nominalfilesizeinbytes.Usedto

estimate remaining tape capacity.

1-58 System Tasks 600716 Rev A

Administrative Tasks

Parameters Description

DEF_MED_SPC_3480 Default 3480 tape length in bytes.
DEF_MED_SPC_3490 Default 3490 tape length in bytes.
DEF_MED_SPC_8590 Default 8590 tape length in bytes.
DEF_MED_SPC_CTIII Default CTIII tape length in bytes
DEF_MED_SPC_CTIV Default CTIV tape length in bytes.
DEF_MED_SPC_D2SM Default small D-2 tape length in bytes.
DEF_MED_SPC_D2MD Default media D-2 tape length in bytes.
DEF_MED_SPC_D2LG Default large D-2 tape length in bytes.
FS_DISK_BLOCK_FACTOR Number of disk blocks to use per transfer

FS_TAPE_BLOCK_FACTOR Number of disk blocks to use per transfer

FS_RSP2150_BLOCK_FACTOR Number of 2150 blocks to use per transfer

Redirect Policy Applications

System Tasks

when reading/writing the disk (default =

10).

when reading/writing a tape (default = 1).

when reading/writing the 2150 (default =

4).

Step 3. Save and close the edited file.

Step 1. Open the crontab file.
Step 2. Modifying the list of DataClass groups where the

policies is applied.

600716 Rev A System Tasks 1-59

Administrative Tasks

NOTES

1-60 System Tasks 600716 Rev A

DataClassManagement.....................2-3

DataClassGroups.......................2-4

ManipulateRelations...................2-10

FileManagement..........................2-22

Pathname.............................2-22

Links.................................2-22

Spanning..............................2-23

Clustering.............................2-24

ModifyFileAttributes..................2-26

GenerateReport .......................2-28

DataMigration ...........................2-30

FileCleanup...........................2-30

MinimumTimeParameters..............2-31

Policies...............................2-31

StoringandRetrievingData................2-40

StoreFiles.............................2-40

CleanUpDatafromDisk................2-42

CopySecondaryFiles...................2-43

2

Operating

Tasks

OperatingTasks

GeneralStorageProcessing..............2-44

RetrieveFiles..........................2-46

DelayedDismount.....................2-52

MediaManagement.......................2-54

MediaServices.........................2-54

LoadandUnloadMedia ................2-56

FormatMedia .........................2-61

Media Duplication .....................2-61

MediaStates...........................2-63

StorageLimit..........................2-65

GenerateMediaReports ................2-66

AdministrativeTasks

Roadmap

Topic

Refer To

Chapter

Initialize FileServ, configure interface with
VolServ, perform start up and shut down,
modify system configuration, and tune system
for better performance.

Manage: DataClass Groups, files, migration,
data, and media.

Using the FileServ utilities. 3
Troubleshoot operating problems. 4

1

2

2-2 Operating Tasks 600716 Rev A

AdministrativeTasks

DataClass Management

SPECIAL

special/

Files controlled by FileServ are segregated into DataClass
groups. A DataClass group contains a unique set of parameters
that govern the migration behavior of the directories that are
associated with the class.

The figure below depicts directory-to-DataClass relationships:

The DataClass PR ODUCT contains all files under the
/prod/dev and /prod/doc directories, but none under the
/prod/misc directory. This shows that some directories at a
certain level may not be related to a DataClass group.

/

prod/

other/ test/

proc/

private/

misc/ doc/

dev/

TESTERS

build/

PRODUCT

OperaitngTasks

dir/ … dirn/ file1 … filen

public/

The test/proc/special directory is
the onlyassociationdirectory point
for the DataClass SPECIAL. All
files beneath /test/proc/special are
managed together.

All files under /test/build and /test/proc/public belong to D ataClass
TESTERS. This illustrates that the assignment ofmigrationdirectories
to a DataClass group is not restricted to a certain level in the tree
structure. Thus,migrationdirectories fromdifferentfile systems can be
associated with the same DataClass identifier.

600716 Rev A Operating Tasks 2-3

dir/ … dirn/

file1 … filen

dir/ … dirn/

AdministrativeTasks

Migration policy parameters are configurable on a DataClass
group basis, which provides the FileServ administrator with
control over the behavior of the FileServ system. The minimum
time required on disk before migration and file cleanup action
are examples of DataClass migration policy parameters. Quotas
for media usage (both a soft warning limit and a hard limit) are
also kept on a DataClass group basis. DataClass group
parameters are recorded so that tuning is accomplished while
the FileServ system is active.

FileServ uses DataClass groups as the means to segregate files
on media. All files on media are of the same DataClass group.
This provides a level of physical security for those sites for
which it is required. This segregation ensures that retrieval of
files from different user groups (as defined by the DataClass
group parameters) does not require access of the same physical
media.

DataClass Groups

Characteristics of DataClass groups are established and
modified so that data is handled differently among DataClass
groups. Initially, configuring or changing the parameter settings
for DataClass groups involves DataClass manipulation. This
allows flexible handling of data to suit the user’s needs.The
table below lists the tasks performed on DataClass groups:

Topic Page

Modify Group with fsmodclass Command 2-5
Rename Group with fsclassrnm Command 2-6
Remove Group with fsrmclass Command 2-7
Generate Reports with fsclassinfo Command 2-7

2-4 Operating Tasks 600716 Rev A

AdministrativeTasks

Note

All GUI class operations are run from ADMIN-> Define Class

->Create Groups or with the fsaddclass command.

To create a DataClass group, follow the steps below.

Tip

A DataClass group must be defined before directories can be
associated with it.

Step 1. To verify the parameter settings before attempting

any modification, use the

fsclassinfo command

to view the DataClass group parameters.

OperaitngTasks

Step 2. Run the

fsaddclass command and specify a

DataClass group name.

% fsaddclass prodclass

Step 3. Use other appropriate options, as needed. For option

information, refer to the Command Reference book.

Modify Group with
fsmodclass Command

600716 Rev A Operating Tasks 2-5

The fsmodclass command modifies DataClass group
parameters.

Note

For more information on the fsmodclass command, refer to
the Command Reference book.

AdministrativeTasks

Step 1. Run the fsmodclass command and specify a

DataClass group name.

% fsmodclass prodclass -n joe

Step 2. Use fsclassinfo to compare each DataClass

group parameter. Then either change the class
parameters for the new class to allow spanning or
change the class parameters for t he old class to
disallow spanning.

-Specifyoldclass.

-Specifynewclass (newclass name cannot be the

same as oldclass name). The directories
associated with oldclass become associated with
newclass, and oldclass is deleted.

% fsclassrnm prodclass iradclass

Rename Group with
fsclassrnm Command

The fsclassrnm operation allows the name of a DataClass
group to be changed.

Note

For more information on the fsclassrnm command, refer to
the Command Reference book.

All files and media associated with the previous DataClass
group still exist in the new DataClass group. If the new
specified DataClass group already exists, the previous
DataClass group is merged into the new DataClass group. No
restrictions exist when merging two DataClass groups. If two
DataClass groups use different media types, the merge still
occurs.

2-6 Operating Tasks 600716 Rev A

AdministrativeTasks

Remove Group with
fsrmclass Command

Generate Reports with
fsclassinfo Command

The fsrmclass operation removes a DataClass group and its
parameters from FileServ.

Note

For more information on the fsrmclass command, refer to
the Command Reference book.

This procedure also deletes the directory-to-DataClass
associations that involve the specified DataClass group. Empty
all directories in the DataClass group before the

fsrmclass

operation is executed. If any association point directory is not
empty, the directory is not deleted and remains in the file
system unassociated with any DataClass group. A status
message is displayed that indicates the directories are, or are not
successfully removed. The UNIX command,

rmdir,isusedto

delete the directory from the UNIX system.

The Class Information Report displays DataClass groups and
parameters.

OperaitngTasks

For the specified DataClass groups, the

fsclassinfo

command or Class Information screen lists the parameters
and the points of each DataClass association.

Note

For more information on the fsclassinfo command, refer to
the Command Reference book.

The long format of the report shows a listing of
directory-to-DataClass association points. The long option
gives the DataClass group and its parameters, followed by a list
of directories associated with each DataClass group.

The short report is the default and lists each specified DataClass
group and all its parameters.

600716 Rev A Operating Tasks 2-7

AdministrativeTasks

If no class is specified, a short report on all DataClass groups is
generated.

The generated report is sent to

stdout but can be redirected to

a file or piped to a printer.
The output of a long report is shown below:

% fsclassinfo low_twr6 -l

--------------------------------------------------------------­Class Information Report Sun Jan 31 14:18:03 1999
Class ID: low_twr6

---------------------------------------------------------------

Soft Limit: 80 Max Copies: 2
Hard Limit: 95 Media Type: D2S

Notify ID: adic File Spanning: n

Security Code: 1CPY File Cleanup: IMMEDIATE

Account Number: PTRU Media Cleanup: SYSTEM

Drive Pool: fspool File Clustering: n

Default Copies: 1 Mintime (min): 1

Associated Directories:

/arch1/low_twr6
/arch3/XLfiles/low_twr6

FS0000 31 174105 fsclassinfo completed: Command Successful

The table below describes the report’s fields:

Field Description

Soft Limit Number of media used for the DataClass

group.

Hard Limit Number of media allocated for the

DataClass group.

2-8 Operating Tasks 600716 Rev A

AdministrativeTasks

Field Description

Notify ID E-mail address where notification is sent

when the soft limit or hard limit is
reached.

Security Code Four-character DataClass group security

code.

Account Number Five-character DataClass group account

number.

Drive Pool Name of drive pool associated with the

DataClass group.

Default Copies Number of copies stored on media.

Note:TheDefault Copiesparameter
defines the required number of copies that
must be made.

Max Copies Maximum number of copies allowed for

each file associated with the DataClass

group.
Media Type Media type for the DataClass group.
File Spanning Indicates whether file spanning of media

is enabled for the DataClass group.
File Cleanup File cleanup action for the DataClass

group.
Media Cleanup Media cleanup action for the DataClass

group.
File Clustering Indicates whether file clustering is

enabled or not enabled.
Mintime Minimum time (in minutes) a file must

reside on disk before being eligible for

storage, or for removal from disk if all file

copies reside on media.

OperaitngTasks

600716 Rev A Operating Tasks 2-9

AdministrativeTasks

Manipulate Relations

Migration directories are defined by associating directories with
a DataClass group. A DataClass group is associated with one or
more directory paths. This association is defined as a relation
between the DataClass group and the directory. The directory is
known as the association point. Relations are added and deleted
in a file system.

The table below lists the tasks performed on DataClass
groups:

Topic Page

Add Relations with fsaddrelation Command 2-10 Associate New Data with New Relations 2-11 Associate New Directories with Files 2-12 Remove Relations with fsrmrelation

Command
Change Relation Points 2-17
Generate DataClass Report 2-21

2-16

Note

All GUI relation operations are executed from ADMIN->Define
Class/Directory Relations.

Add Relations with

Arelationisaddedwiththe

fsaddrelation operation.

fsaddrelation
Command

2-10 Operating Tasks 600716 Rev A

Note

For more information on the fsaddrelation command, refer
to the Command Reference book.

AdministrativeTasks

This procedure allows you to associate a DataClass group
definition with a directory. All files and directories beneath the
association point are included in and governed by the DataClass
group parameters.

To add a DataClass group association to a directory, it must not
be superior to or subordinate to any directory that already has a
Directory-to-DataClass relationship.

If the subdirectories already have the same DataClass
relationship, the association point can be rolled up. For more
information, see “Change Relation Points” on page 2-17.The
DataClass association point cannot be a directory in the

root

file system unless it is a mount point for a new file system.

Associate New Data
with New Relations

The DataClass group associated with a directory also
determines the media to which the files in that directory is
migrated. The files in a migration directory are only migrated to
media that contain files with the same DataClass group
association.

After adding a new relation, run the fsdump command to
associate any new data with the new relation (the new mount
point).

Caution

Failure to run fsdump after adding relations may impact
system performance.

The fsdump command creates an fs_dump.file that
contains an entry for each associated directory and stored file in
the file system. The

fs_dump.file to reconcile the restored files from the dump

fsaudit command uses the

tape and the FileServ database.

OperaitngTasks

600716 Rev A Operating Tasks 2-11

AdministrativeTasks

Associate New
Directories with Files

Files can be present in a directory when the fsaddrelation
is performed.

Creating a directory under a directory that is an association
point automatically associates the newly created directory with
the DataClass group of its parent directory.

Note

When adding a DataClass relation to a directory that contains
files, no users are allowed in the file system at the time the
command is issued or the command fails.

Returned status shows that the file system is busy. A file system
must be inactive because it must be unmounted, mapped, and
remounted at the time of the fsaddrelation to ensure that
associated file information is accurate upon completion.

The file system is mapped by unmounting the file system and
remounting it exclusively for the mapping process. It is
recommendedtoperformthe

fsaddrelation to a populated

directory during a slack time. Users cannot access any files in
the file system during the fsaddrelation processing.

Following the mapping and execution of the

fsaddrelation

operation, the file system is unmounted and remounted to allow
user access again.

Because the

grep the major and minor device numbers of the file system to

check for users. On SGI systems, the user can run the

fstat options are limited, list all open files and

fuser

command to find the same information.

Note

For more information about major and minor device numbers,
refer to the manual page for the UNIX fstat or fuser
commands.

2-12 Operating Tasks 600716 Rev A

AdministrativeTasks

Major and minor device numbers are not necessary. Instead, use
the device name of the file system as listed by the UNIX

df

command.

Legal Directory-to-DataClass Relationship

/dir1

DataClass A

dir2

dir4dir3 dir5

Illegal Directory-to-DataClass Relationship

dir6

dir8

/dir1

DataClass A

dir2

dir4dir3 dir5

DataClass A cannot be associated with dir2 because its
subdirectory dir5 is already associated with DataClass B.

dir6

dir8

dir9

DataClass B

OperaitngTasks

dir9

DataClass B

600716 Rev A Operating Tasks 2-13

AdministrativeTasks

Below is an example of the df command. In the example, the
numbers given by fuser are processes accessing files in
To get more information on the process, use

grep for the process number.

% df

Filesystem Type blocks use avail %use Mounted on
/dev/root efs 205614 46958 158656 23% /
/dev/usr efs 2068050 1678616 389434 81% /usr
/dev/dsk/dks1d1s2 efs 5680906 4089070 1591836 72% /fs
/dev/dsk/dks3d3s0 xfs 1949616 1103528 846088 57% /lst1

%fuser/dev/dsk/dks3d3s0
/dev/dsk/dks3d3s010620co 11762c 10738co

ps -elf and

/tst1.

Example

Step 1. Use the UNIX ls command to verify that the

directory to be associated already exists.

% ls
data
irad

Step 2. If the directory does not exist, use the UNIX mkdir

command to create the directory. The specified
directory cannot be a directory in the root file
system unless it is a mount point for a new file
system.

% mkdir production
% ls
data
irad
production

2-14 Operating Tasks 600716 Rev A

AdministrativeTasks

Step 3. Verify that the DataClass group is defined by using

the

fsclassinfo command.

Note

The fsclassinfo command displays
information for all DataClass groups.

Step 4. If the DataClass group is not defined, see “All GUI

class operations are run from ADMIN-> Define
Class ->Create Groups or with the fsaddclass
command.” on page 2-5.

Step 5. Run the fsaddrelation command and specify

the DataClass group and directory to be
associated.

% fsaddrelation production -c england

OperaitngTasks

Note

The entire path name need not be entered. The
directorypath is resolved using the current
working directory. The directory notation, “.”
(current directory) and “.” (previous directory), can
be used.

Step 6. After adding a relation to a directory, the directory’s

file system is dumped so that the parent directory of
the relation point is present in the dump file. If
several relations are added to the file system, the file
system dump is performed after all the relations are
made.

% fsdump -f /arch1/site1_production.dumpfile /site1/production

600716 Rev A Operating Tasks 2-15

AdministrativeTasks

Remove Relations with
fsrmrelation Command

A directory-to-DataClass relationship is removed and the
directory is made a nonmigration directory by using the

fsrmrelation operation.

Note

For more information on the fsrmrelation command, refer
to the Command Reference book.

Removing a DataClass relationship from a directory causes it to
be a nonmigration directory by FileServ. Therefore, files that
are copied, saved, or moved into this directory by users (after
the directory is disassociated from a DataClass group) are not
migrated to media. The relationship is restored, and the
directory is made migration by using the

fsrmrelation

operation.
Before issuing the fsrmrelation operation, all files and

subdirectories in the association point directory must be deleted
or moved so that the directory is empty. Directories are not
deleted by fsrmrelation.

Step 1. Run the fsrmrelation command.

Note

The directory must be empty before the
fsrmrelation command is allowed. If the
directory contains files or other subdirectories, the
fsrmrelation command fails.

Specify the name of the directory to disassociate.

% fsrmrelation production

2-16 Operating Tasks 600716 Rev A

AdministrativeTasks

Change Relation Points

Roll Up DataClass
Groups

Association points are moved up or down in the file system
hierarchy tree from their original definition with the

fsrollup

and fsrolldown commands,or Define Class/Directory

Relations

menu.

This is a useful operation in adjusting the size and
manageability of migration directory structures associated with
DataClass identifiers.

The common parent directory of one or more association points
in a DataClass group is included in the DataClass group using

fsrollup command.

the

Note

For more information on the fsrollup command, refer to the
Command Reference book.

This causes FileServ to associate the specified directory in the
command with the DataClass group of its subordinate
directories. The entries in FileServ that associate the
subordinate directories with the DataClass group are removed.
The specified directory becomes an association point in the
DataClass group. If the specified directory includes either
subordinate directories associated with a different DataClass
group, or nonmigration directories, the

fsrollup command

fails.

OperaitngTasks

600716 Rev A Operating Tasks 2-17

AdministrativeTasks

In the figure below, the fsrollup command fails to roll up to

dir1 from dir2 because dir6 is not a migration directory.

Before Rollup

DataClass A

After the command

fsrollup /dir1/dir2

/dir1

dir6

dir2

dir4dir3 dir5

dir7

DataClass A

/dir1

dir2

DataClass A

dir4dir3

fsrollup function is performed on only one hierarchical

The

dir5

directory level at a time. Roll up of a DataClass group to a
directory that is two or more levels above an upper boundary
directory of the DataClass group is not allowed. The user
cannot roll up past a file system mount point. The specified
directory contains only subordinate directories and no other
files.

dir6

dir7

Perform this adjustment before many files are stored to the
directories.

Step 1. Verify that the rollup does not cause contention with

other migration directories

Step 2. Run the fsrollup command.

2-18 Operating Tasks 600716 Rev A

AdministrativeTasks

Step 3. Specify the name of the directory to be rolled up to

(the new association point).

% fsrollup production

Note

All subordinate directories of directory must be in
the same DataClass group. The directory
specified in directory can only contain subordinate
directories and no other files

Roll Down DataClass
Groups

The DataClass association point directory level is changed
using the

Note

For more information on the fsrolldown command, refer to
the Command Reference book.

fsrolldown command.

A directory at the association point of the DataClass group is
excluded from the DataClass group by specifying it in the

fsrolldown command. This causes each subdirectory of that

directory to become an association point for the DataClass
group. The specified directory no longer maintains a
directory-to-DataClass relationship and, therefore, is a
nonmigration directory. The specified directory contains only
subordinate directories and no other files. When rolling down a
directory, files must be moved into directories before the
command is invoked. It is preferable to perform this adjustment
before many files are stored to the directories.

The association is only rolled down to an association point for
each directory under the original association point. The Roll
Down operation is performed on only one hierarchical directory
level at a time.

OperaitngTasks

600716 Rev A Operating Tasks 2-19

AdministrativeTasks

Before Rolldown

FileServ does not permit you to roll down to a directory that is
two or more levels below an association point of the DataClass
group.

/dir1

DataClass A

After the command

fsrolldown /dir1/dir2

dir2

dir6

dir4dir3 dir5

/dir1

DataClass A

dir2

dir4dir3

dir5

dir6

dir7

Anew
nonmigration
directory can
be added
following the
rolldown.

Step 1. Ensure that no regular files are in the specified

directory. The only nodesare subdirectories, as these
each become new association points.

Step 2. Run the fsrolldown command. Specify the name

of the directory to roll down (the old association
point).

% fsrolldown production

2-20 Operating Tasks 600716 Rev A

AdministrativeTasks

Note

The directory specified in directory can only
contain subordinate directories and no other files.

Generate DataClass
Report

While DataClass relation points are listed in the long format of
the Class Information Report, individual directories at any
position in the file system can be checked for their DataClass
relationship with the fsdirclass command or Directory

to Class Information

Note

For more information on the fsdirclass command, refer to
the Command Reference book.

screen.

The Relation Information Report displays the class associated
with the specified directory. If the specified directory is not
associated with a class, FileServ returns an error message.

Step 1. Run the fsdirclass command. Specify the

name of the directory to be examined.

Step 2. An example of the output is shown below:

% fsdirclass /production

OperaitngTasks

FS0070 02 03881 fsdirclass completed:
/production located in class england.

600716 Rev A Operating Tasks 2-21

AdministrativeTasks

File Management

Pathname

File management tracks file information, requests file copies,
and controls disk space of files under FileServ control.

The table below lists file topics:

Topic Page

Pathname 2-22
Links 2-22
Spanning 2-23
Clustering 2-24
Modify File Attributes 2-26
Generate Report 2-28

The directories and subdirectories under a migration point must
have a full path name less than or equal to 255 characters.

Note

If a directory name is created with greater than 255 characters,
the system administrator receives a caution on the console
and logfile to immediately remove the directory. Files in this
directory cannot be stored.

Links

2-22 Operating Tasks 600716 Rev A

FileServ supports hard links and soft links.

Note

A hard link can be created after a file is stored or the

fschfiat command is performed on the file.

AdministrativeTasks

When hard-linked files are stored and retrieved, the common
file data is stored or retrieved for all of the links, no matter
which file name is submitted with the

fsstore command.

The return status for the operation lists a file name of any one of
the links and not necessarily the file name submitted as an
argument with the command. If a different linked file name is
returned in the status, the file data was correctly handled.

FileServ prevents hard links between files across DataClass
boundaries.

Symbolic links can cross DataClass boundaries and file system
boundaries.

Spanning

Tip

ADIC does not recommend you use symbolic links across
DataClass groups.

The DataClass parameters that control the original file are the
DataClass groups of the file links, regardless of the location.
Soft links that cross DataClass groups are misleading, because
the file data can actually reside in a different class.

FileServ supports file spanning across media. If a file is larger
than a single piece if media, the file will span to another piece
of media until the entire file is stored.

A file that spans multiple media always starts at the beginning
of each additional media required to store the file. The file is
stored on media until all available space is used, the remaining
part of the file (spanned portion) is stored on a blank media. If
the file ove rflows another media, another blank is used until the
entire file is stored.

OperaitngTasks

600716 Rev A Operating Tasks 2-23

AdministrativeTasks

File spanning is enabled or disabled for each DataClass group
by the

fsaddclass command. The fsmodclass allows

modification of DataClass group processing parameters while

fsfileinfo command reports all the locations of the

the
spanned file.

Clustering

FileServ supports file clustering. File clustering is the
accumulation of files associated with a DataClass group. When
these files are stored on media, they are seen as one logical file.
Any file in a cluster is retrieved as any other non-clustered
FileServ file.

File clustering can be defined when adding a DataClass group
to the file system (

fsaddclass)orbythefsmodclass

command. File clustering offers two advantages over individual
file storage. The first advantage is the media space saved when
clustering. The amount of space consumed by a cluster of files
is less than the space used if files are stored individually. The
second advantage is that the amount of time to store a cluster of
files is less than the sum of the time required to store each file
separately in the cluster. Clustered file information is sent i n
one continuous stream of data to the drive for storage on media.
Unclustered files require the drive to stop, insert tape marks,
file labels, and perform database updates for each file, which
results in increased storage time.

The system administrator controls the maximum size of the
files to be clustered and the clustered file size for all supported
media types.

2-24 Operating Tasks 600716 Rev A