🚀 go-pugleaf

trant@sgi.com writes:
>
> The method mentioned by Marcus is not a real option in my center
>where
>I have several "production" machines. I need to store data off-site
>and I also
>need to have a local copy of the file for easy recovery.

	Ideally (in the best of all possible worlds) offsite backup would
be done by running your dumps to an NSR server at another site. This would
be really really nice, IMHO. I agree about the requirement for offsite
store for "production" facilities, but I suspect you could get pretty
darn "offsite" if you just did it over a network (especially with some of
the huge sprawling bridged-together-massive "LAN"s that we're seeing
these days). I could, for example, do NSR dumps over my "LAN" and
spin a tape 10miles away...

	Right now if we had a fire and my machine with the tapes burned up
I'd be in deep yoghurt, since I keep the tapes in a box right next to the
system. Hmmm....  Maybe now that you mention it, I'll migrate a few of
them home.

	With respect to the "only incremental" issue - I neglected to
mention that I often do a "save" of entire directory trees, and when I
move or reconfigure a machine I often do a complete dump of that one
system - so it's not purely incremental, but it's still very irregular.

	I also have to admit that before I switched to NSR and the
backup policy I've currently implemented dumps only got done when I
was in the office and had the time. IE: rarely. So even if my current
scheme has some technical weaknesses, the net result is that life is a
lot better all around. My co-workers haven't killed me yet.

mjr.