Use the -file option of the bak restoreftfamily command to restore each fileset that has an entry in a specified file. The command examines the Backup Database to determine the tapes that contain the last full dump and all subsequent incremental dumps of each specified fileset and each fileset to the site indicated in the specified file. It does not consult the FLDB.
An entry for a fileset in a file to be used with the command must have the following format:
machine aggregate fileset [comments …]
The entry provides the following information:
machine
Specifies the file Server machine to which the fileset is to be restored. Identify the machine by its DCE path name (for example, /../abc/com/hosts/fs1), its
host name (for example, fs1.abc.com), or its IP address (for example, 11.22.33.44).
aggregate
Specifies the aggregate to which the fileset is to be restored. Identify the aggregate by its device name (for example, /dev/lv01) or by its aggregate name
(for example, lfs1). These names are specified in the first and second fields of the entry for the aggregate in the dcelocal/var/dfs/dfstab file.
fileset
Specifies the fileset to be restored. Specify the name of the read/write version of the fileset, even if the backup version of the fileset was actually dumped. The
command automatically appends a .backup extension to the name of the fileset if it can find no record in the Backup Database of a backup performed for the read/write version. (Note that you
can specify the name of the backup version of the fileset if the backup version was dumped to tape.)
comments …
All remaining text. The command treats any other text provided with the entry for the fileset as a comment and ignores it. Any additional text
is optional.
Do not use wildcards (for example, .*) in an entry. Also, do not include a newline character in an entry. Each entry must appear on a single line of the file. The command uses only the first line for a given fileset; it ignores all subsequent lines for the fileset.
If you restore a fileset to the site at which it currently exists, the command overwrites the existing version of the fileset. If you restore a fileset to a site other than the site at which it currently exists, you must do one of the following before issuing the command:
· Use the fts zap command to delete the existing fileset. The restored fileset continues to use its existing FLDB entry and fileset ID number, and the fileset's FLDB entry is updated to record the new site.
· Use the fts delete command to delete the existing fileset and its FLDB entry. The restored fileset receives anew FLDB entry and a new fileset ID number.
Using the fts zap command is the better approach because it preserves a fileset's existing ID number, which allows Cache Managers to continue to access the fileset without updating their tables of mappings between fileset names and fileset ID numbers. The bak restoreftfamily command fails if you do not use the fts zap or fts delete command to delete an existing fileset before using the bak restoreftfamily command to restore the fileset to a new site.