Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!mit-eddie!uw-beaver!rice!sun-spots-request
From: nolan@cis.ohio-state.edu (Michael C. Nolan)
Newsgroups: comp.sys.sun
Subject: Re: accidental rm
Keywords: Miscellaneous
Message-ID: <8903090526.AA24402@tut.cis.ohio-state.edu>
Date: 14 Mar 89 08:52:58 GMT
References: <8902241934.AA18715@ursa-major.SPDCC.COM>
Sender: usenet@rice.edu
Organization: Ohio State University Computer and Information Science
Lines: 16
Approved: Sun-Spots@rice.edu
Original-Date: Thu, 9 Mar 89 00:26:03 EST
X-Sun-Spots-Digest: Volume 7, Issue 197, message 3 of 12

>"restore"---provided that you run "dump" on a regular basis.  No
>joke.  Backups are more than just protection against disk catastrophe,
>they're good for when the department chairman accidentally removes the
>only copy of the proposal that was due in yesterday. ...   --wnl

This of course assumes you can convince the system manager that it's its
job to do backups.  I'm in a very data-intensive (images) environment,
where about 1/3 of the data can change every day, and there are good
reasons why nobody wants the job of backing it all up, least of all the
system manager who is also doing development.  With workstations this may
be especially difficult, as the "system" can be distributed over a wide
area.  No answers here, it's a problem.

nolan@hiips.lpl.arizona.edu;   ...!noao!solpl!hiips

[[ Said in jest:  "that's what undergraduates are for!"  --wnl ]]