RESTORE(8) | System Manager's Manual | RESTORE(8) |
restore
, rrestore
—
restore |
-i [-cdhmuvyN ]
[-b bsize]
[-D algorithm]
[-f file]
[-M mfile]
[-s fileno] |
restore |
-R [-cduvyN ]
[-b bsize]
[-D algorithm]
[-f file]
[-M mfile]
[-s fileno] |
restore |
-r [-cduvyN ]
[-b bsize]
[-D algorithm]
[-f file]
[-M mfile]
[-s fileno] |
restore |
-t [-cdhuvy ]
[-b bsize]
[-f file]
[-s fileno]
[file ...] |
restore |
-x [-cdhmuvyN ]
[-b bsize]
[-D algorithm]
[-f file]
[-M mfile]
[-s fileno]
[file ...]
(The 4.3BSD option syntax is implemented for backward compatibility, but is not documented here.) |
restore
command performs the inverse function of
dump(8). A full backup of a file
system may be restored and subsequent incremental backups layered on top of
it. Single files and directory subtrees may be restored from full or partial
backups. restore
works across a network; to do this
see the -f
flag described below. Other arguments to
the command are file or directory names specifying the files that are to be
restored. Unless the -h
flag is specified (see below),
the appearance of a directory name refers to the files and (recursively)
subdirectories of that directory.
If any file arguments are given with the
-x
flag, or specified in the command shell with the
-i
flag, the permissions of the root directory
will not be applied to the current directory, unless one
of those file arguments explicitly represents the root inode (e.g.: a
literal ‘.’). This is a change from the traditional behaviour,
which used to be to always prompt the user.
Exactly one of the following flags is required:
-i
restore
provides a shell like interface that
allows the user to move around the directory tree selecting files to be
extracted. The available commands are given below; for those commands that
require an argument, the default is the current directory.
add
[arg]-h
flag is specified on the command line).
Files that are on the extraction list are prepended with a
“*” when they are listed by
ls
.cd
argdelete
[arg]-h
flag is specified on the command line). The
most expedient way to extract most of the files from a directory is to
add the directory to the extraction list and then delete those files
that are not needed.extract
restore
will ask which volume the user
wishes to mount. The fastest way to extract a few files is to start
with the last volume, and work towards the first volume.help
,
?
ls
[arg]pwd
quit
,
xit
setmodes
verbose
-v
flag is toggled. When set,
the verbose flag causes the ls
command to list
the inode numbers of all entries. It also causes
restore
to print out information about each
file as it is extracted.what
Debug
-R
restore
requests a particular tape of a multi
volume set on which to restart a full restore (see the
-r
flag below). This is useful if the restore has
been interrupted.-r
-r
flag may be used to restore any necessary
incremental backups on top of the level 0. The -r
flag precludes an interactive file extraction and can be detrimental to
one's health if not used carefully (not to mention the disk). An example:
newfs /dev/rsd0g mount /dev/sd0g /mnt cd /mnt restore rf /dev/rst0
Note that restore
leaves a file
restoresymtable in the root directory to pass
information between incremental restore passes. This file should be
removed when the last incremental has been restored.
restore
, in conjunction with
newfs(8) and
dump(8), may be used to
modify file system parameters such as size or block size.
-t
-h
flag has been specified. Note that the
-t
flag replaces the function of the old
dumpdir
program.-x
-h
flag is not specified, the directory is
recursively extracted. The owner, modification time, and mode are restored
(if possible). If no file argument is given, then the root directory is
extracted, which results in the entire content of the backup being
extracted, unless the -h
flag has been
specified.The following additional options may be specified:
-b
bsize-b
option is not specified, restore
tries to
determine the block size dynamically.-c
restore
will try to determine
dynamically whether the dump was made from an old (pre-4.4) or new format
file system. The -c
flag disables this check, and
only allows reading a dump in the old format.-D
algorithm-N
.-d
-f
file-
’ (the
standard input). If the name of the file is of the form
“host:file”, or “user@host:file”,
restore
reads from the named file on the remote
host using rmt(8). If the name
of the file is
‘-
’,
restore
reads from standard input. Thus,
dump(8) and
restore
can be used in a pipeline to dump and
restore a file system with the command
dump 0f - /usr | (cd /mnt; restore xf -)
-h
-M
mfilesort mfile | mtree -e -i -u
-m
-N
-s
fileno-u
-u
(unlink) flag removes files before
extracting them. This is useful when an executable file is in use. Ignored
if -t
or -N
flag is
given.-v
restore
does its work silently. The
-v
(verbose) flag causes it to type the name of
each file it treats preceded by its file type.-y
The historic alternate name rrestore
was
once required when restoring from a remote host. This functionality is now
built into restore
itself.
restore
:
_PATH_DEFTAPE
in /usr/include/paths.h.-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. If the -x
or
-i
flag has been specified,
restore
will also ask which volume the user wishes
to mount. The fastest way to extract a few files is to start with the last
volume, and work towards the first 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.
restore
may have to
resynchronize itself. This message lists the number of blocks that were
skipped over.restore
command appeared in
4.2BSD.
restore
can get confused when doing incremental restores
from dumps that were made on active file systems.
A level zero dump must be done after a full restore. Because
restore
runs in user mode, it has no control over
inode allocation; thus a full dump must be done to get a new set of
directories reflecting the new inode numbering, even though the content of
the files is unchanged.
The temporary files /tmp/rstdir* and
/tmp/rstmode* are generated with a unique name based
on the date of the dump and the process ID (see
mktemp(3)), except for when
-r
or -R
is used. Because
-R
allows you to restart a
-r
operation that may have been interrupted, the
temporary files should be the same across different processes. In all other
cases, the files are unique because it is possible to have two different
dumps started at the same time, and separate operations shouldn't conflict
with each other.
July 15, 2018 | NetBSD 9.4 |