News for hackers. Stuff that matters.
Re:AWS Data Pipeline by jacques_chester on Friday December 21, 2012 @11:30AM (#4953315)
> It might not be appropriate for you, but a good way to handle MySQL backups is to maintain a mirror.

    DELETE * FROM business_critical_data; WHERE obsolete = true;
You were saying? :D
Re:AWS Data Pipeline by iamjustlooking on Friday December 21, 2012 @11:45AM (#4953394)
You can run your daily/hourly backups on the mirror and not impact performance on your main database.
Re:AWS Data Pipeline by jacques_chester on Friday December 21, 2012 @08:51PM (#4955452)
Right. But the grandparent comment was suggestive of the possibility that he or she wanted the mirror to fulfil multiple roles, including being the backup.
Re:AWS Data Pipeline by Negitivefrags on Friday December 21, 2012 @02:11PM (#4954028)
The mirror is to run the backups on, not the backup itself.
Re:AWS Data Pipeline by dsl on Friday December 21, 2012 @03:03PM (#4954270)
CHANGE MASTER TO MASTER_DELAY = 3600;

Your slave will always be 5 minutes behind the master. You were saying?

Re:AWS Data Pipeline by jacques_chester on Friday December 21, 2012 @09:06PM (#4955491)
If this is your tactic, I'd think the binary log would be the winning way to rollback a bad delete.
Re:AWS Data Pipeline by mseebach on Friday December 21, 2012 @11:45AM (#4953389)
Well, with a functional mirror to run manual queries against, you wouldn't be running the risk of running such a query on your prod DB anyway. But yeah, you still need a dump.
Re:AWS Data Pipeline by jacques_chester on Friday December 21, 2012 @09:29PM (#4955545)
There's lots of disaster reports that start with "shouldn't" and "normally we wouldn't" :)

http://www.taobackup.com/