[2447] in Release_7.7_team
Re: ADSM scheduled backup
daemon@ATHENA.MIT.EDU (Jonathon Weiss)
Sun Oct 15 17:56:08 2000
Message-Id: <200010152155.RAA23418@Bearing-An-Hourglass.mit.edu>
From: Jonathon Weiss <jweiss@MIT.EDU>
To: Alex T Prengel <alexp@MIT.EDU>
cc: release-team@MIT.EDU
In-reply-to: Your message of "Thu, 12 Oct 2000 15:31:12 EDT."
<200010121931.PAA14691@astrophel.mit.edu>
Date: Sun, 15 Oct 2000 17:55:58 -0400
> 1. exclude filesystems like /usr/vice/cache on SGI, /var/usr/vice, /,
> /usr on Suns (and similarly for Linux).
You may also want to exclude /proc and /dev/fd on solaris, depending
on whether they are sufficiently special that ADSM would ignore them
anyway. There are also similar filesystems on other platforms.
I would not exclude / on any platforms. It contains a lot of config
files that someone may want to recover.
I would exclude any file named srvtab, krb5.keytab, ssh_host_key,
ssh_host_key.pub, and ssh_random_seed. I would also exclude /tmp,
/var/tmp, and /var/rtmp. Most of these exclusions are to prevent
cryptographic secrets from going over the net in the clear.
> 2. exclude all non /var top level directories (like /etc, /dev etc.).
/etc in particular contains lots of config files (and generally isn't
too big)
> 3. exclude some /var directories we don't want backed up (like /var/boot,
> /var/dmedia etc. on SGI, likewise for Sun and Linux).
We probbaly want /var/server on this list.
We may want /var/sadm on it on Solaris.
Jonathon
