• New here? Register here now for access to all the forums, download game torrents, private messages, polls, Sportsbook, etc. Plus, stay connected and follow BP on Instagram @buckeyeplanet and Facebook.

9/26/10 - Database Errors between 5-5:30am

Jump to latest Follow Reply
Sort by date Sort by votes
Clarity

Clarity

Will Bryant
Staff member
Sometime around 5am ET portions of the database crashed -- so if you got/saw those notices, it wasn't just you. As of this post we're (obviously) back up and everything appears to be fully healthy. Running a few more mysql commands and then all should be well. I will watch it closely today, but I don't expect any more problems.
 
JCOSU86;1781834; said:
Why kind of maintenance do you do on this? What is in the scripts you run?
Click to expand...


This time it was an errno 126 that occurred as the machine was doing its morning database backups. The drive I use for that was only at 75% capacity, but my best guess is that it was squeezed for space and that resulted in one of the key vB tables crashing. Either way, I just did a repair, and then ran vB's own repair/optimize routine on the whole database. Got the drive down to 58% capacity by killing some very old backups and it hasn't happened since.
 
Upvote 0
Clarity;1782019; said:
This time it was an errno 126 that occurred as the machine was doing its morning database backups. The drive I use for that was only at 75% capacity, but my best guess is that it was squeezed for space and that resulted in one of the key vB tables crashing. Either way, I just did a repair, and then ran vB's own repair/optimize routine on the whole database. Got the drive down to 58% capacity by killing some very old backups and it hasn't happened since.
Click to expand...
How many backups do you keep? Are they full backups or cumulative (just changes from the last one)? I would think a couple of full backups are all you need...

Do you copy to tape?
 
Upvote 0
Clarity;1782019; said:
This time it was an errno 126 that occurred as the machine was doing its morning database backups. The drive I use for that was only at 75% capacity, but my best guess is that it was squeezed for space and that resulted in one of the key vB tables crashing. Either way, I just did a repair, and then ran vB's own repair/optimize routine on the whole database. Got the drive down to 58% capacity by killing some very old backups and it hasn't happened since.
Click to expand...
:hatepc: I dont know WTF your talking about, but it sounds good to me! Hell im lucky i can turn this damn Commodore 64 on!:smash:
 
Upvote 0
JCOSU86;1782230; said:
How many backups do you keep? Are they full backups or cumulative (just changes from the last one)? I would think a couple of full backups are all you need...

Do you copy to tape?
Click to expand...

We keep 5 days worth of full copies on our box (this morning's copy will replace the one from 9/25), and a single daily to a remote location (not tape). We also have backups of the webdirs and configs on and off box.

Our drives just aren't very big, but I just hadn't bothered to delete old 'extra' backups (some related to when we recovered the lost Troy Smith posts, some related to major db changes, etc.). Now that I have, we seem to be good to go for the time being.

It could also have been that the table crash was unrelated to drive space. We had been floating around 70-75% capacity on that partition (one dedicated to backups, the databases themselves are elsewhere) for months. Whatever it was, the 'fix' was quick and easy this time.
 
Upvote 0
You must log in or register to reply here.
Back
Top