Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!ucbvax!LOCKE.HS.WASHINGTON.EDU!BRUCE
From: BRUCE@LOCKE.HS.WASHINGTON.EDU (BRUCE EDWARDS)
Newsgroups: comp.os.vms
Subject: RE: Backing up the system disk from DCL
Message-ID: <8808082242.AA18293@ucbvax.berkeley.edu>
Date: 8 Aug 88 16:53:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 26

Mike,

     We tend to back up our system disk at DCL level.  We use /IGNORE=INTER
and the PAGEFILE and SWAPFILES get created on a restore, but without any
data.  Our system disk is an RA81 and we generate an RP06 offline pack with
the system root every so often.  After we restore the disk from the Backup
tapes we install the additional pointers for the [SYSEXE] and [SYSMAINT]
directories write the Boot block and use an different boot file to bring
up the system.  We also backup (to another disk) every hour or so some
key datafiles.  Things may not be perfect when you restore, but you tend
to lose less.  We also keep an eye on which files are interlocked to spot
any new problems.  It is a lot easier to set up this procedure ahead of
time then to wait until problems occur.  This way we can run in a degraded
mode until the Disk is repaired and also allows us to regenerate the system
disk on a new RA81.  We have run this procedure with both HSC and UDA based
RA-81's and are currently running VMS 4.7.  The major drawbacks relate to
what files are open.  Some files need to be individually repaired,
some we just grab a different copy and some we ignore.  We keep 3 backups
of our hourly important data file backup. Hope this helps

Bruce Edwards
John Locke Computer Center
University Of Washington SB-50
Seattle, WA 98195

Bitnet  -- BRUCE@UWALOCKE
Internet--bruce@locke.hs.washington.edu (128.208.10.1)