fbackup.1m (2010 09)

f
fbackup(1M) fbackup(1M)
(TO BE OBSOLETED)
/usr/sbin/fbackup -0i /usr -e /usr/lib -f /dev/rtape/tape4QIC150
The second example is more complicated, and assumes the user wants to maintain a database of past
fbackup sessions so that incremental backups are possible.
If sufficient on-line storage is available, it may be desirable to keep several of the most recent index files
on disk. This eliminates the need to recover the index from the backup media to determine if the files to
be recovered are on that set. One method of maintaining on-line index files is outlined below. The sys-
tem administrator must do the following once before
fbackup is run for the first time (creating inter-
mediate level directories where necessary):
• Create a suitable configuration file called
config in the directory
/var/adm/fbackupfiles
.
• Create a graph file called
usr-usrlib in the directory
/var/adm/fbackupfiles/graphs
.
• Create a directory called
usr-usrlib in the directory
/var/adm/fbackupfiles/indices
.
A shell script that performs the following tasks could be run for each
fbackup session:
• Build an index file path name based on both the graph file used (passed as a parameter to the
script) and the start time of the session (obtained from the system). For example:
/var/adm/fbackupfiles/indices/usr-usrlib/871128.15:17
(for Nov 28, 1987 at 3:17 PM)
• Invoke
fbackup with this path name as its index file name. For example:
cd /var/adm/fbackupfiles
/usr/sbin/fbackup -0uc config -g graphs/usr-usrlib\
-I indices/usr-usrlib/871128.15:17\
-f /dev/rtape/tape4QIC150
When the session completes successfully, the index is automatically placed in the proper location.
WARNINGS
The
fbackup, frecover, and ftio commands are deprecated for creating new archives. In a future
HP-UX release, creation of new archives with these commands will not be supported. Support will be
continued for archive retrieval. Use the standard pax command (portable archive interchange) to create
archives. See pax (1).
fbackup consists of multiple executable objects, all of which are expected to reside in directory
/usr/sbin.
fbackup does not require special privileges. However, if the user does not have access to a given file,
the file is not backed up.
For security reasons, configuration files and the
chgvol and error executable files should only be writ-
able by their owners.
In HP-UX 11i Version 3, the maximum value for fields returned via
uname() was increased (from 8 to
256). To accommodate the larger size, a format change was necessary. A new magic number,
FBACKUP*LABEL, was created to distinguish this new format.
Likewise with HP-UX 10.20, HP-UX added support for large files (greater than 2GB) and increased
UID/GIDs (greater than 60,000). The magic number associated with this release through HP-UX 11i Ver-
sion 2 (inclusive) is
FBACKUP_LABEL.
Archives and files with formats and attributes that are unsupported on previous HP-UX releases could
cause severe problems or unpredictable behavior if attempts were made to restore onto these systems.
For this reason,
fbackup creates tapes with a magic number that is only recognized on releases which
support the features and format being archived. This prevents fbackup tape archives from being
restored on earlier HP-UX systems than are supported. frecover still reads all tape formats so that
fbackup tape archives created on earlier HP-UX systems can be restored.
EOF marks are used for checkpointing on all magnetic tape devices. On DLT tape devices, these EOF
marks are also used for fast searching on a selective recovery; "fast searching" in this case means spacing
to the nearest checkpoint before the desired file, and then reading until the file is found. With this dual
purpose for checkpoints, caution should be used when changing the checkpoint frequency parameter.
6 Hewlett-Packard Company − 6 − HP-UX 11i Version 3: September 2010