I'm interesting in hearing about anyones experiences with using mk-slave-delay.

Currently we have a MySQL server with replication slave running as a backup. This works well, and have dry-run tested swapping them over in case of failure. However in reality we are a lot more likely to accidently drop a record/table/database than we are to destroy the server entirely. So we are toying with the idea of running a delayed slave, which provides a constant hour-beind backup, ready for us to pull records from in case of accidents.

So have people managed something similar with mk-slave-delay? I'm hoping it's as impressive as the other maatkit tools!

link|improve this question
(Now set as coommunity wiki). – Coops Jul 28 '09 at 11:58
Anyone else think this sounds like spam – David Pashley Jul 28 '09 at 14:16
Spamming people for their opinions - is that not just flamebaiting? But really, the set of maakit tools is pretty useful. I've only been using them 2 weeks and I've come to depend on them day to day. – Coops Jul 28 '09 at 17:14
@David No this doesn't sound like spam to me. – Rory Jul 29 '09 at 21:47
feedback

3 Answers

up vote 2 down vote accepted

Well I've started playing with it, and so far it has worked without any hassle. Nice and easy. I guess it's just a case of fiddling with the settings to get the it's performance right.

link|improve this answer
feedback

I have no experience with mk-slave-delay, but you could just dump the DB every hour.

link|improve this answer
Yeah I've used scripts to do that before, but the idea a "hot" backup is quite appealing. – Coops Jul 29 '09 at 19:47
feedback

i have been trying to set it up. once succeeded as a test case and seemed fine. but am facing no slave status error at the moment.:) Not sure that helps...

link|improve this answer
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.