Configuring Secure Clusters for Cross-Cluster Mirroring and Replication
Cross-cluster tickets are required on secure clusters that need to pull data from
another secure cluster and on secure clusters that need to push data to
another secure cluster. For example:
- Volume mirroring is a pull operation. The volume data is pulled by the destination cluster from the source cluster. Because the destination cluster is performing the operation, the destination cluster receives a ticket that is generated on the source cluster.
- Table and streams replication is a push operation. The table or stream data is pushed from the source cluster to the destination cluster. Because the source cluster is performing the operation, the source cluster receives a ticket that is generated on the destination cluster.
You can configure secure clusters for cross-cluster mirroring and replication manually
(as described below) or automatically by running the
configure-crosscluster.sh
utility. If you choose to run the utility,
the utility configures the clusters for both mirroring and replication in both
directions. For more information, see configure-crosscluster.sh
.