Manual Pages
Table of Contents
restore - restore files or file systems from backups made
with the filer's dump command
restore key args...
The restore restores files from backup tapes created with
the dump (see na_dump(1)) command. A full backup of a file
system may be restored and subsequent incremental backups
layered on top of it. The actions of restore are controlled
by the given key, which is a string of characters containing
at most one function letter and possibly one or more function
modifiers.
The function portion of the key is specified by one of the
following letters:
- r
- Restores (rebuilds a file system or subtree). The target
subtree should be made pristine by removing it from
a client of the server or, if the entire file system or
all subtrees of the file system are to be restored, by
booting from floppy disk and selecting the "Install new
file system." option, before starting the restoration
of the initial level 0 backup. If the level 0 restores
successfully, the r key may be used to restore any
necessary incremental backups on top of the level 0.
Note that restore r will restore all files from the
dump tape(s).
An example:
restore rf rst0a
Note that restore leaves a file restore_symboltable in
the directory that was dumped to pass information
between incremental restore passes. This file should
be removed when the last incremental has been restored.
- R
- restore requests a particular tape of a multi-volume
set on which to restart a full restore (see the r key
above). This is useful if the restore has been interrupted.
- t
- Lists the names of the specified files if they occur on
the backup. If no file argument is given, then the
root directory is listed, which results in the entire
content of the backup being listed.
- x
- Extracts the named files. If a named file matches a
directory whose contents were backed up, the directory
is recursively extracted. The owner, modification
time, and mode are restored. If no filename argument
is specified, the backup root directory is extracted.
This results in the entire backup being restored.
The following characters may be used in addition to the
letter that selects the function desired.
- b
- The next argument to restore is used as the block size
of the media (in kilobytes). If the b option is not
specified, restore tries to determine the media block
size dynamically.
- f
- The next argument to restore is used as the name of the
archive instead of the standard input. If the name of
the file is -, restore reads from standard input.
- s
- The next argument to restore is a number which selects
the file on a multi-file dump tape. File numbering
starts at 1.
- D
- By default, files will be restored into the directory
from which they were dumped. If the D option is specified,
the next argument to restore is the full absolute
pathname of a directory into which the files should be
restored.
- v
- Normally restore does its work silently. The v (verbose)
key causes it to type the name of each file it
treats preceded by its file type.
- y
- restore will not ask whether it should abort the
restore if it encounters an error. It will always try
to skip over the bad block(s) and continue as best it
can.
Complains about bad key characters.
Complains if it gets a read error. If y has been specified,
or the user responds y, restore will attempt to continue the
restore.
If a backup was made using more than one tape volume,
restore will notify the user when it is time to mount the
next volume.
There are numerous consistency checks that can be listed by
restore. Most checks are self-explanatory or can ``never
happen''. Common errors are given below.
filename: not found on tape
The specified file name was listed in the tape directory,
but was not found on the tape. This is caused by
tape read errors while looking for the file, and from
using a dump tape created on an active file system.
expected next file inumber, got inumber
A file that was not listed in the directory showed up.
This can occur when using a dump created on an active
file system.
Incremental dump too low
When doing incremental restore, a dump that was written
before the previous incremental dump, or that has too
low an incremental level has been loaded.
Incremental dump too high
When doing incremental restore, a dump that does not
begin its coverage where the previous incremental dump
left off, or that has too high an incremental level has
been loaded.
Tape read error while restoring filename
Tape read error while skipping over inode inumber
Tape read error while trying to resynchronize
A tape (or other media) read error has occurred. If a
file name is specified, then its contents are probably
partially wrong. If an inode is being skipped or the
tape is trying to resynchronize, then no extracted
files have been corrupted, though files may not be
found on the tape.
resync restore, skipped num blocks
After a dump read error, restore may have to resynchronize
itself. This message lists the number of
blocks that were skipped over.
- /tmp/rstdir*
- file containing directories on the
tape.
- /tmp/rstmode*
- owner, mode, and time stamps for directories.
restore_symboltable information passed between incremental
restores.
na_dump(1)
A level zero dump must be done after a full restore.
restore has no control over inode allocation; thus a full
restore must be done to get a new set of directories
reflecting the new inode numbering, even though the contents
of the files is unchanged.
restore does not support the -i option for interactive restoring
of files. Alternatively, provided your file access
is limited to NFS, you could use restore -i from a UNIX
client. (That alternative won't work correctly for a file
system with CIFS clients, because the UNIX restore utility
doesn't support the multi-protocol directory structures used
by the filer.) If your tape drive is local to the filer, you
can use the rmt facility (see na_rmt(8)) on the filer to
access the local tape drive from the client doing the
interactive restore.
Table of Contents