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

f
fbackup(1M) fbackup(1M)
• 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/rmt/c0t0d0BEST
When the session completes successfully, the index is automatically placed in the proper location.
WARNINGS
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.
With release 10.20, HP-UX supports large files (greater than 2GB) and increased UID/GIDs (greater than
60,000). Archives containing files with these attributes would cause severe problems on systems that do
not support the increased sizes. For this reason,
fbackup creates tapes with a new magic number
("FBACKUP_LABEL"). This prevents
fbackup tape archives from being restored on pre-10.20 HP-UX
systems.
frecover still reads both tape formats so that fbackup tape archives created on pre-10.20
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 pur-
pose for checkpoints, caution should be used when changing the checkpoint frequency parameter.
Starting with HP-UX Release 8.0, fbackup does not back up network special files because RFA network-
ing is obsolete. A warning message is issued if a network special file is encountered in the backup graph
and the file is skipped.
The use of fbackup for backing up NFS mounted file systems is not guaranteed to work as expected if the
backup is done as a privileged user. This is due to the manner in which NFS handles privileged-user access
by mapping user root and uid 0 to user nobody, usually uid -2, thus disallowing root privileges on the
remote system to a root user on the local system.
The utility set comprised of fbackup and frecover was originally designed for use on systems
equipped with not more than one gigabyte of total file system storage. Although the utilities have no pro-
gramming limitations that restrict users to this size, complete backups and recoveries of substantially
larger systems can cause a large amount of system activity due to the amount of virtual memory (swap
space) used to store the indices. Users who want to use these utilities, but are noticing poor system-wide
performance due to the size of the backup, are encouraged to back up their systems in multiple smaller ses-
sions, rather than attempting to back up the entire system at one time.
Due to present file-system limitations, files whose inode data, but not their contents, are modified while a
backup is in progress might be omitted from the next incremental backup of the same graph. Also,
fbackup does not reset the inode change times of files to their original values.
fbackup should not be used with no-rewind devices, for example, /dev/rmt/0mn .
fbackup allocates resources that are not returned to the system if it is killed in an ungraceful manner. If
it is necessary to kill fbackup, send it a SIGTERM, not a SIGKILL.
HP-UX 11i Version 1: September 2005 − 6 − Hewlett-Packard Company Section 1M−−219