Johnathan Bailes wrote:
Many of the apps it was noted reside on the nas server and are remotely mounted. Therefore, the decision came down to only back up certain files in /etc to provide for an easier re-install.I got ideas of course -- passwd, shadow, nsswitch.conf, exports etc... However, anybody got any more complete ideas on what should and should NOT be backed up.
On our production servers I backup the following:
/root, /etc, /boot, /var/lib/mysql, /var/www, /home,
/var/spool/mail, /var/spool/cron, and /var/yp (/usr/lib/yp if it's a NIS slave)
You don't have to backup /boot because all it really has in it are your kernels, however I like to keep a copy of that stuff anyway, including grub. It's not that large, so it won't hurt. I don't really care for the rpm stuff because if the system should get compromised, or a drive should go south, I generally just reload the whole system from scratch - takes me all of about 30 minutes to do.
You may also want to think of a rotation policy with this. In our case, we do a 14 days rotation, and a 52 weeks rotation of Sundays and once a month I will dump that month's weekly backups to tape as well. I use rsync for the daily and weekly rotations, coupled with hard links which allows me to put all 14 days of roughly 6Gb worth of data on a 15Gb NFS partition - the same goes for the 52 weekly ones. Quite nice actually. A nightly backup runs under 5 minutes.
And as Bret (Bert?) can vouch for me, I've been working on my backup (Bash) script all these days, making it better, cleaner, yaddi yaddi yadda.
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
