On May 7, 4:15 pm, "goo...@venix.com" <goo...@venix.com> wrote: > MySQL has a mechanism for a database to read the log from a master > database and replay the commands. This provides a loose coupling with > near real-time backup of the data. Should the backup server stop or > lose contact, the primary server is unaffected. When the backup > server regains contact, it restarts the log processing from the point > where it left off.
MySQL log based replication is asynchronous. It's only useful if losing some transactions in case of a crash isn't a problem. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
