Blog Tag: Maintenance

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.

Why does the DIY approach fail to deliver vs. the Tungsten Clustering solution for geo-distributed MySQL multimaster deployments? Before we dive into the 10 reasons, note why commercially-supported enterprise software is less risky and in fact less costly.

Zero-Downtime Cluster Maintenance: Comparing the Procedures for Upgrades versus DB/OS Maintenance

How to move the Relay role to another node in a Composite Tungsten Cluster

When it comes to zero downtime, proxies are the first line components of a cluster. In order to achieve High Availability (HA) for MySQL, MariaDB and Percona Server, a commonly deployed setup consists of configuring load balancers (hardware or software) on top of those proxies.

Tungsten Clustering offers a graphical administration tool called the Tungsten Dashboard™ to help with your management burden. The GUI makes the deployment much easier to visualize and administer.

One nice thing about Tungsten Clustering is that you need just a single command to move the master role to another host in your cluster.

In this blog post, we discuss failover concepts and administration.

The Tungsten Replicator is an extraordinarily powerful and flexible tool capable of moving vast volumes of data from source to target.

The Tungsten Replicator is an extraordinarily powerful and flexible tool capable of moving vast volumes of data from source to target.

In this blog post we will discuss the basics of how to implement and use filters in the Tungsten Replicator.

Managing a single cluster takes time and attention, and handling multiple clusters spread out over many sites is even more demanding. Tungsten Clustering offers a graphical administration tool called the Tungsten Dashboard™ to help with your management burden. You are able to view, monitor and maintain all of your clusters all in one place.

Think about it - your global, cloud-based application needs to be online and available for the business to run. Downtime is to be avoided like the plague. Perhaps you even have multiple cloud providers to span.

How do we create a database service layer that handles all kinds of failures?