3.Start the recovery of the HSM file system by invoking the following command on the consolidated FSE system or FSE server:
#fserecover
Windows specific
To recover an HSM file system on a Windows FSE client:
1.Using the fsepartition
C:\>fse
2.Format the HSM file system using Computer Management or the format command.
3.Unmount the HSM file system once again as described in step 1.
4.Start recovery of the HSM file system by invoking the following command on the consolidated FSE system or FSE server:
C:\>fserecover
Assuming the prerequisites are met, the recovery process will start recreating the file system structure as follows:
1.The recovery job checks if the recovery has already been started so it can be resumed from the last recovered fileID.
2.It verifies that the HSM file system is not mounted and then mounts it on the temporary mount point.
3.It removes the existing HSMDB.
4.It scans the FSC and recovers the file system.
5.The FSC scanner retains the last recovered file ID that is written in the recovery progress status file. This enables file system recovery to be resumed after a power failure or other interruptions. In case this file is lost, recovery is started from the beginning. If you want to start an interrupted recovery from the start, you need to delete this file.
Linux specific
On Linux platform, the full pathname of the recovery progress status file is
/var/opt/fse/tmp/.PartitionName_hsmfs_recover. Windows specific
On Windows platform, the full pathname of the recovery progress status file is
%InstallPath%\var\tmp\.PartitionName_hsmfs_recover.
The value of %InstallPath% depends on the choice made in the FSE installation process. It defaults to C:\Program
6.It unmounts the temporarily mounted HSM FS and removes temporary mount points and device files.
Status of user data on the recovered HSM file system
Once the HSM file system is recovered, the states of directories and files are as follows:
•Directories may not have proper change, modify, and access time set.
•All files are offline.
Since the files are offline after the recovery is complete, they are automatically recalled as needed. You can also manually recall them using the fsefile command.
•File indexes (Windows specific) and
•File access and creation times are the same as their originals, but other file time attributes may not have their original values.
The File System Catalog may contain multiple file system object entries with different file IDs mapping to the same pathname on the HSM file system, most probably as a consequence of move, rename, or delete and create operations. The recovery process detects such objects and handles them appropriately.
File system objects that map to the same pathname are recreated as follows:
HP StorageWorks File System Extender Software user guide 237