HP-UX System Administrator's Guide: Routine Management Tasks HP-UX 11i v3 (B3921-90023, September 2010)

This example will back up the entire structure except the invoices directory. The device
file for this example is /dev/rmt/1h, specified using the -f option. For this example,
we need to plan for the incremental backup (next example), so we must do three things:
1. Use a graph file to specify which files will be included/excluded.
2. Specify the -u option to update the file /var/adm/fbackupfiles/dates.
3. Specify a backup level.
Because this will be a full backup, we'll use the backup level 0. Any backup level would
do as long as it is the lowest backup level in use. See Backup Levels for details about
how backup levels are interpreted by fbackup.
The graph file for this example will be /var/adm/fbackupfiles/graphs/g1 and the contents
will look like:
i /home
e /home/text/invoices
The fbackup command to accomplish the above is:
fbackup -f /dev/rmt/1h -0 -u -g /var/adm/fbackupfiles/graphs/g1
Example: Incremental Backup to a DLT Tape
This example is an extension of the previous one. All characteristics of the previous
example will remain the same except that this will be an incremental backup at a point
in time following the previous example's backup.
We'll use the backup level 5. The exact number is not critical as long as it is higher than
the level used in the previous example. See Backup Levels for details about how backup
levels are interpreted by fbackup.
fbackup -f /dev/rmt/1h -5 -u -g /var/adm/fbackupfiles/graphs/g1
Example: Backing Up to Two Devices
This example will show how it is possible to specify more than one device to receive
the output from fbackup. When more than one device is specified, the second one is
written to when the media on the first device has filled up. If the media on the first
device fills up and the remaining data to be backed up will fit on the media on the
second device, an unattended backup possible. With only one device, a media change
would be required in this situation.
Also, in this example, an index file will be created called /tmp/index. An index is
written to the beginning of each tape, listing all files in the specified graph being backed
up. However, if a file is removed after the index is written but before the file is backed
up to tape (or something else happens that prevents the file from being backed up),
the index will not be completely accurate. If you tell fbackup to make an online index
file (using the -I option), it will create the file after the backup is complete. Therefore,
the online index file will be completely accurate with respect to which files are on each
volume of the backup.
Backing Up Data 131