Recovery & Repair

Galera Cluster is a high available database that can handle failure of some of its nodes just fine. How should you decide on the size of the cluster and is it enough to have a quorum to tell the cluster is highly available? This blog post will answer those questions.

In this blog post, we look deeper into one of the most advanced features offered by ClusterControl called automatic database recovery and failover. ClusterControl is able to recover clusters, nodes and database-related processes to ensure you achieve the best database uptime possible.

This article gives an overview of the two most popular backup utilities available for MySQL, namely MySQL Enterprise Backup and Percona XtraBackup. We will discuss some best practices that can be applied to high availability topologies in order to make our backups reliable, secure and consistent.

In a PostgreSQL database, VACUUM is the process to reclaim space occupied by dead tuples. In this blog, we will look into this process to know how it works and which options are available.

In this blog, we'll show you how to install a PostgreSQL Cluster from scratch, convert the asynchronous replication (default) to a synchronous one. I’ll also show you how to rollback if the response time is not acceptable as you can easily go back to the previous state. You will also see how to deploy, configure, and monitor a PostgreSQL synchronous replication easily using ClusterControl using only one tool for the entire process.

If you are looking at replicating data from a PostgreSQL cluster to another, you can use the new ClusterControl 1.7.4 with its new Cluster-to-Cluster replication feature. In this blog, you will see how to configure such a setup and what it can do for you.

Ever wondered how to run multiple Galera clusters and keep them in sync? That’s exactly what you can do with the new Cluster-to-Cluster replication feature in ClusterControl 1.7.4.  In this blog, you will see how to configure replication between two Percona XtraDB or MariaDB Galera Clusters.

Replicating your database cluster to a remote datacenter is key in achieving Disaster Recovery with minimal RTO and RPO, but there are other reasons like datacenter migration or geo distribution. However, if managing a cluster was not hard enough, setting up and managing replicated clusters takes complexity to another level. In this blog, we will have a peek at a new ClusterControl 1.7.4 feature that allows you to set up replication between clusters.

A hot standby is a common term in computing, especially on highly distributed systems. It's a method for redundancy in which one system runs simultaneously with an identical primary system. In this blog how you can create a Hot Standby Node on Amazon AWS for Galera Cluster 4.0 using MariaDB.

Master switches are very common operations in replication setups. They are part of every migration - from one environment to another, from older version of MySQL to more recent one. In a live production environment, you may want to reduce the impact they have on the application. If you wonder how to do it, we are here to help. In this first part we will go over the initial setup of the environment. In the upcoming next part we will explain the process of transparent master switch with ProxySQL.

Hosting your database with a cloud provider, such as Microsoft Azure, still requires you to prepare and define your disaster recovery policy. In this blog, we will cover all of the backup and restore methods Azure offers for MySQL.

Designing a large system that is fault-tolerant, highly-available, with no Single-Point-Of-Failure (SPOF) requires proper testing to determine how it would react when things go wrong. In this blog we will explore the failover and failback operations of Amazon RDS using Aurora.

In this blog post, we will analyze different failure scenarios in MongoDB production database systems, ranging from single-server issues to datacenter failover plans. We will walk you through recovery and failover procedures for the respective scenario.

Almost all cloud vendors provide some sort of high availability options in their managed relational databases. In this blog we are going to explore the failover handling for MySQL SQL nodes on Google Cloud Platform

In this blog we’ll take a look at the most common PostgreSQL failure scenarios and show you how you can solve or cope with the issues. We’ll also look at how ClusterControl can help us get back online

WordPress is, by far, the most popular CMS in the world powering millions of websites from small to large. But how can you ensure the unavailability of your database will not impact the website? In this blog post we will show how to achieve failover for your WordPress website using ClusterControl.

In this blog post, we compare automatic failover times for Amazon Aurora, Amazon RDS for MySQL, and MySQL Replication deployed and managed by ClusterControl. The type of failover that we are going to do is slave promotion in case of master goes down, where the most up-to-date slave takes over the master role in the cluster to resume the database service.

Disaster recovery environments can be expensive. Luckily, they don’t always have to be. This blog post explains how to us Amazon AWS to set up a DR solution on a shoestring budget.

The recent release of ClusterControl 1.7.3 offers new functionality which allows for a multi-postgresql installation on the same host. This type of setup can save you money and resources by running two instances on the same server. In this blog will show how to do it with ClusterControl.

A load balancer similar to the likes of ProxySQL & HAProxy, MariaDB MaxScale has its own diverse features and capabilities. MaxScale has the ability to do auto-failover which can save you from catastrophe as well as a switch over mechanism to make your life easier during maintenance. This blog explores this failover feature and how you can leverage it as part of your setup.