Configuring Data Replication from One Source to Multiple Targets
Configuring Data Replication from One Source to Multiple Targets
You can use the Server Manager with the InitialSync, Extractor, and Applier components to replicate data from a single source to multiple targets.
Data Replication does not support replicating data from a single source to multiple Amazon Redshift
or Apache Kafka targets.
One of the target databases is considered to be the
primary target database
. The other
secondary target databases
must be the same target type as the primary target. Also, all of the mapped target tables must have identical schema definitions. However, the target schemas can have different names.
All of the mapped columns in the secondary target tables must have the same names as the corresponding columns in the primary target tables and have datatypes that are compatible with those of the corresponding columns in the primary target tables.
When you configure replication, define one primary target and multiple secondary targets. The primary target is the target database that you defined on the
Target Database
tab.
To configure and run the replication job, complete the following high-level tasks from the Data Replication Console:
Define a Server Manager Main server on a machine in your environment and connect to it. The Main server does not need to run on the source or primary target.
Define a subserver for each of the other target machines.
From the
Server Manager
tab >
Connections
view, define a connection for the primary target database and a connection for each secondary target database.
Create and save the configuration. On the
Target Database
tab, specify the connection that you defined for the primary target database.
On the
Routing
tab, define each target server and connection. Optionally, perform the following tasks:
Filter rows by table so that different targets receive different subsets of rows.
Exclude one or more entire tables from replication to a particular target.
Rename the target schema so that each target uses a different schema name.
Override the apply mode or audit log table schema for a particular target.