![]() |
|
|
|||||||
| Administrative Another way to contact admins and moderators. |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||||||||
|
Downtime this afternoon (Monday, April 27)
Seems our /data partition was 100% full, so mysql couldn't write. No hardware crash (which I'm very happy about, we've gone 6 weeks without one since the kernel changes).
Anyway, we're back up now. |
| Sponsored Links |
|
|||||||||
|
Word up C-Dogg
Thanks |
|
|||||||||
|
What did you do?
|
|
|||||||||
|
Mysql's bin logs were turned on. They're still on (and building 1gb files every day and a half or so), but we're going to turn them off. We do a fresh mysqlhotcopy nightly anyway, so I'm not terribly concerned about having those files. As a quick remedy, I just moved a dozen of them over to another array and restarted mysql.
|
|
|||||||||
|
OK, the bin(ary) log allows for point-in-time recovery. In other words, if you don't back it up, and the site crashes at 1:19 PM, then you can only recover up to the last full backup. Backing up the bin logs allows for recovery to 1:19 PM.
I'm not advocating either, it depends on what you feel you can lose. |
|
|||||||||
|
Quote:
We have them going back a month and a half. At 1g every 36 hours or so, it adds up. |
|
|||||||||
|
Quote:
I found this link which seems to indicate there is a way within SQL to get the logs to expire automatically (and it's configurable too) Patterns ? Blog Archive ? MySQL: Purge binary logs Hope that helps you C-dawg. |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|