Restoring incremental backups
Incremental restores build on each other the way incremental backups build on the initial level-0 backup. Therefore, to restore an incremental backup, you need all the backup tapes from the level-0 backup through the last backup that you want to restore.
Specifying a full restore
A full restore rebuilds the file system, qtree, or subtree that was in the backup that a tape file contains.
What a table-of-contents restore is
You can display a table of contents of the files or qtrees in a tape file for a tape restore. This is useful in determining what files or qtrees exist on a tape and their locations. For qtrees, the restore lists the qtree properties.
Specifying a resume restore
If an entire tape file restore is stopped, you can resume the restore and avoid restoring again what has already been restored. However, there are some restrictions on this operation.
Specifying tape devices in the restore command
When you performed a backup, you specified one or more tape devices. The files written by these devices can be on one or more tapes. When restoring, you have to list the tape devices in the same order that you used in the backup.
Specifying a single tape file on a multifile tape
You can have more than one tape file on a tape. Tape files do not have names. You can restore a single tape file on a tape that contains more than one tape file. You do this by moving the tape to the beginning of the file that is to be restored.
Specifying the restore destination
The destination acts as the root of the backup that you are restoring. You specify a different restore destination if you are restoring the backed up data to a different location.
Specifying the blocking factor during restore
The blocking factor specifies the number of tape blocks that are transferred in each write operation. A tape block is 1 kilobyte of data. When you restore, you must use the same blocking factor that you used for the backup. The default blocking factor is 63.
Displaying detailed status output
You can get information about the progress of a restore on a file-by-file basis. If you have a restore problem, this output can be useful for your own diagnostics, as well as for technical support. Because of the volume of information that needs to be processed by a console, getting detailed output can slow down a restore considerably.
Ignoring inode limitations
If the restore consists mostly of files to be updated rather than new files, you can instruct the storage system to ignore the inode limitations.
Specifying automatic confirmations
An automatic confirmation automatically answers all restore questions with a "yes." You usually use this mode on restores that are run using a Remote Shell connection.
Restore examples: Multiple tape restores
There are different types of multiple tape restores, such as multiple tapes on a single-tape drive, multiple tapes on two single-tape drives, and multiple tapes on a tape library.