UESPWiki talk:Database Outage (July 2009)

Other Thoughts

• Having the binary logs and actual database files on two separate hard drives would prevent both from being wiped out by a bad hard drive (and would also prevent a flaky hard drive from causing corruption to both logs and files)
• Having the OS (everything provided by iWeb) on a separate drive from everything else might also make hard drive replacements (or any type of hardware replacement/upgrade/etc.) less difficult
• An easier option than making offsite backups available to multiple admins might be to place another copy of all backups onto util1/content3 (or some other computer that's already available) -- requires less bandwidth, faster to retrieve the data, and would have been sufficient during all of the recent problems. (Plus, if all of iWeb goes down, I doubt that a few extra days before we can access our offsite backups is going to be our primary problem!)
• Implement backup of mysql basic info (mysql users, permissions; i.e., the contents of the mysql database) -- probably only necessary weekly
• Implement backup of OS-type configuration files (passwd, groups, my.cnf, httpd.conf, etc) -- needs to be done on all servers, but again weekly is probably sufficiently frequent
• Keep me away from tall ladders :P (Mitigation measures already put in place by my husband, in collaboration with other family members)

--Nephele^Talk 00:10, 5 August 2009 (UTC)

Good comments...Thanks! -- Daveh 01:25, 5 August 2009 (UTC)