Replication can be configured from any source appliance to any replication target regardless of whether each is part of a cluster and whether the appliance's cluster peer has replication configured in either direction.
The following rules govern the behavior of replication updates for clustered appliances:
Replication updates for projects and shares are sent from whichever cluster peer has imported the containing storage pool.
Storage pools that are owned by each controller can replicate to the same replication target, only if OS8.6.0 (or later) is installed on both controllers.
Replication updates are received by whichever peer has imported the IP address configured in the replication action on the source. Administrators must ensure that the controller using this IP address will always have the storage pool containing the replica imported. This is ensured by assigning the pool and IP address resources to the same controller during cluster configuration.
Replication updates (both to and from an appliance) that are in progress when an appliance exports the corresponding storage pool or IP address (as part of a takeover or failback) will fail. Replication updates using storage pools and IP addresses unaffected by a takeover or failback operation will be unaffected by the operation.
Related Topics