By ddwang@cn.ibm.com, likezhao@cn.ibm.com, liyjcdl@cn.ibm.com

Notes: Sample screenshots in this paper are based on Fusion 2.7.0, and AMQ Stream 2.4.0. This solution is suitable for Fusion 2.6.0+ releases.

For short, we use BnR to stand for Fusion’s Backup&Restore service.

Background:

IBM Storage Fusion is a data services platform for Red Hat OpenShift. BnR is one of storage services on Fusion platform. It provides enterprise backup and restore solution for customer’s container applications to ensure enterprise data safety.

BnR’s Hub uses the event streaming capability from AMQ, when BnR-Hub service is installed from Fusion UI, AMQ will be installed automatically by BnR in ibm-backup-restore namespace. And BnR-spoke installation isn’t impacted by AMQ, since it doesn’t include AMQ component.

In some situation, business applications may also integrate with AMQ. If the business AMQ is in a specific namespace, there is no conflict with BnR-Hub installation. If it’s shared in global namespace (All Namespace), BnR-Hub installation will fail, due to AMQ conflict.

Requirement:

When global AMQ exists, how to install Fusion Backup&Restore service?

Solution:

To make BnR cowork with global AMQ, BnR’s AMQ version should align with global AMQ version, like 2.4.0-x in Fusion 2.7.0. If not, please contact Fusion team to confirm the compatible AMQ range. Otherwise, BnR-Hub service may not work well after installation.

Scenario 1: Global AMQ exists first, install Fusion BnR-Hub service.

[Step1] In OCP UI, Check AMQ(e.g. 2.4.0-x) installed well within All Namespace.

[Step2] In Fusion UI, install BnR-Hub service as normal.

[Step3] During BnR-Hub installation, in OCP UI, AMQ Streams is installed with “Failed” in ibm-backup-restore namespace.

Meanwhile, from Fusion UI, BnR-Hub keeps installing.

[Step4] Uninstall the newly installed AMQ Streams operator Fusion in ibm-backup-restore namespace.

[Step5] In Fusin UI, monitor the BnR-Hub installation complete.

[Step6] In Fusin UI, try to backup an application to S3, then restore it, to verify BnR service works well. This also verify BnR-Hub co-work with global AMQ well.

Scenario 2: Fusion BnR-Hub service works first, install global AMQ.

Risks: BnR-Hub service is suspended for a while during global AMQ installation procedure(may in minutes)

[Step1] In OCP UI, check AMQ(e.g. 2.4.0-x) installed well in ibm-backup-restore namespace. And BnR service is installed well and can work well.

[Step2] Install a global AMQ in All Namespace from OperatorHub as normal, this is one of parts of business application. (As described above, if AMQ is installed in a specific namespace, it won’t impact BnR)

[Step3] Select the amq-stream-2.4.x, the “All namespaces on this cluster”, and “Manual” installation. Then launch installation. Encounter “Operator installation failed” error as expected.

[Step4] Uninstall the BnR’s AMQ operator from ibm-backup-restore namespace.

[Step5] After BnR’s AMQ installation, the global AMQ continues installation automatically until complete.

[Step6] Go to the detail page of AMQ, in the “All instances” page, verify BnR’s CRs have been generated under global AMQ.

[Step7] In Fusin UI, try to backup an application to S3, then restore it, to verify BnR service works well. This also verify BnR-Hub co-work with global AMQ well.

Done.

Hope this doc helpful for you, please feel free to contact for further discussion.