User's Manual

222 Backup, restore, and recovery
How it works?
You need to ensure that the prerequisites are met and consider the backup process, before you start
backing up the FSE implementation.
Prerequisites
Common
• If tape will be used as a backup destination, backup FSE media pool and backup FSE media have to
be configured.
For more information on the configuration procedures, see section ”Backup media management” on
page 223.
Linux specific
• All FSE components that will be backed up, except the global configuration files, must reside on LVM
logical volumes.
• Parameters in the FSE backup configuration file should be set appropriately.
For details, see section ”Backup configuration file on Linux platform” on page 222 or the fsebackup
man page.
• The dm-snapshot module must be loaded.
SUSE Linux specific
For information on how to load the dm-snapshot module and configure its automatic loading at
system startup, see section ”Loading the dm-snapshot module on SUSE Linux operating system” on
page 222.
Windows 2000 Server specific
• StorageCraft Volume Snapshot must be installed on the system. Note that snapshots are not visible as
drive letters and are available only to the fsebackup command.
Backup configuration file on Linux platform
FSE backup configuration template and FSE backup configuration file are named backup.cfg. FSE
backup configuration template is located in the directory /opt/fse/newconfig. FSE backup
configuration file is located in the directory /etc/opt/fse.
In the FSE backup configuration file, you can only configure the parameter SNAPSHOT_PCT, which
represents percentage of the ordinary logical volume size that is reserved for the LVM snapshot.
SNAPSHOT_PCT defaults to ten percent (10 %). You should increase this value if there is high traffic
expected on the HSM file system with many changes to the file system contents while FSE backup process
is in progress.
Loading the dm-snapshot module on SUSE Linux operating system
On the supported SUSE Linux operating system, the dm-snapshot module, which is required for the FSE
backup, is not loaded automatically.
To load the module, invoke the following command:
To configure automatic loading of the module at subsequent system startups, add the string dm-snapshot
to the variable MODULES_LOADED_ON_BOOT in the file /etc/sysconfig/kernel, like shown in the
following example:
# modprobe dm-snapshot
## Type: string
## ServiceRestart: boot.loadmodules
#
# This variable contains the list of modules to be loaded
# once the main filesystem is active