Administrative Tasks FileServ Version 4.
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.
READER COMMENT FORM ADIC includes this Form in an effort to provide the best possible documentation to our customers. Please take a few moments to mail or FAX your response to: ADIC Software Documentation 10949 East Peakview Ave. Englewood, CO 80111 FAX: 303-792-2465 E-mail: swpubs@adic.com Question Circle One Information was complete. Agree Disagree Information was easy to find. Agree Disagree Information was easy to follow.
NOTES
Contents Preface Purpose of This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3 Who Should Read This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3 How This Book is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-3 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P-4 Books . . . . . . . . .
Administrative Tasks Store and Truncate Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10 Database Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10 chk_point.pl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11 checkDBALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-12 keyBuildAll . . . . . . . . . . . . .
Administrative Tasks Edit Devices with fsconfig Command . . . . . . . . . . . . . . . . . . . . . . . . . . .1-48 Add a Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-49 Edit Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-50 Delete a Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-50 Generate Report . . . . . . . . . . . . . . . . . . .
Administrative Tasks Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-31 Storage Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-32 Cleanup Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-34 Overflow Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administrative Tasks Media States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-63 Storage Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-65 Generate Media Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-66 Media Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-66 Media List . . . . . . . .
Administrative Tasks Dump Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-9 Restore Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11 Audit Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17 File System Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preface P Purpose of This Book . . . . . . . . . . . . . . . . . . . . . . .P-3 Who Should Read This Book. . . . . . . . . . . . . . . . .P-3 How This Book is Organized . . . . . . . . . . . . . . . .P-3 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .P-4 Books. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .P-5 Online Books . . . . . . . . . . . . . . . . . . . . . . . . . . .P-5 Related Publications . . . . . . . . . . . . . . . . . . . . .
Administrative Tasks NOTES P-2 Preface 600716 Rev A
Purpose of This Book This book describes the management tasks, utilities, and troubleshooting tools used in operating FileServ. Who Should Read This Book This book is written for the system administrator who is operating and troubleshooting FileServ. How This Book is Organized It assumes the administrator has a strong familiarity with: • UNIX operating systems. • Applications running in their site environment.
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. FS0000 03 204773 fsmedinfo completed: Command Successful. The root prompt is shown as a percent sign. % su root What you should type in is shown in Courier bold font. fsadmret Site-specific variables are in a Times italics font.
Books The books described below are part of the technical documentation set, and are shipped on CD: FileServ Overview An overview of FileServ. Contains a glossary. Administrative Tasks System tasks, operating tasks, FileServ utilities, and troubleshooting problems. Installing FileServ Describes: server requirements, installation procedures, configuration parameters, and tools to troubleshoot install problems. Command Reference An alphabetical list of FileServ commands.
Administrative Tasks Related Publications The publications described in the table below are created and distributed on an as-needed basis. Related Publications “Release Notes” Description For each version of FileServ, the “Release Notes” contain: • Summary of enhancements. • Describes: - Fixed problems. - Known problems. - Installation and configuration issues. • Lists: - Operating system patches. - System requirements. “Product Alerts” Informs customers of technical problems and solutions.
General Parameters. . . . . . . . . . . . . . . . . . 1-28 System Administration Parameters . . . . 1-28 Default Parameters . . . . . . . . . . . . . . . . . . 1-36 1 VolServ-specific Parameters . . . . . . . . . . 1-40 Installation Parameters. . . . . . . . . . . . . . . 1-41 Software Maintenance Parameters . . . . . 1-43 Media Stats Parameters . . . . . . . . . . . . . . 1-44 Logging Parameters . . . . . . . . . . . . . . . . . 1-44 Edit System Parameters . . . . . . . . . . . . . .
Administrative Tasks 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. 1 Manage: DataClass Groups, files, migration, data, and media. 2 Using the FileServ utilities. 3 Troubleshoot operating problems. 4 Note For complete information on the FileServ commands used in these tasks, refer to the Command Reference book.
Administrative Tasks Initialize FileServ Running FileServ for the first time involves the following tasks listed in the table below: Task 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 System Tasks Access the Host Server Page To access the host where FileServ has been installed to transfer files to or from the migration directories, us
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.
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. • ADDBLANK or ADDBLNK • CHECKIN • IMPORT • DATA • MIGRATE • REMOVE System Tasks The following mediaclasstype exist: An example of a valid MediaClass name is F0_D2S_ADDBLANK.
Administrative Tasks Register the Configuration • F0_D2S_MIGRATE • F0_D2S_REMOVE 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. The fsconfig command provides hardware component configuration.
Administrative Tasks • Truncation policies for files and media types associated with the DataClass group. Note Associate Directories System Tasks For more information on the fsaddclass command, refer to the Command Reference book. 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.
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.
Administrative Tasks Create Migration Policies Migration policies initiate movement of file data from disk to tape. Tip System Tasks 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).
Administrative Tasks Routine Processing 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 Store and Truncate Files 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 cron process execute the operations.
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. System Tasks Periodic database maintenance is required to prevent data loss, improve FileServ software performance, and simplify recovery procedures if needed.
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.
Administrative Tasks The table below shows the suggested database maintenance intervals for each database utility. Note Database Maintenance Script Normal Usage Heavy Usage $FS_HOME/internal/chk_point/chk_point.
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.
Administrative Tasks The utilities that operate on specific file systems are: blockpos, dirdb, fileattr, filecmnt, filecomp and filexpir. Note System Tasks The one table utility that does not work like the others is the keytest utility. All of the utilities, with the exception of keytest, have two modes: • Command Line Mode. • Interactive Mode. Both modes are described below.
Administrative Tasks First, you check the devdb table for the entry containing /test2. Notice there is a field called “device key” associated with /test2. This is the value you will use for device specific table utilities that are associated with the /test2 file system. Step 3. To look at the fileattr entries for the files on /test2 and to send the output to a file called test2.files, enter the following command: # fileattr 4 -ftest2.files Examine the file at your leisure.
Administrative Tasks Option -k key Description Query for a specific record key. A working knowledge of the database internals is often needed to provide the proper key. Interactive Mode System Tasks Each table utility has a different requirement for the key. For additional information, see the HELP screen. To start a utility in Interactive Mode, include the -i option on the command line. If the-i option is used, FileServ ignores the -k key option.
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.
Administrative Tasks • Heavy storage, retrieval, modification, creation, or deletion of files in migration directories. System Tasks 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.
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 command will not replace the 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.
Administrative Tasks Run a fsmedinfo -l report to verify all files deleted from media. If files still exist, rerun the fsclean command. Note System Tasks Execute the fsundelete command twice to make sure all your required files have been undeleted. The fsundelete command allows recovery of removed or modified copies of files as long as an entry exists in the trashcan. Only the primary copy is recoverable with the fsundelete command.
Administrative Tasks Startup and Shutdown 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.
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 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.
Administrative Tasks 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 directory are deleted during a contingency start.
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: 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. System Tasks Step 1.
Administrative Tasks Any media introduction or removal operations in progress are interrupted. The requests resume and 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.
Administrative Tasks Managing System Configuration 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.
Administrative Tasks Configurable System Parameters General Parameters Category Page Installation Parameters 1-41 Software Maintenance Parameters 1-43 Media Stats Parameters 1-44 Logging Parameters 1-44 The fs_sysparm file contains parameters that control general FileServ activities. The parameters in this file are grouped into the following categories: Description Page System Administration Used to tune system performance and media usage.
Administrative Tasks Parameter Definition FILE_LBL_FMT_TAPE adic00000001 Defines the way data labels are written to tape devices. 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 written to RSP-2150 devices.
Administrative Tasks Parameter DEFAULT_MEDIA_TYPE Default DLT Definition Default media type used with commands with optional media types. DEF_MED_SPC_3480 220000000 Default tape length of a 3480 cartridge in bytes. DEF_MED_SPC_3490 400000000 Default tape length of a 3490 cartridge in bytes. DEF_MED_SPC_3490E 800000000 Default tape length of a 3490E cartridge in bytes. DEF_MED_SPC_D2SM 25000000000 Default tape length of a D-2 small cassette in bytes.
Administrative Tasks Parameter Definition 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.
Administrative Tasks Parameter Default (continued) Definition The FS_CALLOUT_SLEEP_INT and MAX_DMON_SUSP_ERRORS parameters can be tuned, 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.
Administrative Tasks Parameter MAX_WRITES Definition 100 Number of retries on IPC send failure. The MAX_READS and MAX_WRITES parameters are set to 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.
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. (Valid 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.
Administrative Tasks Parameter FS_DRIVE_ERR _THRESHOLD Default 20 Definition Threshold value when equalled or exceeded results in drives being taken offline. Maximum number of files allowed on a single 3480 cartridge tape. 95 Percentage value used to check against to determine if media can be migrated. 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.
Administrative Tasks Parameter CLEANUP_PROCESSING FS_PRINTER_PATH Definition 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. /usr/bin/lpr MDM_POSITION_VALIDATION Default Parameters Default YES Default printer used for printing reports from the GUI. Enables validation of the tape position prior to the first file in a file set.
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 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.
Administrative Tasks Parameter CLASS_DEF_MEDIA_TYPE Default DLT Definition 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). The value can also be modified for an existing class by using the fsmodclass command.
Administrative Tasks Parameter 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).
Administrative Tasks 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. Parameter Default Definition ADVANCE_NOTIFICATION_ PERIOD 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. DEF_FILE_RETENTION_ PERIOD 0 Time a file is kept on the disk.
Administrative Tasks Parameter VS_PROGRAM_NUMBER Default Definition XXXXXXX If enabled, the VolServ program number to be used by this FileServ system. To disable, comment out the parameter. 99 VS_DEF_QUANTITY fs_F0drivepool VS_DEFAULT_DRIVEPOOL XXXXXXX VS_DIR Installation Parameters System Tasks Default media quantity for entry/exit port operations. (Range 1-99) Default VolServ drive pool used for retrieves. This drive pool contains all FileServ-configured drive components.
Administrative Tasks Parameter FS_DATABASE FS_CONSOLE FS_DEFAULT_SUBSYSTEM Default Definition 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. /dev/console Identifies the device path for the FileServ console. V0 Default component ID only for the fsmedin, fsmedout, and fsqueue commands when the user does not specify the subsystem on the command.
Administrative Tasks Software Maintenance Parameters 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.
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 e Enables or disables various priorities of the tape statistic logging.
Administrative Tasks Parameter FS_FACILITY Default 1 Definition System Tasks Logging facility used for priority 0-7 messages directed to the syslog. The configuration for the syslog is in the /etc/syslog.conf file.
Administrative Tasks Parameter FS_LOG_MASK Default Definition 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.
Administrative Tasks An example for the CLASS_MTIME parameter is shown below: rm CLASS_MTIME=10; CLASS_MTIME=30; System Tasks 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.
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.
Administrative Tasks • FS_VS_QUEUE_D2S_THRESHOLD = 9 • FS_VS_QUEUE_D2M_THRESHOLD = 9 • FS_VS_QUEUE_D2L_THRESHOLD = 9 System Tasks When adding or deleting a drive to the system, the system parameter FS_VS_QUEUE_XXX_THRESHOLD value located under $FS_HOME/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.
Administrative Tasks Edit Device Delete a Device 1-50 System Tasks 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. 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.
Administrative Tasks Generate Report Step 1. Run the fsconfig command. Use the -h option to show the configuration of all component. Step 2. System Tasks Or, use the -i option to show the configuration of a specific component.
Administrative Tasks Hardware Configuration Report Fri Jan 29 09:13:49 1999 Component ID: V0,11 -----------------------------------------------------------Device pathname: User Alias: Component Type: Drive Type: Drive ID: Delay Time: Drive Compatibility Drive Names /dev/er90/s1 ER90_DR2 DRIVE ER90 11 1000 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.
Administrative Tasks Drive Names 3490E Supported Drives 4490E Supported Media 3490 Cartridges* Media Types 3480 3490E Cartridges M2483N (Fujitsu) 3490 Cartridges* 3480 M2483ND (Fujitsu) 3490 Cartridges* System Tasks 3490E Cartridges 3480 3490E Cartridges 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.
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 offline or maintenance state, FileServ does not attempt any processing with that component.
Administrative Tasks Use the -s option to indicate the required new state of the component. Valid state entries are: UNAVAIL, MAINT, ON, OFF, and UNKNOWN. 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 Step 2. Adding and deleting drives from an Automated Media Library (AML) requires technical support assistance.
Administrative Tasks Step 4. Change directory to $FS_HOME (directory where FileServ is located). Step 5. Source FileServ cshrc by entering source .cshrc. 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: 1-56 System Tasks • Enter VolServ library used by FileServ software. • Enter drive identifier to add to FileServ.
Administrative Tasks Fine-tune Parameters The following parameters can be fine-tuned for better system performance: Parameter Reallocate Drives 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.
Administrative Tasks Step 2. Modify any of the drive parameters identified in the table below: Parameters 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. FS_THRESHOLD_DEC_NUM Threshold decrement number variable. The value for the drive failure level when access to a drive is successful. Step 3.
Administrative Tasks Parameters 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.
Administrative Tasks NOTES 1-60 System Tasks 600716 Rev A
DataClass Management . . . . . . . . . . . . . . . . . . . . . 2-3 2 Operating Tasks Operating Tasks DataClass Groups . . . . . . . . . . . . . . . . . . . . . . . 2-4 Manipulate Relations . . . . . . . . . . . . . . . . . . . 2-10 File Management. . . . . . . . . . . . . . . . . . . . . . . . . . 2-22 Pathname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22 Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22 Spanning. . . . . . . . . . . . . . . . . . . . . . . . .
AdministrativeTasks Roadmap Topic 2-2 Operating Tasks Refer To Chapter Initialize FileServ, configure interface with VolServ, perform start up and shut down, modify system configuration, and tune system for better performance. 1 Manage: DataClass Groups, files, migration, data, and media. 2 Using the FileServ utilities. 3 Troubleshoot operating problems.
AdministrativeTasks DataClass Management 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 PRODUCT contains all files under the /prod/dev and /prod/doc directories, but none under the /prod/misc directory.
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.
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. To verify the parameter settings before attempting any modification, use the fsclassinfo command to view the DataClass group parameters. Step 2. Run the fsaddclass command and specify a DataClass group name.
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 the old class to disallow spanning. - Specify oldclass. - Specify newclass (newclass name cannot be the same as oldclass name).
AdministrativeTasks Remove Group with fsrmclass 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. Generate Reports with fsclassinfo Command The Class Information Report displays DataClass groups and parameters. For the specified DataClass groups, the fsclassinfo command or Class Information screen lists the parameters and the points of each DataClass association.
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.
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. 600716 Rev A Max Copies Maximum number of copies allowed for each file associated with the DataClass group.
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.
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.
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.
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.
AdministrativeTasks Below is an example of the df command. In the example, the numbers given by fuser are processes accessing files in /tst1. To get more information on the process, use ps -elf and grep for the process number.
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.
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.
AdministrativeTasks Change Relation Points 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.
AdministrativeTasks In the figure below, the fsrollup command fails to roll up to dir1 from dir2 because dir6 is not a migration directory. /dir1 Before Rollup dir6 dir2 DataClass A dir3 dir4 dir5 dir7 DataClass A /dir1 After the command fsrollup /dir1/dir2 dir6 dir2 DataClass A dir3 dir4 dir5 dir7 The fsrollup function is performed on only one hierarchical directory level at a time.
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 fsrolldown command.
AdministrativeTasks 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. Before Rolldown /dir1 dir2 DataClass A dir3 dir4 dir6 dir5 /dir1 dir2 After the command fsrolldown /dir1/dir2 DataClass A dir3 dir4 dir6 dir5 dir7 A new nonmigration directory can be added following the rolldown. Step 1. Ensure that no regular files are in the specified directory.
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 screen. Note For more information on the fsdirclass command, refer to the Command Reference book.
AdministrativeTasks File Management File management tracks file information, requests file copies, and controls disk space of files under FileServ control. The table below lists file topics: Topic Pathname 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.
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.
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 the fsfileinfo command reports all the locations of 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.
AdministrativeTasks The cluster.config file, located under the FS_HOME/sysparms directory, controls file clustering parameters. Each DataClass group is added to this file and the applicable file size values are entered (file sizes are expressed in millions of bytes). If the DataClass groups are not added, the filesize.config default values defined in the file are used. The file is read each time a list of files is marked for storage.
AdministrativeTasks ######################################################################### #The following is a sample line which has been commented out #myclass 30 1000 30 50 150 # ######################################################################### # # Never ever change the entry for default unless specifically # directed by technical support personnel.
AdministrativeTasks Files can then share DataClass group parameters with other files in the DataClass group. These files deviate in how policy is applied and in the number of copies of that file that are allowed on media. The fschfiat command allows fine tuning of the file’s attributes without changing the characteristics of the entire DataClass group. For example, the common home directory files .cshrc and .login, are used each time a user logs into the system.
AdministrativeTasks Generate Report To view information about file location and attributes, follow the steps below: Step 1. Run the fsfileinfo command, specifying the names of the files you want reports on. Step 2. For files stored on media, this report returns an identifier for each media where the file is located. Each media ID is accompanied by a number that represents which copy of the file is on the media.
AdministrativeTasks Field Description Class Trunc Identifies whether the file is a candidate for cleanup policy application. File size Size in bytes. Location Identifies whether file resides on disk, tape, or both. Existing Copies Number of copies of the file that currently exist.
AdministrativeTasks Data Migration A migration directory is controlled by FileServ (for example, a directory that has a DataClass association.) Files stored under this directory, as well as any subsequent subdirectories, are migrated from disk to media as specified by the DataClass parameters. A DataClass group can be created so that files of associated directories exhibit certain distinctive migration behavior. These behaviors are controlled by a combination of setting the: • File Cleanup.
AdministrativeTasks Minimum Time Parameters The mintime is the minimum amount of time after the file is written or read before any policy action is taken. The mintime determines eligibility for file storage and for file removal from disk. For the cleanup policy, mintime is calculated as the time elapsed after a file was stored on media before being removed from disk.
AdministrativeTasks Migration and disk cleanup policies are implemented in the following policies: Topic Storage Policy Page Storage Policy 2-32 Cleanup Policy 2-34 Overflow Policy 2-35 Storage policy is used to migrate eligible file data to media. When the policy is initiated, a list is generated to identify the files that must be stored to media.
AdministrativeTasks The filesize.config file as shown in the example below, is read each time a list of files is received for storage. This file is dynamic and enables the system administrator to make changes without recycling FileServ. ######################################################## #This is a FileServ file for placing files on different #media types based on the size of the files themselves.
AdministrativeTasks Cleanup Policy Cleanup policy is used to remove file data from disk. The number of files removed is based on the available disk space requested for a file system. When the cleanup policy is run, each file that is a disk data truncation candidate is assigned a weight. This weight is a factor in determining to remove one particular disk file over another.
AdministrativeTasks Overflow Policy The HIBLK_THRESHOLD and LOBLK_THRESHOLD system variables are located in the fs_sysparm file. These variables are system-wide parameters. FileServ reads the new values at startup time. If FileServ is running, you must recycle the system to pickup the new values. If the overflow hiblk value is reached for a file system, the $FS_HOME/internal/policy_dir/fs_spt_ovflow script is automatically invoked.
AdministrativeTasks • Normal. The normal store request is placed in the queue for processing along with all other resource requests. Note To run fspolicy to store a very large number of files, (a million or more) make sure you have sufficient memory. The required memory should equal the maximum number of files to store times 425. • Emergency. The fspolicy command maintains an internal store and truncate candidate list of files.
AdministrativeTasks Each line in a .crontab file must consist of six positional fields, separated by spaces or tabs, and formatted as follows: minutes hours day-of-month month day-of-week command Any of the first five fields can be a list of values separated by commas. A value is either a number, or a pair of numbers that are separated by a hyphen. This value indicates that the job is performed for all the times in the specified range.
AdministrativeTasks The specification of days is made by two fields (day of the month and day of the week). If both are specified as a list of elements, the policy adheres to both. If one of the fields is an asterisk, the other field determines the day of the month or week. The example below shows this entry runs a command at midnight on the 1st and 15th of each month, as well as every Monday. 0 0 1,15 * 1 To specify days by only one field, the other field is set to *.
AdministrativeTasks • The two cases where storage policy is run on groupaclass and groupbclass run at 15 minutes past 4 and at 40 minutes past 4, respectively, every day of the year. • The storage policy application for tempclass is run at midnight on weekdays. Finally, storage policy is run for permclass at midnight on weekends only. Using this method, policies are run at whatever intervals are required.
AdministrativeTasks Storing and Retrieving Data The set of DataClass group parameters govern how FileServ processes the movement of data from disk to media. The directories controlled by DataClass group parameters are called migration directories because the data is moved (migrated) from disk to media. Movement of files from disk to media is also called file storage.
AdministrativeTasks In addition to providing an immediate store functionality, the fsstore command allows the user to override, on a file basis, the default values for the DataClass parameters that affect storage processing. Two parameters affect how the file data is handled during the storage processing. The first parameter specifies the cleanup action and the second specifies the number of secondary file copies.
AdministrativeTasks Clean Up Data from Disk Cleanup is the removal of data from disk after the application of the storage policy. Cleanup is specified with one of the commands below: • fsstore. • fspolicy -t. Note The fspolicy command cannot be used to simultaneously store and cleanup disk data. • fschfiat. You can overrides the cleanup action for a specific file by changing the file’s attributes through the fschfiat command.
AdministrativeTasks Cleanup by DataClass A DataClass group parameter specifies the default cleanup action. A Cleanup policy can be: • Completely disabled. - • Immediate truncation following the storage policy. - Valid only if all copies defined by the file’s attributes are stored. If all copies are not made, the cleanup action does not occur, because that file is not eligible for cleanup.
AdministrativeTasks A secondary file copy is written at the time the file is stored with the fsstore command by specifying the number of copies (including the primary file) up to the maximum number of copies set for the DataClass group. The number of secondary copies specified for a file cannot exceed the DataClass maxcopies parameter value. Note The current maximum allowable value for maxcopies is two copies, a primary and a secondary.
AdministrativeTasks After a file is eligible for storage, the file data for the primary copy is written to media. A volume is chosen for storage as either a default for the DataClass group (specified when the DataClass group is defined by the system administrator), or as a media type specified by the user when the fsstore command is issued.
AdministrativeTasks Retrieve Files Files that reside only on media are retrieved to disk when accessed by the user during usual operations. Files can also be retrieved to disk by issuing a fsretrieve command. The fsretrieve command requires the name of each file to be retrieved. Multiple files can be retrieved with the same command. Note For more information on the fsretrieve command, refer to the Command Reference book.
AdministrativeTasks The fsretrieve command usually retrieves the primary copy of the file requested. If the primary copy is inaccessible or corrupted, the command defaults to the secondary copy. Completion status returns when the files are successfully copied onto disk. The fsfileinfo command can be used to determine if a file is on tape, disk, or both. The file in the migration directory is associated with its media copy.
AdministrativeTasks Retrieve Files from Trashcan FileServ recovers a particular version of a migrated file that was modified or removed from an archival directory on disk. As migrated files are modified or removed, an entry is placed in the trashcan with information to recover the file. Only the primary copy of the file can be recovered, not the secondary copy. When archival directories are removed from disk, an entry is also placed in the trashcan.
AdministrativeTasks The fsundelete -u recovers a previous version of a migrated file or deleted migration directories. The command is specified with the full path name and restores the FileServ pointer to the area of the media where the data is stored. If a file is moved within a directory (renamed with the mv command), the file name is not updated in the FileServ database. If the file is deleted, the previous name appears in the trashcan.
AdministrativeTasks Clean up Trashcan Another command that must be routinely run is fsclean. The fsclean command purges the FileServ trashcan information. Caution Use of fsclean eliminates the ability to recover files from the trashcan with the fsundelete command! Precautions must be taken when using the fsclean command. 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.
AdministrativeTasks Retrieve Partial Files The fsretrieve command supports partial file copy to disk from media. A new file name is required, as well as a start and ending byte for the file data. With these parameters, the part of the file specified in the byte range is copied onto disk into the new file name. The byte range is zero relative, meaning that if the file size (in bytes) is known, any part of the file is retrieved by specifying a range of bytes between 0 and the last byte (file size -1).
AdministrativeTasks Retrieve Secondary Files If a file is stored to media as both a primary and secondary copy, the secondary copy of the file can be retrieved to disk as a new file by using the fsretrieve -c command. This is the only command that allows access to the secondary copy of a file. Delayed Dismount FileServ provides the system administrator with the ability to configure each FileServ drive to delay the dismount of media after store and retrieve operations.
AdministrativeTasks Media delayed in a drive can be dismounted with the fsdismount command. The fschstate or fsstate commands can be used to determine if a drive is in a delayed-dismount status. Note For more information on these commands, refer to the fsaddclass command in the Command Reference book.
AdministrativeTasks Media Management This section describes operations required by both the VolServ operator and the FileServ system administrator for each media management function. WARNING BE CAREFUL when interacting with the mechanical interfaces to the automated libraries. Ensure hands, long hair, and loose clothing are clear of the entry port during normal media operations DO NOT operate the robot when the library is open. (Use fschstate -s off before opening the library.
AdministrativeTasks MediaClass Group Definitions There are 54 MediaClass names with the following form: FileServID_mediatype_mediaclasstype There are ten possible values for FileServ ID: F0 through F9. Six values of mediaclasstype exist: ADDBLANK or ADDBLNK, CHECKIN, IMPORT, DATA, MIGRATE, and REMOVE. An example of a valid MediaClass name is F0_D2S_ADDBLANK. When entering media, the VolServ operator uses the IMPORT, ADDBLANK, and CHECKIN MediaClass names.
AdministrativeTasks Media Class Type Load and Unload Media Definition DATA All media entered into the system used by FileServ is automatically reclassified to this MediaClass group after the fsmedin command is performed successfully MIGRATE Media classified as DATA that are filled to a percentage equal to or exceeding FileServ system parameter PERCENT_FULL_TO_MIGRATE value is reclassified as MIGRATE and can be migrated to a different library mode based on the configuration of VolServ library action.
AdministrativeTasks Remove Media Step 1. Run the fsmedout command with the media identifiers and the -r option for the media to be checked out. The -t labeltext option is not supported at this time. Step 2. The physical location of the media (-l location) is used for tracking the media and is limited to 255 characters. Media are logically checked out of the FileServ system. Step 3. Operaitng Tasks Add Blank Media Contact the VolServ operator to complete the operation and to obtain the media.
AdministrativeTasks Each type of media supported by FileServ has a default media length specified in the system parameters; -DEF_MED_SPC_mediatype. If two media of the same type have a different length, the -l option of the fsmedin command overrides the default value. For example, if two libraries are used the default media length can only apply to one library. Therefore, whenever adding blank media to the other library, the -l option must be used. 2-58 Operating Tasks Step 1.
AdministrativeTasks Remove Blank Media The fsmedout command allows the removal of blank media. Note For more information on the fsmedout command, refer to the Command Reference book. Two ways exist to remove blank media from the FileServ domain: • Checkout blank media. • Remove blank media. The fsmedout -r command can temporarily remove blank media, retain information about the media in the FileServ database, and logically remove the media from the FileServ domain.
AdministrativeTasks Checked-out blank media can be re-entered into the FileServ system using the fsmedin -r command. If the re-entry of the Checked-out media is no longer required, the fsrminfo command is used to remove all knowledge of the media from the FileServ system. Caution If you use the fsrminfo command to remove files, both the primary and secondary copies are removed. However, only the primary copy can be recovered. Remove Blank Media The fsmedout -b command allows removal of blank media.
AdministrativeTasks Format Media All blank media introduced into the storage subsystem can be submitted for immediate formatting or withheld from formatting. Media withheld (-w) from formatting is automatically formatted when chosen for data storage or by manually issuing the fsformat command. Note For more information on the fsformat command, refer to the Command Reference book.
AdministrativeTasks Both types of duplications are described below. Note For more information on the fsmedcopy or fsfilecopy commands, refer to the Command Reference book. Copy Media The fsmedcopy -r command is used to replace media by moving data onto newer, better media or reclaiming the wasted space because of fragmentation. Note Running the fsmedcopy -r command is time consuming because of the update of file information.
AdministrativeTasks Copy Files The fsfilecopy -r command functions like the fsmedcopy command, except it replaces specified files, instead of the entire media. A single file from media or several files from several media can be replaced. The only restriction is that all files must be in the same DataClass group. Specified files from the original media are moved onto either a blank media, specified media, or a different media type not defined by the DataClass group. Only active files can be copied.
AdministrativeTasks The valid states for media in the FileServ system include the following: State Description Protect Reserved for read-only operations. Unprotect Available for read and write operations. Available Error free and resident in the storage subsystem. Unavailable Not used because it is removed from the storage subsystem or has extensive errors. Suspect A read/write or position error occurred with that media in a drive. Unsuspect Free from errors and problems.
AdministrativeTasks Storage Limit Every FileServ installation has a storage limit capacity. If the storage limit capacity is exceeded, E-mail is sent to the system administrator and a message is logged in the system log file. All Storage requests fail until the system administrator deletes a sufficient number of files to place the system under the storage limit. The fsusedspace command shows, in Gigabytes (GB), the total amount of stored primary copy data in the storage subsystem.
AdministrativeTasks After the amount of used storage is under the storage limit, FileServ must be cycled to re-enable Imports and Store requests. The STORE_LIMIT_NOTICE system parameter located in $FS_HOME/sysparm directory, defines the range, in GB that remain before the storage capacity is exceeded. Note The fs_sysparm file is located in the directory $FS_HOME/sysparms, where $FS_HOME is the directory where FileServ is installed.
AdministrativeTasks Step 1. Run the fsmedinfo command and specify one or more media identifiers to report. Step 2. Use the -l option to obtain a long report.
AdministrativeTasks --------------------------------------------------------------3773 Active Mon Dec 7 16:58:11 1998 ???/xxx : Parent_Unknown 3773 Active Mon Dec 7 16:58:13 1998 ???/yyy : Parent_Unknown 3773 Active Mon Dec 7 16:58:16 1998 ???/zzz : Parent_Unknown Media List The fsmedlist command or Media List screen produces a list of all the media, or the media in a particular DataClass group.
AdministrativeTasks Step 3. The -l option generates a longer report shown below that includes the identifiers of the media for each of the categories previously described. If no options are specified, all of the media identifiers in each category are listed, as shown below. The list is sent to stdout and can be redirected to a file or piped to a printer.
AdministrativeTasks NOTES 2-70 Operating Tasks 600716 Rev A
Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 fspic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 autostart scripts . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 3 dbcheck. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4 keybuild . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Administrative Tasks Roadmap Topic 3-2 Utilities Refer To Chapter Initialize FileServ, configure interface with VolServ, perform start up and shut down, modify system configuration, and tune system for better performance. 1 Manage: DataClass, files, migration, data, and media. 2 Using the FileServ utilities. 3 Troubleshoot operating problems.
Administrative Tasks Utilities The $FS_HOME/util directory contains software tools used to simplify various operations. An explanation of each software tool is explained in the .README files. fspic The fspic utility displays a status of the FileServ system including: • Hardware components. • Media mounted in drives. • Number of minutes since the media was accessed. This utility also monitors disk usage for all migration file systems under FileServ, as well as certain database locations.
Administrative Tasks FileServ and Amass Autostart If FileServ and AMASS are on the same platform, the FileServ processes must be started before the AMASS processes. If the autostart scripts are enabled for both FileServ and AMASS, the FileServ autostart script must be executed before the AMASS autostart script. Assign a name to the FileServ autostart script so that it will start before the AMASS autostart script. An example of the FileServ and AMASS autostart script names int /etc/rx2.
Administrative Tasks Option Description -k Performs key file structure checking. -dk Causes dbcheck to ensure the key file contains the key for each key field in each data file. -kd Causes dbcheck to ensure that a record exists for each key in each key file. -ts Performs timestamp consistency checks. -r# Reports percentage complete to the file stderr. -p# Sets to the # the number of pages in the cache for use in dbcheck. -f# Sets to # the number of open files for dbcheck.
Administrative Tasks keybuild The keybuild utility will rebuild all key files for a database. It rebuilds the key files by first reinitializing the file, and then sequentially reading all records from each data file and recreating each key field from the contents of the record. Step 1. From the $FS_HOME/util directory enter the following: # keybuild dbname where: Option dbname Step 2. 3-6 Utilities Description Name of the database whose key files you want to rebuild.
Data Retrieval Fails. . . . . . . . . . . . . . . . . . . . . . . . . 4-3 Commands that ID Problems . . . . . . . . . . . . . . . . 4-4 Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . 4-4 4 Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Status Messages. . . . . . . . . . . . . . . . . . . . . . . . . 4-5 Syslog Messages . . . . . . . . . . . . . . . . . . . . . . . . 4-6 Recover Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 Dump Data.
Administrative Tasks Roadmap Topic 4-2 Trouble- shooting Tools Refer To Chapter Initialize FileServ, configure interface with VolServ, perform start up and shut down, modify system configuration, and tune system for better performance. 1 Managing: DataClass, files, migration, data, and media. 2 Using the FileServ utilities. 3 Troubleshoot operating problems.
Administrative Tasks Data Retrieval Fails If a data retrieval operation fails, the returned status message usually provides information to determine the cause of the failure. Reissuing the request usually corrects the problem. However, if a message appears indicating one of the reasons below is responsible for the failure, additional troubleshooting is needed before reissuing the request. A database access error. • An abnormal process failure (a process abnormally terminates or is killed).
Administrative Tasks Commands that ID Problems The commands in the table below will help you to further troubleshoot problems. For information on these commands, refer to the man pages.
Administrative Tasks Messages Messages are displayed in response to a command or when certain events occur. Messages are divided into two categories: • Status messages. • Syslog messages. Every status and syslog message that results from a FileServ command includes a request identifier. The request identifier is a unique number assigned to each request at the point it is initiated in the FileServ system.
Administrative Tasks Syslog Messages Syslog messages are sent to a logging facility to inform a system administrator of important system conditions, to record additional information about these conditions, or to record the occurrence of an event. Each message has an associated priority that determines how the logging facility processes the message. Console messages are viewed from a shell window on the FileServ system console.
Administrative Tasks The log_monitor script is a alternative to newfslog for log maintenance. This script can be run as needed to refresh log files, or called from cron to monitor the logs and prevent them from filling up the $FS_HOME file system. Log cleaning will only be triggered when the command line parameters are met. The system variables $FS_HOME, $LOG_PATH, and $NONARCH_LOG_PATH must be defined before the script will run.
Administrative Tasks Step 5. Issue the UNIX tail command of the file logfile. % tail -f $FS_HOME/syslogs/logfile As host messages are generated, they are displayed in this window. Step 6. Determine the log file where you can extract information, for example, $FS_HOME/syslogs/logfile. Step 7. Change directory (cd) to the directory where the log files are stored and make sure that they exist. Step 8. Run the fsextlog command specifying the log file where information is extracted.
Administrative Tasks Recover Data To support data recovery due to a disk crash, the following tasks are required: Task Dump Data Page Dump Data 4-9 Restore Data 4-11 Audit Database 4-17 The fsdump command is used to perform a dump of each file system. Note For more information on the fsdump command, refer to the Command Reference book. Enter a -f dumpfilename to specify the file system to be dumped. The fsdump command creates a fs_dump.file for each file system dumped.
Administrative Tasks The fsdump command also supports recovery for backup of nonmigration file systems. A log message advises the system administrator that the file system is not archival. The dump continues, but the fs_dump.file does not exist and is not dumped to the dump tape. The fsdump command does not continue if the file system does not exist, another dump procedure is in progress, or for improper syntax.
Administrative Tasks If problems are discovered, correct them before continuing. Step 6. Mount a tape on a drive. Step 7. Run the fsdump command with the arguments appropriate to the platform as specified in the man page. Enter the destination file or drive and any optional arguments if appropriate. % fsdump -f /dev/rmt/tps0d3 /arch The fsdump utility prompts the user to change tapes if more than one tape is required. A sequence number is given each tape, starting at 1. • Change tapes when prompted.
Administrative Tasks Restoration of the entire file system is not required if a dump tape is lost or bad. However, restoration is recommended. Step 1. Verify the new system is large enough to contain all the data restored from tape by using the UNIX df command. The /arch3 file system is used throughout this example. % df FILESYSTEM TYPE /dev/dsk/dks2d6s7 xfs BLOCKS USE AVAIL USE 2081008 1524392 556616 74 Step 2. MOOUNTED ON arch3 Run the xfsrestore command.
Administrative Tasks Use the UNIX mkdir command to create the parent and rerun the fsaudit -r -f command. If the procedure fails, call technical support. Step 5. Run the keyBuildAll utility to update the key files in the database. Step 6. Run fsaudit -f twice on the recovered file system. • The first time fsaudit -f will clean up discrepancies left by the audit recovery. • The second time it should not find any problems.
Administrative Tasks Restore Data in Interactive Mode Step 1. Verify that the disk file system is large enough to contain all the data restored from tape by using the UNIX df command. % df FILESYSTEM TYPE /dev/dsk/dks2d6s7 xfs BLOCKS USE AVAIL USE 2081008 1524392 556616 74 Step 2. MOOUNTED ON arch Run the xfsrestore -i command. % xfsrestore -f /dev/rmt/tps0d3 /arch3 An interactive shell is invoked with the -> prompt. Step 3.
Administrative Tasks All relation points in the dumped file system are specified on the extraction list. All relation point parents must exist. If a failure occurs, add the missing relation points to the extraction list and continue. Step 5. Add any additional files and directories from the dump tape to the extraction list. File names are entered on a single line or one at a time. List the files and directories and verify that all files to be extracted from tape are starred (*).
Administrative Tasks If the fsaudit command fails with a message that indicates a relation parent unknown, the relation point parents are not on the dump tape. This situation occurs if: • All files are not recovered from the dump tape (bad dump tape). • Dump is not made after a DataClass relation is added to a directory. Use the UNIX mkdir command to create the parent and rerun the fsaudit -r -f command. If the procedure fails, call technical support. Step 9.
Administrative Tasks Step 12. To rebuild the candidate lists, run the following: % fspolicy -s -y -w % fspolicy -t -y -w Audit Database The fsaudit command serves two purposes: • Recovery of file systems. • Database maintenance compares UNIX file system information and FileServ database information. The fsaudit command for database maintenance does not use the fs_dump.file.
Administrative Tasks Database Maintenance Running fsaudit Command The FileServ database contains UNIX file system information to track the following: • Migration file systems. • Media where files are stored. • Association points in the UNIX file system. • Files in directories that are related to DataClass groups. FileServ and database software must be online and running for execution of fsaudit.
Administrative Tasks When using the fsaudit -r command, all parent directories of relation points must be present in the fs_dump.file. If a parent directory does not exist for a relation point in the fs_dump.file, the fsaudit command fails.
Administrative Tasks Troubleshoot System Performance If the DataClass mintime parameter for the DataClass groups and cron setting that govern the frequency of the migration policy application for a DataClass group are set to too short a time, FileServ may be invoked too frequently. This is known as thrashing because the policy is applied so frequently that it prevents other system operations that have lower priority.
Administrative Tasks Reports The table below lists the reports generated by FileServ: Report DataClass Report Page DataClass Report 4-21 Media Fragmentation Report 4-22 Media Movement Report 4-23 Resource Queue Report 4-24 History Report 4-25 Component Statistics Report 4-26 Hardware Configuration Report 4-27 To view the parameter settings for each DataClass identifier, follow the steps below: Step 1. Run the fsclassinfo command.
Administrative Tasks Account Number: Drive Pool: Default Copies: 12345 Media Cleanup: fspool File Clustering: 1 Mintime (min): CLASS n 10 Associated Directories: /data/joe/prod001 /data/june/prod002 FS0000 31 174105 fsclassinfo completed: Command Successful. Media Fragmentation Report To view a list of media suspected as fragmented, follow the steps below: Step 1. Run the fsmedcopy command.
Administrative Tasks In the example for media 000005, the amount of wasted space is 92.46 percent, which represents. 81.36 percent of the total space. Media Movement Report To view a report showing media that has been removed or added to the storage system, follow the steps below: Step 1. Run the fsmoverpt command to generate a report that lists the movement of all media. Use other appropriate options as needed. For command information, refer to the Command Reference book. Step 2.
Administrative Tasks Resource Queue Report To view a snapshot of FileServ requests waiting for resources, follow the steps below: Step 1.
Administrative Tasks Step 2. History Report Use other appropriate options as needed. For command information, refer to the Command Reference book. To view a history of media and components, follow the steps below: Step 1. Run the fshistrpt command with the -m mediaID option for a media history report.
Administrative Tasks Step 2. Or, run the fshistrpt command with the -h option for a component history report.
Administrative Tasks An example of the output is shown below: % fschstate --------------------------------------------------------------------Component Status Report Thu Jan 21 17:27:52 1999 Component Alias Drive ID State Status Media ID AMLJ_CTIII_DRO 101 ON FREE NONE AMLJ_CTIII_DR1 102 ON FREE NONE VolSub N/A ON N/A N/A The FileServ system is active. FS0000 07 1464244 fschstate completed: Command Successful. * Drives not configured in FileServ.
Administrative Tasks An example of the output is shown below: % fsconfig -------------------------------------------------------------------Hardware Configuration Report Component ID: V0,10 Thur Feb 4 16:41:41 1999 Device pathname: user Alias: Component Type: Drive Type: Drive ID: Delay Time: /dev/er90/s0 ER90_DR1 DRIVE ER90 10 0 Hardware Configuration Report Component ID: V0, 11 Thur Feb 4 16:41:41 1999 Device pathname: User Alias: Component Type: Drive Type: Drive ID: Delay Time: /dev/er90/s1 ER90
Administrative Tasks Contact Technical Support Before contacting technical support, follow the steps below: Step 1. Obtain the following information: • FileServ Serial Number: _________________ • Host ID: ____________________ Step 2. Contact technical support and be prepared to supply the above information to them. Technical support can be reached as follows: • 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. • techsup@adic.
Administrative Tasks NOTES 4-30 Trouble- shooting Tools 600716 Rev A
Index A add relation dump file . . . . . . . . . . . . . . . . . . 2-15 adobe acrobat reader . . . . . . . . . . . . . P-5 AML archive add drives . . . . . . . . . . . . . . 1-27, 1-55 delete drives . . . . . . . . . . . . . . . . 1-55 ATAC. . . . . . . . . . . . . . . . . . . . 1-22, 4-29 autostart amass . . . . . . . . . . . . . . . . . . . . . . 3-4 fileserv . . . . . . . . . . . . . . . . . . . . . 3-4 scripts . . . . . . . . . . . . . . . . . . . . . . 3-3 B blank media add . . . . . . . . . . . . . .
Administrative Tasks D data migration . . . . . . . . . . . . . . . . . . 2-30 physical security . . . . . . . . . . . . . 2-4 restore. . . . . . . . . . . . . . . . . . . . . 4-11 retrieve . . . . . . . . . . . . . . . . . . . . 2-40 database maintenance . . . . . . . . . . . . . . . . 1-10 maintenance scripts . . . . . . . . . . 1-42 recovery . . . . . . . . . . . . . . . . . . . 1-19 table utilities. . . . . . . . . . . . . . . . 1-14 dataclass group add . . . . . . . . . . . . . . . . . . .
Administrative Tasks fs_sysparm . . . . . . . . . . . . . . . . . 2-66 log file maintenance . . . . . . . . . . . . . . . . . 4-6 newfslog. . . . . . . . . . . . . . . . . . . . 4-6 M management dataclass . . . . . . . . . . . . . . . . . . . . 2-2 dataclass groups . . . . . . . . . . . . . . 2-2 media . . . . . . . . . . . . . . . . . . . . . . . . . 1-4 3480 tape cartridges . . . . . . . . . . 1-38 blank. . . . . . . . . . . . . . . . . . . . . . 2-59 file lists. . . . . . . . . . . . . . . . . . . .
Administrative Tasks R reader adobe acrobat . . . . . . . . . . . . . . . . P-5 recovery processing startup and shutdown . . . . . . . . . 1-23 relation add . . . . . . . . . . . . . . . . . . . . . . . 2-10 change points . . . . . . . . . . . . . . . 2-17 manipulation . . . . . . . . . . . . . . . 2-10 remove . . . . . . . . . . . . . . . . . . . . 2-16 remote login . . . . . . . . . . . . . . . . . . . . 1-3 report media fragmentation . . . . . . . . . 4-22 media list . . . . . . . . . . . . . . . . . .
Administrative Tasks CONNECT_RETRIES . . . . . . . 1-32 CONNECT_SLEEP_TIME . . . . 1-32 DEF_FILE_RETENTION_PERIOD. 1-40 DEF_MED_SPC_3480 . . . . . . . 1-30 DEF_MED_SPC_CTIII. . . . . . . 1-30 DEF_MED_SPC_CTIV. . . . . . . 1-30 DEF_MED_SPC_D2LG . . . . . . 1-30 DEF_MED_SPC_D2MD. . . . . . 1-30 DEF_MED_SPC_D2SM . . . . . . 1-30 DEFAULT_MEDIA_TYPE . . . 1-30 DMON_POLL_TIME . . . . . . . . 1-33 File Copy Block Factors . . . . . . 1-35 FILE_LBL_FMT_3590 . . . . . . . 1-29 FILE_LBL_FMT_DLT . . . . . . .
Administrative Tasks PERCENT_FULL_TO_MIGRATE . 1-35 STARVATION_PERCENT . . . 1-34 STORE_LIMIT_NOTICE . . . . . 1-31 TSC_LOG_MASK . . . . . . . . . . 1-44 USER_ID . . . . . . . . . . . . . . . . . . 1-37 VS_DEF_QUANTITY . . . . . . . 1-41 VS_DEFAULT_DRIVEPOOL . . 1-4, 1-41 VS_DIR . . . . . . . . . . . . . . . . . . . 1-41 VS_HOSTNAME . . . . . . . . . . . 1-40 VS_PROGRAM_NUMBER . . . 1-41 V VolServ . . . . . . . . . . . . . . . . . . . . . . . 1-40 X xfsrestore . . . . . . . . . . . . . . . . . . . . . .
