Severalnines Blog
The automation and management blog for open source databases

Severalnines blog

Filter by:
Apply (1) filters
52 blog posts in 1 category

Top Common Issues with MHA and How to Fix Them

MHA (Master High Availability) is a popular failover solution used in MySQL Master-Slave topologies. It is stable and used in production by large companies such as Facebook. In this blog, we outline the most common but important issues that you might encounter when running MHA. We’ll also see how to resolve them.

How to Automate Database Failover with ClusterControl

It might not be possible to avoid disasters, but with some preparation, it is certainly feasible to reduce the impact on your business. Automatic failover is one of those things. The goal of database failover automation is to minimize your downtime and reduce loss of money. However, failover can not always be automated as there are risks; false positives may lead to unnecessary escalations.

In this blog, we’ll have a look components you may use to build an automated stack, and take a closer look at ClusterControl’s failover functionality.

An Overview of Streaming Replication for TimescaleDB

TimescaleDB uses a stream of write-ahead log (WAL) records to keep the standby databases synchronized. In this blog, we’ll review some concepts related to Streaming Replication and how ClusterControl can help us configure it in an easy way.

How to Perform a Failback Operation for MySQL Replication Setup

In case of master failure in a MySQL Replication setup, the most updated slave can be promoted to new master and all slaves repointed to the new master. But once the failed master has been fixed, what is the best way to re-introduce it as master, so as to restore the original topology.

This blog post shows how to perform the MySQL master failback operation.

How to Achieve Automatic Failover for TimescaleDB

Failover is the process of moving to a healthy standby component, during a failure or maintenance event. The quicker it can be done, the faster you can be back online. If you’re looking at minimizing downtime and meet your SLAs through an automated approach for TimescaleDB, then this blog is for you.

Master High Availability Manager (MHA) Has Crashed! What Do I Do Now?

How do I ensure that MHA (Master High Availability Manager) will always perform the failover for me? What would happen if it crashes? This blog post will answer your questions.

Understanding the Effects of High Latency in High Availability MySQL and MariaDB Solutions

To insulate our database infrastructure from failures, we build redundant cluster systems. For instance, MySQL and MariaDB high availability can be implemented by master-slave as well as master-master replication solutions. There are a number of variables that affect our choice solution. In this blog, we will look into considerations around latency.

Configuring PostgreSQL for Business Continuity

Business continuity for databases means databases must be continuously operational even during the disasters. It is imperative to ensure that production databases are available for the applications all the time even during the disasters, otherwise, could end-up being an expensive deal.

How to Replicate PostgreSQL Data to Remote Sites

In a busy database environment with larger size databases, the need for real-time data replication is a common occurrence. Applications often need the production data to be replicated in real-time to remote sites for analytics and other critical business operations needs. This blog provides an overview of several options you can use to replicate your PostgreSQL data to a remote site.

HA for MySQL and MariaDB - Comparing Master-Master Replication to Galera Cluster

Replication and Galera Cluster are both widely used to implement high availability for MySQL/MariaDB, but when should you pick one over the other? What are the limitations of each solution, and what are the trade offs?
In this blog post, we will look at the differences in terms of data consistency, conflict resolution, failover, node provisioning and robustness.