HP-UX Reference (11i v1 05/09) - 1M System Administration Commands A-M (vol 3)

f
fbackup(1M) fbackup(1M)
• Maximum number of times a magnetic tape volume can be used.
• Name of a file to be executed when a volume change occurs. This file must exist and
be executable.
• Name of a file to be executed when a fatal error occurs. This file must exist and be
executable.
• The number of files between the fast search marks on DDS tapes. The cost of
these marks are negligible in terms of space on the DDS tape. Not all DDS tape dev-
ices support fast search marks.
Each entry in the configuration file consists of one line of text in the following format:
identifier, white space, argument. In the following sample configuration file, the number of
blocks per record is set to 16; the number of shared memory records is set to 16; the check-
point frequency is set to 256; the number of file reader processes is set to 2; the maximum
number of retries of an active file is set to 5; the maximum retry space for active files is set
to 5,000,000 bytes; the maximum number of times a magnetic tape volume can be used is
set to 100; the file to be executed at volume change time is
/var/adm/fbackupfiles/chgvol
; the file to be executed when a fatal error occurs
is
/var/adm/fbackupfiles/error
; and the number of files between fast search
marks on DDS tapes is set to 200.
blocksperrecord 16
records 16
checkpointfreq 256
readerprocesses 2 (maximum of 6)
maxretries 5
retrylimit 5000000
maxvoluses 100
chgvol /var/adm/fbackupfiles/chgvol
error /var/adm/fbackupfiles/error
filesperfsm 200
Each value listed is also the default value, except
chgvol and error, which default to
null values.
-d path This specifies a path to a database for use with incremental backups. It overrides the
default database file /var/adm/fbackupfiles/dates
.
-e path path specifies a tree to be excluded from the backup graph. This tree must be a subtree of
part of the backup graph. Otherwise, specifying it will not exclude any files from the
graph. There is no limit on how many times the -e option can be specified.
-f device device specifies the name of an output file. If the name of the file is
-, fbackup writes to
the standard output. There is no default output file; at least one must be specified. If more
than one output file is specified,
fbackup uses each one successively and then repeats in a
cyclical pattern. Patterns can be used in the device name in a manner resembling file name
expansion as done by the shell (see sh-bourne(1) and other shell manual entries). The pat-
terns must be protected from expansion by the shell by quoting them. The expansion of the
pattern results in all matching names being in the list of devices used.
There is slightly different behavior if remote devices are used. A device on the remote
machine can be specified in the form machine:device. fbackup creates a server process
from /usr/sbin/rmt on the remote machine to access the tape device. If
/usr/sbin/rmt does not exist on the remote system, fbackup creates a server pro-
cess from /etc/rmt on the remote machine to access the tape device. Only magnetic
tapes can be remote devices. When remote DDS tape devices are used, the fast search
marks capability is not used.
-g graph graph defines the graph file. The graph file is a text file containing the list of file names of
trees to be included or excluded from the backup graph. These trees are interpreted in the
same manner as when they are specified with the -i and -e options. Graph file entries
consist of a line beginning with either i or e, followed by white space, and then the path
name of a tree. Lines not beginning with i or e are treated as an error. There is no
default graph file. For example, to back up all of /usr except for the subtree /usr/lib,
a file could be created with the following two records:
Section 1M−−216 Hewlett-Packard Company − 3 − HP-UX 11i Version 1: September 2005