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

v
vxrestore(1M) vxrestore(1M)
bad name
hole in map
gethead: bad bitmap encountered
gethead: unknown inode type number
linkit: unknown type number
initsymtable called from command n
unextracted directory name
bad entry entry details
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.
WARNINGS
vxrestore can get confused when doing incremental restores from dump tapes that were made on active
file systems.
A level 0 dump (see the vxdump(1M) manual page) must be done after a full restore. Because vxre-
store
runs in user code, 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 contents of the files are
unchanged.
HP-UX 11i Version 2: December 2007 Update − 5 − Hewlett-Packard Company 669