Installation Manual

12 Introduction and preparation basics
IMPORTANT: In a mixed FSE implementation, if the FSE processes on the consolidated FSE system are
restarted, you must restart the FSE processes on all external FSE clients to resume the normal FSE operation.
Licensing
There are both per machine and capacity-based licenses for HP File System Extender.
• For every machine that runs an FSE client, you need an FSE client license appropriate to the operating
system.
• For every machine that runs the FSE server, you need a base license appropriate to the operating
system. The base license includes a license to migrate 1 TB to secondary storage managed by the FSE
server.
• To migrate more than 1 TB to the secondary storage, you need additional FSE server capacity licenses.
These are available in 1 TB increments. The migrated capacity is the sum of all capacity migrated to
the secondary storage from all associated FSE clients, including all copies where two or more copies of
migrated files are configured, and all versions of modified migrated files.
• To upgrade the FSE client-managed file system to WORM you need a capacity-based license. This is
available in 1 TB increments. The capacity for this WORM license is based on the physical capacity
occupied by the upgraded FSE file system on the production disk.
Preparing file systems for FSE
In order to optimize operation of the FSE implementation and increase its reliability, you should organize
file systems on the host that will become the FSE server, as well as on the FSE client. If you intend to use
disk media, you also need to prepare file systems to hold disk media files.
The following sections explain the importance of preparing file systems for FSE operation and provide
formulas to estimate the required space for FSE components. These explanations and formulas apply
generally when configuring an FSE implementation. The preparation is described in ”Preparing file
systems” on page 27.
The following table summarizes the main parameters to be considered when setting up the environment.
These parameters are discussed later in this chapter.
Table 2 Pre-installation size considerations
Parameter Description Reference
HSM file system size Determine the minimum HSM file
system size using such data as
expected number of files and
average file size.
”
Formula for the expected HSM
f
ile system size
” on page 15
Fast Recovery Information (FRI) size Determine the expected size of FRI. ”
Formula for the expected size of
Fast R
ecovery Information
” on
page 15
File System Catalog (FSC) size FSC contains location history and
metadata. Determine expected size
of FSC.
”
Formula for the expected File
Sy
stem Catalog size
” on page 15
HSM database (HSMDB) size Determine expected HSM database
size
”
Formula for the expected
Hie
rarchical Storage Manager
Databas
e (HSMDB) size
” on
page 16