G.2 Upgrading to BCC 2.6

If you are upgrading an existing business continuity cluster 2.x to BCC 2.6, you must upgrade the Identity Manager servers in the BCC before you upgrade the peer clusters. See the following resources for upgrade requirements:

Table G-1 Upgrading Identity Manager and Business Continuity Clustering

From

To

See the following:

  • Identity Manager 4.8.5 on OES 2018 SP3

  • Identity Manager 4.8.5 on OES 2018 SP2

Identity Manager 4.8.6 on OES 2023

Section F.0, Upgrading to Identity Manager 4.8.6

Business Continuity Clustering 2.6 on OES versions (OES 2018 SP2, OES 2018 SP3)

Business Continuity Clustering 2.6 on OES 2023

Section G.0, Upgrading to BCC 2.6 on OES 2023.

When you upgrade the server to OES 2023, BCC is automatically upgraded to BCC 2.6 version. For more information, see Upgrading to OES 2023 in the OES 2023: Installation Guide.

  • If Novell Business Continuity Cluster pattern is selected while upgrading the older OES versions to OES 2023, the BCC is automatically upgraded to BCC 2.6.

    For example, if you are upgrading BCC 2.6 on OES 2018 SP2 to BCC 2.6 on OES 2023, on the Installation Settings page, the following are listed under the Update Options:

    • Product MicroFocus Open Enterprise Server 2018 SP2 will be upgraded to MicroFocus Open Enterprise Server 2023.

  • If Novell Business Continuity Cluster pattern is not selected while upgrading the older OES versions to OES 2023, complete the OES upgrade and then manually install and configure the BCC. For more information on installing and configuring BCC, see Section 5.4, Installing and Configuring the Business Continuity Clustering Software.

Verify that BCC is working as expected by checking the BCC connection and resource status with iManager on every peer cluster.