vrestore, rvrestore - Restores files from savesets that are produced by
vdump and rvdump
/sbin/vrestore -t [-f device]
/sbin/vrestore -l [-Q] [-f device]
/sbin/vrestore -i [-mqQv] [-f device] [-D path] [-o opt]
/sbin/vrestore -x [-mqQv] [-f device] [-D path] [-o opt] [file...]
/sbin/rvrestore -t [-f nodename:device]
/sbin/rvrestore -l [-Q] [-f nodename:device]
/sbin/rvrestore -i [-mqQv] [-f nodename:device] [-D path] [-o opt]
/sbin/rvrestore -x [-mqQv] [-f nodename:device] [-D path] [-o opt]
Specifies the destination path of where to restore the files. Without
the -D option, the files are restored to the current directory.
When an argument follows the -f option, it specifies the name of the
storage device that contains the saveset to be restored. The argument
replaces the default device /dev/tape/tape0_d1.
For rvrestore, the mandatory specification is nodename:device to
specify the remote machine name that holds the saveset to be restored.
There is no default device.
-h Displays usage help for the command.
-i Permits interactive restoration of files read from a saveset. After
reading directory information from the saveset, the vrestore command
provides a shell-like interface that allows you to select the files you
want to restore. Some of the following interactive commands require an
arg parameter that is a subdirectory or one or more file names. The
other interactive commands use the current directory as default when
the arg parameter is not specified. Multiple file names can be
separated by spaces. Quotes (") can be used around a file name that
contains space(s). File names containing quotes (") can be specified
by preceding the quote with a backslash (\). The interactive commands
are explained in the following list:
Adds the files in the saveset specified by arg to the list of files
to be restored. Files on the list of files to be restored are
prepended with the * (asterisk) character when they are listed with
the ls interactive command.
Changes the current saveset directory to the directory specified
with the arg parameter.
Deletes all files and their subdirectories specified by the arg
parameter from the list of files to be restored.
An expedient way to select wanted files from any directory in a
saveset is to add the directory to the list of files to be restored
and then delete the ones that are not wanted.
extract or restore
Restores files, previously added by using the add command, to the
current destination directory.
Displays help information for the interactive commands.
Lists files in the current saveset directory or the directory
specified with the arg parameter. Directory entries are appended
with a slash (/) character. Entries that have been marked to be
restored are prepended with an asterisk (*) character.
pwd Writes the path name of the current saveset directory to the stan-
dard output device.
quit or exit
Exits immediately, even when the files on the list of files to be
restored have not been read.
Escapes from the shell, runs the system command, then returns to
Selects the -v modifier (see the -v option). The name of each file
restored from the saveset is written to the standard output device.
? Displays help information for the interactive commands.
-l Lists the entire saveset structure.
-m Does not preserve the owner, group, or modes of each file from the dev-
Specifies the action to take when a file already exists. The options
yes Overwrites existing files without any query. The default is yes.
no Does not overwrite existing files.
ask Asks whether to overwrite an existing file.
-q Prints only error messages; does not print information messages.
-Q Specifies that quota files should not be restored.
-t Lists the names and size (in bytes) of all files contained in a
saveset. Exception: the sizes of any AdvFS quota files are not shown.
-v Writes the name of each file read from the storage device to the stan-
dard output device. Without this option the vrestore command does not
notify you about progress on reading from the storage device.
-V Displays the current version for the command.
-x Extracts a specific file or files from the saveset. Use this command
as an alternate to using the add command in interactive mode. The -x
option can precede any other options, but the file... list must be the
last item on the command line.
For example, to restore the files file1 and file2 from the saveset on
the default device, /dev/tape/tape0_d1, to the /mnt directory, enter:
# vrestore -x -D /mnt file1 file2
Specifies the file or files to restore when using the -x option. All
other options must precede any file names on the command line.
The vrestore and rvrestore commands restore data from a saveset previously
archived by the vdump command or the rvdump command. The data, which can be
restored from a file, a pipe (not applicable for the rvrestore command), or
a storage device (typically tape), is written to the specified directory.
The default storage device from which files are read is /dev/tape/tape0_d1.
You can use the -f option to specify a different device or file. Tape
storage devices can contain more than one saveset. The vrestore and rvre-
store commands restore any associated extended attributes, including ACLs,
in the archive data. See the proplist(4) and acl(4) reference pages.
The vrestore and rvrestore commands are the restore facility for the AdvFS
file system. However, the commands can be used to restore UFS and NFS
files that have been archived by using the vdump or rvdump commands.
The default directory into which the files are restored is the current
directory. You can specify an alternate directory by using the -D option.
Use the -t option to list the file names and sizes of the files in a
saveset without restoring any files.
When you are using the interactive shell and the AdvFS user and group quota
files are available in the saveset for restoration, the file names used to
refer to them will be quota.user and quota.group, regardless of what the
quota files are named in either the backed up fileset or in the destination
fileset. Restoration of the quota files does not change the names of the
quota files in the destination fileset. Use the -Q option if you do not
want to restore quota files.
If the destination fileset is AdvFS, and the saveset contains AdvFS fileset
quotas, the fileset quotas are restored, even when they differ from the
fileset quotas of the destination fileset. By using the -Q option, -o no,
option or -o ask option, you can prevent this behavior.
The vdump and rvdump commands can write many savesets to a tape. If you
want to use the vrestore or the rvrestore commands to restore a particular
saveset, you must first position the tape to the saveset by using the mt
command with the fsf option to move through your tape.
The source directory path from a vdump command line is stored as a string
in the header record of the saveset produced. The vrestore command
displays this string when it restores the archived saveset. The string
truncates at 128 characters. Several vrestore command options, including
-t, -l, -i, and -x, display the source directory path. The command is the
exact string from the vdump command: it contains no relative pathname
expansions or resolved symbolic links.
For example, if a vdump command line contained instructions to dump files
from a directory named /usr/specs, which was a symbolic link to a directory
named /tmp_mnt/pease1/usr/specs, the source directory string displayed by
the vrestore command would be /usr/specs:
The vdump command:
% vdump -0 -f mydump /usr/specs
The vrestore command and string displayed:
% vrestore -t -f mydump
vrestore: Date of the vdump save-set: "date"
>>>>>> vrestore: Save-set source directory: /usr/specs
Files that were saved on a system running a pre-Version 5 operating system
will be restored by a Version 5 operating system in the same manner as they
would have been restored by a pre-Version 5 system. This means that any UFS
sparse files archived with the vdump command prior to Tru64 UNIX Version
5.0 will be allocated disk space and filled with zeros and any AdvFS
striped sparse files archived with the vdump command prior to Version 4.0D
will be allocated disk space and filled with zeros. If you save and restore
your sparse files under Version 5, they will remain sparse.
Note that an incremental dump only captures the files that have changed,
ignoring all others. This means that if you perform a level 0 dump and a
later incremental dump, deleted files are not marked as gone (deleted). If
you then do a complete restore with a level 0 saveset and incremental
backups, the deleted files will be restored. You must then delete these
You do not have to be the root user to use the vrestore command, but you
must have write access to the directory to which you want to restore the
To run the rvrestore command, you must be able to execute the rsh command
from the remote node from which you want to restore. See rsh(1) for server
and client access rules.
Filesets that have been archived by using the vdump or rvdump command must
be restored by using the vrestore or rvrestore command. The vdump and
rvdump commands are not interchangeable with the dump and rdump commands.
Similarly, the vrestore and rvrestore commands are not interchangeable with
the restore and rrestore commands.
A saveset stored on a block special device file containing disk block 0
that has not had the disk label cleared will contain an error and no files
will be restored. See vdump(8) for more information.
Only the root user can restore AdvFS quota files and fileset quotas. A
warning message is displayed when a non-root user attempts to use the vre-
store command to restore AdvFS quota files or fileset quotas. Use the -Q
option to prevent the restoration of quota files.
The vrestore command in operating system versions earlier than Version 4.0
cannot be used to restore savesets produced by the vdump command in Version
4.0 or higher systems.
The vrestore command in Tru64 UNIX Version 5.0 cannot interactively restore
quota files that have been saved by the vdump command in Version 4.0D and
earlier. However, the command mode of the vrestore command in Tru64 UNIX
Version 5.0 can restore such quota files.
AdvFS quota files can be restored to either an AdvFS fileset or a UFS file
system, but UFS quota files cannot be restored to an AdvFS fileset. If
AdvFS quota files are to be restored to a UFS file system, quotas must be
enabled on the UFS file system. Otherwise, the operation fails. AdvFS
fileset quotas cannot be restored to a UFS file system because there is no
UFS analog to AdvFS fileset quotas.
Attempting to use a vrestore or rvrestore to restore to a base directory
that has a default directory access control list (ACL) or a default access
ACL may cause unintended ACLs to be created on the restored files and
directories. If ACLs are enabled on the system, check all ACLs after using
the vrestore or rvrestore command. View the documents in SEE ALSO for more
information about access control lists (ACLs).
1. To restore a local archive produced by the vdump command and mounted
on the default storage device to the mnt directory, enter a command
similar to the following:
% vrestore -D /mnt
2. To restore a remote archive produced by the vdump or rvdump command
and mounted on the default storage device on machine node pease to the
local mnt directory, enter a command similar to the following:
# rvrestore -xf pease:/dev/tape/tape0 -D /mnt
3. When the restore saveset device is the character dash (-), the vre-
store command reads from standard input. Thus, the vdump and vrestore
commands can be used in a pipeline expression to copy filesets. The
following are typical commands; they are equivalent:
# vdump -0 -f - /usr | (cd /mnt; vrestore -x -f -)
# vdump -0f - /usr | vrestore -xf - -D /mnt
The rvdump and rvrestore commands are unable to use the dash (-)
character. The output device must be specified.
4. To restore from a tape containing multiple savesets you created with
the vdump command, use the mt fsf n command (forward space n savesets
or files) to locate the saveset to restore. The following example will
space forward to the third saveset and then restore it:
# mt fsf 2
# vrestore -xf /dev/tape/tape0
The vrestore command path.
The rvrestore command path.
The default storage device.
Commands: mt(1), rsh(1), rvdump(8), vdump(8)
Files: acl(4), proplist(4)