On Dec 30, 12:33 pm, Nick <[email protected]> wrote: > Does knowing the technical details behind why the site is down offer > anything more than another line of text to read?
Here it is, with some simplifications and, probably, mistakes: The database server crashed due to a memory module going bad. Aldie brought it back up (with one of the slots turned off) repaired the database where it was corrupted, and backed it up almost immediately. We started importing the database into our backup server, but that process takes almost a full day. The next day, the import was finished, and shortly thereafter, the main server was repaired by Dell as well. At this point, in theory, we could have started the site back up again, but it would then be vulnerable to the same sort of problem should the db server ever crash again. Aldie decided instead to take the time to (again) set up a second "slave" database that would mirror the master, and could serve as a backup in the event of another such problem with the master. There are several ways to do this, all of them slow. He picked the one that would involve a one-time slow conversion of the database tables to a new format, and would, in the future, allow us to set up the slave much more efficiently than we can currently. This slow process has taken even longer than expected, but is near the end. When it finishes, Aldie will set up the master and slave database, and, in theory, we should be protected from such a long outage in the future, or at least such a long outage due to database failure. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BGG Down" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/BGG_down?hl=en -~----------~----~----~----~------~----~------~--~---
