So, we're done. There's still a memory upgrade to come, but the main part is finished.
Well, it's running faster, more like the EN World good speed days.
I know you got a dude to do some tweaking and stuff, but can you confirm that y'all have done any variation of the following:
get a snapshot of the server if it is a VM
punch out backups of the DB, really easy and fast if it it is MySQL using mysqldump
make copies of the code & modifications (you never should have lost code, and the original developer should have had a copy).
Having a disaster recovery plan in place would have mitigated the damage. it ain't gotta be fancy and long winded. But backing up your code/site directories was probably just as important as the data. We lost way more code/features than posts from the great crash, when it should have been the reverse. Code don't change that often between backups, data does.
Granted, its possible, you had all the code, but it wasn't compatible with the new vbulletin. I only inquire, because this was a huge setback, and as somone with his own servers running mission critical applications, the minimal steps to restore it shouldn't have been so great a setback.
.
