HP-UX Reference (11i v1 00/12) - 1M System Administration Commands N-Z (vol 4)

__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/naaagt.1m
________________________________________________________________
___ ___
v
vxrestore(1M) vxrestore(1M)
-m Extract by inode numbers rather than by file name. This is useful if only a few files are being
extracted and you want to avoid regenerating the complete pathname to the file.
-v Specify verbose output; list the name of each file restored, preceded by its file type.
-y Do not ask whether to abort the operation if vxrestore encounters a tape error, but con-
tinue. Normally vxrestore asks whether to continue after encountering a read error. With
this option, vxrestore continues without asking, skipping over the bad tape block(s) and
continuing as best it can.
DIAGNOSTICS
vxrestore complains if a read error is encountered. If the -y option has been specified, or you respond
y, vxrestore tries to continue the restore.
If the dump extends over more than one tape, vxrestore asks the user to change tapes. If the -x or
-i option has been specified, vxrestore also asks which volume 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 vxrestore can list. Most checks are self-explanatory or
rarely occur. Here are some common errors:
filename: not found on tape
The specified file name was listed in the tape directory but 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 not listed in the directory appeared. This can occur when using a dump tape created on an
active file system. Dumps should be performed with the file system unmounted or the system in
single-user mode (see init(1M)) to insure a consistent dump. If the HP OnLineJFS product is
installed, the dump can be performed in the multi-user environment using a snapshot file system
with the online backup facility (see the snapof=file option of mount_vxfs(1M)).
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 was loaded.
NOTE: if this error occurs, you are either restoring tapes out of order or restoring from a dump
file that was created using the -T option to vxdump. At this point, vxrestore
displays a
warning message and asks if you want to continue doing the restore. Respond with
y only if
you are sure that you are restoring from a dump file created using the
-T option. Enter
n to
abort the restore.
Incremental tape too high
When doing an incremental restore, a tape that does not begin its coverage where the previous
incremental tape left off, or that has too high an incremental level was loaded.
NOTE: If this error occurs, you are either restoring tapes out of order or restoring from a dump
file that was created using the
-T option to vxdump. At this point vxrestore displays a
warning message and asks if you want to continue doing the restore. Respond with y only if
you are sure that you are restoring from a dump file created using the -T
option. Enter n to
abort the restore.
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 occurred. If a file name is specified, the contents of the restored files may be
incorrect. If vxrestore is skipping an inode or is trying to resynchronize the tape, no
extracted files are corrupted, although files may not be found on the tape.
Resync restore, skipped num blocks
After a tape-read error, vxrestore may have to resynchronize itself. This message indicates
the number of blocks skipped over. This message will also be generated by older versions of
vxrestore while skipping over files larger than 2 gigabytes dumped by a more recent version
of vxdump.
HP-UX Release 11i: December 2000 − 3 − Section 1M−−1055
___
___