| Path to Source Stream |
The path and name of the stream that you want to create
a replica for. |
| Destination Cluster |
The destination cluster for the replica, where gateways
are configured to allow source cluster to send updates. |
| Path to Replica |
The path and name of the replica stream. |
| Replication State |
Specify whether or not to start replication by choosing
one of the following:
- Automatic Setup — Creates
the stream on the destination cluster, registers
the stream on the destination cluster as a
replica, adds the current stream as an upstream
source, copies the content of the current stream
into the replica, and starts replication. In this
case, the replica stream starts empty and
accumulates messages over time.
- Pause Replication —
Creates the stream on the destination cluster,
registers the stream on the destination cluster as
a replica, adds the current stream as an upstream
source, but prevents replication from immediately
starting after. Pausing replica like this allows
you to load the data into the replica from the
current stream, after which you can restart
replication.
Note: If you are interested only in the messages
that are published to the source stream after
replication starts, then you do not need to pause
replication initially. However, if you want the full
set of messages from the source stream that have not
yet been purged or marked for deletion, then pause
replication initially.
|
| Multi-Master Setup |
(Available only with Automatic
Setup) Multi-master topology, in which
there are two primary-secondary relationships, with each
stream playing both the primary and secondary roles.
Client applications update both streams and each stream
replicates updates to the other. If this is not
selected, stream replication will be basic
primary-secondary topology. In this topology, you
replicate in one direction.
See Stream Replication for more information.
|