#Major 6.01 bug!!
3 messages in this thread
Randy,
I have 4 tapes of the 2.0 GB 4mm DAT type that hold multiple backups made
under QB 5.04. Of these four, only one allows "advancing" without
forgetting the tape is a quarteback volume. That particular one had only
one archive on it from 5.04 to begin with and had 3 archives added to it
from 6.01. Note that I always use a straight QB backup with no
compression or any but default options (other than creating a session log
file).
I select Advance from tape control (and it matters not hwo many
sessions to advance past I select) and I see the "Fast advancing tape
…" alert. Then when the tape is finished advancing, I try to
restore from the selected session and I get "This tape does not
contain a valid Quarterback backup." alert. However, I can 'Restore
– test' my way to the required session and get a restore AS LONG AS I
DO NOT UNTAG ANY FILE/DIRECTORY IN THE RESTORE TEST LIST.* But, this
is very time consuming. Basically it appears there is some loss in
downward compatibility of backup tape structure recognition from
6.01 to 5.04 formats. Please fix this. I have a lot of data on this
tapes (between 10 and 17 sessions per tape) and it takes an hour on
average to 'recover-test' past an archive whereas the 'advance' takes
only a few minutes.
I have a GVP G-Force 040 2000, with an externally connected
Maynstream 1300 DAT upgraded to a 2.0 GB capacity by the factory
during refurb. The drive itself is a Archive Python 25588 rev 2.96.
Note that I had no tape handling problems with QB 5.04. It just
crashed my machine 80% of the time when it was invoked, but if it got
past the display of the device list, the tape handling went smoothly.
*NOTE: If I untag some items in the restore test list, when I try a
subsequent restore-test, I get the "…not a Quarterback backup.." message
and the tape is rewound.
wmc – via Autopilot!
Thanks for the report Wayne. We will check into this one and clarify the cross
version compatibility issues.
Randy Brooks
Central Coast Software
A division of New Horizons Software, Inc.
Randy,
6.01 will read the 5.0x file once you get to it. But will not recognize
it if you "space" or "advance" up the tape to it.
5.0x just will not touch 6.01 files as it sees them as password
protected.
I'm telling you – I ain't a happy camper. For two days I've been
working on restoring a tape with 11 backups on it to a useable
state. I've decided it has to be 5.04 as that is the format of all
the other tapes I have that I need to access periodically. Now, if I
could figure out how to keep it from crashing the system. Can you
come up with a 5.05 patch for that? pretty please?!? I've tried it
on entirely different hardware and it does the same thing – hard
crashes the machine just before the device list is put up. Crashes
in such a way as to hard reset the sytem date and time. Crashes it
so that a warm reboot won't recover. Gotta do a power down/up cycle
to clear the fault. If you could just patch in the 6.01 startup code
and leave the 5.04 backup-restore stuff in place, that would be
perfect.
I can't believ no one else is having this problem. It happens on two
differnt A2000s with different ACCs and SCSI devices. The only common
thing is the GVP scsi device software.
wmc – via Autopilot!