Command Reference Guide

2.12 NAME 86
fileID 1. When the recovery is need from the scratch then that file has to be
deleted. At the end of successful recovery operation this file will be 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
depend 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 a 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 has 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.
5. It is not allowed to stop recovery, mount HSM FS as hsmfs, use it for mi-
gration and later resume recovery.
File System Extender 3.2 Command Line Reference