- Joined
- Jan 4, 2001
- Messages
- 10,333
First, let me apologize for the downtime that occurred today. I had our forum vendor perform an upgrade to the gallery, however something went wrong during the process which corrupted the database.
After having spent a few hours trying to fix the issue, I decided it was best to perform a restore from 3:17AM this morning. Due to the backup being on a server offsite, it took 7 hours to pull the backup and then perform the restore. At around 6:30 PM everything seemed to be working great, until the members table in the SQL database became corrupt. No big deal, I ran a repair on the db, which resolved the issue.
At around 7:30 PM I was reading a PM, and noticed that one of the members on the PM had been deleted. Only a few of his posts were left behind, however all identifying data was removed. Turns out, when I repaired the db, this member account had become corrupt. When the repair ran, it removed the account.
At around 8:15 PM I decided enough was enough. I decided to pull a backup from Friday night, and restore that one. Best to go back to a date that I knew was stable.
Long story short, I restored a backup that is 4 days old. I'd rather make 100% sure that all data is intact before it's too late, so we lose 4 days worth of posts. Upside? We know our db is functioning and intact. This time next month, no one will even notice the few days of missing data.
So there you have it. I need a break... and a beer...
After having spent a few hours trying to fix the issue, I decided it was best to perform a restore from 3:17AM this morning. Due to the backup being on a server offsite, it took 7 hours to pull the backup and then perform the restore. At around 6:30 PM everything seemed to be working great, until the members table in the SQL database became corrupt. No big deal, I ran a repair on the db, which resolved the issue.
At around 7:30 PM I was reading a PM, and noticed that one of the members on the PM had been deleted. Only a few of his posts were left behind, however all identifying data was removed. Turns out, when I repaired the db, this member account had become corrupt. When the repair ran, it removed the account.
At around 8:15 PM I decided enough was enough. I decided to pull a backup from Friday night, and restore that one. Best to go back to a date that I knew was stable.
Long story short, I restored a backup that is 4 days old. I'd rather make 100% sure that all data is intact before it's too late, so we lose 4 days worth of posts. Upside? We know our db is functioning and intact. This time next month, no one will even notice the few days of missing data.
So there you have it. I need a break... and a beer...