It is most likely vrestore is not working after my upgrade from V4.0b to
V5.1a because the machine
hardware is unsupported by the minimum version of firmware update required
for V5.1a. I am using an old Alpha server 1000A and according to the v6.3
firmware update documentation, this system has not had a firmware update
for over 3 years. Of course, I blindly updated fw without realizing this.
Sorry to bother those who gave this any thought on my behalf... It really
pays to read the docs more closely.
Thanks!
ORIGINAL MESSAGE:
I have recently upgraded one of my alphas to v5.1A from 4.0B. Backups made
with vdump are not recognizable by vrestore under the new OS. This
includes vdumps done on the old system and on the new. I am using
/dev/tape/tape0_d1. (I have a TLZ09 4mm DAT, using DDS2, 120m).
Vdump works fine, which I can see running in verbose mode. However when I
turn around and run vrestore, the following error occurs (using the same
dev as with vdump): "vrestore: unable to use save-set; invalid or corrupt
format", followed by a program abort with the final message, " vrestore:
can't obtain fileset attributes".
I believe /dev/tape(or ntape/tape0_d1, the default, is what I want based on
ramblings in man pages for "tape".
Received on Thu Mar 27 2003 - 19:05:33 NZST