manual failover

There are three main options for failover operations for Hyper-V replication:Planned failover, as the name implies, is a pre-determined plan to fail over. This approach needs to meet two prerequisites: The virtual machine must be shut down before

Redis SentinelThe module has been integrated into the redis2.4+ version, although it is not release at the moment, but it can be attempted to use and understand, in fact Sentinel is still a bit complicated. The main function of the Sentinel is to

MySQL high availability solution: MHA-based Automatic Failover Cluster bitsCN.com MySQL high availability solution: MHA-based Automatic Failover ClusterComparison of common high availability solutions for MySQL (from the official manual) Only MySQL

MHA IntroductionMHA is a MySQL, a Japanese MySQL Daniel written in Perl failover scheme to ensure the high availability of the database system. During downtime (usually within 10-30 seconds), complete failover, deploy MHA, avoid master-slave

Reference: www. clusterdb. commysqlreplication-and-auto-failover-made-easy-with-mysql-utilities Environment Introduction: master: demoenv-trial-1slaves: demoenv-trial-2demoenv-trial-31. install PerconaServer on all servers: $

MySQL high availability solution: MHA-based automatic failover ClusterComparison of common high availability solutions for MySQL (from the official manual) Only MySQL Cluster and DRBD + Heartbeat are available for automatic database failover. These

The previous article has been prepared for the configuration of the mirrored database, and the next step is to enter the real configuration phase First, set security on the mirror database server and start the database mirroring session 1, expand

This article introduces the manual failover operation and troubleshooting process in the redis master-slave environment. When the master instance goes down, the master instance is upgraded from the master instance to the master instance and data is

SQL Server database mirroring based on availability group failoverMicrosoft began to introduce database mirroring from SQL Server 2005 and quickly became a popular failover solution. A big problem with database mirroring is that failover is database-

Introduction to the high availability of a replica set the replica set achieves high availability through automatic failover. When the master node fails, the slave node can be elected as the master node, in most cases, this process is automatically