HP StorageWorks File System Extender 3.
CONTENTS 1 Contents 1 FSE command index 1 2 FSE command documentation 2 1 FSE command index 1.1 List of FSE commands FSE command-line interface includes the following commands: fse 2 fsebackup 11 fsebak 17 fsecheck 22 fsedrive 26 fsefile 32 fsejob 41 fselibrary 47 fsemedium 54 fsepartition 66 fsepool 77 fserecover 84 fserestore 88 File System Extender 3.
2 FSE command documentation fsesystem 2 2.1 2 91 FSE command documentation NAME fse – Initiate or terminate the FSE server or FSE client operation. Show current status of the FSE daemons. Prepare FSE system for the restore process. Configure mount points for HSM file systems (on Windows systems only). Enable or disable Limited Access Mode for a particular HSM file system (on Windows systems only). 2.1.
2.
2.1 NAME 4 • Service (S+C), • Resource Manager (S), • Management Interface (S), • File System Event Manager∗ (C). ∗ ... there is one File System Event Manager running on each FSE client host. It controls an arbitrary number of HSM file systems that reside on the same FSE client host. Configuration–dependent FSE processes: • Partition Manager (S), • Back End Agent (S), • Library Agent (S). fse status prints info on the configuration–independent FSE processes only.
2.1 NAME 5 • post_start.sh (on Linux systems) or post_start.cmd (on Windows systems) ... this is the post–start helper script. It is executed after all FSE processes have been started up and all existing FSE file systems with an entry in the /etc/fstab file (on Linux systems) or all existing FSE file systems with a defined mount point (on Windows systems) have been mounted, i.e. right after the FSE system is put into its fully operational state; • pre_stop.sh (on Linux systems) or pre_stop.
2.1 NAME 6 4. executes the post–start script, if it exists (see POST–START AND PRE–STOP SCRIPTS for details on the post–start script). If used on FSE server in a distributed FSE system, it: 1. initiates omniNames – the omniORB naming service daemon, if it is not running yet, 2. initiates the FSE server operation starting up all FSE server processes (see FSE PROCESSES for details on FSE server processes), 3. executes the post–start script, if it exists.
2.1 NAME 7 If used on FSE client in a distributed FSE system, it: 1. executes the pre–stop script, if it exists, 2. unmounts all mounted HSM file systems (on Linux systems), 3. terminates the FSE client operation shutting down all running FSE client processes (see FSE PROCESSES for details on FSE client processes). • – –restart This option has the same effect as a consecutive invocation of the fse stop and fse start commands.
2.1 NAME 8 • – –umount Linux systems: The command fse – –mount | – –umount should not be used by the FSE administrator directly. It is called by fse–svc daemon during recovery of FSE file system. Windows systems: Use the command fse – –mount | – –umount with great care. It should be used instead of mountvol command if you want to administrate an FSE partition (for example to enable or disable it).
2.1 NAME 9 point, FSE–HSM continues to run for the HSM file system and online files are still migrated and released. Recalls of offline files are denied. When an offline file is accessed while the HSM file system operates in Limited Access Mode, the application that is accessing the file receives an error and the file is not recalled. For more information on Limited Access Mode, refer to File System Extender User146s Guide.
2.1 NAME 2.1.5 FILES On Linux systems: • /opt/fse/sbin/post_start.sh The post–start helper script. • /opt/fse/sbin/pre_stop.sh The pre–stop helper script. On Windows systems: • %InstallPath%\bin\post_start.cmd The post–start helper script. • %InstallPath%\bin\pre_stop.cmd The pre–stop helper script. 2.1.6 COPYRIGHT Copyright (C) 2004-2005 Hewlett-Packard Copyright (C) 2002-2005 GRAU Data Storage 2.1.7 SEE ALSO fsesystem(8), fsepartition(8), fserestore(8), fseintro(7). File System Extender 3.
2.2 NAME 2.2 11 NAME fsebackup – Back up FSE system state to the backup media. 2.2.1 SYNOPSIS fsebackup {–m | – –media} Barcode... [{–c | – –client} [Client...]] [– –skip– hsmfs] [{–l | – –log–file} LogFileName] fsebackup {–h | – –help} 2.2.2 DESCRIPTION Backup of the FSE system is performed in such a way that it preserves a consistent state of information stored in FSE databases, FSE system files and user data on HSM file systems.
2.2 NAME 12 PREREQUISITES FSE backup uses logical volume snapshot technology to keep FSE system’s operation almost unobstructed during the backup window. To be able for the FSE backup to use this technology, HSM file systems, FSE configuration and all FSE databases and system files have to reside on LVM logical volumes (on Linux systems) or special snapshot software needs to be installed (on Windows systems). This is an essential prerequisite.
2.2 NAME 13 global configuration (backup, trace and CORBA/omniORB configuration files). Offline files on HSM file system are backed up as sparse files. These files practically do not occupy any space on backup medium. FSE backup usually runs in background, started automatically by cron or similar utilities. A special lock file backup.pid is used to prevent starting multiple backup processes in parallel. ACTIVITY LOGGING FSE administrator usually consults the fse.
2.2 NAME 14 Perform backup of the FSE server. Record the backup image data on one or more FSE media with barcode(s) Barcode.... • Barcode... A sequence of barcodes of the FSE media which are used to store backup image data. The media barcodes have to be separated by spaces. • –c, – –client Perform a backup of FSE clients or if specific client hostname is specified by the Client... argument just specific client. This option may only be used together with the – –media option. • Client...
2.2 NAME 2.2.4 15 EXAMPLES • Backup current FSE server state to FSE media with barcodes 000123, 000124 and 000125: fsebackup – –media 000123 000124 000125 • Backup current FSE server state and all FSE clients to FSE media with barcodes 000123, 000124 and 000125: fsebackup – –media 000123 000124 000125 – –client • Backup current FSE server state to FSE medium with barcode 000202. Write additional backup log to file /tmp/backup_000202.log: fsebackup – –media 000202 –l /tmp/backup_000202.
2.2 NAME • /var/opt/fse/lock/backup.pid (on Linux systems), %InstallPath%\var\lock\backup.pid (on Windows systems) FSE backup lock file. 2.2.6 COPYRIGHT Copyright (C) 2004-2005 Hewlett-Packard Copyright (C) 2002-2005 GRAU Data Storage 2.2.7 SEE ALSO fserestore(8), fsebak(8), fserecover(8), fseintro(7). File System Extender 3.
2.3 2.3 NAME 17 NAME fsebak – Achieve a consistent state of all HSMDBs and FSCs to allow an eventual back–up creation. 2.3.1 SYNOPSIS fsebak – –suspend fsebak – –continue StatusCode fsebak – –reserve–medium Barcode fsebak – –change–medium Barcode JobIOR fsebak – –complete–job JobIOR fsebak {–h | – –help} fsebak {–v | – –version} 2.3.2 DESCRIPTION COMMON USAGE fsebak command affects the core FSE components.
2.3 NAME 18 Interface must be running. If the connection to the Management Interface fails, check its status by running the fse status command. In case the Management Interface is not running, start it with the fse start command. Additionally, the Partition Manager processes (fse–pm) for all configured FSE partitions must be running. This can be checked with the fsesystem command.
2.3 NAME 19 If the FSE administrator made sure that the HSMDB and FSC back–ups are stored on a safe medium, (s)he is advised to use value 0 (zero) in place of the StatusCode argument. This value means that all old transaction log files of HSMDBs and FSCs will be removed, as they are not needed any more. If any other value is used as the StatusCode, these transaction logs will be preserved and optionally used again, if needed. 2.3.3 OPTIONS • – –suspend Prepare each HSMDB and FSC for backing up.
2.3 NAME 20 Allocate a new FSE medium to store the back–up archive. Usage of this option causes the job with the interoperable object reference JobIOR to unload the currently allocated FSE medium from the FSE drive, release it, allocate the FSE medium with the specified barcode Barcode from an FSE backup media pool and load it into the same FSE drive. Usage of this option is necessary if the previously reserved medium has not enough free space to store the whole back–up archive.
2.3 NAME 21 • Create an administrative job. Allocate the FSE medium with the barcode backup–003 for a back–up procedure and load it into an FSE drive: fsebak – –reserve–medium backup–003 • Release the currently allocated FSE medium for administrative job with the interoperable object reference IOR:010000000e00... (160–byte text string), unload it, allocate the new FSE medium with the barcode backup–105 and load it into the same FSE drive: fsebak – –change–medium backup–105 IOR:010000000e00...
2.4 NAME 2.4 22 NAME fsecheck – Perform a File System Catalog consistency check against the HSM file system or FSE media. 2.4.1 SYNOPSIS fsecheck {–i | – –fsc–hsmfs} PartitionName fsecheck {–m | – –fsc–media} [– –autocorrect [– –match–media]] PartitionName fsecheck {–h | – –help} fsecheck {–v | – –version} 2.4.2 DESCRIPTION Each FSE command communicates with the FSE system components through the Management Interface (fse–mif). To execute an FSE command, the Management Interface must be running.
2.4 NAME 23 • it is uncertain for some recently created files on the HSM file system, if they are missing from File System Catalog or are too new to have their file ID recorded in File System Catalog yet. fsecheck reports the consistency check findings to the shell output. These findings are also recorded in the FSE check log (see section FILES). Note: The maintenance job for the consistency check of the File System Catalog against HSM file system keeps track of its progress.
2.4 NAME 24 • – –autocorrect Automatically correct errors discovered by the consistency check of File System Catalog against corresponding FSE media. See CHECKING FILE SYSTEM CATALOG CONSISTENCY for details on this process. This option may only be used together with the – –fsc–media option. • – –match–media Correct the errors by removing the entries that have been found only in the File System Catalog and not in the Fast Recovery Information blocks on the FSE media.
2.4 NAME 2.4.5 25 FILES • /var/opt/fse/log/check_hsmfs_fsc_ (on Linux systems), %InstallPath%\var\log\check_hsmfs_fsc_ dows systems) (on Win- Log file with recorded findings of the consistency check of the File System Catalog against the HSM file system. • /var/opt/fse/log/check_media_fsc_.
2.5 NAME 2.5 26 NAME fsedrive – Manage configuration of the FSE drives. 2.5.1 SYNOPSIS fsedrive {–a | – –add} ConfigFileName fsedrive {–r | – –remove} Name [–F | – –force] fsedrive {–s | – –show} Name [RevisionNumber | {–H | – –history}] fsedrive {–m | – –modify} Name ConfigFileName fsedrive {–l | – –list} [–D | – –detail] fsedrive – –disable Name [–F | – –force] fsedrive – –enable Name fsedrive {–h | – –help} fsedrive {–v | – –version} 2.5.
2.5 NAME 27 check its status by running the fse status command. In case the Management Interface is not running, start it with the fse start command. After a successful command execution fsedrive notifies the FSE administrator with a suitable message, which is printed to the standard output stream (stdout). If there was an error during the command execution, an appropriate error message is printed to the standard error stream (stderr). 2.5.
2.5 NAME 28 • –s, – –show If the RevisionNumber argument is given, print the appropriate configuration revision for the FSE drive Name, otherwise print the configuration revision in–use. • RevisionNumber A non–negative integer value which represents the configuration revision to print. • –H, – –history Print configuration history depth for the FSE drive Name. Configuration history depth is the number of the configuration file revisions which are stored in Configuration Database for this FSE drive.
2.5 NAME 29 • –D, – –detail Retrieve additional FSE drive information and display the retrieved data in the ParameterName: ParameterValue format with each parameter in its own line. The following additional information is reported: 1. VendorID ... ID string of the drive manufacturer, 2. ProductID ... ID string of the drive model, 3. SerialNo ... serial number of the drive, 4. FirmwareRev ... revision of the firmware the drive currently uses, 5. ScsiID ... ID string of the corresponding SCSI device, 6.
2.5 NAME 2.5.4 30 EXAMPLES • Configure a new FSE drive from the configuration file standalone_drive.fse: fsedrive – –add standalone_drive.
2.5 NAME • Enable the currently disabled FSE drive named extra_drive: fsedrive – –enable extra_drive 2.5.5 FILES • /opt/fse/newconfig/fse–drive.cfg (on Linux systems), %InstallPath%\newconfig\fse–drive.cfg (on Windows systems) Template for an FSE drive configuration file. 2.5.6 COPYRIGHT Copyright (C) 2004-2005 Hewlett-Packard Copyright (C) 2002-2005 GRAU Data Storage 2.5.7 SEE ALSO fse(8), fselibrary(8), fsemedium(8), fsepool(8), fseintro(7). File System Extender 3.
2.6 NAME 2.6 32 NAME fsefile – Manage files on an HSM file system. Recall older file generations from FSE media. Add files to migration candidate list. Release files from HSM file system. Trigger migration on an FSE partition. Trigger deletion of files from an HSM file system. 2.6.1 SYNOPSIS fsefile {–l | – –list} FileName... [–D | – –detail] fsefile {–H | – –history} {FileName... [–D | – –detail] | – –id PartitionName FileID... [–D | – –detail]} fsefile {–R | – –recall} {FileName...
2.
2.6 NAME 34 Note: The job will continue to run and will write progress to fse.log file. 2.6.3 OPTIONS • –l, – –list Show file ID, current status (dirty, online, offline) and file name of each file specified by FileName.... • FileName... A sequence of file names for files the particular operation is executed on. File names have to be separated by spaces. All files must be located on the same HSM file system (except if used with option – –list).
2.6 NAME 35 Use the PartitionName FileID... argument combination for file identification instead of the FileName... argument. This option may only be used together with the – –history or – – recall option. • PartitionName Name of the FSE partition with files that are being managed or migration job is triggered on. • FileID... A sequence of file IDs for files the particular operation is executed on. File IDs have to be separated by spaces. All files must be located on the same HSM file system.
2.6 NAME 36 Note: Latest migrated generation may only be recalled with the FileName... argument, when file still exists. This limitation results in obligatory usage of the – –into option if the file to be recalled is specified with the – –id PartitionName FileID... argument combination. IMPORTANT: If a non–latest generation of a file is recalled using the – – into option, the two security precautions are: 1. owner and group ownership of the recalled file are both set to root; 2.
2.6 NAME 37 Note: It is required for recall of an older file generation. • Path Absolute path pointing to a directory on a non–HSM file system, where the recalled file generation is saved. • –M, – –migrate Put files specified by the FileName... argument on the corresponding migration candidate list. If certain specified file is offline, it will be recalled first.
2.6 NAME 38 • –D, – –trigger–deletion Trigger deletion of files on an HSM file system, which correspond to the deletion policy defined for the belonging FSE partition. The deletion policy consists of a sequence of FileExpiration – Path parameter pairs that are specified in the FSE partition configuration file.
2.6 NAME 39 • List file IDs of file updateMe.gz in directory /mnt/fse_vg/fse1 and file archive.gz in current directory: fsefile –l /mnt/fse_vg/fse1/updateMe.gz archive.gz • Show history information for files with file ID 21544 and 21560 on an FSE partition named partition_02: fsefile –H – –id partition_02 21544 21560 • Recall latest migrated generation of file fsepkg_1.1.68.tar.gz into the current directory on an HSM file system: fsefile – –recall fsepkg_1.1.68.tar.gz • Recall file fsepkg_1.1.55.tar.
2.
2.7 NAME 2.7 41 NAME fsejob – Monitor execution of running FSE Jobs. Show status of running FSE Jobs. 2.7.1 SYNOPSIS fsejob {–l | – –list} [–M | – –migration] [–R | – –recall] [–A | – –admin] [–C | – –recovery] [–T | – –maint] [PartitionName] [–D | – –detail] fsejob {–t | – –status} JobID fsejob {–a | – –abort} JobID... fsejob {–p | – –priority} JobID {Number | {–I | – –incr} Number | {–D | – – decr} Number} fsejob {–h | – –help} fsejob {–v | – –version} 2.7.
2.7 NAME 42 jobs are monitored. This can be checked with the fsesystem and fsepartition commands. After successful command execution fsejob notifies the FSE administrator with a suitable message, which is printed to the standard output stream (stdout). If there was an error during the command execution, an appropriate error message is printed to the standard error stream (stderr). JOB LIST INFORMATION Job information that is displayed using the – –list option is the following: 1. JobID ...
2.7 NAME 43 3. Drive ... name of the allocated FSE drive that will be used for writing (this copy), 4. Medium ... barcode of the allocated FSE medium (that will store this copy), 5. Volume ... current medium volume that is being written to, 6. Status ... descriptive current status of a job (copy). Note: The "Copy" value is relevant only with migration jobs, but not with all other job types. With multi–copy migration jobs, such status line is printed for each copy that is migrating. 2.7.
2.7 NAME 44 • PartitionName List FSE jobs running on the specified FSE partition only. • –D, – –detail Display the retrieved data in the ParameterName: ParameterValue format with each parameter in its own line. This option may only be used together with the – –list option. • –t, – –status Show status information for the FSE job with the specified identification number JobID. See JOB STATUS INFORMATION for details on the status information that is printed with the help of this option.
2.7 NAME 45 • –D, – –decr Decrease current priority of the FSE job with specified identification number JobID by value Number. • –h, – –help Print the usage information for this FSE command. • –v, – –version Print the copyright and version information for this FSE command. 2.7.
2.7 2.7.5 NAME COPYRIGHT Copyright (C) 2004-2005 Hewlett-Packard Copyright (C) 2002-2005 GRAU Data Storage 2.7.6 SEE ALSO fsesystem(8), fsepartition(8), fsefile(8), fseintro(7). File System Extender 3.
2.8 NAME 2.8 47 NAME fselibrary – Manage configuration of the FSE libraries. 2.8.
2.8 NAME 48 • update Resource Management Database with current status of the drives and media in the operating FSE library, • disable or enable operation of an FSE library. Each FSE command communicates with the FSE system components through the Management Interface (fse–mif). To execute an FSE command, the Management Interface must be running. If the connection to the Management Interface fails, check its status by running the fse status command.
2.8 NAME 49 • Name The name of the FSE library to manage configuration for. • –F, – –force Set forced mode for FSE library remove or disable operation. In this mode, FSE administrator’s confirmation of FSE library removal or disabling is skipped. The command treats it as if FSE administrator would have answered the confirmation question with "Yes". This option may only be used together with the – –remove or – –disable option.
2.8 NAME 50 2. Family ... library family (AIT, LTO), 3. Type ... library type, 4. Host ... fully–qualified domain name (FQDN) of the host the library is attached to, 5. CtrlDev ... library control device file, 6. Status ... current library status (online, disabled). • –D, – –detail Retrieve additional FSE library information and display the retrieved data in the ParameterName: ParameterValue format with each parameter in its own line. The following additional information is reported: 1. ProductID ...
2.8 NAME 51 Status information for an FSE slot includes: 1. Name ... slot index that corresponds to physical position of the slot inside the library, 2. Type ... slot type (repository, import/export, cleaning), 3. Status ... current slot status (full, reserved, free), 4. Medium ... barcode of the medium that is present in the slot. ( string is displayed if the slot is free).
2.8 NAME 52 • –v, –version Print the copyright and version information for this FSE command. 2.8.4 EXAMPLES • Configure a new FSE library from the configuration file main_library.fse: fselibrary –a main_library.
2.8 NAME 53 • Show the inventory of the FSE library named lib_email: fselibrary –i lib_email • Trigger an inventory update on the FSE library named lib_builds: fselibrary –u lib_builds • Trigger an inventory update on the FSE Library named lib_email.
2.9 2.9 NAME 54 NAME fsemedium – Manage configuration of the FSE media. Format and initialize FSE media. Perform maintenance tasks on the FSE media. 2.9.1 SYNOPSIS fsemedium {–a | – –add} Barcode [{–O | – –pool} PoolName] fsemedium {–r | – –remove} Barcode [–F | – –force] fsemedium {–l | – –list} [Barcode] [–V | – –volume] [–D | – –detail] fsemedium {–f | – –format} Barcode [–F | – –force] [–i | – –init] [– –no– monitor] fsemedium {–i | – –init} Barcode [{–V | – –volume} VolumeNumber...
2.9 NAME 2.9.2 55 DESCRIPTION This FSE command manages a single FSE medium.
2.9 NAME 56 JOB PROGRESS MONITORING fsemedium is able to receive messages from Management Interface to give the user ability to monitor the progress of the command. Monitoring is enabled by default and can be disabled by using the – –no–monitor option. When monitoring is enabled, fsemedium command reports events and other relevant information from the FSE processes as long as the job that fsemedium has started is running. After the job terminates, the command exits.
2.9 NAME 57 • PoolName The name of the FSE media pool to add new medium to. • –r, – –remove Remove an existing FSE medium from the FSE system. This is possible if all FSE medium volumes on the medium are empty. Note that unless additional option – –force is specified, the command demands FSE administrator’s confirmation before performing this operation.
2.9 NAME 58 4. medium volume size, 5. current amount of volume free space, 6. percentage of currently occupied volume space, 7. current medium volume status (empty, open, full, recovery, scanned, in reorg, recycled, error).
2.9 NAME 59 – BlockSize ... block size used on FSE medium volumes on the medium, – SysVolSize ... size of the system volume of the medium (if it exists), – CurVol ... consecutive number of the medium volume on which the medium tape is currently positioned, – Key ... internal RMDB key value assigned to the medium. If this option is used with the – –list and – –volume options, the following additional information is reported: – UUID ... universal unique identified of the medium volume, – AccessNum ...
2.9 NAME 60 if additional option – –force is given. Backup media in backup media pool should be formatted, but not initialized. • –F, – –force Set forced mode for FSE medium remove, format, initialize, mark unreliable, mark unusable or mark good operation. There are three kinds of usage of this option in combination with other options.
2.9 NAME 61 • VolumeNumber... A non–negative integer value or a sequence of such values which represent(s) the position(s) of FSE medium volume(s) on the medium layout. • – –mark–unreliable Disallow writing to the FSE medium with barcode Barcode. From that moment on, the data on the medium can only be read. This is done by setting the status of this medium in the Resource Management Database to UNRELIABLE.
2.9 NAME 62 Note: A full FSE medium volume is not used for writing any more. Marking an FSE medium volume as full is useful in situations, when, due to problems with certain medium volume, status of a whole FSE medium is set to unreliable. The medium remains unused although other medium volumes are error–free. In such cases the unreliable medium volume is marked as full and its medium as good to make other medium volumes available to the FSE system again.
2.9 NAME 63 • – –copy–contents Recreate a redundant copy of the unreadable data that is located on a damaged medium. The copy is recreated from the corresponding data in another FSE media pool assigned to the same FSE partition, if it exists. The recreated data is created on the open or empty medium volumes in the FSE media pool to which the damaged medium is assigned.
2.
2.
2.10 2.10 NAME 66 NAME fsepool – Manage configuration of the FSE partitions. 2.10.
2.10 NAME 67 • disable or enable an FSE partition, • scan FSE media that belong to an FSE partition for obsolete data, • display the reorganizational scan statistics for the FSE media that belong to an FSE partition. Each FSE command communicates with the FSE system components through the Management Interface (fse–mif). To execute an FSE command, the Management Interface must be running. If the connection to the Management Interface fails, check its status by running the fse status command.
2.10 NAME 68 2. current partition status (disabled, stopped, running, mounted, unknown), 3. fully–qualified domain name (FQDN) of the machine that hosts the partition, 4. mount point of the HSM file system that belongs to the partition, 5. number of currently running migration jobs on the partition, 6. number of currently running recall jobs on the partition, 7. number of currently running maintenance jobs on the partition, 8. number of currently running recovery jobs on the partition.
2.10 NAME 69 Partition states have the following meaning: ----------------------------------------------------------------------------| STATUS | HSM FILE SYSTEM | PARTITION | PART.
2.10 NAME 70 – all configuration file revisions of this FSE partition from Configuration Database. – FSC and HSMDB database files – media volume information from the RMDB Note: Unless additional option – –force is specified, the command demands FSE administrator’s confirmation before performing this operation. Default answer to the confirmation question is "No".
2.10 NAME 71 stored in Configuration Database for this FSE partition. This option may only be used together with the – –show option. • –m, – –modify Modify the configuration of FSE partition Name with the configuration file ConfigFileName. This action validates the new configuration file, copies it to Configuration Database as a new configuration revision and triggers the FSE partition reconfiguration. During reconfiguration its Partition Manager remains running and operational.
2.10 NAME 72 • –t, – –status Show status of the FSE partition Name. See PARTITION STATUS INFORMATION for details on the status information that is displayed with this option. • – –disable Disable operation of FSE partition Name. Note that unless additional option – –force is specified, the command demands FSE administrator’s confirmation before performing this operation. Default answer to the confirmation question is "No". • – –enable Enable operation of FSE partition Name, which is currently disabled.
2.10 NAME 73 • – –reorg–stat Display the statistics gathered by the reorganizational scan job that was run on the FSE partition Name. The reported values / statistics are displayed for each belonging FSE medium, and are the following: 1. Barcode ... FSE medium barcode, 2. VolNum ... number of FSE medium volumes on the medium, 3. ValidData ... amount of important (non–obsolete) data stored on the medium (in MB), 4. Total ... total amount of data stored on the medium (in MB), 5. SlackSpace ...
2.
2.
2.10 NAME 76 %InstallPath%\newconfig\fse–partiton–NEVER–RELEASE.cfg (on Windows systems) Template for an FSE partition configuration file, with the parameters preset so that releases do not occur on the FSE partition until the free storage space on the partition is exhausted. 2.10.6 COPYRIGHT Copyright (C) 2004-2005 Hewlett-Packard Copyright (C) 2002-2005 GRAU Data Storage 2.10.7 SEE ALSO fse(8), fsepool(8), fsemedium(8), fsesystem(8), fsejob(8), fserecover(8), fseintro(7). File System Extender 3.
2.11 2.11 NAME 77 NAME fsepool – Manage configuration of the FSE media pools. 2.11.1 SYNOPSIS fsepool {–a | – –add} ConfigFileName fsepool {–r | – –remove} Name [–F | – –force] fsepool {–s | – –show} Name [RevisionNumber | {–H | – –history}] fsepool {–m | – –modify} Name ConfigFileName fsepool {–l | – –list} [–D | – –detail] fsepool – –reorg–stat fsepool {–h | – –help} fsepool {–v | – –version} 2.11.2 DESCRIPTION This FSE command manages configuration of the FSE media pools.
2.11 NAME 78 check its status by running the fse status command. In case the Management Interface is not running, start it with the fse start command. After a successful command execution fsepool notifies the FSE administrator with a suitable message, which is printed to the standard output stream (stdout). If there was an error during the command execution, an appropriate error message is printed to the standard error stream (stderr).
2.11 NAME 79 Configure a new FSE media pool with parameters, written in the configuration file ConfigFileName. This action checks the validity of the configuration file, copies the file to Configuration Database and inserts the parameter values into Resource Management Database. FSE media pool names are unique within the FSE installation. • ConfigFileName The name of the FSE media pool configuration file to use. • –r, – –remove Remove an existing FSE media pool from the FSE system.
2.11 NAME 80 are stored in Configuration Database for this FSE media pool. This option may only be used together with the – –show option. • –m, – –modify Modify the configuration of FSE media pool Name with the configuration file ConfigFileName. This action checks the validity of the new configuration file, copies it to Configuration Database as a new configuration revision and triggers the FSE media pool reconfiguration.
2.11 NAME 81 This option may only be used together with the – –list option. • – –reorg–stat Display the statistics gathered by the reorganizational scan job that was run on the FSE partition to which the FSE media pool belongs. The reported values / statistics are the following: 1. Name ... media pool name, 2. NumOfMedia ... number of FSE media that belong to the media pool, 3. ValidData ... amount of important (non–obsolete) data stored on the media of the media pool (in MB), 4. Total ...
2.11 NAME 82 • Remove the configured FSE media pool named system_backup_pool; skip confirmation: fsepool – –remove system_backup_pool –F • Show the current configuration of the FSE media pool named backup_pool: fsepool –s backup_pool • Show the configuration history depth for the FSE media pool named proj_archive_pool: fsepool – –show proj_archive_pool –H • Copy configuration revision 5 of the FSE media pool named mail_archive_pool to a file mail_archive_pool_cfg_5.
2.11 NAME 83 • /opt/fse/newconfig/fse–pool–LTO.cfg (on Linux systems), %InstallPath%\newconfig\fse–pool–LTO.cfg (on Windows systems) Template for a configuration file for an FSE media pool with LTO media. • /opt/fse/newconfig/fse–pool–DISK.cfg (on Linux systems), %InstallPath%\newconfig\fse–pool–DISK.cfg (on Windows systems) Template for a configuration file for an FSE disk media pool. 2.11.6 COPYRIGHT Copyright (C) 2004-2005 Hewlett-Packard Copyright (C) 2002-2005 GRAU Data Storage 2.11.
2.12 2.12 NAME 84 NAME fserecover – Recover a File System Catalog from its redundant duplicate data sources. Recover an HSM file system from existing Name Space Catalog. 2.12.1 SYNOPSIS fserecover {–f | – –fsc} PartitionName fserecover {–i | – –hsmfs} PartitionName fserecover {–h | – –help} fserecover {–v | – –version} 2.12.2 DESCRIPTION fserecover is used for regenerating: • a File System Catalog (FSC) for the specified FSE partition in situations when it is inconsistent, damaged or missing.
2.12 NAME 85 3. at the end of each data volume on FSE media (slow method). If FRI is missing and none of the above methods can be used, the procedure reverts to recovering from migrated metadata (the slowest method). If even this method fails, the recovery process is stopped and an appropriate error is written to FSE error.log. Recovery uses all available FSE drives for accessing multiple volumes at the same time in order to speed up the recovery operation.
2.12 NAME 86 fileID 1. When the recovery is need from the scratch then that file has to be deleted. At the end of successful recovery operation this file will be deleted. Recovery will be done to native FS (Ext3 on Linux systems, NTFS on Windows systems). File state after recovery: 1. After the recovery of HSM FS I–node information will be inconsistent with old data in FSC and FRI. I–nodes of the files are not the same as before recovery. 2.
2.12 NAME 2.12.3 87 OPTIONS • –f, – –fsc Start recovery of the File System Catalog for FSE partition PartitionName. See FSC RECOVERY PROCEDURE for details of this process. • PartitionName The name of the FSE partition to trigger recovery of either File System Catalog or HSM file system. • –i, – –hsmfs Start recovery of the HSM file system for FSE partition PartitionName. See HSM FS RECOVERY PROCEDURE for details of this process. • –h, – –help Print the usage information for this FSE command.
2.13 2.13 NAME 88 NAME fserestore – Restore a complete FSE system state from the backup image data written on FSE backup media. 2.13.1 SYNOPSIS fserestore fserestore {–h | – –help} 2.13.2 DESCRIPTION fserestore is designed for restoration of an FSE system state.
2.13 NAME 89 1. FSE system is properly installed and configured. Refer to the FSE Installation Guide for details. 2. If the FSE system restore is to be performed on a Linux system, tar (tape archiving package) is installed on the system. 3. FSE is in the restore mode (using the commands fse – –stop and fse – – startrestore on the FSE server and FSE client systems). 4. Media with valid backup data (i.e. latest backup image) are available. 5. One drive is available for reading the data from backup media.
2.13 NAME 2.13.4 90 FILES • /var/opt/fse/log/restore.log (on Linux systems), %InstallPath%\var\log\restore.log (on Windows systems) Log file with recorded information about activity of the FSE restore process. 2.13.5 COPYRIGHT Copyright (C) 2004-2005 Hewlett-Packard Copyright (C) 2002-2005 GRAU Data Storage 2.13.6 SEE ALSO fse(8), fsebackup(8), fserecover(8), fsebak(8), fseintro(7). File System Extender 3.
2.14 2.14 NAME 91 NAME fsesystem – Manage FSE system configuration. Report states of FSE partitions. 2.14.1 SYNOPSIS fsesystem {–s | – –show} [RevisionNumber | {–H | – –history}] fsesystem {–m | – –modify} ConfigFileName fsesystem {–t | – –status} fsesystem – –enable–dbg SysDbgLevel [SysDbgFile [SysDbgFlags [SysDbgHSMFS]]] fsesystem – –disable–dbg fsesystem {–h | – –help} fsesystem {–v | – –version} 2.14.
2.14 NAME 92 Interface must be running. If the connection to the Management Interface fails, check its status by running the fse status command. In case the Management Interface is not running, start it with the fse start command. After successful command execution fsesystem notifies the FSE administrator with a suitable message, which is printed to the standard output stream (stdout).
2.14 NAME 93 ∗ ... not relevant Situations described by the lines with X in the column ERROR mean that some error occurred and the FSE administrator’s intervention is necessary to restore the normal FSE operation. 2.14.3 OPTIONS • –s, – –show If the argument RevisionNumber is given, print the appropriate FSE system configuration revision, otherwise print the configuration revision in–use. • RevisionNumber A non–negative integer value which represents the configuration revision to print.
2.14 NAME 94 administrator. Usage of this option overrides current debugging settings in FSE tracing configuration file (see section FILES), but its effect is limited to the period of time until FSE processes are stopped with the fse command (current FSE session). After the processes are restarted, the settings in FSE tracing configuration file apply. Note: Usage of this option has no effect on debugging of the currently running Back End Agents.
2.14 NAME 95 – If string other than "." is specified, it will be considered as a file name for single FSE debug file, where all running FSE processes will write their debugging information into. In both cases the log file(s) will be put in the /var/opt/fse/log/debug directory. This argument may only be used together with the SysDbgLevel argument. If it is not used, each FSE process writes the debugging data to its corresponding standard output stream (stdout).
2.14 NAME 96 events in the HSM file system filter. The flags and the corresponding events are the following: – 0x00000001 .... main HSM file system filter execution flow. – 0x00000002 .... HSM file system filter’s hooking to system functions. – 0x00000004 .... virtual file system (VFS) method calls. – 0x00000008 .... low level communication between user applications and HSM file system filter. – 0x00000010 .... HSM file system events. – 0x00000020 .... read/write/change operations on file HSM attributes.
2.14 NAME 2.14.4 97 EXAMPLES • Show the current system configuration: fsesystem – –show • Show the fourth revision of the FSE system configuration: fsesystem –s 4 • Show the configuration history depth for FSE system configuration: fsesystem – –show – –history • Copy current (latest) configuration revision of the FSE system configuration to a file fse_config.fse in the current directory: fsesystem – –show > fse_config.
2.14 2.14.7 NAME SEE ALSO fse(8), fsejob(8), fsepartition(8), fseintro(7). File System Extender 3.
