Article View: bit.listserv.l-vmctr
Article #794VMBACKUP
From: Paul Lavoie
Date: Mon, 16 Mar 1992 18:50
Date: Mon, 16 Mar 1992 18:50
18 lines
1325 bytes
1325 bytes
On the weekend, just as the WEEKLY backups were coming to an end, the operator "detached" tape drives assigned to VMBACKUP before it had a chance to do it itself. VMBACKUP promptly abended. It did manage to create the WEEKLY catalog but did not have time to update the tapepools (weekly and twins). There is no interface with VMTAPE. The tapepools belong to VMBACKUP (1C0 mdisk). I performed a "CHECK" on the weekly catalog for that day and everything checks out O.K. I'm thinking of "DISCARDING" that catalog and telling them to rerun the weekly backups. On the other hand, I could modify the tapepool files by changing the creation and expiry dates for those tapes that were used during that specific backup. Any thoughts?
Technical Details
Message-ID:
<L-VMCTR%92031614045760@VM1.CC.UAKRON.EDU>Path:
arc1-ca.pugleaf.net!sparky!uunet!paladin.american.edu!auvm!NRCVM01.BITNET!VMRMAINTShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fe320,e259d08334e0aecb,start X-Google-Attributes: gidfe320,public X-Google-ArrivalTime: 1992-03-16 22:09:47 PST Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU Path: arc1-ca.pugleaf.net!sparky!uunet!paladin.american.edu!auvm!NRCVM01.BITNET!VMRMAINT Message-ID: <L-VMCTR%92031614045760@VM1.CC.UAKRON.EDU> Newsgroups: bit.listserv.l-vmctr Date: Mon, 16 Mar 1992 13:50:52 EST Sender: VMCENTER Components Discussion List <L-VMCTR@AKRONVM.BITNET> From: Paul Lavoie <VMRMAINT@NRCVM01.BITNET> Subject: VMBACKUP