Blog Category: Disaster Recovery

Watch this on-demand webinar to learn the right way to deploy geo-distributed databases. We look at the pitfalls of deploying a single site and passive sites, and from there we show how to provide the best user experience by leveraging geo-distributed MySQL.

We’ve been receiving requests recently from MySQL users wanting to understand how InnoDB Cluster compares to Tungsten Clustering, our MySQL HA, disaster recovery, and geo-clustering solution. In response we have come up with this comparative outline, looking at some of the key features of each.

People approach Continuent for many reasons, including: MySQL Continuous Operations: their business is using MySQL for business-critical applications that require zero downtime, including for maintenance updates MySQL Performance: their application performance and user experience are suffering due to a faltering MySQL backend

How to build a multi-region, multi-master MySQL cloud database back- end capable of serving a global, high-volume cloud contact center: this global SaaS provider is a Cloud Contact Center solution provider, who needs to deliver up-to-date data to clients as quickly as possible.

This MySQL high availability and disaster recovery use case is based on a customer of ours who is a government-regulated lottery service and who needs 24x7x365 operations as well as be able to perform maintenance without any disruption to their public facing gaming website.

Version 6+ of Tungsten Clustering comes with a host of improvements for your Multi-Site Multi-Master topology (MSMM); this is partly why it has a new name: Composite Master-Master (CMM). Probably the most notable improvement is that the Managers are more aware. What does that mean?

This is the second post in a series of MySQL use case blogs. It discusses a SaaS provider dealing with sensitive medical data and their need to be able to quickly deploy clusters in AWS and recover from multi-zone AWS outages.

This is the first in a series of use case blogs. It discusses the concept of ‘Geo-scale MySQL’ - or how to build a global, multi-region MySQL cloud back-end capable of serving hundreds of user accounts.

Real time database replication is a must for clustering and other key business purposes, like reporting. There are a number of replication technologies available for MySQL, and some are even bundled into various solutions. When choosing a replication methodology, it is paramount to understand just how the data moves from source to target. In this blog post, we will examine how asynchronous, synchronous, and "semi-synchronous" replication behave when used for clustering. Also, we will explore how replication affects database performance and data availability.

Our colleague Matt Lang walks you through a comparison of building a global, multi-region MySQL / MariaDB / Percona cloud back-end using AWS Aurora versus Continuent Tungsten.

In case you missed the Multimaster webinar recorded live on Thursday, March 28th, 2019:

Learn how NewVoiceMedia built a global, multi-region MySQL cloud back-end to support a high-volume cloud contact center.

Enterprises require high availability for their business-critical applications. Even the smallest unplanned outage or even a planned maintenance operation can cause lost sales, productivity, and erode customer confidence. Additionally, updating and retrieving data needs to be robust to keep up with user demand.