On May 8, 7:53 am, Ants Aasma ants.aa...@gmail.com wrote:
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
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
On May 6, 3:43 am, Ants Aasma ants.aa...@gmail.com wrote:
On May 6, 9:07 am, Vic vctr...@gmail.com wrote:
I'm looking for a way to have my DB replicated in REAL TIME to be used
in case I lose my primary copy.
I saw that the two phase commit exist but I'm not sure if that is the
correct
On May 6, 9:07 am, Vic vctr...@gmail.com wrote:
I'm looking for a way to have my DB replicated in REAL TIME to be used
in case I lose my primary copy.
I saw that the two phase commit exist but I'm not sure if that is the
correct option. I have the feeling that it would be abusing a
