Overview of Outbound Replication
Outbound replication uses a replication channel to copy transactions from a DB system to another location. The channel connects the source DB system to the replica DB system or external replica, and copies transactions from the source to the replica.
Outbound replication is not a managed functionality. You are responsible for configuring and maintaining the channel, and for ensuring that the traffic between source and replica is properly configured.
If the replica is an external MySQL instance, you configure the replication channel on the replica. If the replica is another DB system, you configure the replication channel in MySQL HeatWave Service.
You can configure only a DB system as the source; you cannot configure a read replica as the source.
Prior to MySQL 8.3.0-u2, you cannot configure outbound replication if the DB system has HeatWave Lakehouse enabled.
As of MySQL 8.3.0-u2, you can perform outbound replication on a DB system with HeatWave Lakehouse enabled.
Lakehouse tables can only replicate to replica DB systems. Replicating Lakehouse tables to external replicas such as on-premises MySQL server causes replication to break with errors.
You can set up asynchronous replication from a DB system to achieve goals such as these:
- Scale-out - Spread the load by letting applications read from replicas, while the source handles writes and updates.
- Data distribution - Create a copy of a database for another location to use.
- Disaster recovery - Have a running copy of a database in a remote location for use if the primary location becomes unavailable.