User's Manual

176 Backup, restore, and recovery
Linux specific
On Linux platform, DeviceFile is represented as the string /dev/sgX.
Windows specific
On Windows platform, DeviceFile is represented as the string id:P:B:T:L.
For details on how to identify SCSI device addresses or IDs, see ”About SCSI identification” on
page 60 in chapter ”Configuring FSE” on page 37.
The LTO Ultrium medium is now ready to be used in the FSE backup pool.
Estimating backup frequency
You need to estimate how often you should run an FSE backup. Analyze your needs and your environment
with regard to the backup duration time and the FSE usage policy.
Note that you cannot run more than one fsebackup at a time and that backup frequency depends on the
FSE usage policy. If there is a lot of traffic on your file system and big changes are frequent, this should be
reflected in your plans for backup. The more frequent the changes on the file system, the more frequent
your backups should be. Once you determine these factors, schedule your backups accordingly:
Linux specific
Using the crontab command, configure a regular cron job that will start fsebackup with the desired
frequency and backup set.
Windows specific
Schedule a task to run the fsebackup command at a specified time using either Scheduled Task Wizard
or the at command. To start Scheduled Task Wizard, click Start > Settings > Control Panel, double-click
Scheduled Tasks, and then double-click Add Scheduled Tasks.
NOTE: It is recommended that you perform your backups on a daily basis. You should have at least two
separate sets of backup media and alternate their use, thus ensuring that there is always at least one
successful backup media set available for restore.
Modifying backup configuration on Linux platform
On Linux systems, FSE provides a backup.cfg file in the /etc/opt/fse directory. It can be used for
backup configurations if the defaults do not suit your needs. You can specify different logical
groups/volumes for /var/opt/fse and /var/opt/fse/part mount points according to your specific
configuration. You can also modify the default LVM snapshot size (as a percentage of the original logical
volume size, default is 10). Increase the default value if there are many changes expected on the HSM file
system while the backup is in progress.
If the /etc/opt/fse/backup.cfg file is not found, default values are used for the FSE backup process.
The fsebackup command
FSE backup is started with the fsebackup command, followed by the mandatory --media Barcode
option. When performing a full backup, you need to use the general --client option, while backing up
a specific client requires using the --client ClientName command option.
If you do not want to back up the HSM file system, you can use option --skip-hsmfs together with the
--client option. This way only metadata of the FSE partition (HSMDB) is backed up, while the HSM file
system is skipped. Exceptions to this are symbolic links, file extended attributes (EAs) and access control
lists (ACLs), which are ignored and need to be backed up separately if the file system is not backed up.
Example of backing up an FSE server
The FSE server is going to be backed up to the FSE medium with barcode 100190:
fsebackup --media Barcode [--client ClientName]
# fsebackup --media 100190