Restores filesets from tape
Synopsis
bak restoreft -server machine -aggregate name -fileset name...
[-extension name_extension] [-date
date] [-tcid tc_number] [-noaction] [-help]
Alias
bak ftrestore
Options
-server machine
Names the File Server machine to which to restore each specified fileset. Specify the File Server machine using the machine's DCE pathname, the
machine's host name, or the machine's IP address. If the fileset currently exists at a site other than the one specified with this option and the -aggregate option, you must delete the
existing fileset before restoring it to the specified site.
-aggregate name
Specifies the device name or aggregate name of the aggregate to which to restore each specified fileset. These names are specified in the first and
second fields of the entry for the aggregate in the dcelocal/var/dfs/dfstab file. If the fileset currently exists at a site other than the one specified with this option and the
-server option, you must delete the existing fileset before restoring it to the specified site.
-fileset name
Names each fileset to be restored. Provide the name of the read/write version of each fileset, even if (because of its fileset entry definition in a
fileset family) the backup version of a fileset was actually dumped. The command automatically appends a .backup extension to the name of a fileset if it can find no record in the Backup
Database of a backup performed for the fileset's read/write version.
-extension name_extension
Specifies an extension to add to the restored fileset's name to distinguish it from a fileset of the same name that currently exists in the
file system. This causes the Backup System to restore the data from tape into a new fileset independent of the existing one. Any string other than .readonly or .backup is
acceptable; if a period is to precede the extension, include it in the string provided.
-date date
Specifies the date prior to which a dump must have been made to be included in the restore. The -date option indicates a date-specific restore;
only dump sets dated before the specified date are restored. If omitted, this option defaults to 0 (zero) and a full restore of the most recently dumped version of the fileset occurs.
Otherwise, there are two types of legal values:
mm/dd/yy
Specifies 00:00 (12:00 a.m.) on the indicated date. A value of this type causes a date-specific restore containing only data from dumps done before
the indicated date (for example, 11/22/91).
mm/dd/yy hh:mm
Specifies a time on the indicated date. A value of this type causes a date-specific restore containing only data from dumps
done before the indicated date and time. The time must be in 24-hour format (for example, 20:30 is 8:30 p.m.) Surround the entire argument with " " (double quotes) because it
contains a space.
-tcid tc_number
Specifies the Tape Coordinator ID (TCID) of the Tape Coordinator for the tape drive in which you are placing the necessary tapes.
-noaction
Directs the command to produce the list of tapes necessary to perform the indicated restore without actually performing the operation.
-help
Prints the online help for this command. All other valid options specified with this option are ignored.
Description
The bak restoreft command restores the contents of each fileset indicated with the -fileset option from tape to the indicated site (File Server
machine and aggregate). By default, restores are full, recreating the fileset as it existed when it was last dumped. A full restore includes data from the last full dump and all subsequent
incremental dumps (if any). If incremental dumps exist, you are prompted to insert the necessary tapes into the tape drive. To have the command produce a list of the tapes that the Backup System
would need to perform the indicated restore without actually performing the operation, include the -noaction option with the command.
You can also choose to do a date-specific restore by including the -date option. A date-specific restore returns the fileset to the state it was in at its last dump before the indicated date. Rather than including all dumps to the final one done, it includes only the last full dump and any incremental dumps done before the indicated date.
The precise effect of a restore depends on whether the fileset currently exists in the file system and whether you want to preserve its current state. To replace the current contents of a fileset with data restored from tape, omit the -extension option. The results are as follows:
· If the -server and -aggregate options specify the fileset's current site, the restored data overwrites the fileset's current contents. There is no change in the Fileset Location Database (FLDB) entry for the fileset.
· If the -server and -aggregate options specify a new site, the restored data is stored in a new fileset at the indicated site. If you name a new site and the fileset to be restored currently exists at its old site, you must do one of the following before issuing the command:
- Use the fts zap command to delete the existing fileset. The 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 fileset receives a new FLDB entry and a new fileset ID number.
Using the fts zap command is the better approach because it preserves the 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 restoreft command fails if you do not use the fts zap or fts delete command to delete the existing fileset before using the bak restoreft command to restore the fileset to the new site.
To preserve a fileset's current contents but also introduce a restored version into the file system, use the -extension option. A new fileset at the site specified with the -server and -aggregate options then contains the restored data. It has the same name as the current fileset, with the addition of the distinguishing extension. The Fileset Location (FL) Server automatically assigns the new fileset a fileset ID number and a new FLDB entry, which records all of the appropriate information about the new fileset.
You can also restore a fileset that no longer exists in the file system. A new fileset at the site specified with the -server and -aggregate options is created to contain the restored data.
Data can be dumped and restored between different types of file systems. For example, data dumped from a DCE LFS fileset can be restored to a DCE LFS fileset or to any type of non-LFS fileset; likewise, data dumped from a non-LFS fileset can be restored to a DCE LFS fileset or to a different type of non-LFS fileset. (See your vendor's documentation to verify the level of support for dump and restore operations between different types of file systems.)
Restored data is translated into the appropriate format for the file system to which it is restored. Note that incompatible information may be lost when a fileset is dumped and restored between different types of file systems. For example, ACLs on objects in a DCE LFS fileset may be lost if the fileset is restored to a file system that does not support ACLs.
Use the bak restoredisk command to restore the contents of an entire aggregate. Use the bak restoreftfamily command to restore a fileset family or to restore one or more filesets to the same site or to different sites.
Privilege Required
The issuer must be listed in the admin.bak files on all Backup Database machines. The issuer must also be listed in the admin.fl files on
all Fileset Database machines and in the admin.ft file on the File Server machine to which filesets are to be restored.
Cautions
Overwriting an existing fileset destroys any files created in the current fileset after the date of the last dump included in the restore. It is always safer to
preserve the current fileset by using the -extension option to restore data to a new fileset.
Output
If you do not include the -noaction option, the bak restoreft command returns the unique dump ID number associated with the restore operation. The dump
ID is displayed in the command window directly following the command line and in the Tape Coordinator's monitoring window if the butc command is issued with debug level 1. The dump ID
number is not the same as the job ID number visible with the (bak) jobs command if the bak restoreft command is issued in interactive mode.
If you include the -noaction option, a Tapes needed: header is displayed, followed by a list of the tapes necessary to complete the restore operation. No dump ID number is reported because none is assigned.
Examples
The following command restores the fileset named user.pat to the aggregate named /dev/lv01 on the File Server machine named
/.../abc.com/hosts/fs5:
$ bak restoreft /.../abc.com/hosts/fs5 /dev/lv01 user.pat
Starting restore
bak: dump ID of restore operation: 187
bak: Finished doing restore
Related Information
Commands: bak dump(8dfs)
Files: dfstab(4dfs)