Configuring a synchronous protected path between tenants on different clusters is subject to the following restriction:
If Tenant A replicates a protected path to Tenant B on a remote cluster, it cannot then replicate another path to Tenant C on the same remote cluster (that is, Tenant A cannot have replicated protected paths to more than one tenant on the same remote cluster). It can, however, replicate protected paths to Tenant C (or any other tenant) on a different remote cluster. Similarly, Tenant A can replicate additional protected paths to Tenant B on the same remote cluster.
Prerequisites (all require a cluster admin type VMS manager user):
A virtual IP pool on each of the peer clusters, dedicated to replication. The role of the virtual IP pool must be set to replication.
A replication VIP pool is used exclusively for routing replication traffic between the peers and not for serving data to clients. The CNodes that are assigned virtual IPs from the replication virtual IP pool are used to communicate directly with the remote peer, while other CNodes can communicate only indirectly with the remote peer.If there is no such virtual IP pool on any of the clusters, ask your cluster administrator to create a virtual IP pool, and be sure to set the role to Replication.
A designated replication peer configuration with the destination peer cluster on which data from the protected path will be replicated. For Sync Replication, data is replicated to a single replication peer.
(Optional) If you want to configure replication in secure mode, with mTLS encryption, ask your cluster administrator to make sure that mTLS certificates are installed on every participating cluster.
Follow these steps on the primary cluster to create a synchronous replication protected path with a single secondary cluster.
In the left navigation menu, select Data Protection and then Protected Paths.
On the Protected Paths tab, click Create Protected Path.
Select New Remote Protected Path from the dropdown list.
In the Add Source/Primary dialog, complete these fields:
Name
Enter a name for the protected path.
Path
The path to replicate. Every view on the path and under it must be enabled for S3 Bucket or S3 Endpoint protocol.
Note
If you specify '/' (the root directory), this includes data written via S3.
To specify a path to a specific S3 bucket with name bucket, enter /bucket.
Click Next.
In the Add Destination/Secondary dialog, complete these fields:
ModeSelect Sync Replication.
Cluster
Select the secondary (destination) cluster. This is the replication peer, created above, and on which the data is replicated.
Path
Specify the directory on the remote peer on which the data is replicated. This must be a directory that does not yet exist on the remote peer.
Tip
You cannot use "/" as remote path because that always exists already. Therefore if you would like to replicate all data under the root directory, you will need to replicate this to a subdirectory. e.g. path on peer = "/mirror"
Click Next.
Set the Connection Timeout. If this period of time elapses with no communication between the peered clusters, they will be in a disconnected state.
Click Add. The protected path is created and appears in the Protected Paths tab. It shows Primary Synchronous Replication as the Role.