Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!CRNLNS.BITNET!SYSTEM
From: SYSTEM@CRNLNS.BITNET.UUCP
Newsgroups: mod.computers.vax
Subject: re: doing complete backups regularly
Message-ID: <8703140110.AA06420@ucbvax.Berkeley.EDU>
Date: Thu, 12-Mar-87 12:04:00 EST
Article-I.D.: ucbvax.8703140110.AA06420
Posted: Thu Mar 12 12:04:00 1987
Date-Received: Sat, 14-Mar-87 15:29:25 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 29
Approved: info-vax@sri-kl.arpa

Just to add my two-cents-worth to the discussion,
our Backup strategy is to do a /IMAGE/RECORD Backup weekly while the
system is available for general use (NOT standalone).
We do time-shared incrementals (/MODIFIED/SINCE=BACKUP) every night.

The following commands are extracted from our backup command file:

 $ input := SYS$SYSDEVICE:
 $ output := BKP:ALLSAV/SAVE/REWIND/BUFFER=5/DENSITY='P1'
 $ BACKUP/image/FAST/RECORD/IGNORE:INTERLOCK-
 /jou=USER$DISK:[backup]SYS_'WKLNAM' 'input' 'output'

I have successfully rebuilt a system disk from such /IMAGE tapes,
without a lot of effort: I had to run ANA/DISK/REPAIR an odd number
of times, but that's all.

While it is true that files open at the time of the Backup won't
be properly restored, that is a small loss compared to what would
otherwise be the case.

I hope this helps.

Selden E. Ball, Jr.

Cornell University                 NYNEX: 1-607-255-0688
Laboratory of Nuclear Studies     BITNET: SYSTEM@CRNLNS
Wilson Synchrotron Lab              ARPA: SYSTEM%CRNLNS.BITNET@WISCVM.WISC.EDU
Judd Falls & Dryden Road          PHYSnet/HEPnet/SPAN:
Ithaca, NY, USA  14853             LNS61::SYSTEM = 44283::SYSTEM (node 43.251)