Determining the unusable media

FSE detects read errors when recalling the migrated data from FSE disk or tape media to an HSM file system. After a read error is detected, the status of the FSE medium is automatically set to unusable.

CAUTION: Before treating an FSE medium as unreadable, make sure it is not loaded in a faulty tape drive. In certain circumstances, an FSE medium may acquire the unusable status because of problems with the tape drive in which it is loaded. In this situation, the status of the drive itself is set to error.

You can get a list of all currently unusable media by filtering the output of the fsemedium --listcommand, as follows:

Linux specific

# fsemedium --list grep unusable Windows specific

%InstallPath%\bin>fsemedium --list find "unusable"

The command output will be similar to the following:

000016

LTO-1

LTO-pool_1

unusable

lib:SA:4

 

1

0

000025

LTO-2

LTO-pool_2

unusable

drv:drive_2

(lib:SA:4)

1

0

000103

LTO-3

LTO-pool_3

unusable

drv:drive_1

(lib:SA:6)

1

0

For more information on the fsemedium command, see the FSE CLI reference.

Starting redundant copy recreation

The recreation process is executed for a single FSE medium at a time. The medium does not have to be allocated or loaded into an FSE drive. To start the redundant copy recreation process, invoke the following command:

fsemedium --copy-contents Barcode [--no-monitor]

By default, fsemedium reports the progress of the maintenance job to the standard output and enables you to monitor the recreation process in the command shell. You can disable monitoring (make fsemedium return to the command prompt immediately) by specifying the --no-monitoroption.

With monitoring enabled, the command generates an output similar to the following:

fsemedium --copy-contents 020776

[11:42:09] Started (JobID: 20040121000002).

[11:42:09] Preparing list of source media

[11:42:09] 2 media needed for recall (bc: 050003, 050004)

[11:42:09] Request resources (bc: 050003) ...

[11:42:09] Resources allocated.

[11:42:09] Medium 050003 is already present in drive drv1.

[11:42:09] Starting Back End Agent.

[11:43:58] Medium 050003, volume 1: Reading files…

[12:20:58] Medium 050003, volume 1: Files written to disk buffer.

[12:46:02] Reading finished, releasing resources.

[12:47:12] Requesting resources...

[12:47:12] Resources allocated.

[12:48:42] Loading medium 050010 to drive drv2.

HP StorageWorks File System Extender Software user guide 115