Configuring InfoScale DR Manager by using web console

Last published : Jul 06, 2026
Complete the following steps:
  1. Click Operators > Installed Operators. Select InfoScale DR Manager.
  2. In the main menu, click Global Cluster Membership. You can create a cluster membership.
  3. Click Create GlobalClusterMembership in the upper-right corner of the screen as under.
    image
  4. Assign a Name and click Global Member Clusters. You can enter cluster details here.
  5. Enter Cluster ID of the primary cluster first and its IP address inDR Controller Address. Optionally, you can enter its port number in DR Controller Port.
    Note: The IP address and port number are generated by using Load Balancer. An example of the command to generate the IP address is -oc -n infoscale-vtas expose deployment infoscale-dr-manager --name dr-lb-service --type LoadBalancer --protocol TCP --port 14155 --target-port 14155. The default port number for Load Balancer service in this example is 14155.
  6. Enter Cluster ID of the secondary cluster and its IP address in DR Controller Address. Optionally, you can enter its port number in DR Controller Port.
    Note: This is the IP address and port number of the peer cluster generated by using Load Balancer. Use the command mentioned in the above step.
  7. Enter the Cluster ID of the primary cluster in Local Cluster Name.
  8. Click Create. Wait till it is created. The newly created cluster is listed under Global Cluster Membership.
  9. Repeat steps 1 to 8 on the secondary cluster. In step 7, ensure that you enter the cluster ID of the secondary cluster. After a successful configuration on the secondary cluster, the secondary cluster is the DR cluster.
  10. Run the following command on the primary cluster to verify whether GCM is successfully configured - oc get gcm
    An output similar to the following indicates a successful configuration.
    NAME                        CLUSTER NAME   CLUSTER STATE   PROTOCOL
    global-cluster-membership   Clus1          RUNNING         10    PEER LINK STATE
    {"Clus1":"CONNECTED","Clus2":"CONNECTED"}
  11. You can now configure Data Replication. Select the appropriate project and click Data Replication.
  12. Click Create DataReplication in the upper-right corner of the screen. The following screen opens.
    image
  13. To configure datareplication using traditional IP based way follow the following steps:
    1. For the primary cluster, enter the Cluster Name, its IP address (Can be any Virtual IP address available in the same subnet) in Local Host Address, and its corresponding Net Mask in Local Net Mask.
    2. For the secondary cluster, enter its name in Cluster Name, its IP address (Can be any Virtual IP address available in the same subnet) in Remote Host Address , and its corresponding Net Mask in Remote Netmask. Enter the network interface in Remote NIC.
      Note the following:
      • When configuring Data Replication, the network interface to be used for the Remote NIC and the Local NIC should be the one where the worker node IPs are assigned.
      • If the OCP cluster is set up with the OVNKubernetes Network Plugin, the worker node IP is typically assigned to the br-ex network interface. Therefore, during the data replication configuration, you should enter "br-ex" as the network interface for the Remote NIC and the Local NIC.
    3. Enter the Namespace for which you want to configure data replication.
    4. In Local NIC , enter the network interface of the primary cluster.
  14. To configure datareplication using Load Balancer based way follow these steps:
    1. Ensure all previous datareplication objects are deleted which were configured using traditional ip based way.
    2. Install any load balancer such as metallb is installed.
    3. For primary cluster please enter Cluster Name, its local IP address. It should be the external ip address exposed by the load balancer.
    4. LBEnabled should be true , do not set the local subnet mask and local NIC.
    5. Similarly for Remote Cluster details enter Cluster Name, its IP address. It should be the external ip address exposed by the load balancer.
    6. RemoteLbEnabled should be true and do not set the remote local subnet mask and remote local NIC.
  15. Click Create. Wait till Data Replication is configured and gets listed.
  16. Run the following command on the primary cluster to verify whether Data Replication is successfully configured - oc get datarep -o wide
  17. Review output for
    consistent,up-to-date
  18. Click Disaster Recovery Plan in the main menu to create a plan.
  19. Click Create DisasterRecoveryPlan in the upper-right corner of the screen. The following screen opens.
    image
  20. Assign a Name to this plan.
    Note: The names of clusters and the Data replication plan appear here.
  21. Review the Primary Cluster. Enter the** Namespace** that you want to be a part of this plan.
  22. Review the Data Replication Pointer and Preferred Cluster List.
  23. Click Create and wait till the Disaster Recovery Plan is created and listed.
After these successful configurations, Disaster Recovery (DR) is ready.