🚀 go-pugleaf

I think it is a fair assumption that a lot of VM shops have few (1-3) VM
systems programmers (here, it is I;) and still get a lot done.  I had not
REALLY considered offsite storage of VMARCHIVE tapes, because we already
have problems with the tapes and tape drives.  We are forever closing a
tape set because of I/O errors caused by a bad tape or flaky drive.  Then
you have to have the copies around just to be sure they match, sort of,
since VMARCHIVE twins are not exact copies any more than VMBACKUP twins
are exact copies.

I've been tempted to use VMBACKUP in a second machine to be VMARCHIVE.
Why?  Because it handles I/O errors so much better, because it "owns" the
tapes to begin with, because recall is cleaner, nicer, neater for most
instances than  VMARCHIVE.

Why not?  I don't have the time (see above) to mangle code and doc for
it.

VMARCHIVE and SFS, not!  A royal pain to save your work or recall it.
Since we are an SFS shop, that's a REAL pain.

'Nuff said.
-- 
Mark A. Stevens                           Phone:    708-534-0200
Systems Programmer                        Internet: xmas@uxa.ecn.bgu.edu
Educational Computing Network             BITNET:   XMAS@ECNUXA.BITNET
Board of Governors Universities           VMSHARE:  ECE/MARK