🚀 go-pugleaf

Hello,

Sorry for the late response. We're working on a VMARCHIVE 3rd-copy project:
closed VMARCHIVE tapes have to be copied to a set of tapes, which will be
stored outside our building.

Initially we choose VMBTCPY to do the copying, but it turned out that we have
some 250M cartridges that have to be copied onto 200M ones, and VMBTCPY just
gives up... Apart from that it destroys the labels, which makes housekeeping
quite difficult.

So now I'm working on a version that uses CMS-Pipes to do the copy onto a set
of labeled tapes. It keeps track of the tapes copied as it stores their volser,
date-last used and volser of the 3rd copy on a CMS-file. The CMS-file is dumped
along with the VMARCH database at every run.
All 3rd copy tapes will be written to tape-end which reduces in our case the
final number of 3rd copy tapes by some 30%.
Eventually a destroyed tape can be recovered by running another CMS-Pipes
program. It reads the housekeeping file, determines which 3rd copy tapes to
use, reads them and rewrites the VMARCHIVE tape onto another tape, which will
become an exact copy of the initial VMARCHIVE tape.

Marieke Tiecke <SSCP0055@HASARA11>
               <Marieke@SARA.NL>
Academic Computer Services Amsterdam