Prerequisites

Last published : Jul 06, 2026
  1. InfoScale must be installed and InfoScale pods must be configured on the clusters.
  2. Before proceeding with DR Manager installation, ensure that all the PVCs present in the cluster must either be in Bound state or Terminating state.
  3. Load balancer must be installed and configured. If you choose to install Metallb as the load balancer, steps are listed in Installing InfoScale DR.
  4. Be ready with the following information for every member cluster
    • GlobalClusterMembership: Virtual IP address and a port for each member cluster in GCM. This information is captured in GCM custom resource.
    • Data Replication: Virtual IP address, port, netmask and network interface (NIC) required for each cluster to be specified in DataReplication CR. This information is exclusive for a DataReplication CR and is used to configure InfoScale Volume Replicator.
  5. Ensure that stale Custom Resources (CR) and Custom Resource Definitions (CRD) related to DR do not exist on the clusters.
  6. Optionally if you want to configure DNS resource, DNS keyandDNS private key. To know how to obtain keys, see https://www.veritas.com/support/en_US/doc/129694359-129694362-0/uxrt-731_id-SF1J0175244-129694362.
  7. Multi-homed Bare-Metal Nodes: You must strictly define the interfaces array in the MetalLB L2Advertisement object. Limit the advertisement only to the interface connected to the OpenShift CNI bridge (usually br-ex or eno1).
apiVersion: metallb.io/v1beta1
kind: L2Advertisement
metadata:
  name: vike-vvr-l2-adv
  namespace: metallb-system
spec:
  ipAddressPools:

<vvr-vip-pool-name>
interfaces:

br-ex    # Must match the OVN-Kubernetes bridge or primary CNI interface through
which the traffic would leave.