Backup Infrastructure

From Tardis
Revision as of 18:33, 29 January 2006 by Seth (talk)
Jump to: navigation, search

The other half of the raid array for the homedirs in dalek is sitting in brigadier. We do not have any form of backups of homedirs in place, other than a copy from about a year ago.

Same applies to the webserver, although it's raid is in place, the disk has some very bizarre filesystem errors (re: ~kate/qcmweb)

Things to backup

User data

This is stuff we just can't get back/rebuild

Currently backed up to /root/ldap/backup on baker (the LDAP server). This should backup elsewhere, for obvious reasons.
Home dirs
THIS IS UNRAIDED AND NOT BACKED UP! This has to get fixed on Tardis Day I.
Mail dirs
Web dirs
Raid-Mirrored. Not backed-up.
Not backed up. We should probably do SQL dumps, rather than dumps of the raw db backened.

Other stuff

System configurations
LCFG proved too much of a beast to handle. Best methods for doing this, suggestions?
Tarballing /etc would help in a lot of cases, but isn't a proper solution.
System logs
There's probably some sense in this, if we get haX0rised, but that's probably OTT.
Might be worth sending syslogs to a log server, which only l33t admins can access? - sjh
Seems such a facility already existed on dalek, it just hadn't been used since early 2004 - this was like 300MB of logs a day - would want to seriously bitshift this down to reasonable size if we want to consider storing them - Seth 18:28, 29 January 2006 (GMT)
The wiki
MediaWiki has facilities for this - probably want to automate...


Pert has started installing a new machine - Tennant (CNAME backup.tardis) which contains one 120GB disk in LVM. We will be using backup PC to administer backups.