Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!ucbvax!SMITH.BITNET!MANAGER
From: MANAGER@SMITH.BITNET.UUCP
Newsgroups: comp.os.vms
Subject: justification for standalone backup -- critical files
Message-ID: <8706180937.AA12185@ucbvax.Berkeley.EDU>
Date: Tue, 16-Jun-87 09:27:00 EDT
Article-I.D.: ucbvax.8706180937.AA12185
Posted: Tue Jun 16 09:27:00 1987
Date-Received: Sat, 20-Jun-87 00:52:28 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 15

What about SYSUAF.DAT?  I have on several occasions seen conflicts occur
when SYSUAF.DAT, or part of it anyway, is locked by one process and
therefore can't be read by another process.  This is *rare* (I've seen it
maybe six times and had it happen to me perhaps twice), but it suggests to
me the possibility that the file could not be backed up.

Other files that I'm pretty sure would not be properly saved would be the
various system .LOG files (well...some of them anyway) and maybe accounting
files too.  I wouldn't worry about them, though...SYSUAF.DAT is enough to
keep me doing standalone backups


Mary Malmros
Smith College
MANAGER@SMITH (BITnet)