Example of recall by date

Linux specific

#fsefile --recall /fse/part01/20030328/root/hsmdb.out --date "2003/03/28 16:22:28"

--into /tmp

Example of recall by file migration ID

Windows specific

C:\Program Files\Hewlett-Packard\FSE\bin>fsefile --recall i:\fse\part01\20030328\mylittledoc.doc --migid 268509426688

--into D:\tmp

Each file must be recalled separately. You define argument combination --idPartitionName

a recall by specifying a filename or by using the FileID, as shown in the examples below.

A recall on a deleted file (undelete operation) can be invoked only by using the file ID. In this case, the undeleted file will get the same name as it had when it was migrated for the last time.

Example of recall by file ID instead of filename

Linux specific

#fsefile --recall --id FSEPartition010 30600 --date "2002/12/10 15:36:50"

--into /tmp/fse_deleted_files

Windows specific

C:\Program Files\Hewlett-Packard\FSE\bin>fsefile --recall --id

FSEPartition021 17800

--date "2002/12/18 11:30:20"

--into D:\tmp\fse_deleted_files

Recalling sets of files in an efficient way

There are situations when you need to manually recall numerous files in advance, before they are actually needed. FSE enables you to perform such recalls using the so-called efficient recall functionality. Basic FSE recall functionality is optimized for manual recalls of single files, and cannot efficiently handle consecutive recalls of different files, especially in cases when the files are located on the same FSE medium. Efficient recall functionality in FSE overcomes this deficiency by enabling FSE users to specify sets of files to be recalled and efficiently handling these sets, thus significantly improving recall performance. It has the following advantages over basic recall functionality:

•The specified files are consecutively recalled according to their location on FSE media. The number of tape rewinds is reduced to a minimum - there is only one rewind per one FSE medium and one fsefile invocation. Consequently, FSE drives and media are allocated for shorter time intervals and are made more available to other FSE jobs.

•For each FSE medium from which files are recalled only one FSE job is created. This way the situations with too many pending jobs burdening the FSE implementation are avoided.

Limitations

•Using the efficient recall functionality, only latest migrated file generations can be recalled.

Recalls into a specified directory (the option --into) and recalls by file ID (the option --id) are not supported. They can only be performed one by one.

162 Monitoring and maintaining FSE