User's Manual

100 Managing media
Dedicate a disk with high performance for FSE software installation and HSM file systems. Such a disk
serves as a primary storage space of files with high frequency of user access, which may affect the
performance of the whole FSE implementation. A performance disk is not meant to be a secondary storage
space (file archive storage), thus its capacity is not as important as its high performance, which enables
optimal operation of FSE.
Capacity disk
A capacity disk in the FSE implementation can serve two purposes: to provide storage for FSE disk media
or to provide storage for file systems assigned to the FSE disk buffer.
When used for FSE disk media, it should provide large archive storage space in order to store the migrated
generations of the files located on the HSM file systems. Frequency of user accesses to these files is
relatively low compared to that of the HSM file systems located on the performance disks.
When used for file systems assigned to the FSE disk buffer, it should provide enough storage space to
temporarily store files for migrations and recalls.
The available space on disk media in an FSE disk media pool should correlate to the available space on
the tape media in the FSE tape media pool assigned to the same FSE partition. The FSE tape media pool is
typically used for storing the first copies. Suppose that the tape media pool contains 20 LTO Ultrium 1
media (approximately 20 * 200 GB of available space); the corresponding disk media pool should have
4 TB of available space.
NOTE: HP recommends that a separate file system or volume (disk partition) is assigned to FSE disk buffer
to improve robustness and to avoid potential data loss.
If currently allocated storage space for FSE disk buffer is running out, you can extend FSE disk buffer with
additional file systems or volumes. For details, see chapter ”Monitoring and maintaining FSE”, section
”Extending storage space of FSE disk buffer” on page 176.
For details on the required file system layout, see the FSE installation guide for a particular platform,
chapter ”Introduction and preparation basics”, section ”Organizing the file system layout”.
Local and remote file systems as disk media
FSE supports local file systems to be configured as disk media.
Linux specific
On Linux platform, it is possible to use remote file systems as disk media and to access them via the NFS or
CIFS protocol.
NOTE: If you are configuring a remote file system as a disk medium, you can mount only a complete file
system created for this purpose; mounting shared directories (subtree of a file system) is not supported.
Linux specific
On Linux platform, a file system that will be configured as a disk medium must be mounted to a
subdirectory of /var/opt/fse/dm, for example:
Mounting a file system includes adding appropriate file system entries to the /etc/fstab file. For
automating the mounting, see the man pages for the fstab and mount commands.
Remote file systems are mounted via the NFS protocol. Note that when using an NFS volume as a disk
medium, you must export a file system with the no_squash_root parameter to enable root to access
the file system.
/var/opt/fse/dm/dm000001
/var/opt/fse/dm/dm000002