For HIGH AVAILBILITY articles under category MySql.
How to Configure InnoDB ReplicaSet mysqlshell AdminAPI includes support for InnoDB ReplicaSet, which enables you to create and administer a set of MySQL instances running asynchronous GTID-based replication. An InnoDB ReplicaSet consists of a single primary and multiple replicas. InnoDB ReplicaSet Prerequisites Only instances running MySQL version 8.0 and later are supported. Only GTID-based replication is supported, binary log file
Asynchronous Replication Automatic Failover in MySQL MySQL 8.0.22 supports an asynchronous connection failover mechanism. This feature allows a replica/slave to automatically failover to a new source/master, in case its existing source/master fails. When the existing connection source/master fails, the replica first retries the same connection for the number of times specified by the MASTER_RETRY_COUNT. The
How to Setup MySQL Master-Master Replication (Circular Replication) Master-Master Replication (Circular Replication) also known as ring topology in MySQL, this setup requires two or more MySQL servers which act as a master. All masters receive writes and generate binlogs. Below points should be considered while doing the master-master setup. You need to set an auto-increment
MySQL Multi-Source Replication – GTID Based Sources In this blog post, we will see How to setup MySQL Multi-Source Replication – GTID Based Sources. For this demonstration, we will be using the below configuration. We have already set up 2 mysql instance in test-machine01 server running on port 3306 (Server_ID : 1) & 3307 (Server_ID
Step by Step Physical Standby Database Creation in Oracle Data Guard is used for disaster recovery and high availability. Due to any disaster, if our PRIMARY database got crash so, in that case, our STANDBY may become our PRIMARY database. Here, our client requirement, we need to create a STANDBY database using RMAN backup. Below
MySql Semisynchronous Replication In the previous blog, we saw How to create MySql GTID-based Master Slave Replication – Single DB, Click here to read more. We will use the same configuration to convert it from asynchronous to semisynchronous. MySQL replication by default is asynchronous. MySQL 8.0 supports an interface to semisynchronous replication that is implemented by plugins. Step 1.
MySQL Master Slave Switchover In the previous blog, we saw How to create MySql GTID-based Master Slave Replication – Single DB Click here to read more. We will use the same configuration to perform Switchover between Master & Slave. Current Configuration. Host name IP Role Server ID Installation Link test-machine01 192.168.114.170 Master 1 Click Here test-machine012
MySql GTID-Based Master Slave Replication – Single Database In previous blog we saw How to create MySql File-based Master Slave Replication – All Database Click here to read more. GTID Replication: In this post, we will see How to create MySql GTID-based Master Slave Replication – Single DB. The newer method based on global transaction
Drop MySql Replication Slave Configuration In a previous blog, we had created File Based Master Slave Replication Click here to read more. In this post, we will remove the same master slave configuration. Below are detailed steps: Login to mysql slave instance and use command show slave status \G to get the current configuration. Run
Combo Patch Apply on Primary & Standby Database in Oracle In this article, we are going to demonstrate step by step apply combo patches on Oracle Primary & Standby (DATAGUARD) which released in January 2021, combo patch contains PSU (31985579) and OJVM (32119956) patches. Below is the database, system, patch id, etc. details. COMPONENTS PRIMARY
