GKN%OAK.SAINET.MFENET@LLL-MFE.ARPA (01/08/86)
Date: Wed, 8-JAN-1986 08:27 EST
To: Info-VAX@SRI-KL.Arpa
Message-ID: <[OAK.SAINET.MFENET].9D51EF60.008E8B6A.GKN>
US-Mail: Science Applications; P.O. Box 2501; Oak Ridge, TN 37831
Telephone: (615) 482-9031
X-VMS-Mail-To: ARPA%"Info-VAX@SRI-KL.Arpa"
From: Arpa%"sutter%ohio-state.csnet@CSNET-RELAY.ARPA"
Subj: nightly system disk backups?
Date: Fri, 3 Jan 86 22:43:06 est
Message-Id: <8601080143.AA01191@ucbvax.berkeley.edu>
... Any suggestions on how to build this system on the second disk?
Do I just need to copy my [sys0...] and [syse...] over, keep them
updated every midnight, and that's that? It surely can't be that
simple. What do you do about this sort of thing? Any suggestions
are welcome!
Look at SYS$UPDATE:VMSKITBLD.COM. This will place a bare-bones bootable
VMS directory tree on a volume. My system device is an RP07, but I have
a spare RP06 pack around here which has an empty VMS V4.1 system on it
which I built this way (I'll get around to putting V4.2 on it Real Soon Now).
Anyway, I would consider doing this just to have something to start the
recovery procedure from. As for a complete copy, how often do you change
things on SYS$SYSTEM and friends? The only files which change on a regular
basis on our system are SYSUAF.DAT, NETUAF.DAT and RIGHTSLIST.DAT, which
get backed up on our daily incremental backups. We do an image backup of one
of our disks (we have 2 eagles, an RP07, 2 RM05s, and an RP06) per day, and
incrementals every day with a /Since:<date-of-last-image>.
Just a couple of thoughts.
gkn