ufsrestore(1M) ufsrestore(1M)
NAME
ufsrestore - incremental file system restore
SYNOPSIS
/sbin/ufsrestore options [filename ...]
DESCRIPTION
ufsrestore restores files from backup tapes created with the
ufsdump(1M) command. options is a string of at least one of the
options listed below, along with any modifiers and arguments you sup-
ply. Remaining arguments to ufsrestore are the names of files (or
directories) which are to be restored to disk. Unless the h modifier
is in effect, a directory name refers to the files it contains, and
(recursively) its subdirectories and the files they contain.
OPTIONS
i Interactive. After reading in the directory information from the
tape, ufsrestore invokes an interactive interface that allows you
to browse through the dump tape's directory hierarchy and select
individual files to be extracted. See INTERACTIVE COMMANDS,
below, for a description of available commands.
r Restores the entire tape and loads the tape's full contents into
the current directory. This option should be used only to restore
a complete dump tape onto a clear filesystem, or to restore an
incremental dump tape after a full "level 0" restore.
R Resumes restoring. ufsrestore requests a particular tape of a
multivolume set from which to resume a full restore (see the r
option above). This allows ufsrestore to start from a checkpoint
when it is interrupted in the middle of a full restore.
t Table of contents. Lists each filename that appears on the tape.
If no filename argument is given, the root directory is listed.
This results in a list of all files on the tape, unless the h
modifier is in effect.
x Extracts the named files from the tape. If a named file matches a
directory whose contents were written onto the tape, and the h
modifier is not in effect, the directory is recursively
extracted. The owner, modification time, and mode are restored
(if possible). If no filename argument is given, the root direc-
tory is extracted. This results in the entire tape being
extracted unless the h modifier is in effect.
c Converts the contents of the dump tape to the new filesystem for-
mat.
d Debug. Turns on debugging output.
Page 1 Reliant UNIX 5.44 Printed 11/98
ufsrestore(1M) ufsrestore(1M)
h Extracts the actual directory, rather than the files that it
references. This prevents hierarchical restoration of complete
subtrees from the tape.
m Extracts by inode numbers rather than by filename to avoid regen-
erating complete pathnames. This is useful if only a few files
are being extracted.
v Verbose. ufsrestore displays the name of each file it restores,
preceded by its file type.
y Does not ask whether to abort the restore in the event of tape
errors. ufsrestore tries to skip over the bad tape block(s) and
continue as best it can.
b factor
Blocking factor. Specifies the blocking factor for tape reads.
Note: A tape block is 512 bytes.
f dump-file
Uses dump-file instead of /dev/rmt8 as the file to restore from.
If dump-file is specified as "-", ufsrestore reads from standard
input. This allows, ufsdump(1M) and ufsrestore to be used in a
pipeline to dump and restore a file system:
ufsdump 0f - /dev/ios0/rsdisk000s3 | (cd /mnt; ufsrestore xf -)
s n Skips to the n'th file when there are multiple dump files on the
same tape. For example, the command:
ufsrestore xfs /dev/ios0/rstape000h 5
would position you at the fifth file on the tape.
INTERACTIVE COMMANDS
ufsrestore enters interactive mode when invoked with the i option.
Interactive commands are reminiscent of the shell. For those commands
that accept an argument, the default is the current directory.
ls [directory] List files in directory or the current directory,
represented by a "." (period). Directories are
appended with a "/" (backslash). Entries marked for
extraction are prefixed with a "*" (asterisk). If
the verbose option is in effect, inode numbers are
also listed.
cd directory Change to directory directory (within the dump-
tape).
pwd Print the full pathname of the current working
directory.
Page 2 Reliant UNIX 5.44 Printed 11/98
ufsrestore(1M) ufsrestore(1M)
add [filename] Add the current directory, or the named file or
directory directory to the list of files to
extract. If a directory is specified, add that
directory and its files (recursively) to the
extraction list (unless the h modifier is in
effect).
delete [filename] Delete the current directory, or the named file or
directory from the list of files to extract. If a
directory is specified, delete that directory and
all its descendents from the extraction list
(unless the h modifier is in effect). The most
expedient way to extract a majority of files from a
directory is to add that directory to the extrac-
tion list, and then delete specific files to omit.
extract Extract all files on the extraction list from the
dump tape. ufsrestore asks which volume the user
wishes to mount. The fastest way to extract a small
number of files is to start with the last tape
volume and work toward the first. The owner, modi-
fication time, and mode are restored (if possible).
verbose Toggle the status of the v modifier. While v is in
effect, the ls command lists the inode numbers of
all entries, and ufsrestore displays information
about each file as it is extracted.
help Display a summary of the available commands.
quit ufsrestore exits immediately, even if the extrac-
tion list is not empty.
SECURITY NOTES
Only a superuser can do a dump of a filesystem. This prevents users
from being able to gain access to files with selective read permis-
sions.
There are special considerations for specifying the remote username in
the dump-file to the f option. In order to specify a user other than
the one who invoked the remote dump or restore utility, the user who
invoked the utility must have permission from the remote user. This is
accomplished by making the appropriate entry in the .rhosts file which
resides in the remote user's home directory. The entry should include
the originating hostname and username (which will always be "root"
since only a superuser can dump a filesystem).
In addition to the normal security checks, the security parameters can
affect the use of the remote dump and restore utilities.
Page 3 Reliant UNIX 5.44 Printed 11/98
ufsrestore(1M) ufsrestore(1M)
If the AUTOLOGINMINUID parameter is set to a positive number on the
remote host system, then users with user ids less than that number
cannot use automatic remote access.
If the DISABLERHOSTS parameter is set to "yes" on the remote host
system, then any .rhosts files will be ignored on the remote host sys-
tem. If the DISABLERHOSTS parameter is set to "no" on the remote host
system, then any .rhosts files must be writable only by the owner.
NOTES
ufsrestore can get confused when doing incremental restores from dump
tapes that were made on active file systems.
A "level 0" dump must be done after a full restore. Because ufsrestore
runs in user mode, it has no control over inode allocation; this means
that ufsrestore repositions the files, although it does not change
their contents. Thus, a full dump must be done to get a new set of
directories reflecting the new file positions, so that later incremen-
tal dumps will be correct.
DIAGNOSTICS
ufsrestore complains about bad option characters.
Read errors result in complaints. If y has been specified, or the user
responds y, ufsrestore will attempt to continue.
If the dump extends over more than one tape, ufsrestore asks the user
to change tapes. If the x or i option has been specified, ufsrestore
also asks which volume the user wishes to mount.
There are numerous consistency checks that can be listed by
ufsrestore. Most checks are self-explanatory. Common errors are given
below.
Converting to new file system format.
A dump tape created from the old file system has been loaded. It
is automatically converted to the new file system format.
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 tape created on an active file system.
Incremental tape too low
When doing an incremental restore, a tape that was written before
the previous incremental tape, or that has too low an incremental
level has been loaded.
Page 4 Reliant UNIX 5.44 Printed 11/98
ufsrestore(1M) ufsrestore(1M)
Incremental tape too high
When doing incremental restore, a tape that does not begin its
coverage where the previous incremental tape left off, or one
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 read error has occurred.
If a file name is specified, then its contents are probably par-
tially 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 ufsrestore, skipped num
After a tape read error, ufsrestore may have to resynchronize
itself. This message lists the number of blocks that were skipped
over.
FILES
/dev/rmt8
the default tape drive
/tmp/rstdir*
file containing directories on the tape
/tmp/rstmode*
owner, mode, and timestamps for directories
./restoresymtable
information passed between incremental restores
SEE ALSO
ufsdump(1M), mkfs(1M), mount(1M).
Page 5 Reliant UNIX 5.44 Printed 11/98