Article View: bit.listserv.l-vmctr
Article #134Re: VMarchive dasd crash
From: Bill Williams
Date: Mon, 11 Jan 1993 20:41
Date: Mon, 11 Jan 1993 20:41
44 lines
2839 bytes
2839 bytes
On Sat, 9 Jan 1993 03:57:06 GMT Stan Horwitz said:
>...stuff deleted... exactly how much
>trouble will we be in if this catalog file become corrupt or destroyed?
>
>The archived files will be fine (in this scenerio), but we won't have a
>record of what's there. We definitely need a backup procedure for the
>master VMArchive catalog file. ...
> ... What I want to know is if there is anyway of backing up this
>single file perhaps hourly to another disk file just in case the original
>goes bad. This way, all we'l lose is an hour's archiving activity. Could
>we just schedule a vmschedule job to kick in every hour and do this backup.
>I was told this wouldn't work, but it seems like a good idea to me.
There are several pros/cons here depending upon the size of this catalog
data. Don't forget your STAGE and ONLINE areas, too!. How about this:
When you get ready for your hourly SUBMIT ARCHIVES you also follow
through with a VMBACKUP to the VMARCH MDisks which contain the VMArchive
data -- catalog, ONLINE, and with proper POST, etc. your STAGE could
catch anything which might be incoming during your SUB ARCHIVEs.
The drawback is whether VMARCH will be unavailable during the VMBACKUP
QUIESCE for an unacceptable period of time. Also, this will be no good
if VMBACKUP takes an hour to back up VMARCHIVE! :-)
If this idea doesn't work, you can also have a duplicate MDisks defined
-- the same sizes but on a different HDA -- for the critical VMARCH
MDisks, and have some special userid set up (preferrably OWNING the
duplicate MDIsks) which you VMSchedule to come up with links to the REAL
Mdisks and DDR them once an hour.
Both these ideas have holes, but as I hope to imply -- they are just
*IDEAS* and not intended to represent a cookbook.
My *best* suggestion is to call SCI Tech Support and ask them!
I, too, am curious as to how other sites handle this situation.
---------------------------------------
Bill Williams -- ETSU Systems Support
East
Tennessee (615) 929-6853
State
University <CMS2@ETSU.BITNET>
Technical Details
Message-ID:
<L-VMCTR%93011116022707@VM1.CC.UAKRON.EDU>Path:
arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!howland.reston.ans.net!paladin.american.edu!auvm!ETSU.BITNET!CMS2Show Full Headers
Complete Article Headers
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!howland.reston.ans.net!paladin.american.edu!auvm!ETSU.BITNET!CMS2 Return-Path: <@VM1.CC.UAKRON.EDU:CMS2@ETSU.BITNET> Message-ID: <L-VMCTR%93011116022707@VM1.CC.UAKRON.EDU> Newsgroups: bit.listserv.l-vmctr Date: Mon, 11 Jan 1993 15:41:53 EST Sender: VMCENTER Components Discussion List <L-VMCTR@AKRONVM.BITNET> From: Bill Williams <CMS2@ETSU.BITNET> Organization: East Tennessee State University Subject: Re: VMarchive dasd crash In-Reply-To: Message of Sat, 9 Jan 1993 03:57:06 GMT from <STAN@VM.TEMPLE.EDU> Lines: 44