HP StorageWorks File System Extender Software CLI reference First edition (October 2006) Part number: T3648-96013
CONTENTS 2 Contents 1 FSE command index 2 2 FSE command documentation 3 1 FSE command index 1.
2 FSE command documentation fsesystem 2 2.1 3 108 FSE command documentation NAME fse: Initiate or terminate the FSE server or FSE client operation. Show current status of the FSE daemons (services). Configure mount points for HSM file systems (on Windows platform only). Enable or disable Limited Access Mode for a particular HSM file system (on Windows platform only). 2.1.
2.1 NAME 4 all. FSE administrator has to know exactly what he is doing when using this command.
2.1 NAME 5 each FSE client as FSE client processes (marked with C character) and some on both/all (marked with S+C characters). Configuration–independent FSE processes – FSE daemons (services) are: • 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.
2.1 NAME 6 POST–START AND PRE–STOP SCRIPTS FSE administrator can set up two helper scripts which perform arbitrary automated tasks at the FSE implementation (FSE server, FSE client) startup and shut–down time. They are executed by the fse command. Both helper scripts have to be placed in the /opt/fse/sbin (on Linux systems) or %InstallPath%\bin directory (on Windows systems) on a local machine, and have to be named as specified below: • post_start.sh (on Linux systems) or post_start.
2.1 NAME 7 • Regular ...... the volume is mounted using HSM file system and operates as a regular FSE partition. • WORM ......... the volume is mounted using HSM file system and operates as a WORM FSE partition. • LAM .......... the volume is mounted using HSM file system and operates in the Limited Access Mode. The operation of HSM FS filter for that volume was manually switched to LAM using the fse – –limit–access command.
2.1 NAME 2.1.3 8 OPTIONS • – –start This option has different effects depending on whether the fse command is executed in a consolidated FSE implementation, in a distributed FSE implementation on an FSE server, or in a distributed FSE implementation on an FSE client. If used on a consolidated FSE system, the – –start option: 1. initiates omniNames – the omniORB naming service daemon, if it is not running yet, 2.
2.1 NAME 9 • – –stop As with the – –start option, the effects of this option depend on where the fse command is executed. If used on a consolidated FSE system, the – –stop option: 1. executes the pre–stop script, if it exists (see POST–START AND PRE–STOP SCRIPTS for details on the pre–stop script), 2. unmounts all mounted HSM file systems (on Linux systems), 3. terminates the FSE operation shutting down all running FSE processes (see FSE PROCESSES for details on FSE processes).
2.1 NAME 10 • – –status Show status of each FSE (server, client) daemon (service), i.e. configuration–independent FSE (server, client) process. For details on FSE daemon (service) status info, see section FSE PROCESSES. • – –mount • – –umount Linux systems: The command fse – –mount | – –umount should not be used by the FSE administrator directly. It is called by fse–svc daemon (service) during a recovery of an HSM file system. Windows systems: Use the command fse – –mount | – –umount with great care.
2.1 NAME 11 NTFS, and thus gain control over it. Note that the fse – –dismount–ntfs command will fail in case the volume is in use, that is, when some processes have open handles on it. • – –limit–access Windows systems only: Switch the HSM FS filter operation for managing accesses to the volume VolumeName from Full Access Mode to Limited Access Mode. In this mode, modifications on the corresponding HSM file system are not allowed.
2.1 NAME 12 Windows systems only: Retrieve additional volume 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. Device ... the device string of the device which the volume is linked to. Additionally, a more descriptive content is reported for the Status parameter. This option can only be used in combination with the – –list–volumes option. 2.1.
2.1 NAME 13 • Retrieve additional information about volumes on the local system; display each of the retrieved parameters in a separate line (on Windows systems): fse – –list–volumes – –detail 2.1.5 FILES • /opt/fse/sbin/post_start.sh (on Linux systems), %InstallPath%\bin\post_start.cmd (on Windows systems) The post–start helper script. • /opt/fse/sbin/pre_stop.sh (on Linux systems), %InstallPath%\bin\pre_stop.cmd (on Windows systems) The pre–stop helper script. 2.1.
2.2 2.2 NAME 14 NAME fsebackup: Create backup image with complete FSE server state. 2.2.1 SYNOPSIS fsebackup [{–f | – –file} BackupFileName [– –nomedia]] fsebackup [{–f | – –file} BackupFileName] [{–m | – –medium} Barcode [–i | – –init]] fsebackup {–h | – –help} fsebackup {–v | – –version} 2.2.2 DESCRIPTION Each FSE command communicates with the FSE processes through the Management Interface (fse–mif). To execute an FSE command, the Management Interface must be running.
2.2 NAME 15 In case of disaster, you can use the fserestore command to restore the complete FSE state from such backup image. The backed up items include entities that are shared among FSE clients in the FSE implementation, as well as entities that belong to each particular FSE client. The following entities are backed up: • Global configuration files (omniORB.cfg, services.cfg, trace.
2.2 NAME 16 backed up have to reside on LVM logical volumes (on Linux systems) or additional snapshot software needs to be installed in advance (on Windows systems). This is an essential prerequisite. For details on the required snapshot software on Windows platform, see the FSE release notes. When tape is used as backup destination, FSE backup stores backup images to tape media of the backup FSE media pool. This media pool should therefore be configured before fsebackup is run.
2.2 NAME 17 databases, and then the transaction log files are removed. This action achieves the required consistency of HSMDBs. 3. Transaction log files of File System Catalogs (FSCs) are committed to the main databases. This action achieves the required consistency of FSCs. 4. Snapshots of the volumes with FSE databases and system files are created. 5. FSE server is resumed.
2.2 NAME 18 • HSM_LV_VAR = hsm_vg/var This parameter is obsolete in the current FSE product. It is ignored by the backup process. • HSM_LV_PART = hsm_vg/part This parameter is obsolete in the current FSE product. It is ignored by the backup process. • SNAPSHOT_PCT = 10 Size of the LVM logical volume snapshot, expressed in percentage of the original LVM logical volume size. If the /etc/opt/fse/backup.cfg file is not found, default values are used for the current FSE backup session.
2.2 NAME 2.2.3 19 OPTIONS • –f, – –file Perform FSE backup and copy the backup image to disk or both backup destinations: disk and tape. With disk destination, location and filename of the backup image file are defined by the argument BackupFileName.
2.2 NAME 20 • – –nomedia Do not copy the backup image to tape, but only create backup image file on disk. This option can only be used in combination with the – –file option, and cannot be used in combination with the – –medium option. • –m, – –medium Perform FSE backup and copy the backup image to tape medium with barcode Barcode.
2.2 NAME 2.2.4 21 EXAMPLES • Perform backup and copy the backup image to tape medium in the backup FSE media pool: fsebackup • Perform backup and copy the backup image to the file backup_image_file.tar.bz2 in the current directory on a local disk volume and to tape medium in the backup FSE media pool: fsebackup –f backup_image_file.tar.bz2 • Perform backup and copy the backup image to a file in the current directory on the local disk volume.
2.2 NAME 2.2.5 22 FILES • /opt/fse/newconfig/backup.cfg (on Linux systems) Template for FSE backup configuration file. • /etc/opt/fse/backup.cfg (on Linux systems) FSE backup configuration file. • /var/opt/fse/log/backup.log (on Linux systems), %InstallPath%\var\log\backup.log (on Windows systems) Log file with information about activity of the FSE backup process. • /var/opt/fse/log/fse.log (on Linux systems), %InstallPath%\var\log\fse.log (on Windows systems) FSE event log file.
2.3 2.3 NAME 23 NAME fsebak: Suspend all HSMDBs and FSCs to achieve a consistent state of these FSE databases to allow eventual copying. 2.3.1 SYNOPSIS fsebak – –suspend fsebak – –continue StatusCode fsebak {–h | – –help} fsebak {–v | – –version} 2.3.2 DESCRIPTION COMMON USAGE The fsebak command affects core FSE components. It should be used with a maximum care as its usage can lead to improper FSE system operation or no operation at all.
2.3 NAME 24 Partition Manager processes (fse–pm) for all configured FSE partitions must be running. This can be checked with the fsesystem command. After successful command execution, fsebak notifies the FSE administrator with a suitable message, which is printed to the standard output stream (stdout). If there was an error during command execution, an appropriate error message is printed to the standard error stream (stderr).
2.3 NAME 2.3.3 25 OPTIONS • – –suspend Prepare each HSMDB and FSC for copying to another location. This action temporarily suspends the normal FSE system operation in all running Partition Managers. See DESCRIPTION for details of this operation. • – –continue Unblock the FSE system operation using the value StatusCode. This enables the incoming job requests in all running Partition Managers and restores the normal FSE system operation.
2.3 2.3.5 NAME COPYRIGHT Copyright (C) 2004-2005 Hewlett-Packard Copyright (C) 2002-2005 GRAU Data Storage 2.3.6 SEE ALSO fse(8), fsesystem(8), fseintro(7).
2.4 2.4 NAME 27 NAME fsecheck: Perform an HSM file system consistency check against the File System Catalog or a File System Catalog consistency check against the FSE media. 2.4.1 SYNOPSIS fsecheck {–i | – –fsc–hsmfs} PartitionName fsecheck {–m | – –fsc–media} {PartitionName | {–B | – –barcode} Barcode... [{–V | – –volume} VolumeNumber...]} [– –autocorrect [– –match–media]] fsecheck {–h | – –help} fsecheck {–v | – –version} 2.4.
2.4 NAME 28 • some files that are present on the HSM file system or on the FSE media are missing from File System Catalog, • 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).
2.4 NAME 29 • –m, – –fsc–media Perform a consistency check on the FSE partition PartitionName comparing the corresponding File System Catalog against the associated FSE media. For details on this process, see section CHECKING FILE SYSTEM CATALOG CONSISTENCY. • – –autocorrect Automatically correct errors discovered by the consistency check of File System Catalog against corresponding FSE media. For details on this process, see section CHECKING FILE SYSTEM CATALOG CONSISTENCY.
2.4 NAME 30 • –V, – –volume Limit the consistency check to the FSE medium volumes listed in the VolumeNumber argument. This option can only be used in combination with the – –barcode option, and cannot be used if more than one medium is specified in Barcode.... • 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.
2.4 NAME 31 • Trigger a File System Catalog consistency check against FSE media assigned to the same FSE partition: fsecheck – –fsc–media – –barcode 000101 000102 dm002 • Trigger a File System Catalog consistency check against the specified volumes on the specified FSE medium: fsecheck – –fsc–media – –barcode 000101 – –volume 1 3 8 – –autocorrect 2.4.5 FILES • /var/opt/fse/log/check_hsmfs_fsc_.
2.5 NAME 2.5 32 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 33 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 a successful command execution fsedrive notifies the FSE administrator with a suitable message, which is printed to the standard output stream (stdout).
2.5 NAME 34 • –s, – –show If the RevisionNumber argument is specified, 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 35 • –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 ..........
2.5 NAME 2.5.4 36 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).
2.6 NAME 2.6 38 NAME fsefile: Manage files on an HSM file system. Recall latest or older file generations from FSE media. Recall large sets of files from FSE media. Add files to dirty file list. Release files from an 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... [–s | – –size] [–D | – –detail] fsefile {–H | – –history} {FileName... [–D | – –detail] | – –id PartitionName FileID...
2.
2.6 NAME 40 the command returns the control immediately after it has started a corresponding job. In this case no information from the job is received, even in case of errors. Monitoring can be cancelled by pressing ∧ C in the shell where fsefile runs. Note: The job will continue to run and will write progress to the fse.log file. 2.6.
2.6 NAME 41 • –H, – –history For each migrated generation, show file ID, migration ID, migration date and time, total size of data streams that were migrated, type of data that was migrated, and file name. Type of the migrated data can be one or more of the following: 1. H .......... header. 2. D .......... data. 3. M .......... metadata. 4. A .......... alternate data stream. If the file has been renamed between migrations, this command displays the last file name for all the generations.
2.6 NAME 42 Note: If a certain file is located on HSM file system other than the HSM file system of the first specified file, a warning is printed and the file is not processed. • –R, – –recall Recall a migrated generation of a file that is currently present on an HSM file system or was present at some moment in the past.
2.6 NAME 43 is recalled in one recall job, thus reducing recall job overhead and unnecessary rewinds of tape media. Successfully recalled files are logged into the HSM file system log file, hsmfs_.log. Files that failed to be recalled are logged into the FSE error log file, error.log, with a single failure indicator in the FSE event log file, fse.log. For location of log files, see section FILES in the fseintro man page.
2.6 NAME 44 • – –date Specify that latest generation migrated before point in time, defined by the Date argument, has to be recalled. This option can only be used in combination with the – –recall option. • Date Date and time of the point in time, used to specify particular migrated file generation. Date and time strings have to conform to format of YYYY/MM/DD hh:mm:ss and must be together enclosed in double quotes.
2.6 NAME 45 – file is present on the HSM file system but had not been recognized by the FSE implementation for some reason. Adding it to the migration candidate list with this command preserves its attributes; – the file is already migrated to an FSE medium that has its current status set to UNRELIABLE or it is obviously worn out. In these cases the file can be re–migrated to another FSE medium.
2.6 NAME 46 Set forced mode for triggering the deletion of files on an HSM file system. In this mode, FSE administrator’s confirmation of triggering the file deletion is skipped. The command treats it as if FSE administrator would have answered the confirmation question with "Yes". This option can only be used in combination with the – –trigger–deletion option. • – –no–monitor Disable monitoring of the formatting, initialization or maintenance job which is to be performed on the HSM file system.
2.6 NAME 47 • Recall latest migrated generation of files specified in the file RecallFileList.txt in the UTF–8 format into current directory on an HSM file system: fsefile – –recall – –if RecallFileList.txt – –utf8 • Recall latest migrated generation of files entered on the standard input into current directory on an HSM file system: fsefile – –recall – –if • 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.
2.
2.7 NAME 2.7 49 NAME fsejob: Monitor execution of running FSE jobs. Show status of running FSE jobs. Manage 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 50 is not running, start it with the fse – –start command. There should also be a Partition Manager process (fse–pm) running for FSE partition for which the 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).
2.7 NAME 51 2. Phase .......... current phase the job is executing (for this copy), 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.
2.7 NAME 52 • –T, – –maint List maintenance jobs. • 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 can only be used in combination with the – –list option. • –t, – –status Show status information for the FSE job with the specified identification number JobID.
2.7 NAME 53 • –I, – –incr Increase current priority of the FSE job with specified identification number JobID by value Number. • –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 NAME 54 • Increase priority of FSE job with identification number 20021127000049 by 1000: fsejob –p 20021206000614 –I 1000 2.7.5 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).
2.8 NAME 2.8 55 NAME fselibrary: Manage configuration of the FSE libraries. Monitor inventory of the FSE libraries. 2.8.
2.8 NAME 56 • show current status of the configured drives and slots in the operating FSE library (barcodes of the media in drives and the media assigned to slots), • 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 processes through the Management Interface (fse–mif). To execute an FSE command, the Management Interface must be running.
2.8 NAME 57 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". • 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.
2.8 NAME 58 • –l, – –list Display status information for configured FSE libraries within the FSE implementation. Reported status information for an FSE library includes: 1. Name .......... library name, 2. Family .......... library family (AIT, LTO), 3. Type .......... library type (SCSI, manual, unknown), 4. Host .......... fully–qualified domain name (FQDN) of the host the library is attached to, 5. CtrlDev .......... library control device file, 6. Status ..........
2.8 NAME 59 1. Name .......... drive name, 2. Type .......... item type (drive), 3. Status .......... current drive status (online, in use, disabled, error), 4. Medium .......... barcode of the FSE medium that is loaded in the drive ( string is displayed if the drive is empty). 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, mail, cleaning), 3. Status .........
2.8 NAME 60 • – –enable Enable operation of FSE library Name, which is currently disabled. Enabling the library means making it available to the FSE implementation again. • –h, – –help Print the usage information for this FSE command. • –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 61 • List names and states of the currently configured FSE libraries: fselibrary –l • Retrieve additional information about the currently configured FSE libraries: fselibrary – –list –D • 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.8 2.8.7 NAME SEE ALSO fse(8), fsedrive(8), fsemedium(8), fsepool(8), fseintro(7).
2.9 2.9 NAME 63 NAME fsemedium: Manage configuration of the FSE media. Format and initialize FSE media. Perform maintenance tasks on the FSE media. Duplicate or reorganize FSE media. Recreate a copy of the unreadable data located on damaged FSE media. Modify current status of the FSE media. 2.9.
2.9 NAME 2.9.2 64 DESCRIPTION This FSE command manages a single FSE medium.
2.9 NAME 65 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 66 • –O, – –pool Assign a new FSE medium with barcode Barcode to the FSE media pool PoolName. This option can only be used in combination with the – –add option. • 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.
2.9 NAME 67 Status information for an FSE medium volume includes: 1. Barcode .......... name of the corresponding FSE medium, 2. VolNum .......... index of the volume on medium, 3. Type .......... medium volume type (data, system), 4. Size[MB] .......... medium volume size (in MB), 5. Avail[MB] .......... current amount of volume free space (in MB), 6. Used[%] .......... percentage of currently occupied volume space, 7. Status ..........
2.9 NAME 68 – SlotAddr .......... address of the library slot assigned to the medium, – SlotType .......... type of the library slot assigned to the medium, – DrvName .......... name of the drive the medium is loaded into (if any), – SerialNo .......... medium serial number, – BlockSize .......... block size used on FSE medium volumes on the medium, – SysVolSize .......... size of the system volume of the medium (if it exists), – CurVol ..........
2.9 NAME 69 volumes is performed as well. Formatting an FSE medium means partitioning it into FSE medium volumes, according to the parameters specified by the corresponding FSE media pool configuration. In case of FSE disk media formatting will create subdirectories for each of the volumes. The name of the directory will be the volume number. Note: FSE medium must be assigned to an FSE media pool before it can be formatted.
2.9 NAME 70 – if – –remove, – –mark–unreliable, – –mark–unusable or – –mark– good option is specified, skip FSE administrator’s confirmation of FSE medium removal, marking the medium unreliable, marking it unusable or marking it "good"; treat it as if FSE administrator would have answered the confirmation question with "Yes".
2.9 NAME 71 to UNRELIABLE. 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". • – –mark–unusable Disallow reading from and writing to the FSE medium with barcode Barcode. From that moment on, the data on the medium can be neither read nor medium can be written to.
2.9 NAME 72 If the – –no–monitor option is not specified, the progress of the maintenance job that performs medium volume closing will be reported to the command output. • – –recreate–fri Recreate missing Fast Recovery Information on disk from the migrated metadata on specified FSE medium or FSE medium volume. For all medium volumes which are closed, the recreated Fast Recovery Information is also copied to the end part of these volumes.
2.9 NAME 73 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. If the – –no–monitor option is not specified, the progress of the maintenance job that performs the recreation will be reported to the command output. For details of the redundant copy recreation process, see the FSE user guide. • –h, – –help Print the usage information for this FSE command.
2.
2.9 NAME 75 • Start the media reorganization job for all medium volumes on the medium with barcode tape_55; disable monitoring: fsemedium – –reorg tape_55 – –no–monitor • Start the media reorganization job for medium volumes 1, 2, 5, and 7 on the medium with barcode tape_56: fsemedium – –reorg tape_56 – –volume 1 2 5 7 • Recreate a copy of the files located on the medium with barcode damaged_med: fsemedium – –copy–contents damaged_med 2.9.
2.10 2.10 NAME 76 NAME fsepartition: Manage configuration of the FSE partitions. Scan the FSE partitions for obsolete data and report the corresponding statistics. 2.10.
2.10 NAME 77 • list names and current status for configured partitions in the FSE implementation, • show current status of an FSE partition, • 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 processes through the Management Interface (fse–mif).
2.10 NAME 78 PARTITION STATUS INFORMATION Partition status information that is printed using the – –status option is the following: 1. Partition .......... partition name, 2. Status .......... current partition status (ready, disabled, recovery mode, mounted, error, unknown), 3. Host .......... fully–qualified domain name (FQDN) of the machine that hosts the partition, 4. Mountpoint .......... mount point of the HSM file system that belongs to the partition, 5. # of Migration Jobs ..........
2.10 NAME 79 6. SysAvail[MB] .......... total available space on all system volumes on the FSE media in this media pool (in MB), 7. SysUsed[%] .......... percentage of the total used space on all system volumes on the FSE media in this media pool, 8. #Good .......... number of "good" FSE media in this media pool (the media whose status is not set to unreliable or unusable), 9. #Unusable .......... number of unusable FSE media in this media pool, 10. #Unreliable ..........
2.10 NAME 80 file, copies the file to Configuration Database and inserts the parameter values into Resource Management Database. FSE partition names are unique within one FSE implementation. A new Partition Manager for this partition is started after the validation checks pass. Partition Manager is one of the configuration–dependent FSE processes in the FSE implementation.
2.10 NAME 81 • Name The name of the FSE partition to manage configuration for or perform an operation on. • –F, – –force Set forced mode for FSE partition removal. In this mode, FSE administrator’s confirmation of FSE partition removal is skipped. The command treats it as if FSE administrator would have answered the confirmation question with "Yes". This option can only be used in combination with the – –remove or – –disable option.
2.10 NAME 82 2. Status .......... current partition status (ready, disabled, recovery mode, mounted, error, unknown), 3. Host .......... fully–qualified domain name (FQDN) of the machine that hosts the partition, 4. Mountpoint .......... mount point of the HSM file system that belongs to the partition. • –D, – –detail Retrieve additional FSE partition information and display the retrieved data in the ParameterName: ParameterValue format with each parameter in its own line.
2.10 NAME 83 • – –enable Enable operation of FSE partition Name, which is currently disabled. • – –reorg–scan Scan FSE medium volumes on all media that belong to the FSE partition Name for obsolete data using the mandatory ExpirationDate and optional NumberOfGenerations parameter. The scan statistics are recorded in the corresponding File System Catalog, in order to be used by the reorganization job. Note that the scanning process may take a considerable amount of time.
2.10 NAME 84 5. SlackSpace .......... the percentage of storage space on the medium that is occupied by the data which was treated as obsolete by the reorganizational scan job. For more information on the media reorganization, see the FSE user guide. • SlackThreshold% Omit the media with a slack space percentage lower than SlackThreshold% from the report generated by the – –reorg–stat option. This option can only be used in combination with the – –reorg–stat option.
2.10 NAME 85 • Show the configuration history depth for the FSE partition named client_01_documents: fsepartition –s client_01_documents –H • Copy current (latest) configuration revision of the FSE partition named mail_partition_01 to a file mail_partition_01_cfg.fse in the current directory: fsepartition – –show mail_partition_01 > mail_partition_01_cfg.fse • Copy the configuration revision 3 of the FSE partition named fse_part_001 to a file fse_part_001_cfg_3.
2.
2.10 NAME 87 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).
2.11 NAME 2.11 88 NAME fsepool: Manage configuration of the FSE media pools. Report the FSE media pool–related statistics gathered during the scan for obsolete data. 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.11 NAME 89 Each FSE command communicates with the FSE processes 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. In case the Management Interface is not running, start it with the fse – –start command.
2.11 NAME 2.11.3 90 OPTIONS • –a, – –add 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 implementation. • ConfigFileName The name of the FSE media pool configuration file to use.
2.11 NAME 91 • –H, – –history Print configuration history depth for the FSE media pool Name. Configuration history depth is the number of the configuration file revisions which are stored in Configuration Database for this FSE media pool. This option can only be used in combination with the – –show option. • –m, – –modify Modify the configuration of FSE media pool Name with the configuration file ConfigFileName.
2.11 NAME 92 • –D, – –detail Retrieve additional FSE media pool 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. UUID .......... universal unique identified of the media pool, 2. PartUUID .......... universal unique identified of the FSE partition to which the media pool is assigned, 3. Key .......... internal RMDB key value assigned to the media pool.
2.11 NAME 2.11.4 93 EXAMPLES • Configure a new FSE media pool from the configuration file mail_archive_pool.fse: fsepool – –add mail_archive_pool.
2.11 NAME 2.11.5 94 FILES • /opt/fse/newconfig/fse–pool–AIT.cfg (on Linux systems), %InstallPath%\newconfig\fse–pool–AIT.cfg (on Windows systems) Template for a configuration file for an FSE media pool with AIT media. • /opt/fse/newconfig/fse–pool–AIT–MANY–SMALL–FILES.cfg (on Linux systems), %InstallPath%\newconfig\fse–pool–AIT–MANY–SMALL–FILES.cfg Windows systems) (on Template for a configuration file for an FSE media pool with AIT media on which numerous files of small size will be stored.
2.11 2.11.7 NAME 95 SEE ALSO fsepartition(8), fsemedium(8), fselibrary(8), fsedrive(8), fsebackup(8), fserestore(8), fseintro(7).
2.12 2.12 NAME 96 NAME fserecover: Recover a File System Catalog from its redundant duplicate data sources (FSE media and Fast Recovery Information). 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.12 NAME 97 2. on system volume on FSE media (fast method), 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 98 This file provides data for incremental recovery after power outage or similar inconvenient situations. If this file does not exist then recovery will start from file ID 1. When a recovery from scratch is required, this file has to be deleted. At the end of successful recovery operation this file is deleted. Recovery will be done to native FS (Ext3 on Linux systems, NTFS on Windows systems). File state after recovery: 1.
2.12 NAME 99 5. It is not allowed to stop recovery, mount HSM FS as hsmfs, use it for migration and later resume recovery. 2.12.3 OPTIONS • –f, – –fsc Start recovery of the File System Catalog for FSE partition PartitionName. For details of this process, see section FSC RECOVERY PROCEDURE. • 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.
2.12 2.12.6 NAME SEE ALSO fsecheck(8), fsepartition(8), fseintro(7).
2.13 2.13 NAME 101 NAME fserestore: Restore complete FSE server state from the most recent backup image. Retrieve a sequence of backup images from tape medium to disk. 2.13.1 SYNOPSIS fserestore {–f | – –file} BackupFileName fserestore {–d | – –device} DeviceFile [{–o | – –offset} OffsetNumber [{–c | – – count} CountNumber]] [– –retrieve–to DirectoryPath] fserestore {–h | – –help} fserestore {–v | – –version} 2.13.2 DESCRIPTION This FSE command executes restore of the FSE server.
2.13 NAME 102 RESTORE CONCEPTS fserestore copies the backup image from the specified restore source to a local directory, and performs restore of the FSE server using data from the backup image file. The restore source can be either local or remote disk volume, remote share, or FSE medium that is loaded in an FSE drive. The restore process reverts completely the state of FSE server to the point in time when the backup image was created.
2.13 NAME THE RESTORE PROCESS 103 The restore process performs the following steps: 1. According to the specified restore source, one or more backup images are copied from disk (local or remote disk volume or share) or tape (FSE medium in the backup FSE media pool) and temporarily stored in FSE disk buffer. 2.
2.13 NAME 104 • –d, – –device Use tape medium as the source for retrieval of backup image(s). With this source, FSE restore reads data from FSE medium loaded in the FSE drive with control device DeviceFile. Additional options – –offset, – –count, and – –retrieve–to determine how many backup images are read from tape and whether FSE restore is actually performed. • DeviceFile Name of the control device file for the FSE drive that is used to read backup image(s) from tape.
2.13 NAME 105 • – –retrieve–to Store the retrieved backup image(s) to the directory DirectoryPath on a local or remote disk volume or share, instead of FSE disk buffer. This option can only be used in combination with the – –device option. • DirectoryPath Absolute or relative path pointing to an existing directory where the retrieved backup image files are copied. The retrieved files use their original file names that were used during FSE backup.
2.
2.13 2.13.6 NAME COPYRIGHT Copyright (C) 2004-2005 Hewlett-Packard Copyright (C) 2002-2005 GRAU Data Storage 2.13.7 SEE ALSO fse(8), fsebackup(8), fserecover(8), fseintro(7).
2.14 2.14 NAME 108 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 109 Each FSE command communicates with the FSE processes 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. In case the Management Interface is not running, start it with the fse – –start command.
2.14 NAME 110 | recovery mode | enabled | running | not mounted | | | mounted | enabled | running | mounted | | | error | enabled | not running | not mounted | X | | unknown | * | * | * | X | ------------------------------------------------------------------- ∗ ... 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.
2.14 NAME 111 the status information that is printed with the help of this option, see section STATUS INFORMATION. • – –enable–dbg Enable debugging or change current settings for debugging of FSE processes according to the SysDbgLevel argument and the SysDbgFile, SysDbgFlags and SysDbgHSMFS arguments, if they are specified by the FSE administrator.
2.14 NAME 112 • SysDbgFile An alphanumeric string which specifies where the debugging information is recorded. This argument can be used in two ways: – If the character "." (a dot) is specified, FSE processes will write their debugging data in corresponding files with file names of the form _.log. Each generated log file will correspond to a single running FSE process; – If string other than ".
2.14 NAME 113 – V .......... Verbose third–party debugging. This argument can only be used in combination with the SysDbgFile argument. If it is not used, no events are logged – only the FSE debug file header is printed. • SysDbgHSMFS HSM file system debugging flags, specified by a positive hexadecimal integer number of the form 0xNNNNNNNN. These flags enable logging of the events in the HSM file system filter. The flags and the corresponding events are the following: – 0x00000001 ..........
2.14 NAME 114 • –h, – –help Print the usage information for this FSE command. • –v, – –version Print the copyright and version information for this FSE command. 2.14.
2.14 NAME • /etc/opt/fse/trace.cfg (on Linux systems), %InstallPath%\etc\trace.cfg (on Windows systems) FSE tracing configuration file. 2.14.6 COPYRIGHT Copyright (C) 2004-2005 Hewlett-Packard Copyright (C) 2002-2005 GRAU Data Storage 2.14.7 SEE ALSO fse(8), fsejob(8), fsepartition(8), fseintro(7).
