[jacques_chester]

> 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

[iamjustlooking]

You can run your daily/hourly backups on the mirror and not impact performance on your main database.

[jacques_chester]

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.

[Negitivefrags]

The mirror is to run the backups on, not the backup itself.

[dsl]

CHANGE MASTER TO MASTER_DELAY = 3600;

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

[jacques_chester]

If this is your tactic, I'd think the binary log would be the winning way to rollback a bad delete.

[mseebach]

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.

[jacques_chester]

There's lots of disaster reports that start with "shouldn't" and "normally we wouldn't" :)

http://www.taobackup.com/