Backup and Restore 2 Manual

BRCOM RESTORE Command
Backup and Restore 2 Manual—522696-019
7-59
OSS Restore Examples
Restoring OSS Objects Including Mount Points
To include the files from another fileset in the restore, specify the
FOLLOWMOUNTPTS ON job option. For example:
BR> RESTORE =mytape, OSS /usr, FOLLOWMOUNTPTS ON ;
In this example, /local is a mount point in this OSS directory structure:
/usr/bin
/usr/local/home
/usr/local/home/fred
/usr/local/home/bill

If the local fileset is mounted on the OSS file-system prior to the restore
operation, local remains a mounted fileset after the restore.

However, if /local is not mounted on the OSS file system prior to the restore,
/local becomes a directory on the /usr fileset and not a separately mounted
fileset.
Restoring OSS Objects Excluding Mount Points
To restrict the restore to objects destined for the fileset to which the specified target
directory belongs, use the FOLLOWMPOUNTPTS OFF job option. For example:
BR> RESTORE =mytape, OSS /usr, FOLLOWMOUNTPTS OFF ;
The /local directory is a mount point in this OSS directory structure:
/usr/bin
/usr/local/home
/usr/local/home/fred
/usr/local/home/bill
This directory is produced:
/usr/bin
Because the /local directory is a mount point, the /home subdirectory and the fred
and bill files are not restored.
The mount point exclusion applies to the entire set of directories and files, not to the
objects on tape. OSS fileset information is not stored for objects on tape.
Restoring OSS Hard Links
A hard-linked file has multiple file names associated with a single inode number. The
inode number is the internal storage pointer to the disk file. In these examples, the
/usr/project/file1, /usr/project/file2, and /usr/project/file3 are
hard links to the same file.