User's Manual

HP StorageWorks File System Extender Software user guide 11
HSM file systems can be exported to be accessed via NFS protocol.
Access using CIFS protocol is enabled by a specially customized Samba package. Files that are written to
or read from an HSM file system through a Samba connection are handled like all other files created or
accessed locally on the HSM file system. The customized package enables Samba to notify remote CIFS
clients (especially Windows Explorer on Windows platform) when a file is offline, thus preventing
unnecessary recalls of offline files. For further information on Samba integration, see the FSE release notes.
Windows FSE system specific
FSE supports remote access to FSE partitions through regular CIFS protocol (Windows shares) without any
further requirements.
FSE architecture
FSE takes complete control over the HSM file systems, thus maximizing their operational efficiency.
Handling of the files residing on the HSM file systems is defined with different policies.
Basically, FSE copies new or modified file information from a file on an HSM file system to FSE media,
releases rarely used files and makes them offline, and recalls offline files when necessary. These are the
principal FSE operations, called migration, release, and recall.
Figure 2 Main operations in FSE
FSE operations
FSE main operations are migration, release, recall, and deletion. They are configured with user-defined
policies. For more information on configuring policies, see ”Migration, release, recall, and deletion” on
page 123. After they are configured, the policies enable automatic, unattended execution of the
corresponding operations. However, these operations can also be triggered manually using the fsefile
command. For details on manual triggering, see the FSE CLI reference.
Regardless of how they are invoked, the migration, recall, and deletion operations are represented and
controlled in the FSE implementation by so-called FSE jobs. Using the fsejob command, an FSE
administrator can display information about existing jobs or manipulate them. Example situations when
such manipulation is needed are the following:
• the priority of a particular recall job has to be increased, because urgently needed documents have to
be recalled from FSE media, and there are currently other jobs with higher priorities running in the FSE
implementation.
• a library in the FSE implementation has run out of FSE media and therefore additional media need to
be added to it and initialized, in order to get the media available and migration jobs running again.
For details on monitoring FSE jobs, see ”Monitoring FSE jobs” on page 157. For more information about
the fsejob command, see the FSE CLI reference.
Migration
Migration is a process of copying files from the HSM file system to FSE media. If a file is not modified for a
configured period of time, it passes the so-called file age check and becomes a candidate for migration
(migration candidate).
Migration is done in two steps: