HP StorageWorks File System Extender CLI Reference Guide

Page 1
HP StorageWorks
File System Extender Software
CLI reference
First edition (October 2006)
Part number: T3648-96013
Page 2
CONTENTS 2
Contents
1 FSE command index 2
2 FSE command documentation 3
1.1 List of FSE commands
FSE command-line interface includes the following commands:
fse 3 fsebackup 14 fsebak 23 fsecheck 27 fsedrive 32 fsefile 38 fsejob 49 fselibrary 55 fsemedium 63 fsepartition 76 fsepool 88 fserecover 96 fserestore 101
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 3
2 FSE command documentation 3
fsesystem 108

2 FSE command documentation

2.1 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.1 SYNOPSIS
fse ––start fse ––stop fse ––restart fse ––status fse ––mount MountPoint VolumeName fse ––umount MountPoint VolumeName fse ––dismount–ntfs VolumeName fse ––limit–access VolumeName fse ––full–access VolumeName fse ––list–volumes [– –detail]
2.1.2 DESCRIPTION
The fse command (startup script on Linux systems, executable on Windows sys­tems) affects core FSE components. It should be used with a maximum care as its usage can lead to improper FSE server or client operation or no operation at
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 4
2.1 NAME 4
all. FSE administrator has to know exactly what he is doing when using this com­mand.
The command is used to perform these FSE administrator’s tasks:
• startor shut down FSE processes to enable or cease the FSE implementation (FSE server, FSE client) operation,
• restart FSE (server, client) processes in case of problems,
• print status information for the configuration–independent FSE daemons (services) running in the FSE implementation (FSE server, FSE client),
• on Windows systems, configure mount points for HSM file systems, mount or unmount HSM file systems,
• on Windows systems, dismount a newly formatted volume, enable or dis­able Limited Access Mode for a particular HSM file system,
• on Windows systems, enumerate all local volumes and report their status with respect to the FSE implementation.
FSE PROCESSES Core FSE components, as for fse command, are run­ning FSE processes, that are responsible for proper FSE operation. There are two groups of FSE processes: configuration–independent and configuration– dependent. The configuration–independent FSE processes, also called FSE dae­mons (services), allow FSE software to operate and intercommunicate. The configuration–dependent FSE processes control a single configured FSE resource. FSE administrator may configure more than one resource of the same kind, so there can be several FSE processes of the same kind running simultaneously. Cur­rently, the only resources that are controlled by their own processes are FSE par­tition and FSE library.
CONSOLIDATED AND DISTRIBUTED FSE IMPLEMENTATIONS It is possible to either set up FSE on a consolidated system or distribute its function­ality across one FSE server and an arbitrary number of FSE clients. In first case, all FSE processes are running on the same system, in the other some of them only on FSE server as FSE server processes (marked with S character), some only on
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 5
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.
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. For each FSE daemon (service) fse – –status prints its binary name, its current status (running, stopped) and the associated process ID(s). If the command is executed on FSE server (FSE client) it only prints info on the FSE server (FSE client) daemons (services). The daemon (service) binary names are listed in the following table.
-------------------------------------------­| PROCESS | FSE DAEMON (SERVICE) |
-------------------------------------------­| fse-svc | Service | | fse-rm | Resource Manager | | fse-mif | Management Interface | | fse-fsevtmgr | File System Event Manager |
--------------------------------------------
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 6
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.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 HSM file systems with an entry in the /etc/fstab file (on Linux systems) or all existing HSM file systems with a defined mount point (on Windows systems) have been mounted, i.e. right after the FSE implementation is put into its fully operational state;
pre_stop.sh (on Linux systems) or pre_stop.cmd (on Windows systems) .....
this is the pre–stop helper script. It is executed before all mounted HSM file systems are unmounted and all running FSE processes are shut down, i.e. right before the FSE implementation is pulled out of its fully operational state.
If any of these scripts does not exist, it is simply ignored. IMPORTANT: The commands that you specify in the post–start and pre–stop
scripts should not block the execution of the fse command. Thus, they have to conform to the following rules:
• They must not require interactive input.
• They must finish in a reasonable time and afterwards return the control to the script afterwards.
VOLUME STATES ON WINDOWS SYSTEMS On Windows systems, the fse – –list–volumes [––detail] command enumerates volumes on the local system
and reports their states from the FSE viewpoint. Possible values of the reported parameter Status and their explanations are:
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 7
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. Use the fse – –full–access command to switch the HSM FS filter operation for the volume back to the Full Access Mode.
LAM–No–HSM ... this status is the same as LAM with the only difference that the fse–hsm process is not running. There are various causes of this condition. If you have run the fse ––umount command on this volume recently, you can start fse–hsm by running the fse – –mount command. If the command reports an error "HSM already started. Unmount first.", run fse ––umount again and examine the FSE error log to determine the cause of the fse–hsm failure.
Unattached ... this status is the same as Unknown with the only difference that the HSM FS filter once had control over the volume.
No–Config .... this status is the same as LAM–No–HSM but the cause is
different. Possible reasons are a disabled or removed FSE partition. To re­sume using the volume as HSM file system, enable or add the corresponding FSE partition again. To use the volume natively (through NTFS), run the command fse – –dismount–ntfs.
Inactive ..... the volume is prepared to be mounted using HSM file system
but the HSM FS filter is not attached to it yet. Either the volume was format­ted and the corresponding FSE partition has not been configured yet, or the volume has not been accessed yet. Run the command fse ––mount on the volume. If the volume status does not change, run fse ––dismount–ntfs.
Unknown ...... the volume is not under the FSE control or the fse–fsevtmgr
process is not running. In the latter case, most probably the FileSystemID variable in the FSE partition configuration has wrong contents that must be corrected.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 8
2.1 NAME 8
2.1.3 OPTIONS
––start This option has different effects depending on whether the fse command is
executed in a consolidated FSE implementation, in a distributed FSE imple­mentation 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. initiates the FSE operation starting up all FSE processes (see FSE PROCESSES for details on FSE processes),
3. mounts all existing HSM file systems with an entry in the /etc/fstab file (on Linux systems),
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 implementation, 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.
If used on FSE client in a distributed FSE implementation, it:
1. initiates the FSE client operation starting up all FSE client processes (see FSE PROCESSES for details on FSE client processes),
2. mounts all existing HSM file systems with an entry in the /etc/fstab file (on Linux systems),
3. executes the post–start script, if it exists.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 9
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).
If used on FSE server in a distributed FSE system, it:
1. executes the pre–stop script, if it exists,
2. terminates the FSE server operation shutting down all running FSE server processes (see FSE PROCESSES for details on FSE server processes).
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 pro­cesses).
––restart This option has the same effect as a consecutive invocationof the fse – –stop
and fse – –start commands.
Note:
In a distributed or mixed FSE implementation, restarting the FSE pro­cesses on FSE server requires restarting processes on particular FSE client to allow normal operation of each FSE partition configured on that client.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 10
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 (ser­vice) during a recovery of an HSM file system.
Windowssystems: Use the command fse – –mount | – –umount with great care. It should be used instead of mountvol command if you want to ad­ministrate an FSE partition (for example to enable or disable it).
– fse ––mount command will create a mount point MountPoint for the
volume VolumeName and trigger HSM FS filter to connect to volume device file and start fse–hsm.
– fse ––umount command will stop fse–hsm and switch the HSM FS
filter operation for managing accesses to the volume VolumeName from Full Access Mode to Limited Access Mode. For information on Limited Access Mode, see description of the ––limit–access option.
MountPoint A directory path that represents the mount point to which the VolumeName
NTFS volume will be mounted.
VolumeName Volume ID of an NTFS volume that stores an HSM file system on a Win-
dowsclient. Volume ID is volume name without the \\?\ prefix and without the trailing backslash.
––dismount–ntfs Windows systems only: Dismount the newly formatted NTFS volume
VolumeName. Dismount is achieved by sending an appropriate code (the FSCTL_DISMOUNT_VOLUME ioctrl code) to the volume. Later, when the volume is mounted again, the HSM FS filter can attach to it before
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 11
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 pro­cesses have open handles on it.
––limit–access Windows systems only: Switch the HSM FS filter operation for manag-
ing 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. The volume remains mounted to its mount 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 of­fline 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, see the FSE user guide.
––full–access Windows systems only: Switch the HSM FS filter operation for manag-
ing accesses to the volume VolumeName from Limited Access Mode to Full Access Mode. This change is possible only if the corresponding fse–hsm process is running and the HSM file system on the volume operates in Lim­ited Access Mode. For more information on Full Access Mode, see the FSE user guide.
––list–volumes Windows systems only: Enumerate all volumes on the local system and
report their states with respect to the FSE implementation. Reported infor­mation for a volume includes:
1. Volume ID ..... ID string of the volume,
2. Status ........ current volume status,
3. Mount point ... volume mount point.
See section VOLUME STATES ON WINDOWS SYSTEMS for descrip- tion of the volume states.
––detail
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 12
2.1 NAME 12
Windows systems only: Retrieve additional volume information and dis-
play the retrieved data in the ParameterName: ParameterValue format with each parameter in its own line. The following additional information is re­ported:
1. Device ... the device string of the device which the volume is linked to.
Additionally, a more descriptive content is reported for the Status parame­ter. This option can only be used in combination with the – –list–volumes option.
2.1.4 EXAMPLES
• Create a mount point for the specified volume and trigger HSM FS filter to connect to volume device file and start fse–hsm (on Windows systems):
fse ––mount I:\fs02 \\?\Volume{86eec883–a640–11d7–9be3– 00096bb08bc0}\
• Stop fse–hsm and enable Limited Access Mode for the specified volume (on Windows systems):
fse ––umount c:\emptydir \\?\Volume{d9568629–da27–11d7–bf21– 0050da45607}\
• Disconnect NTFS from the specified volume (on Windows systems):
fse ––dismount–ntfs \\?\Volume{d9568629–da27–11d7–bf21– 0050da45607}\
• Enable Limited Access Mode for the specified volume (on Windows sys­tems):
fse ––limit–access \\?\Volume{d9568629–da27–11d7–bf21– 0050da45607}\
• Disable Limited Access Mode (switch back to Full Access Mode) for the specified volume (on Windows systems):
fse – –full–access \\?\Volume{d9568629–da27–11d7–bf21– 0050da45607}\
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 13
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.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).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 14
2.2 NAME 14
2.2 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 Manage­ment Interface (fse–mif). Toexecutean 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. Additionally, fsebackup also requires Partition Manager processes (fse–pm) for all configured FSE partitions to be running. This can be checked with the fsesystem or fsepartition command. If tape will be used as a backup destination, Resource Manager (fse–rm) must also be running. You can check its status with the fse command.
After a successful command execution fsebackup 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).
BACKUP CONCEPTS fsebackup creates backup image with consistent state of FSE databases and system files on the FSE server at a particular point in time. Backup image can be stored on disk (local or remote disk volume or share), on tape (FSE medium in the backup FSE media pool), or on both backup destinations.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 15
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.cfg)
• Resource Management Database (RMDB)
• Configuration Database (CfgDB)
• File System Catalogs (FSCs)
• Fast Recovery Information (FRI)
Additionally, the log files on the FSE server are also backed up:
• FSEeventlog (renamed to fse_<YYYY><MM><DD>.log in the backup image, where <YYYY><MM><DD> is the current timestamp)
• FSE error log (renamed to error_<YYYY><MM><DD>.log in the backup image, where <YYYY><MM><DD> is the current timestamp)
• HSM file system logs (only if FSE server is part of a consolidated FSE system)
Note:
User data on HSM file systems and the belonging Hierarchical Storage Man­agement Databases (HSMDBs) are not backed up. If disaster occurs on a particular HSM file system, you can use the inherent HSM file system recov­ery functionality to recover from it. HSM file system recovery can be started with the fserecovercommand. For more information, see the FSE user guide.
PREREQUISITES FSE backup uses logical volume snapshot technology to keep the operation of FSE implementation almost unobstructed during the backup window. To be able for the FSE backup to use this technology, all entities that are
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 16
2.2 NAME 16
backed up have to reside on LVM logical volumes (on Linux systems) or addi­tional 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. Backup FSE media pool is an FSE me­dia pool configured with the BACKUP type and preferably one data volume on its media. Since FSE backup uses only the first data volume on each backup medium, this way you ensure that storage capacity of the backup FSE media pool is opti­mally used. For details on configuring media pools, see the fsepool man page. Note that backup FSE media must be formatted and initialized before they can be used.
Warning:
As an FSE administrator, it is your responsibility to keep track of which backup image is stored on which backup FSE medium (with tape as backup destination) or in which backup image file (with disk as backup destination). With tape as backup destination, fsebackup only checks if the backup FSE media pool is configured, and if there is enough free space on any medium in it or on the backup medium specified in the command line (if the ––medium option is specified). To avoid potential data loss, HP also suggests that you periodically check condition of tape media in the backup FSE media pool.
THE BACKUP PROCESS If all prerequisites are fulfilled, the backup process can begin. The process is executed by a backup job. The file backup.pid prevents two backup jobs from being run in parallel in the same FSE implementation.
The backup process performs the following steps. Each step starts only if all previous steps were successful:
1. FSE server is internally suspended. Operation of all running Partition Man­agers is temporarily blocked, in order to achievea consistent state of all File System Catalogs (FSCs) and other entities that will be backed up.
2. Data from transaction log files of Hierarchical Storage Management Databases (HSMDBs) on the FSE clients are committed to the main
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 17
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. Operation of all running Partition Managers is un­blocked so that Partition Managers can process existing job requests and accept new ones.
6. Backup data is collected, archived, and compressed into a single backup image file, which is temporarily stored in the FSE disk buffer storage space. On all supported platforms, backup image files use the .tar.bz2 file format.
7. According to the specified backup destination, the backup image is copied to disk (local or remote disk volume or share), tape (FSE medium in the backup FSE media pool), or both.
8. Transaction log files of File System Catalogs (FSCs), which were commit­ted in step 3, are removed.
9. Snapshots of disk volumes are removed.
Note:
You can configure a regular cron job (on Linux systems) or schedule a task (on Windows systems) to periodically run FSE backup.
ACTIVITYLOGGING fsebackup reports its progress to the FSE backup log. To figure out the required backup window, consult the FSE event log. You can determine the backup start and stop times from a previously run backup session. Errors encountered during backup process are reported to the FSE error log. For location and names of log files, see section FILES.
BACKUP CONFIGURATION On Linux systems, before starting backup, you must check parameters in the backup configuration file and modify them, if needed. Backup configuration file is named backup.cfg and located on the FSE server (see section FILES). Configurable parameters and their default values are the following:
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 18
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 cur­rent FSE backup session.
On Windows systems, the backup configuration file backup.cfg is obsolete and ignored by the backup process.
ABORTING THE BACKUP To abort an ongoing FSE backup process, you need to abort the backup job. In certain cases, aborting the fsebackup command itself is also required. Perform the steps:
1. Run the fsejob ––abort command to abort the FSE backup job. At the command line, you must specify the backup job ID. For details, see the fsejob man page.
2. In the window where fsebackup was invoked, press CTRL+C to abort fse-
backup.
Note:
This step is not required if tape was specified as the only backup des­tination, and the FSE backup job was waiting for resources at the mo­ment you aborted it.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 19
2.2 NAME 19
2.2.3 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. With tape destination, the backup image is written to a medium that belongs to the backup FSE media pool:
– if the ––medium option is not specified, the backup image is written
to the first available medium;
– if the ––medium option is specified, the backup image is written to
the medium with barcode Barcode.
If this medium already contains backup images from previous FSE backup sessions, the new backup image is appended to the existing backup image set. If – –file and BackupFileName are omitted from the fsebackup invoca- tion, the backup image is copied to tape only.
IMPORTANT: If both backup destinations are selected (the – –file option is specified without the additional – –nomedia option), and the backup im­age cannot be copied to tape for some reason (FSE media pool is not con­figured, all backup FSE media are full, the backup FSE medium specified by the options ––media Barcode is full), the backup session as a whole will fail. However, the actual backup process will partially succeed and the backup image will be copied to disk. In the opposite case, when the backup image cannot be copied to disk for some reason, the backup process will fail completely and the backup image will neither be copied to tape.
BackupFileName Name of the file in which FSE backup image will be stored. The name can
contain absolute or relative path. On Windows systems, paths to shares in the UNC format are also supported. If the character "." (a dot) is specified at the end of BackupFileName, the filename is automatically constructed from name of the host on which fsebackup is run and the current timestamp. The following template is used for automatic generation: <HostName><YYYY><MM><DD><hh><mm><ss>.tar.bz2. The .tar.bz2 exten­sion is also appended to the filename if the specified filename does not al­ready include it.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 20
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 bar-
code Barcode. Copying will fail if any of the following conditions are true:
– medium does not belong to the backup FSE media pool or does not
exist,
medium is marked as unreliable or unusable,medium does not have enough free storage space for the backup image
(the additional option ––init was not specified),
medium does not have enough free storage space for the backup im-
age, but could not be initialized for some reason (the additional option ––init was specified).
If ––medium and Barcode are omitted from the fsebackup invocation, and the ––nomedia option is not specified, the backup image is copied to the first available backup FSE medium. This option cannot be used in combi­nation with the ––nomedia option.
Barcode The alphanumeric string that identifies the FSE medium to which the
backup image will be copied.
–i, – –init If there is not enough free storage space, initialize the medium with barcode
Barcode before copying the backup image to it. This option can only be used in combination with the – –medium option.
–h, – –help Print the usage information for this FSE command.
–v, – –version Print the copyright and version information for this FSE command.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 21
2.2 NAME 21
2.2.4 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. Name of the backup image file is automatically constructed according to the template:
fsebackup ––file . – –nomedia
• Perform backup and copy the backup image to the file backup_image_­file.tar.bz2 in the directory /mnt/backup/ on a disk volume, which may be
located on a local or remote disk, depending on NFS configuration on the FSE server (on Linux systems):
fsebackup –f /mnt/backup/backup_image_file.tar.bz2 ––nomedia
• Perform backup and copy the backup image to the file on a local or remote disk share, specified by UNC string \\backup–server\backup_- share\backup_image.tar.bz2, and to tape medium in the backup FSE media pool (on Windows systems):
fsebackup ––file \\backup–server\backup_share\backup_image.tar.bz2
• Perform backup and copy the backup image to tape medium with barcode bkp_med_02 in the backup FSE media pool. Initialize the medium before copying, if there is not enough storage space left on the medium:
fsebackup ––medium bkp_med_02 –i
• 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 with barcode bkp_med_10 in the backup FSE media pool:
fsebackup –f backup_image_file.tar.bz2 –m bkp_med_10
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 22
2.2 NAME 22
2.2.5 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. You can use it to determine the required backup window.
/var/opt/fse/log/error.log (on Linux systems), %InstallPath%\var\log\error.log (on Windows systems) FSE error log file.
backup/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), fserecover(8), fseintro(7).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 23
2.3 NAME 23
2.3 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. FSE administrator has to know exactly what he is doing when using this command. fsebak is primarily meant to be used by the FSE support personnel.
INTERNAL COMMAND OPERATION fsebak prepares Hierarchical Stor­age Management Databases (HSMDBs) and File System Catalogs (FSCs) of all configured FSE partitions for an eventual copying. To achieve database consis­tency, operation of all currently running Partition Managers has to be temporarily suspended. Duplicate copies of HSMDBs and FSCs can then be created using other system commands. After copying Partition Managers are unblocked using fsebak once again. This action restores the normal FSE system operation.
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. In case the Management Interface is not running, start it with the fse start command. Additionally, the
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 24
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).
ACHIEVING THE FSE DATABASE CONSISTENCY fsebak – –suspend
follows for each running Partition Manager the following procedure:
• block the incoming job requests in Partition Manager;
• make the corresponding HSMDB and FSC incorporate all changes from their transaction logs into the main database files;
• write temporary files hsm.ref and fsc.ref with references to HSMDBs and FSCs for use with the – –continue option;
• report action success or failure.
Note:
Contents of hsm.ref and fsc.ref files should not be directly altered in any way.
If all these steps are successfully completed, duplicate copies of HSMDBs and FSCs can be made.
RESUMING NORMAL FSE SYSTEM OPERATION fsebak ––continue
StatusCode follows for each running Partition Manager the following procedure:
• read references to HSMDBs and FSCs from files hsm.ref and fsc.ref) and delete these two files;
• start accepting incoming job requests in Partition Manager and resume nor­mal operation.
If the value 0 (zero) is used in place of the StatusCode argument, all old transaction log files of HSMDBs and FSCs are removed, as the assumption is they will not be needed any more. If any other value is used as the StatusCode, these transaction logs are preserved for a potential future use.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 25
2.3 NAME 25
2.3.3 OPTIONS
––suspend Prepare each HSMDB and FSC for copying to another location. This ac-
tion 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 en-
ables the incoming job requests in all running Partition Managers and re­stores the normal FSE system operation.
StatusCode The status code, which is used with the option – –continue. See section
DESCRIPTION for an explanation of the meaning and proper usage of this value.
–h, – –help Print the usage information for this FSE command.
–v, – –version Print the copyright and version information for this FSE command.
2.3.4 EXAMPLES
• Suspend the normal FSE system operation, including HSMDBs and FSCs:
fsebak ––suspend
• Resume the normal FSE system operation after HSMDBs and FSCs were suspended:
fsebak ––continue 0
• Resume the normal FSE operation after HSMDBs and FSCs were sus­pended, but preserve the HSMDB and FSC transaction log files for an op­tional future use:
fsebak ––continue 1
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 26
2.3 NAME 26
2.3.5 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).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 27
2.4 NAME 27
2.4 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 DESCRIPTION
Each FSE command communicates with the FSE processes through the Manage­ment Interface (fse–mif). Toexecutean 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.
After a successful command execution fsecheck 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).
CHECKING FILE SYSTEM CATALOG CONSISTENCY fsecheck com­mand creates a maintenance job on the specified FSE partition. The maintenance job is executed by the corresponding Partition Manager and performs a File Sys­tem Catalog consistency check. The process can perform two types of consistency checks: it can either compare file entries which are present in File System Catalog with Fast Recovery Information (FRI) on the corresponding FSE media, or com­pare files on an HSM file system with entries in the corresponding File System Catalog. It detects the situations, where:
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 28
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).
Note:
The maintenance job for the consistency check of an HSM file system against the corresponding File System Catalog keeps track of its progress. If it is aborted with the fsejob command and later re–run with fsecheck, it resumes its operation from the interruption point on.
fsecheck command also offers automatic correction, which can be enabled as an addition to the comparison of File System Catalog against FSE media. The cor­rection procedure updates File System Catalog with missing information about file splits that has been found in Fast Recovery Information on FSE media. It can also remove the File System Catalog entries that have not been found in the be­longing Fast Recovery Information blocks on FSE media. An entry in this context means information about the location on the FSE media of any of the following: file generation, file copy, file split.
2.4.3 OPTIONS
–i, – –fsc–hsmfs Perform a consistency check on the FSE partition PartitionName compar-
ing an HSM file system against the corresponding File System Catalog. For details on this process, see section CHECKING FILE SYSTEM CATA- LOG CONSISTENCY.
PartitionName The name of the FSE partition to perform consistency check for.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 29
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 CAT- ALOG CONSISTENCY.
––autocorrect Automatically correct errors discovered by the consistency check of File
System Catalog against corresponding FSE media. For details on this pro­cess, see section CHECKING FILE SYSTEM CATALOG CONSIS-
TENCY. This option can only be used in combination 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. This type of correction further synchronizes the FSC content with the data actually present on the media. For details on this process, see section CHECKING FILE SYSTEM CATALOG CONSISTENCY. This option can only be used in combination with the ––autocorrectoption.
–B, – –barcode Perform a consistency check on the FSE partition PartitionName comparing
corresponding File System Catalog against the FSE media specified in the
Barcode argument. For details on this process, see section CHECKING FILE SYSTEM CATALOG CONSISTENCY. This option can only be
used in combination with the – –fsc–media option.
Barcode... A sequence of identifiers of the FSE media that are being checked. In most
cases, identifiers are numerical barcodes. With disk media, identifiers are relative parts of the disk media mount points (for example: dm_001, dm_-
002). Note that the following limitations apply:
media that are unavailable will not be processed.media that are specified in the command line must belong to the same
FSE partition. In the opposite case, the fsecheck command will fail.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 30
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 repre-
sent(s) the position(s) of FSE medium volume(s) on the medium layout. Note that the following limitation applies:
– medium volumes that are unavailable will not be processed.
–h, – –help Print the usage information for this FSE command.
–v, – –version Print the copyright and version information for this FSE command.
2.4.4 EXAMPLES
• Trigger a File System Catalog consistency check against HSM file system of the FSE partition daily_reports:
fsecheck ––fsc–hsmfs daily_reports
• Trigger a File System Catalog consistency check against FSE media as­signed to the FSE partition archive_part_32:
fsecheck ––fsc–media archive_part_32
• Trigger a File System Catalog consistency check against FSE media as­signed to the FSE partition archive_part_45. Enable automatic correction:
fsecheck ––fsc–media – –autocorrect archive_part_45
• Trigger a File System Catalog consistency check against FSE media as­signed to the FSE partition temp_partition. Enable extended automatic cor­rection:
fsecheck ––fsc–media – –autocorrect – –match–media temp_partition
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 31
2.4 NAME 31
• Trigger a File System Catalog consistency check against FSE media as­signed to the same FSE partition:
fsecheck ––fsc–media – –barcode 000101 000102 dm002
• Trigger a File System Catalog consistency check against the specified vol­umes 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_<PartitionName>.log (on Linux sys- tems),
%InstallPath%\var\log\check_hsmfs_fsc_<PartitionName> (on Win- dows systems)
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_<PartitionName>.log (on Linux sys- tems),
%InstallPath%\var\log\check_media_fsc_<PartitionName> (on Win- dows systems)
Log file with recorded findings of the consistency check of the File System Catalog against the FSE media.
2.4.6 COPYRIGHT
Copyright (C) 2004-2005 Hewlett-Packard Copyright (C) 2002-2005 GRAU Data Storage
2.4.7 SEE ALSO
fserecover(8), fseintro(7).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 32
2.5 NAME 32
2.5 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 DESCRIPTION
This FSE command manages configuration of the FSE drives. It is used to perform these FSE administrator’s tasks:
• configure a new or remove an existing FSE drive,
• retrieve the configuration of an existing FSE drive,
• reconfigure an existing FSE drive,
• list configured drives in the FSE implementation,
• disable or enable operation of an FSE drive.
Each FSE command communicates with the FSE processes through the Manage­ment Interface (fse–mif). Toexecutean FSE command, the Management Interface
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 33
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). If there was an error during the command execution, an appropriate error message is printed to the standard error stream (stderr).
2.5.3 OPTIONS
–a, – –add Configure a new FSE drive 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 drive names are unique within the FSE implementation.
ConfigFileName The name of the FSE drive configuration file to use.
–r, – –remove Remove an existing FSE drive from the FSE system. This includes re-
moval of all configuration file revisions of this FSE drive from Configu­ration Database. Note that unless additional option – –force is specified, the command demands FSE administrator’s confirmation before perform­ing this operation. Default answer to the confirmation question is "No".
Name The name of the FSE drive to manage configuration for.
–F, – –force Set forced mode for FSE drive remove or disable operation. In this mode,
FSE administrator’s confirmation of FSE drive removal or disabling is skipped. The command treats it as if FSE administrator would have an­swered the confirmation question with "Yes". This option can only be used in combination with the ––remove or ––disable option.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 34
2.5 NAME 34
–s, – –show If the RevisionNumber argument is specified, print the appropriate config-
uration 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. This option can only be used in combination with the ––show option.
–m, – –modify Modify the configuration of FSE drive 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 drive reconfiguration.
–l, – –list Display status information for configured FSE drives within the FSE imple-
mentation. Reported information for an FSE drive includes:
1. Name .......... drive name,
2. Family .......... drive family (AIT, SAIT, LTO),
3. Library .......... name of the corresponding FSE library,
4. Host .......... fully–qualified domain name (FQDN) of the host the
drive is attached to,
5. CtrlDev .......... drive control device file,
6. Status .......... current drive status (online, in use, error, disabled),
7. Medium .......... barcode of the medium which is present in the drive
(optional).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 35
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.......... revisionof the firmware the drive currently uses,
5. ScsiID .......... ID string of the corresponding SCSI device,
6. Index .......... index of the drive inside the FSE library,
7. UsageCount .......... usage counter for the drive,
8. Capabilities .......... code for the drive features,
9. Key .......... internal RMDB key value assigned to the drive.
This option can only be used in combination with the ––list option.
––disable Disable operation of FSE drive Name. Disabling the drive means putting it
offline in case it needs cleaning or servicing. Note that unless additional op­tion – –force is specified, the command demands FSE administrator’s con­firmation before performing this operation. Default answer to the confirma­tion question is "No".
––enable Enable operation of FSE drive Name, which is currently disabled. Enabling
the drive 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.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 36
2.5 NAME 36
2.5.4 EXAMPLES
• Configure a new FSE drive from the configuration file standalone_drive.fse:
fsedrive ––add standalone_drive.fse
• Remove the configured FSE drive named lib_drive_01:
fsedrive ––remove lib_drive_01
• Remove the configured FSE drive named drive_AB; skip confirmation:
fsedrive ––remove drive_AB –F
• Show the current configuration of the FSE drive named system_drive:
fsedrive ––show system_drive
• Show the configuration revision 4 of the FSE drive named system_drive_­backup:
fsedrive –s system_drive_backup 4
• Showthe configuration history depth for the FSE drivenamed standalone_­drive:
fsedrive ––show standalone_drive – –history
• Copy the first (oldest) configuration revision of the FSE drive named lib_­drive_03 to a file lib_drive_03_cfg_1.fse in the current directory:
fsedrive ––show lib_drive_03 1 > lib_drive_03_cfg_1.fse
• Apply a new configuration for the FSE drive named standalone from the configuration file standalone–new.fse:
fsedrive ––modify standalone standalone–new.fse
• List names and states of the currently configured FSE drives:
fsedrive ––list
• Retrieve additional information about the currently configured FSE drives:
fsedrive ––list ––detail
• Disable the FSE drive named drive_5:
fsedrive ––disable drive_5
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 37
2.5 NAME 37
• 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).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 38
2.6 NAME 38
2.6 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 File-
ID... [–D | – –detail]} fsefile {–R | – –recall} {––if [InputFile] [–8 | – –utf8] | FileName... [{––date
Date | – –migid MigID} ––into Path] | – –id PartitionName FileID... [– –date Date | – –migid MigID] ––into Path}
fsefile {–M | ––migrate} FileName... fsefile {–S | ––release} FileName... fsefile {–T | ––trigger–migration} PartitionName fsefile {–D | – –trigger–deletion} PartitionName[–F| – –force] [– –no–monitor] fsefile {–h | ––help} fsefile {–v | ––version}
2.6.2 DESCRIPTION
This FSE command manages files on an HSM file system, which belongs to a particular FSE partition. It is used to perform these FSE administrator’s tasks:
• show file ID, current status, and file size (optional) of a file on an HSM file system,
• show history with information about older migrated generations of a file on an HSM file system,
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 39
2.6 NAME 39
• explicitly recall a file from FSE media to an HSM file system,
• recall an older migrated generation of a file from FSE media to an arbitrary location on a non–HSM file system,
• recall latest generation of a set of files from FSE media to an HSM file system,
• explicitly put a file on the dirty file list for corresponding FSE partition,
• unconditionally release an already migrated file on an HSM file system,
• trigger migration of files that are currently considered migration candidates on particular FSE partition and trigger migration of files which were not migrated because of some failed migration,
• trigger deletion of files from an HSM file system, which are covered by the configured deletion policy in the belonging FSE partition configuration file.
Each FSE command communicates with the FSE processes through the Manage­ment Interface (fse–mif). Toexecutean 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.
After a successful command execution fsefile 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 PROGRESS MONITORING fsefile is able to receive messages from Management Interface to give the user ability to monitor the progress of the com­mand.
Monitoring is enabled by default and can be disabled by using the – –no–monitor option.
When monitoring is enabled, fsefile command reports events and other relevant information from the FSE processes as long as the job that fsefile has started is running. After the job terminates, the command exits. If monitoring is disabled,
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 40
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.3 OPTIONS
–l, – –list Show file ID, current status (dirty, online, offline), file size (only when the
additional option – –size is specified), 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).
If you specify only filenames (without paths), the current directory has to be the one where the specified file is (was) located.
Filenames that contain spaces must be enclosed in double quotes.
Note:
If certain file is located on a HSM file system other than the HSM file system of the first specified file, a suitable warning is printed and the file is not processed.
–s, – –size Display file sizes. This option can only be used in combination with the
––list option.
–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 combi­nation with the ––list or – –history option.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 41
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. On Linux systems, files have only one stream and the migrated sizes are equal to the file size. On Windows systems, this is not always the case. This information is printed for each file specified by the FileName... argument or the ––id PartitionName FileID... argument combination.
––id Use the PartitionName FileID... argument combination for file identifica-
tion instead of the FileName... argument. This option can only be used in combination 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. File ID is a positive decimal integer number. The file ID of a particular file may be obtained with ––list command or by searching in the HSM file system log file for the corresponding file name. The HSM file system log file is named hsmfs_<PartitionName>.log. For file location, see section FILES in the fseintro man page.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 42
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. A generation may be recalled:
– in place to the corresponding HSM file system (this is allowed only if
the latest generation is specified);
– into an arbitrary directory on a non–HSM file system (this is allowed
for any generation).
Recall is done separately for each file specified either by the FileName... argument or by the ––id PartitionName FileID... argument combination; each file triggers its own recall job. Independently of the file specification method used, a particular older migrated generation can be specified using either the – –date Date or the ––migid MigID argument combination.
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. all time stamps of the recalled file are set to current date and time.
––if Recall latest generation of a set of files, specified in the file InputFile. Sev-
eral FSE recall jobs are created for such recall, based on location of the migrated data on FSE media. The data located on a particular FSE medium
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 43
2.6 NAME 43
is recalled in one recall job, thus reducing recall job overhead and unneces­sary rewinds of tape media.
Successfully recalled files are logged into the HSM file system log file, hsmfs_<PartitionName>.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.
You can further increase performance of the recall jobs triggered with the –– ifoption by specifying the parameter SeekThreshold in the file drive.cfg. For description of drive.cfg and its location, see section FILES in the fseintro man page. The value of SeekThreshold affects the Back End Agent behavior when recalling several files in one recall job. If the difference in locations of two files on the medium is greater than SeekThreshold, the Back End Agent seeks to the position of the latter, rather than "reading" through the gap on the medium. If the parameter is not defined or drive.cfg does not exist, a default value is used, depending on the type of media from which data is recalled. With tape media, SeekThreshold defaults to 5% of the medium size. With disk media, SeekThreshold always defaults to disk block size. This option can only be used in combination with the ––recall option.
InputFile File name (with optional path) of the file that contains list of files to be
recalled using the efficient recall functionality. In InputFile each file must be specified on a separate line. For every file, you can provide either only its file name or you can precede the file name with a corresponding path relative to the mount point directory. If InputFile is not specified, the standard input is used as a source for file list.
Note:
Due to an underlying omniORB/CORBA limitation, the upper limit on the file list size is 26000 entries.
–8, – –utf8 Specify that the contents of the file InputFile (if InputFile is specified with
the ––if option) or the standard input (if InputFile is not specified) are in the UTF–8 format. This option can only be used in combination with the
––if option.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 44
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 combi­nation 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.
––migid Specify that generation, which had been migrated by migration job with
migration ID MigID, has to be recalled. This option can only be used in combination with the ––recall option.
MigID Migration ID of a migration job by which a file generation had been mi-
grated. Migration ID is a twelve–digit positive decimal integer number. The migration ID of a particular file generation can be obtained from the output of the ––history option.
––into Specify that recalled file generation has to be saved into directory with ab-
solute path Path. The path must point to a directory on a non–HSM file system. This option can only be used in combination with the ––recall option.
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 dirty
file list. If certain specified file is offline, it will be recalled first. This options comes handy in situations when:
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 45
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;
– thefile 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.
Note:
If specified file is already migrating or present on the release candidate list it cannot be added to the migration candidate list.
–S, – –release Unconditionally release files, specified by the FileName... argument. All
files must be located on the same HSM file system. The purpose of this operation is to gain free space on an HSM file system by releasing (large) files from it. The files released this way must be on the release candidate list. For details on the unconditional release process, see the FSE user guide.
–T, – –trigger–migration Trigger migration job for files that are currently present on the migration
candidate list on FSE partition PartitionName. Trigger migration job for files that were not migrated because migration of
those files failed.
–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 pol­icy consists of a sequence of FileExpiration – Path parameter pairs that are specified in the FSE partition configuration file. Although the deletion re­moves the corresponding files from the HSM file system, their migrated generations still exist on FSE media, unless the media reorganization with appropriate parameters has been run on the media that hold the migrated copies. If this is not the case, these migrated generations can still be re­called. For more information on configuring the deletion policy, see the FSE user guide.
–F, – –force
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 46
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 dele­tion 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. Monitoring is enabled by default. For details on monitoring, see section JOB PROGRESS MONI- TORING.
–h, – –help Print the usage information for this FSE command.
–v, – –version Print the copyright and version information for this FSE command.
2.6.4 EXAMPLES
• List current status of the file updateMe.gz in the current directory; display each of the retrieved parameters in a separate line:
fsefile ––list updateMe.gz – –detail
• 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
• List current status of the files file_1, file_2, and file_3 in the current direc­tory; also display file sizes:
fsefile ––list file_1 file_2 file_3 – –size
• 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
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 47
2.6 NAME 47
• Recall latest migrated generation of files specified in the file RecallFile­List.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
• Recalllatest migrated generation of file fsepkg_1.1.68.tar.gzinto the current directory on an HSM file system:
fsefile ––recall fsepkg_1.1.68.tar.gz
• Recall file fsepkg_1.1.55.tar.gz whose latest generation was migrated by migration job with ID 266142980096 into the directory /tmp/fse_recalled_­files on a non–HSM file system:
fsefile –R fsepkg_1.1.55.tar.gz ––migid 266142980096 ––into /tmp/fse_- recalled_files
• Recall last generation of file fsepkg_206_update.tar.gz that was migrated before 2525/01/01 10:00:00 into the directory /tmp/fse_older_files on a non–HSM file system:
fsefile ––recall fsepkg_206_update.tar.gz ––date "2525/01/01 10:00:00" ––into /tmp/fse_older_files
• Recall last generation of file with file ID 30600 that was migrated before 2002/12/10 15:36:50 on an FSE partition named FSEPartition010 into the directory /tmp/fse_deleted_files on a non–HSM file system:
fsefile ––recall ––id FSEPartition010 30600 – –date "2002/12/10 15:36:50" – –into /tmp/fse_deleted_files
• Recall older generation of file with file ID 18769 on an FSE partition named partitionH that was migrated by migration job with ID 266142980096 into the directory /tmp/fse on a non–HSM file system:
fsefile –R – –id partitionH 18769 ––migid 266142980096 ––into /tmp/fse
• Put files big_file_A and big_file_B on the corresponding migration candi­date list:
fsefile ––migrate big_file_A big_file_B
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 48
2.6 NAME 48
• Unconditionally release files week_50, week_51 and /mnt/fse_vg/weekly– archives/week_52 (current directory has to be set to /mnt/fse_vg/weekly– archives in order to release all files specified):
fsefile –S week_50 week_51 /mnt/fse_vg/weekly–archives/week_52
• Trigger a migration job for files on the migration candidate list on FSE partition named partition_03:
fsefile ––trigger–migration partition_03
• Trigger a file deletion job on the FSE partition named partition_delete_me; skip the confirmation question and disable monitoring:
fsefile ––trigger–deletion partition_delete_me –F – –no–monitor
2.6.5 COPYRIGHT
Copyright (C) 2004-2005 Hewlett-Packard Copyright (C) 2002-2005 GRAU Data Storage
2.6.6 SEE ALSO
fsepartition(8), fsejob(8), fseintro(7).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 49
2.7 NAME 49
2.7 NAME
fsejob:
Monitor execution of running FSE jobs. Show status of running FSE jobs. Man­age 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 DESCRIPTION
This FSE command monitors execution of FSE jobs. It is used to perform these FSE administrator’s tasks:
• list running FSE jobs in whole FSE implementation or on a particular FSE partition,
• show current status of an FSE job,
• abort execution of specified FSE jobs,
• change the priority of an FSE job.
Each FSE command communicates with the FSE processes through the Manage­ment Interface (fse–mif). Toexecutean 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
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 50
2.7 NAME 50
is not running, start it with the fse ––start command. There should also be a Par­tition 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). 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 .......... job identification number (JobID),
2. Partition .......... name of the FSE partition on which the job is running,
3. Type .......... job type (migration, recall, admin, maintenance, reorg, recov-
ery, backup, unknown),
4. Priority .......... current job priority,
5. Started .......... job starting date and time in the format of YYYY/MM/DD
hh:mm:ss,
6. Status .......... current job status (phase).
... A numerical value is shown for jobs which are in phase of waiting for free re­sources and a "n/a" string for jobs which already allocated the required resources.
The job id is a numerical identification of a job that consists of the start date of the job and its sequence number for that particular day.
JOB STATUS INFORMATION Job status information that is printed using the – –status option consists of two parts. First part is the same information as reported by the ––list option, in this case laid out in rows rather than in columns. For description of the reported data, see section JOB LIST INFORMATION. Second part consists of one or more lines, each with the following information:
1. Copy .......... consecutive number of migrated data copy,
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 51
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. With multi–copy migration jobs, such status line is printed for each copy that is being migrated.
2.7.3 OPTIONS
–l, – –list List FSE jobs currently running in the FSE implementation or on the spec-
ified FSE partition, if the PartitionName argument is specified. Additional option qualifiers can be used to narrow the scope of this option. For details on the information that is printed with the help of this option, see section JOB LIST INFORMATION.
–M, – –migration List migration jobs.
–R, – –recall List recall jobs.
–A, – –admin List administrative jobs.
–C, – –recovery List recovery jobs.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 52
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 combi­nation with the ––list option.
–t, – –status Show status information for the FSE job with the specified identification
number JobID. For details on the status information that is printed with the help of this option, see section JOB STATUS INFORMATION
JobID Identification number of the FSE job to show status or change the priority
for.
–a, – –abort Abort FSE jobs specified by the sequence of their identification numbers
with the JobID... argument.
JobID... A sequence of identification numbers for FSE jobs to be aborted. Identifi-
cation numbers must be separated by spaces.
–p, – –priority If no additional option is specified, change priority of the FSE job with
specified identification number JobID to priority Number. If additional – – incr option is specified, increase its current priority by value Number. If additional – –decr option is specified, decrease its current priority by value Number.
Number A value for target FSE job priority, priority increase or priority decrease.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 53
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 num-
ber 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.4 EXAMPLES
• List FSE jobs which are running on FSE partition partition_01:
fsejob –l partition_01
• List all FSE migration and recall jobs which are running in the FSE imple­mentation:
fsejob ––list – –migration ––recall
• List FSE administrative jobs which are running on FSE partition partition_­new; display each of the retrieved parameters in a separate line:
fsejob –l –A partition_new –D
• Show status of FSE job with identification number 20021203000092:
fsejob ––status 20021203000092
• Abort execution of FSE jobs with identification numbers 20021126000803 and 20021126000804:
fsejob ––abort 20021126000803 20021126000804
• Set priority of FSE job with identification number 20021125000714 to 4096:
fsejob ––priority 20021206000614 4096
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 54
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).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 55
2.8 NAME 55
2.8 NAME
fselibrary:
Manage configuration of the FSE libraries. Monitor inventoryofthe FSE libraries.
2.8.1 SYNOPSIS
fselibrary {–a | ––add} ConfigFileName fselibrary {–r | ––remove} Name [–F | – –force] fselibrary {–s | ––show Name [RevisionNumber | {–H | – –history}] fselibrary {–m | ––modify} Name ConfigFileName fselibrary {–l | ––list} [–D | ––detail] fselibrary {–i | ––show–inventory} LibraryName fselibrary {–u | ––update–inventory} LibraryName [–R | ––rescan] fselibrary ––disable Name [–F | – –force] fselibrary ––enable Name fselibrary {–h | ––help} fselibrary {–v | ––version}
2.8.2 DESCRIPTION
This FSE command manages configuration of the FSE libraries. It is used to perform these FSE administrator’s tasks:
• configure a new or remove an existing FSE library,
• retrieve the configuration of an existing FSE library,
• reconfigure an existing FSE library,
• list names and status information for configured libraries in the FSE imple­mentation,
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 56
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),
• updateResource Management Database with current status of the drivesand media in the operating FSE library,
• disable or enable operation of an FSE library.
Each FSE command communicates with the FSE processes through the Manage­ment Interface (fse–mif). Toexecutean 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.
After successful command execution fselibrary 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.8.3 OPTIONS
–a, – –add Configure a new FSE library with parameters, written in the configura-
tion file ConfigFileName. This action checks the validity of the configu­ration file, copies the file to Configuration Database and inserts the param­eter values into Resource Management Database. FSE library names are unique within the FSE implementation. If everything went fine new Li­brary Agent for this library is started afterward. Library Agent is one of the configuration–dependent FSE processes in the FSE implementation. It is responsible for handling and interpreting requests addressed to the FSE library.
ConfigFileName The name of the FSE library configuration file to use.
–r, – –remove Remove an existing FSE library from the FSE implementation. This in-
cludes shutdown of Library Agent for this library and removal of all config­uration file revisions of this FSE library from Configuration Database. Note
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 57
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. The command treats it as if FSE administrator would have an­swered the confirmation question with "Yes". This option can only be used in combination with the ––remove or ––disable option.
–s, – –show If the argument RevisionNumber is specified, print the appropriate configu-
ration revision for the FSE library 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 library Name. Configuration
history depth is the number of the configuration file revisions which are stored in Configuration Database for this FSE library. This option can only be used in combination with the ––show option.
–m, – –modify Modify the configuration of FSE library 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 library reconfiguration. During reconfiguration its Library Agent is temporarily disabled. It is shut down before reconfiguration and restarted afterward.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 58
2.8 NAME 58
–l, – –list Display status information for configured FSE libraries within the FSE im-
plementation. 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 li-
brary is attached to,
5. CtrlDev .......... library control device file,
6. Status .......... current library status (online, error, 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 .......... ID string of the library model,
2. SerialNo .......... serial number of the library,
3. VendorID .......... ID string of the library manufacturer,
4. FirmwareRev .......... revision of the firmware the library currently
uses,
5. LoadNr .......... number of drive loads performed since the library was
configured in the FSE implementation,
6. UnloadNr.......... number of drive unloads performed since the library
was configured in the FSE implementation,
7. Key .......... internal RMDB key value assigned to the library.
This option can only be used in combination with the ––list option.
–i, – –show–inventory List names and status information for configured FSE drives in the FSE li-
brary LibraryName and indexes and status information for configured FSE slots in the same library. Reported status information for an FSE drive in­cludes:
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 59
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
(<empty> 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.......... current slot status (full, in use, reserved, free, unknown),
4. Medium .......... barcode of the medium that is present in the slot.
(<empty> string is displayed if the slot is free).
Note:
A "reserved" slot is physically empty, but it is reserved for storage of the particular FSE medium, which may be currently loaded in an FSE drive or put offline.
LibraryName The name of the FSE library to show or update inventory in.
–u, – –update–inventory Trigger inventory update on the FSE library LibraryName.
–R, – –rescan Specify, that physical slot rescan has to be done during the inventory update.
This option can only be used in combination with the – –update–inventory option.
––disable Disable operation of FSE library Name. Disabling the library means putting
it offline in case it needs maintenance. Note that unless additional option ––force is specified, the command demands FSE administrator’s confirma­tion before performing this operation. Default answer to the confirmation question is "No".
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 60
2.8 NAME 60
––enable Enable operation of FSE library Name, which is currently disabled. En-
abling 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.fse
• Remove the configured FSE library named lib_main:
fselibrary –r lib_main
• Remove the configured FSE library named lib_supplemental; skip confir­mation:
fselibrary –r lib_supplemental ––force
• Show the current configuration of the FSE drive named system_lib:
fselibrary ––show system_lib
• Show the configuration history depth for FSE library named lib_archive_2:
fselibrary –s lib_archive_2 –H
• Copy current (latest) configuration revision of the FSE library named storage_library to a file storage_library_cfg.fse in the current directory:
fselibrary ––show main_library > storage_library_cfg.fse
• Apply a new configuration for the FSE library named lib_archive from the configuration file new_archive_library.fse:
fselibrary ––modify lib_archive new_archive_library.fse
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 61
2.8 NAME 61
• List names and states of the currently configured FSE libraries:
fselibrary –l
• Retrieve additional information about the currently configured FSE li­braries:
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. Perform a physical barcode rescan:
fselibrary ––update–inventory lib_email ––rescan
• Disable the FSE library named AIT_library; skip confirmation:
fselibrary ––disable AIT_library – –force
• Enable the currently disabled FSE library named LTO_library:
fselibrary ––enable LTO_library
2.8.5 FILES
/opt/fse/newconfig/fse–library.cfg (on Linux systems), %InstallPath%\newconfig\fse–library.cfg (on Windows systems)
Template for an FSE library configuration file.
2.8.6 COPYRIGHT
Copyright (C) 2004-2005 Hewlett-Packard Copyright (C) 2002-2005 GRAU Data Storage
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 62
2.8 NAME 62
2.8.7 SEE ALSO
fse(8), fsedrive(8), fsemedium(8), fsepool(8), fseintro(7).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 63
2.9 NAME 63
2.9 NAME
fsemedium:
Manage configuration of the FSE media. Format and initialize FSE media. Per­form 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.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...] [–F | – –
force] [– –no–monitor] fsemedium ––mark–unreliable Barcode [–F | – –force] fsemedium ––mark–unusable Barcode [–F | ––force] fsemedium ––mark–good Barcode [–F | ––force] fsemedium ––close–volume Barcode VolumeNumber [––no–monitor] fsemedium ––recreate–fri Barcode [{–V | – –volume} VolumeNumber...] [– –
no–monitor] fsemedium ––duplicate SourceBarcode TargetBarcode [– –no–monitor] [–F |
––force] fsemedium ––reorg Barcode [{–V | – –volume} VolumeNumber...] [– –no–
monitor] fsemedium ––copy–contents Barcode [– –no–monitor] fsemedium {–h | ––help} fsemedium {–v | ––version}
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 64
2.9 NAME 64
2.9.2 DESCRIPTION
This FSE command manages a single FSE medium. It is used to perform these FSE administrator’s tasks:
• configure a new or remove an existing FSE medium,
• list barcodes and status information for configured media in the FSE imple­mentation,
• show status information for medium volumes on configured FSE media,
• format and/or initialize a configured FSE medium,
• change an FSE medium status to unreliable, unusable, or remove either of these two statuses (change the status to "good"),
• mark an FSE medium volume as full and handle its Fast Recovery Informa­tion appropriately,
• recreate missing Fast Recovery Information on disk from the migrated meta– data,
• duplicate a medium to a medium of the same tape (copy all data and Fast Recovery Information from the source to the target medium),
• reorganizea medium or specified medium volumes preserving only the data that was determined as valid during the reorganizational scan job,
• recreate a redundant copy of the unreadable data located on damaged FSE media.
Each FSE command communicates with the FSE processes through the Manage­ment Interface (fse–mif). Toexecutean 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.
After a successful command execution fsemedium 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).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 65
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 rel­evant information from the FSE processes as long as the job that fsemedium has started is running. After the job terminates, the command exits. If monitoring is disabled, the command returns the control immediately after it has started a cor­responding 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 fsemedium runs.
Note:
The job will continue to run and will write progress to the fse.log file.
2.9.3 OPTIONS
–a, – –add Add a new FSE medium with barcode Barcode to the FSE configuration. If
additional option – –pool with the argument PoolName is specified, assign this FSE medium to the specified FSE media pool. If this option is not specified, the medium entry is added to the Resource Management Database but the medium itself is left unassigned with its configurable parameters unset.
Note:
FSE medium must be assigned to some FSE media pool, before it can be used.
Barcode The identifier of the FSE medium that is being managed. In most cases,
the identifier is a numerical barcode. With disk medium, the identifier is the relative part of the disk medium mount point (for example: dm_001, dm_002).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 66
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. Note that unless additional option ––force is specified, the command demands FSE admin­istrator’s confirmation before performing this operation. Default answer to the confirmation question is "No".
–l, – –list If this option is used alone it list barcodes and status information of the
FSE media that is configured within the FSE implementation. If additional argument Barcode with the ––volume option is specified then it shows the status of all medium volumes on medium with the specified barcode. If the argument combination ––list – –volume is used then the status of all medium volumes on all configured FSE media is displayed. Reported status information for an FSE medium includes:
1. Barcode .......... medium barcode,
2. Type .......... medium type (AIT–1, AIT–2, AIT–3, SAIT–1, LTO 1,
LTO 2, LTO 3, DDS, disk, unknown),
3. Pool .......... name of FSE media pool the medium belongs to,
4. Status .......... current status of the medium (uninitialized, free, open,
in use, full, unreliable, unusable, unknown),
5. Location .......... current location of the medium in an FSE library slot
(library name and slot number) or in an FSE drive (drive name),
6. #Vol .......... number of volumes on the medium,
7. SysVolNo .......... index of system volume (value 0 is displayed if it is
not present).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 67
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 .......... current medium volume status (empty, open, full, re-
covery, scanned, in reorg, recycled, error).
–V, – –volume There are four kinds of usage of this option in combination with other op-
tions:
– if the – –list option is specified, show status of all medium volumes on
the medium with the Barcode barcode, or status of the medium vol­umes on all media configured in the FSE implementation (if Barcode is omitted);
– if the ––init option is specified, initialize only medium volume(s)
VolumeNumber... (the medium has to be already formatted);
– if the – –recreate–fri option is specified, populate system volume on
the medium with Fast Recovery Information from this volume (if it is closed);
– if the ––reorg option is specified, reorganize only medium volume(s)
with consecutive number(s) VolumeNumber....
–D, – –detail Retrieve additional FSE medium or FSE medium volume information and
display the retrieved data in the ParameterName: ParameterValue format with each parameter in its own line.
If this option is used with the – –list option, the following additional infor­mation is reported:
– LibName .......... name of the library the medium is located in,
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 68
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 .......... 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 .......... number of accesses to the data on the volume,
– WriteNum .......... number of writings to the volume,
– OwriteNum.......... number of overwritings of the data on the volume,
– InitTime .......... date and time of the last volume initialization event,
– AccessTime .......... date and time of the last volume access event,
– WriteTime .......... date and time of the last volume write event,
– OwriteTime .......... date and time of the last volume overwrite event,
– LastVer .......... date and time of the last volume verification event,
– ValidData .......... amount of the data on the volume that was treated
as valid by the reorganizational scan job (in MB, the value equals 0 if the volume has not been scanned),
– TotalData .......... amount of the data on the volume (in MB).
–f, – –format Format a new or an already used FSE medium with barcode Barcode. If
additional option ––init is specified then the initialization of the medium
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 69
2.9 NAME 69
volumes is performed as well. Formatting an FSE medium means partition­ing 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. If the medium is not empty, its formatting is allowed only if additional option ––force is specified. Backup media need not be formatted if they are configured with a single data volume and no system volume.
–F, – –force Set forced mode for FSE medium removal, formatting, initialization, mark-
ing unreliable, marking unusable or marking "good" operation. There are three kinds of usage of this option in combination with other options. This option will:
– ifthe ––formatoption is specified, allow formatting of the FSE media
that contain valid FSE user data.
Note:
FSE medium volumes that store valid FSE user data are the vol­umes which:
store some data that is referenced by the belonging File System
*
Catalog (FSC); belong to an FSE media pool which is currently assigned to an
*
FSE partition; havethe parameter Used[%] greater than zero in the output of the
*
command fsemedium – –list ––volume.
FSE medium volumes that do not store valid FSE user data are the volumes for which any of the above criteria is not met.
– if the – –init option is specified as the first option after the command
name, allow initialization of the FSE medium volumes that contain valid FSE user data.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 70
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 an­swered the confirmation question with "Yes".
– if the ––duplicate option is specified, allow duplication also to FSE
media that either contain valid data or header such as a tar archive, ECMA or ANSI label, have already been initialized, or belong to FSE media pool that is already assigned to an FSE partition.
–i, – –init Initialize the specified or all FSE medium volumes on the FSE medium
with barcode Barcode. Initializing an FSE medium volume means (over– )writing its volume header, thus preparing this volume for usage in the FSE implementation.
Note:
FSE medium volume must be associated (via its FSE medium and FSE media pool) to an FSE partition before it can be initialized. If the medium volume is not empty, its initialization is allowed only if ad­ditional option ––force is specified. Backup media should not be ini­tialized, but formatted only.
––no–monitor Disable monitoring of the formatting, initialization, maintenance, or reorga-
nization job which is to be performed on the FSE medium. Monitoringis en­abled by default. For details on monitoring, see section JOB PROGRESS MONITORING.
VolumeNumber... A non–negative integer value or a sequence of such values which repre-
sent(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
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 71
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 Bar-
code. From that moment on, the data on the medium can be neither read nor medium can be written to. This is done by setting the status of this medium in the Resource Management Database to UNUSABLE. Note that unless additional option ––force is specified, the command demands FSE admin­istrator’s confirmation before performing this operation. Default answer to the confirmation question is "No".
––mark–good Make the FSE medium with barcode Barcode fully operational for normal
usage. From this moment on, the data on the medium can be read and the medium can be written to. This is done by removing the unreliable or un­usable status of this medium in the Resource Management Database and restoring the status that the medium had before it was marked as unreli­able or unusable. Note that unless additional option – –force is specified, the command demands FSE administrator’s confirmation before perform­ing this operation. Default answer to the confirmation question is "No".
––close–volume Mark specified FSE medium volume as full and set its status in the Re-
source Management Database accordingly. This operation also saves Fast Recovery Information (FRI) to the end part of the medium volume and to the medium’s system volume, if it is present. If writing FRI to medium fails an appropriate warning is displayed.
Note:
A full FSE medium volume is not used for writing any more. Mark­ing 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 the unreliable status of its medium is re­moved to make other medium volumes available to the FSE system again.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 72
2.9 NAME 72
If the ––no–monitor option is not specified, the progress of the mainte­nance 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 Informa­tion is also copied to the end part of these volumes.
Note:
Fast Recovery Information on disk speeds up the eventual File System Catalog recovery.
––duplicate Duplicate a source medium to a target medium of the same tape media fam-
ily. All data will be copied bit–by–bit: medium volume header (including medium volume UUID), medium volume data and Fast Recovery Informa­tion (from all data volumes as well as system volume). Target medium may not belong to any media pool that is assigned to a partition. For details, see the FSE user guide. If a user wants to replace a medium with its duplicate, then he labels the duplicate medium with original barcode and replaces the original with its copy. For details of the duplication process, see the FSE user guide.
––reorg Start the media reorganization job for the specified FSE medium or FSE
medium volume(s). If the – –no–monitor option is not specified, the progress of the reorganization job will be reported to the command out­put. Note that you can only start the reorganization job if the FSE medium volumes involved in the process have already been scanned for obsolete data. Note that the reorganization process may take a considerable amount of time. For the reorganization process details, see the FSE user guide .
––copy–contents Recreate a redundant copy of the unreadable data that is located on a dam-
aged medium. The copy is recreated from the corresponding data in another
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 73
2.9 NAME 73
FSE media pool assigned to the same FSE partition, if it exists. The recre­ated 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 op­tion is not specified, the progress of the maintenance job that performs the recreation will be reported to the command output. For details of the redun­dant copy recreation process, see the FSE user guide.
–h, – –help Print the usage information for this FSE command.
–v, – –version Print the copyright and version information for this FSE command.
2.9.4 EXAMPLES
• Add a new FSE medium with barcode backup_tape_05 to the FSE configu­ration:
fsemedium ––add backup_tape_05
• Add a new FSE medium with barcode backup_tape_10 to the FSE configu­ration and assign it to FSE media pool pool_bkp:
fsemedium –a backup_tape_10 – –pool pool_bkp
• Remove the FSE medium with barcode backup_tape_13 from the FSE con­figuration:
fsemedium –r backup_tape_13
• Remove the FSE medium with barcode backup_tape_78 from the FSE con­figuration; skip confirmation:
fsemedium –r backup_tape_78 –F
• List barcodes of the configured FSE media within the FSE implementation:
fsemedium ––list
• Show status of all medium volumes on the FSE medium with barcode archive_tape_ABB:
fsemedium –l archive_tape_ABB –V
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 74
2.9 NAME 74
• Format the FSE medium with barcode work_34; disable monitoring:
fsemedium –f work_34 ––no–monitor
• Format the FSE medium with barcode work_35 in FORCED mode and ini­tialize all FSE medium volumes on it:
fsemedium ––format work_35 –F ––init
• Initialize all medium volumes on FSE medium with barcode work_offline_­45 in FORCED mode:
fsemedium –i work_offline_45 – –force
• Initialize volume number 1 on the FSE medium with barcode tape_4a; dis­able monitoring:
fsemedium ––init tape_4a ––volume 1 – –no–monitor
• Disallow further writing to the FSE medium with barcode old_tape_23:
fsemedium ––mark–unreliable old_tape_23
• Pull the FSE medium with barcode dailyFiles_A out of the operation; skip confirmation:
fsemedium ––mark–unusable dailyFiles_A ––force
• Makethe FSE medium with barcode dailyFiles_B fully available for writing and reading:
fsemedium ––mark–good dailyFiles_B
• Mark erroneous volume number 3 on the FSE medium with barcode ait_60 as FULL and populate the volume and the medium’s system volume with Fast Recovery Information:
fsemedium ––close–volume ait_60 3
• Recreate Fast Recovery Information for data volumes 1, 2 and 4 on FSE medium with barcode weeklyFiles01; disable monitoring:
fsemedium ––recreate–fri weeklyFiles01 –V 1 2 4 ––no–monitor
• Duplicate source medium with barcode tape_44 to target medium with bar­code copytape_44; disable monitoring:
fsemedium ––duplicate tape_44 copytape_44 ––no–monitor
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 75
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.5 COPYRIGHT
Copyright (C) 2004-2005 Hewlett-Packard Copyright (C) 2002-2005 GRAU Data Storage
2.9.6 SEE ALSO
fselibrary(8), fsedrive(8), fsepool(8), fsepartition(8), fseintro(7).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 76
2.10 NAME 76
2.10 NAME
fsepartition:
Manage configuration of the FSE partitions. Scan the FSE partitions for obsolete data and report the corresponding statistics.
2.10.1 SYNOPSIS
fsepartition {–a | ––add} ConfigFileName fsepartition {–r | ––remove} Name [–F | – –force] fsepartition {–s | ––show} Name [RevisionNumber | {–H | – –history}] fsepartition {–m | ––modify} Name ConfigFileName fsepartition {–l | ––list} [–D | ––detail] fsepartition {–t | ––status} Name fsepartition ––disable Name [–F | – –force] fsepartition ––enable Name fsepartition ––reorg–scan Name ExpirationDate [NumberOfGenerations] fsepartition ––reorg–stat Name [SlackThreshold%] fsepartition {–h | ––help} fsepartition {–v | ––version}
2.10.2 DESCRIPTION
This FSE command manages configuration of FSE partitions. It is used to perform these FSE administrator’s tasks:
• configure a new or remove an existing FSE partition,
• retrieve the configuration of an existing FSE partition,
• reconfigure an existing FSE partition,
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 77
2.10 NAME 77
• list names and current status for configured partitions in the FSE implemen­tation,
• 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 Manage­ment Interface (fse–mif). Toexecutean 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.
After a successful command execution fsepartition 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).
PARTITION TYPE When configuring a new FSE partition with the – –add option, FSE administrator has the possibility to define two different FSE partition types: regular and WORM. The chosen partition type affects the characteristics of the underlying HSM file system. Regular FSE partition type uses a common HSM file system with all its features and capabilities, whereas WORM FSE par­tition type uses a modified HSM file system, a WORM HSM file system, which forbids changing contents of files once they are written to the file system.
The preferred FSE partition type can be specified by setting appropriate value for a variable in the FSE partition configuration template.
Note:
A WORM FSE partition does not necessarily need to have WORM FSE me­dia pools assigned. See the fsepool man page for details on WORM FSE media pools.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 78
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 .......... number of currently running migration jobs on
the partition,
6. # of Recall Jobs .......... number of currently running recall jobs on the
partition,
7. # of Maintenance Jobs .......... number of currently running maintenance
jobs on the partition,
8. # of Recovery Jobs .......... number of currently running recovery jobs on
the partition.
For each FSE media pool that is currently assigned to the partition the following information is printed:
1. Pool .......... media pool name,
2. Size[MB] .......... total size on the FSE media in this media pool (in MB),
3. Avail[MB] .......... total available space on the FSE media in this media pool
(in MB),
4. Used[%].......... percentage of the total used space on the FSE media in this
media pool,
5. SysSize[MB] .......... total size of all system volumes on the FSE media in
this media pool (in MB),
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 79
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 vol-
umes 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 .......... number of unreliable FSE media in this media pool,
11. #Uninit .......... number of uninitialized FSE media in this media pool.
Partition states have the following meaning:
-------------------------------------------------------------------­| STATUS | HSM FS | PARTITION | PART. MANAGER | NORMAL |
-------------------------------------------------------------------­| ready | not mounted | enabled | running | yes | | disabled | not mounted | disabled | not running | yes | | recovery mode | not mounted | enabled | running | yes | | mounted | mounted | enabled | running | yes | | error | * | enabled | not running | no | | unknown | * | * | * | no |
--------------------------------------------------------------------
... not relevant
Note:
Situations described by the lines with word no in the column NORMAL mean that the FSE administrator’s intervention is necessary to restore the normal FSE operation.
2.10.3 OPTIONS
–a, – –add Configure a new FSE partition with parameters, written in the configuration
file ConfigFileName. This action checks the validity of the configuration
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 80
2.10 NAME 80
file, copies the file to Configuration Database and inserts the parameter val­ues 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. It is responsible for managing the data flow between HSM file system and FSE media in the FSE media pools that belong to this FSE partition.
ConfigFileName The name of the FSE partition configuration file to use.
–r, – –remove Remove an existing FSE partition from the FSE implementation. This in-
cludes shutdown of Partition Manager for this partition and removal of:
– allconfiguration file revisions of this FSE partition from Configuration
Database,
FSC and HSMDB database files,media volume information from the RMDB.
Warning:
If the HSM files system of the removed FSE partition is located on an external FSE client, you must manually remove HSMDB after the par­tition configuration removal. Remove the HSMDB files by deleting the following directory on the client: /var/opt/fse/part/<PartitionName> (on Linux systems), %InstallPath%\var\part\<PartitionName> (on Windows systems).
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".
Warning:
Before using this option, FSE administrator must be familiar with con­cepts of the FSE operation and has to be well aware of the existing data
loss risk due to improper usage of – –remove.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 81
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 administra-
tor’sconfirmation 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.
–s, – –show If the argument RevisionNumber is specified, print the appropriate configu-
ration revision for the FSE partition 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 partition Name. Configuration
history depth is the number of the configuration file revisions which are stored in Configuration Database for this FSE partition. This option can only be used in combination 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.
–l, – –list Display status information for configured FSE partitions within the FSE
implementation. Reported information for an FSE partition includes:
1. Partition .......... partition name,
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 82
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. The following additional information is reported:
1. UUID .......... universal unique identifier assigned to the partition,
2. FSID .......... file system identifier in the form of the path to the device
file (on Linux systems) or the volume ID (on Windows systems).
3. Options .......... partition type indicator (regular, WORM),
4. MigIdTime.......... timestamp (in the internal FSE format) of the latest
migration job that was started on the partition,
5. MigIdCount .......... indicator of multiple migration jobs started on
the partition in a period of one second,
6. Activity .......... current partition activity (idle, job(s) running, PM not
running, reorg scan in progress, PM unreachable, HSM unreachable, recovery in progress, recovery pending, mount in progress, unknown).
This option can only be used in combination with the ––list option.
–t, – –status Show status of the FSE partition Name. See section 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 confirma­tion before performing this operation. Default answer to the confirmation question is "No".
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 83
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 reorganiza­tion job. Note that the scanning process may take a considerable amount of time. For more information on the media reorganization, see the FSE user guide.
ExpirationDate Treat all migrated file data generations that were created after Expiration-
Date as valid. You have to specify the ExpirationDate parameter in the form of "YYYY/MM/DD HH:mm:ss" or "YYYY/MM/DD". In the latter case, the time 00:00:00 is assumed. Note that if additional NumberOfGenerations parameter is specified, not all such generations may be preserved by the reorganization process. This depends on the actual value of NumberOf- Generations.
NumberOfGenerations Treat at most NumberOfGenerations latest migrated file data generations as
valid. Specifying this parameter, you can reduce the number of generations that would be preserved using the ExpirationDate parameter alone.
––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 valid (non–obsolete) data stored on the
medium (in MB),
4. Total .......... total amount of data stored on the medium (in MB),
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 84
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 reor­ganizational 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.
–h, – –help Print the usage information for this FSE command.
–v, – –version Print the copyright and version information for this FSE command.
2.10.4 EXAMPLES
• Configure a new FSE partition from the configuration file client_02_part_-
05.fse:
fsepartition ––add client_02_part_05.fse
• Remove the configured FSE partition named client_08_part_04:
fsepartition –r client_08_part_04
• Remove the configured FSE partition named client_03_part_02; skip con­firmation:
fsepartition –r client_03_part_03 ––force
• Showthe current configuration of the FSE partition named client_01_part_­02:
fsepartition ––show client_01_part_02
• Show the configuration revision 2 of the FSE partition named client_01_­part_04:
fsepartition –s client_01_part_04 2
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 85
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 direc­tory:
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.fse in current directory:
fsepartition –s fse_part_001 3 >fse_part_001_cfg_3.fse
• Apply a new configuration for the FSE partition named client_02_part_05 from the configuration file client_02_part_05_modified.fse:
fsepartition ––modify client_02_part_05 client_02_part_05_modified.fse
• List names and states of the currently configured FSE partitions:
fsepartition ––list
• Show status information for FSE partition named mail_partition_01:
fsepartition ––status mail_partition_01
• Disable the FSE partition named client_03_astro_pics; skip confirmation:
fsepartition ––disable client_03_astro_pics –F
• Enable the currently disabled FSE partition named client_01_temporary_­store:
fsepartition ––enable client_01_temporary_store
• Run the reorganizational scan job on the FSE partition named temporary_­part; treat all migrated data generations created after noon of 15th july 2004 as valid:
fsepartition ––reorg–scan temporary_part "2004/07/15 12:00:00"
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 86
2.10 NAME 86
• Run the reorganizational scan job on the FSE partition named very_­temporary_part; treat at most 15 latest migrated data generations created after 10:00 AM of 20th september 2003 as valid:
fsepartition – –reorg–scan very_temporary_part "2003/09/20 10:00:00" 15
• Display the reorganizational statistics gathered by the reorganizational scan job for the FSE partition named client_03_astro_pics; omit reporting the FSE media with FSE slack space percentage lower than 70%:
fsepartition ––reorg–stat client_03_astro_pics 70
2.10.5 FILES
/opt/fse/newconfig/fse–partition.cfg (on Linux systems), %InstallPath%\newconfig\fse–partition.cfg (on Windows systems)
Template for an FSE partition configuration file.
/opt/fse/newconfig/fse–partition–CLI–DISK.cfg (on Linux systems), %InstallPath%\newconfig\fse–partition–CLI–DISK.cfg (on Windows sys-
tems) Template for an FSE partition configuration file, with the parameters pre-
set so that the partition policies are more suitable for usage with FSE disk media.
/opt/fse/newconfig/fse–partition–NEVER–RELEASE.cfg (on Linux sys­tems),
%InstallPath%\newconfig\fse–partition–NEVER–RELEASE.cfg (on Win­dows 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
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 87
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), fsein­tro(7).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 88
2.11 NAME 88
2.11 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 DESCRIPTION
This FSE command manages configuration of the FSE media pools. It is used to perform these FSE administrator’s tasks:
• configure a new or remove an existing FSE media pool,
• retrieve the configuration of an existing FSE media pool,
• reconfigure an existing FSE media pool,
• list names and status information for configured media pools in the FSE implementation,
• report the FSE media pool–related statistics gathered during the scan for obsolete data.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 89
2.11 NAME 89
Each FSE command communicates with the FSE processes through the Manage­ment Interface (fse–mif). Toexecutean 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.
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).
MEDIA POOL TYPES There are three FSE media pool types that can be spec­ified when configuring a new FSE media pool: regular, WORM and backup.
Regular FSE media pool is used for storing data, which is migrated from an HSM file system. FSE media that belong to this type of media pool can be overwritten, reorganized, re–initialized and re–formatted.
WORM FSE media pool differs from a regular FSE media pool in one impor­tant characteristic: it is impossible to overwrite data on the media that belong to this kind of media pool. Such media are called WORM media. Data that had already been migrated to a WORM medium cannot be overwritten, it can only be appended to. A WORM medium cannot be reorganized, re–initialized or re–formatted. WORM FSE media pool type is therefore suitable for storing permanent archives and for other similar purposes.
Backup FSE media pool is essentially different from the other two FSE media pool types. FSE media in this type of media pool do not store user data migrated from an HSM file system; they hold backup copies of the FSE server state created by the fsebackup command. To be able to backup and restore the FSE server, there must be a backup FSE media pool configured, to allow backup FSE media allocation by the fsebackup and fserestore commands. A backup pool should be configured with only one volume. Backup media in this pool must be initialized. For details about FSE backup, see the fsebackup man page.
Note:
There can be only one backup FSE media pool configured in an FSE imple­mentation.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 90
2.11 NAME 90
2.11.3 OPTIONS
–a, – –add Configure a new FSE media pool with parameters, written in the configura-
tion file ConfigFileName. This action checks the validity of the configura­tion 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.
–r, – –remove Remove an existing FSE media pool from the FSE implementation. This
includes removal of all configuration file revisions of this FSE media pool from Configuration Database. 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".
Name The name of the FSE media pool to manage configuration for.
–F, – –force Set forced mode for FSE media pool removal. In this mode, FSE adminis-
trator’s confirmation of FSE media pool removal is skipped. The command treats it as if FSE administrator would have answered the confirmation ques­tion with "Yes". This option can only be used in combination with the – – remove option.
–s, – –show If the RevisionNumber argument is specified, print the appropriate configu-
ration revision for the FSE media pool Name, otherwise print the configu­ration revision in–use.
RevisionNumber A non–negative integer value which represents the configuration revision to
print.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 91
2.11 NAME 91
–H, – –history Print configuration history depth for the FSE media pool Name. Configu-
ration 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. This action checks the validity of the new configura­tion file, copies it to Configuration Database as a new configuration revision and triggers the FSE media pool reconfiguration.
–l, – –list List names and status information for configured FSE media pools within
the FSE implementation. Reported information for an FSE media pool in­cludes:
1. Pool .......... media pool name,
2. Family .......... media pool family (AIT, SAIT, LTO, disk),
3. Type .......... media pool type (regular, WORM, backup),
4. Partition .......... name of FSE partition the media pool is assigned to,
5. BlkSize[KB] .......... block size on the corresponding FSE media (in
KB),
6. #Vol .......... number of volumes on the corresponding FSE media,
7. VSize[MB] .......... size of the data volume on the corresponding FSE
media (in MB),
8. SysVol .......... system volume position (first, middle, last, none, un-
known) on the corresponding FSE media,
9. SysVol[MB] .......... size of system volume on the corresponding FSE
media (if it is present) (in MB).
See MEDIA POOL TYPES for description and usage of different FSE media pool types.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 92
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.
This option can only be used in combination 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 valid (non–obsolete) data stored on the
media of the media pool (in MB),
4. Total .......... total amount of data stored on the media of the media
pool (in MB),
5. SlackSpace .......... the percentage of storage space on FSE media that
is occupied by the data which was treated as obsolete by the reorgani­zational scan job.
For more information on the media reorganization, see the FSE user guide.
–h, – –help Print the usage information for this FSE command.
–v, – –version Print the copyright and version information for this FSE command.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 93
2.11 NAME 93
2.11.4 EXAMPLES
• Configure a new FSE media pool from the configuration file mail_archive_­pool.fse:
fsepool ––add mail_archive_pool.fse
• Remove the configured FSE media pool named system_archive_pool:
fsepool ––remove system_archive_pool
• Remove the configured FSE media pool named system_backup_pool; skip confirmation:
fsepool ––remove system_backup_pool –F
• Showthe 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
• Copyconfiguration revision 5 of the FSE media pool named mail_archive_­pool to a file mail_archive_pool_cfg_5.fse in the current directory:
fsepool –s mail_archive_pool 15 > mail_archive_pool_cfg_5.fse
• Apply a new configuration for the FSE media pool named system_archive_­pool from the configuration file new_system_archive_pool.fse:
fsepool ––modify system_archive_pool new_system_archive_pool.fse
• List names and states of the currently configured FSE media pools:
fsepool ––list
• Retrieve additional information about the currently configured FSE media pools:
fsepool –l –D
• Display the reorganizational statistics gathered by the reorganizational scan job:
fsepool ––reorg–stat
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 94
2.11 NAME 94
2.11.5 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 sys- tems),
%InstallPath%\newconfig\fse–pool–AIT–MANY–SMALL–FILES.cfg (on Windows systems)
Template for a configuration file for an FSE media pool with AIT media on which numerous files of small size will be stored.
/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–SAIT.cfg (on Linux systems), %InstallPath%\newconfig\fse–pool–SAIT.cfg (on Windows systems) Template for a configuration file for an FSE media pool with SAIT 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.
/opt/fse/newconfig/fse–pool–BKP.cfg (on Linux systems), %InstallPath%\newconfig\fse–pool–BKP.cfg (on Windows systems) Template for a configuration file for a backup FSE media pool. The template
is preset for use with LTO media, but you can modify this setting.
2.11.6 COPYRIGHT
Copyright (C) 2004-2005 Hewlett-Packard Copyright (C) 2002-2005 GRAU Data Storage
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 95
2.11 NAME 95
2.11.7 SEE ALSO
fsepartition(8), fsemedium(8), fselibrary(8), fsedrive(8), fsebackup(8), fsere­store(8), fseintro(7).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 96
2.12 NAME 96
2.12 NAME
fserecover:
Recover a File System Catalog from its redundant duplicate data sources (FSE media and Fast RecoveryInformation). Recoveran 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.
• an HSM file system (HSM FS) for the specified FSE partition in situations when it is inconsistent, damaged or missing.
FSC RECOVERYPROCEDURE A File System Catalog is regenerated either from the Fast Recovery Information (FRI) blocks, if they are present, or from the migrated metadata. For safety reasons, FRI blocks have multiple copies on different levels of FSE storage hierarchy. Their locations are the temporary files on disk, system volume on FSE media and end part of each data volume on FSE media.
The regeneration procedure always tries to choose the fastest recovery method and achievethe shortest recovery time. It starts with searching for FRI in the following order:
1. on disk (the fastest method),
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 97
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 abovemethods 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. The FSE partition for which File System Catalog recovery is running is blocked for file accesses and all incoming jobs.
IMPORTANT: If FSE processes are stopped during the recovery operation, re­covery will continue after the FSE processes will be started again.
HSM FS RECOVERY PROCEDURE An HSM file system is regenerated from the Name Space Catalog (NSC), which holds all necessary information about the HSM file system.
To recover an HSM file system from scratch the administrator has to:
1. unmount the inconsistent HSM file system
2. format the HSM file system
3. unmount the empty HSM file system (on Windows FSE clients only)
4. start recovery of the HSM file system
Recovery job can be stopped with the command:
fsejob –a <JobID>
If recovery of HSM file system is started again it will resume recov­ery from the last recovered file ID. That file ID is retrieved from the file /var/opt/fse/tmp/.<PartitionName>_hsmfs_recover (on Linux systems) or %Installpath%\var\tmp\.<PartitionName>_hsmfs_recover (on Windows sys­tems).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 98
2.12 NAME 98
This file provides data for incremental recovery after power outage or similar in­convenient 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. 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. File access and create time will be set properly, other file time attributes may be not set during recovery.
3. File will be offline.
4. Directory may not have proper change, modify, and access time set. This depends on files that are restored after directory.
LIMITATIONS
1. If NSC does not exist for particular FSE partition then HSM FS recovery from NSC is not possible. This could occur after upgrade from old version of FSE in case that NSC is not recreated for an existing FSE partition and some disaster happens.
2. It is not recommended to start recovery of HSM FS in case that NSC database is not fully recreated after upgrade of FSE system. In that case results will not be as expected.
3. Symbolic links cannot be recovered because they are not written to tape (no migration of symbolic link to FSE media).
4. Windows Alternate Data Streams (ADS) will be not fully supported for re­covery (recall of ADS is not supported yet). The names of ADS will be stored in NSC, but not data, therefore they will not be recoverable until they can be recalled from tape.
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 99
2.12 NAME 99
5. It is not allowed to stop recovery, mount HSM FS as hsmfs, use it for mi­gration 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. For
details of this process, see section HSM FS RECOVERYPROCEDURE.
–h, – –help Print the usage information for this FSE command.
–v, – –version Print the copyright and version information for this FSE command.
2.12.4 EXAMPLES
• Start recovery of the File System Catalog for FSE partition fse_fs01:
fserecover – –fsc fse_fs01
• Start recovery of the HSM file system for FSE partition fse_fs01:
fserecover – –hsmfs fse_fs01
2.12.5 COPYRIGHT
Copyright (C) 2004-2005 Hewlett-Packard Copyright (C) 2002-2005 GRAU Data Storage
HP StorageWorksFileSystemExtenderSoftware CLI reference
Page 100
2.12 NAME 100
2.12.6 SEE ALSO
fsecheck(8), fsepartition(8), fseintro(7).
HP StorageWorksFileSystemExtenderSoftware CLI reference
Loading...