🚀 go-pugleaf

In article <C0MAzp.Ap2@zoo.toronto.edu> henry@zoo.toronto.edu (Henry Spencer) writes:
>In article <C0KKpo.63w@ccu.umanitoba.ca> mills@ccu.umanitoba.ca (Gary Mills) writes:
>>I'm wondering how other news admins do backups on the news partitions?
>
>We don't.  The turnover is so high that it makes backups huge, and we
>can't see any good reason to back it up.  If we lose that filesystem,
>we'd just mkfs it and start from scratch.

I agree. If you have /var/spool/news as a separate partition, it should be
relatively easy to recover from a major failure by starting the news system
from scratch. After all, anything in there would have gotten deleted (expired)
sooner or later anyway... why bother? As far as backups/crashes are concerned,
there are a *LOT* worse things you can lose than the /var/spool/news dir.

>We do backup /usr/lib/news, although our history files are located
>elsewhere (in the news filesystem) so they don't get backed up.  The
>control files, like active and sys, are the things you really don't
>want to lose.  They're small and don't cost much to back up.

Same here, with the exception that we DO have the history file (physically)
in /usr/lib/news... not that it matters, since I suppose that they should get
nuked if you want to start over from scratch anyway.

Last time I had to re-do my news system from scratch was several months ago,
when some of my news files became corrupted. I used the opportunity to 
upgrade my system to the performance Cnews release. It just took one or two
days of intense catching-up, and stabilized back to the level where it was
before pretty quickly.
-- 
      Francisco X DeJesus  ----- S A I C -----  dejesus@chinalake.navy.mil
 ------------------------------------------------------------------------------
  * disclaimer: Opinions expressed here are mine. Typos and errors are yours *
 "Duck Season!" "Rabbit Season!" "...rabbit season." "It's Duck Season! SHOOT!"