[12:49:09] Starting Back End Agent.
[12:49:58] Medium 050010, volume 3: Writing disk buffer.
[13:00:58] Medium 050010, volume 3: Disk buffer written to medium volume.
[13:11:50] Writing finished, releasing resources.
[11:42:09] Request resources (bc: 050004) ...
[11:42:09] Resources allocated.
[11:42:09] Medium 050004 is already present in drive drv3.
[11:42:09] Starting Back End Agent.
[12:21:02] Medium 050004, volume 2: Reading files.
[12:45:58] Medium 050004, volume 2: Files written to disk buffer.
[12:46:02] Reading finished, releasing resources.
[12:47:12] Requesting resources...
[12:47:12] Resources allocated.
[11:42:09] Medium 050010 is already present in drive drv2.
[12:49:09] Starting Back End Agent.
[12:49:58] Medium 050010, volume 3: Writing disk buffer.
[13:00:58] Medium 050010, volume 3: Disk buffer written to medium volume.
[13:11:50] Writing finished, releasing resources.
[13:12:38] Finished.
Regardless of the monitoring setting, the fsemedium command logs the recreation process progress into the FSE event log, while any errors encountered during the recreation process are logged into the FSE error log.
Linux specific
On Linux platform, FSE error log is located in the directory /var/opt/fse/log.
Windows specific
On Windows platform, FSE error log is located in the directory %InstallPath%\var\log.
The value of %InstallPath% depends on the choice made in the FSE installation process. It defaults to C:\Program
In terms of data safety, a configuration with only one FSE media pool assigned to a particular FSE partition is dangerous. If a damaged, unusable FSE medium is part of such an FSE media pool, the only migrated data copy is permanently lost. The only exceptions are the migrated file generations on the unusable medium that are still present on the HSM file system. These file generations would normally be lost during their release, but you can prevent their loss by manually adding them to the dirty file list.
To put online files on the dirty file list, enter the following command at the command prompt:
fsefile
Note that fsefile must be run on the FSE client that hosts the FSE partition.
The command puts all specified files on the dirty file list. This way, the files are scheduled for regular migration according to the migration policy defined for the FSE partition. To migrate the files immediately after the MinFileAge interval for these files has expired, use the fsefile
For details on the MinFileAge parameter, see ”Migration policy parameters” on page 127.
For more information on the fsefile command, see the FSE CLI reference.
116 Managing media