4 ms·
> 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
by jacques_chester 14y ago
> 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
- Negitivefrags 14y agoThe mirror is to run the backups on, not the backup itself.
- mseebach 14y agoWell, 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 14y agoThere's lots of disaster reports that start with "shouldn't" and "normally we wouldn't" :) http://www.taobackup.com/ http://www.taobackup.com/
- iamjustlooking 14y agoYou can run your daily/hourly backups on the mirror and not impact performance on your main database.
- jacques_chester 14y agoRight. But the grandparent comment was suggestive of the possibility that he or she wanted the mirror to fulfil multiple roles, including being the backup.
- dsl 14y agoCHANGE MASTER TO MASTER_DELAY = 3600; Your slave will always be 5 minutes behind the master. You were saying?
- jacques_chester 14y agoIf this is your tactic, I'd think the binary log would be the winning way to rollback a bad delete.