Upgrade and upsize considerations in Metro-DR

As a prerequisite, know these upgrade and upside considerations before you use Metro-DR.

  • When any of the following activities are in progress on a site, then do not attempt any other activity from the list on either this site or the other site:
    • Upgrade
    • Scale out
    • Scale up

      For example, when scale up is in progress, do not trigger upgrade and vice versa.

    • Node maintenance / replacement or repair
    • Disk maintenance /replacement or repair
    • Unhealthy state of open shift or storage cluster
  • When one of the site is at a lower version level than the other, do not any attempt any operations on either of the sites in the Metro-DR cluster. For example, site 1 is at IBM Fusion HCI System 2.8.2 (lower level) and site 2 is at IBM Fusion HCI System 2.9.0.
  • In case of the following situations, do an upgrade or scale up to obtain parity between the two sites:
    Note: Ensure you bring them both to the same level at the earliest as the tolerant limit is only couple of days.
    • Ensure that the IBM Fusion version is at the same level for both site 1 and site 2.
    • Ensure that the OpenShift® Container Platform version is at the same level for both site 1 an site 2.
    • Ensure that the submariner version is at the same level for both site 1 and site 2.
    • Add nodes when mismatch in the number of nodes between sites exist.
    • Add disks when mismatch in the number of disks between sites exist.

If these mismatches exist, the tolerant limit is 2 days and you need to bring them both at the same level at the earliest.