CompuServe Messages

#Major 6.01 bug!!

    30-Jan-94 00:15:45
Sb: #Major 6.01 bug!!
Fm: Wayne Cole 76370,621
To: Central Coast Software 75300,1416
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!