A main pillar of the EDB Postgres™ Platform from EnterpriseDB™ (EDB) is the Management Suite, which provides capabilities for disaster recovery, high availability, monitoring, management, and tuning of PostgreSQL and EDB Postgres Advanced Server. EDB significantly advanced the Management Suite recently with the release of EDB Postgres™ Failover Manager 2.1. (Read the press release here.)
EDB Postgres Failover Manager provides highly available, fault tolerant database clusters built using PostgreSQL streaming replication to reduce downtime and keep data available when a main database fails. EDB Failover Manager provides the cluster monitoring, failure detection, and failover procedures that can be integrated into a variety of 9s-based high availability solutions.
EDB Failover Manager 2.1 advanced the Management Suite by providing a controlled switchover capability, which improves the general manageability of streaming replication clusters, and more configuration options to allow customization of failover procedures to meet various requirements.
One of the most frequently requested features from users of EDB Failover Manager has been to enable a ‘controlled switchover.’ This is the process by which when a replica is promoted to be a master, the old master is reconfigured to become a read replica of the new master. This is an important feature that supports two common use cases: (1) it enables the testing of failover procedures, and (2) it supports a near-zero downtime maintenance schedule.
In both use cases, the new switchover option for efm promote <cluster-name> -switchover should be used during a planned maintenance window. If the standby to be promoted isn’t up to date with the master, switchover will not be allowed. During this operation, the following occurs:
When testing failover procedures, this function ensures that your cluster continues to operate with the proper number of replicas, without requiring a full rebuild of the old master server.
To support near-zero downtime, this capability makes it possible for you to perform planned maintenance—for example, operating system or database patch applications—with minimal impact to your cluster. We recommend performing maintenance operations on your replicas first and restarting the replica databases as needed. When the cluster is in a state of no replication lag, you can use the switchover option when promoting one of the replicas so that you can subsequently update the old master with the same maintenance applications.
More Configuration Options and Custom Hooks
The more we see customers use EDB Failover Manager, the greater the need for the system to be flexible to support various deployment configurations. In this release, we added a number of improvements that allow customers to better integrate EDB Failover Manager notifications into their existing IT infrastructures and more discretely control failover procedures. These improvements include:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.