Table of Contents
Advertisement
"Example: Replication Configuration for Clustered Appliances" on page 535
■
Example: Replication Configuration for Clustered
Appliances
The goal of this example is to configure replication properly to ensure that projects continue to
replicate after a cluster takeover, cluster failback, or after performing reverse replication on a
target appliance.
Configuration Guidelines
■
Example: Configuring Replication for Clustered Appliances
■
Replication Data Path Illustrated Examples
■
Configuration Guidelines
When configuring replication for clustered appliances, follow these guidelines:
Ensure that both replication source and target appliances are in the CLUSTERED state. For
■
details, see
Table 44, "Cluster States," on page
Select network interfaces and IP addresses to be used for replication traffic on the
■
replication source and target appliances.
Select a singleton network interface. Unlike a private network interface, a singleton
■
network interface will be taken over by the surviving controller following the loss
of one of the controllers in the cluster. Using a singleton interface ensures successful
replication following a cluster takeover or failback transition. For more information
about singleton interfaces, see
Ensure that the selected network interface on the source appliance and the pool from
■
which the data will be replicated are both assigned to the same controller. This is always
the case when the source cluster is in the CLUSTERED state.
Similarly for the target cluster, the selected network interface on the target appliance
■
and the pool into which the data will be replicated must both be assigned to the
same controller. This association is guaranteed when the replication configuration is
performed while the target cluster is in CLUSTERED state.
The source and the target appliances must be able to successfully communicate using the
■
selected network interfaces and IP addresses.
Create static /32 host-based routing between target and source appliances to ensure that
■
following replication reversal, the selected interface is used for outbound replication traffic
when reversal has transformed the current target into a replication source.
209.
Table 43, "Cluster Resource Management," on page
Remote Replication Concepts
208.
Remote Replication
535
Advertisement
Table of Contents
