DaniWeb Downtime ... all my fault
Well, I just got myself through a major disaster. A couple of days ago, vBulletin, the forum system which powers the core of DaniWeb, released a shiny new version, vB 3.6. Every day since, they've been announcing new features - many of which look just awesome!
This afternoon, they finally released public beta. My first instinct was to naturally wait until stable. However, when 7pm rolled around, my anxiousness got the better of me.
I dutifully backed up the database and the filesystem, and away I went. Only to find that the upgrade wasn't trivial by any means, but rather required many file edits and template edits and all kinds of stuff ... the kinda stuff that you'd be crazy to not have a test server running for at least a week first before attempting the upgrade.
Well ... that was behind me now. So the clock is ticking ... 8 pm rolls around, and I try to crazily scramble to fix one thing after another. Maybe if I pull an allnighter ...
And then I think about that SQL backup I saved! But last time I ran a mysql > source to restore the database, it took about 8 hours, and that was months ago! Imagine how long it would take this time.
On the other hand, once I went through the 8+ hours of downtime, we'd at least be back to normal before the morning. My only other option at this point was to pull an allnighter - or two - scrambling to upgrade all of my hacks and additions and templates and everything else to be 3.6 compatible. Remember, only the CORE of DaniWeb is based on vB - the portal, blogs, code snippet library, tutorials, link directory, and all of the extra features, which are all integrated btw, are my own creation.
So, I sighed, I took a deep breath, and I flushed out the live database, and restored from backup. And ... drumroll please ... it finished in less than five minutes. I promise you. In fact, if I am lying, I wouldn't be able to type this all out right now, one hour after I started this whole disaster (Which turned into about 30 mins on and off of downtime during and after the upgrade when I didn't know what to do with myself).
The moral of the story is don't underestimate the power of a new dual core dual opteron as a dedicated database server. I swear to you guys ... what used to take a full half of a day on a Dual Xeon took 5 minutes max on a dual core Dual Opteron. Aside from the difference in the processor, the other advantage (and it's a big one) is that I now had a dedicated database server which was able to focus entirely on restoring the backup, and didn't have to deal with constant Apache connections and 1000+ users trying to browse a site that's down.
So ... the upgrade will be for another day, after it's already been fully prepared on a test server and ... did I mention ... when it's outta beta?
Offline 
