Offsite backups

[Dan Brosemer <odin@cleannorth.org>]

I created a key with which to encrypt our data that is backed up to tape.
The key will be put on floppies or CDs and given to check signers.  The key
still needs a passphrase to be useful, though.  I know that, and I'd like
someone else (who won't write it down) to know it as well in case it's me
who starts the fire that wipes out all our data except the offsite backups
and I get caught in it.  (hey, contingency, right?)

Dee will take the tapes home Wednesday and Friday nights.  She'll bring in
one tape at a time on Tuesdays and Thursdays.

The key expires on Wed Jun 18 14:10:24 2003 EDT

I did the second-last test today.  Data written with our drive can be read
by other drives... This means in the event of a catastrophic failure, we can
read the data off in a new drive.

Final test will be a week after the first backup when we bring a tape back
to make sure they don't typically encounter too much EMF in their trip
to/from the office.

I'll try to have the thursday backup ready to go offsite.

The ToDo list stands at:

Fax stuff... maybe make leia do it?  That or use an external modem.
Tighten firewall rules outgres filtering and filter DMZ.
central logging/log processing and hardcopy logging.
Automatically update virus definitions on clients.
Automatically create and print reports on the fax usage (see 'S:\docs\fax')
Research a virus scanner for Obiwan
VNC on WinNT machines

newuser script
        - create UNIX account   (adduser)
        - create SAMBA account  (smbpasswd -a)
        - auto-setup Netscape   (/home/odin/bin/netscape.pl)

-Dan

-- 
"There are two limits that this standard places on the number of
characters in a line. Each line of characters MUST be no more than
998 characters, and SHOULD be no more than 78 characters, excluding
the CRLF."       -- rfc2822 - Internet Message Format