> > I am no expert on playing around with IP addresses, but I would think
this
> > a rather dodgy option. Wouldn't connections which you appear to have
open
> > still get through, and connect to something unexpected? Dynamic DND
would
> > probably work. I cannot guarantee access to the DNS syste
Hello,
I am no expert on playing around with IP addresses, but I would think this
a rather dodgy option. Wouldn't connections which you appear to have open
still get through, and connect to something unexpected? Dynamic DND would
probably work. I cannot guarantee access to the DNS system I (or rat
> I was considering having a floating IP for each of the machines, so that
> if one dies, the other takes over the others IP address, thus making
> changes at the application level unnecessary really.
I am no expert on playing around with IP addresses, but I would think this
a rather dodgy optio
Hi,
thank you very much for your reply!
I think it's simpler than you thought.
This is just the kind of response I was hoping for :)
Just set up circular replication (A replicates B, B replicates A) and
> ensure, at the application level, that
you only write on one machine for each separate dat
I think it's simpler than you thought. Just set up circular replication (A
replicates B, B replicates A) and ensure, at the application level, that
you only write on one machine for each separate database. MySQL handles
circular replication: updates travel round the circle until the reach the
mach
