Do data center regions offer redundancy using Master to Master mySQL?

If I create two droplets, one in a New York data center and another in San Francisco and then create a Master to Master replication of a mySQL database (using this DO Community article: will that provide redundancy should one of the data center go down/offline? Or if my one droplet is down in NY the one in SanFran will also be down? I would think not, but would like confirmation.

I’m on a shared hosting plan now with another provider and need redundancy with my database.

I’m looking to use a fail over solution as explained in this article:

DO seems like a good option but want to make sure this is how it would function. Any other suggestions on how to make mySQL DB redundant? It’s not a large database but critical for my clients to have access.


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Whilst this will work as you expect in terms of redundancy you have not taken into consideration the latency between the two DC’s. I’m not sure what the latency between the two of them but it could cause issues in a master-master config even with Semisynchronous Replication enabled and configured correctly. Just something to consider.

Hey there,

If you created a Master-Master replication across two datacenters and one datacenter went down, that would not affect the other droplet in the other datacenter. Using your example, if the NYC droplet went down, the SFO1 would continue to operate. In this scenario, you would just have to switch over to using the SFO1 droplet for your DB access.