McGuire_Ed@GRINNELL.MAILNET (08/11/86)
>Date: Fri, 8-AUG-1986 13:15 EST >From: Daniel B Dobkin <DDOBKIN%NYBVX1.BITNET@WISCVM.ARPA> >Subject: BACKUP tape problem > >... apparently, BACKUP does nothing to ensure >that subsequent tapes are appropriately labelled when doing a write >operation. Only after someone needed a file restored from the second or >third tape did we discover that BACKUP complains about the tape not being >ANSI-labelled. We've never seen this problem. We regularly restore files from multivolume save sets, and I believe that many of the tapes were fresh out of the box, i.e. had no label at all. BACKUP writes a label that is a variant of the original, with a sequence number. Isn't there a qualifier on the MOUNT command that can disable automatic continuation-volume initialization? If this mechanism broke down, I'd call it a bug. If the tapes really contain portions of BACKUP savesets with no ANSI labels, you _might_ be able to salvage the data by adding an ANSI label to the tape. You could do this by using COPY to transfer the data from tape to disk (COPY works with tapes that have been MOUNTed/FOREIGN, it copies tape labels as files etc.), then initialize a new tape and use the SET MAGTAPE commands to skip past the tape label and maybe write a tape mark, then use COPY to transfer the data back to the tape. I can't give you step-by-step instructions because I haven't hacked a volume together like that in a long time.