IBM Support

IBM Fusion 2.11.0 hotfix

General Page

Download and apply the hotfix for IBM Fusion to resolve issues in Backup & Restore service 2.11.0.

Follow the instructions to apply this hotfix:

  1. For offline environments, use the following script to mirror hotfix images to offline registry before applying hotfix:
    br-2.11.0patch-offline-mirror.sh.

    Note: Log into cp.icr.io and your image destination repository.

    For example:

    Script usage: ./br-2.11.0patch-offline-mirror.sh <TARGET_PATH>

    Where TARGET_PATH is "$LOCAL_ISF_REGISTRY/$LOCAL_ISF_REPOSITORY"
     
  2. Download the br-post-install-patch-2.11.0.sh and apply it as follows:
    • Download or copy the <br-post-install-patch-2.11.0.sh> to local folder.
    • Run the following command to apply the patch.
      Note: Make sure you are logged in to the cluster from CLI.

      chmod +x <br-post-install-patch-2.11.0.sh>

      For example: 
      br-post-install-patch-2.11.0.sh -hci
      br-post-install-patch-2.11.0.sh -sds 

This hotfix fixes the following Backup & Restore issues:

  • Removed the validation for label, if label contains more than 63 character, then the label will be truncated for Velero Backup CR.
  • Fix KeyError while accessing intrinsic variable APP.namespace.name during restore.
  • Redis certificate expiration causes jobs to fail.
  • OADP datamover pods get assigned to a node without the backup volumes when PV topology is a subset of the StorageClass topology with StorageClass field volumeBindingMode.
  • Restore fails with error Backup inventory info not returned from application service for applicationId.
  • Unable to restore 2.9 backup with 2.10.
  • Backup fails intermittently with error Hit exception during "group/rg" : argument of type 'NoneType' is not iterable.
  • Jobs taking long to go from CancelPending to Cancelled state.
  • Alert triggered for old backup job completion.
  • Backup fails due to a timeout when deleting VolumeSnapshotContent.
  • Change AWS S3 connections with OADP to use virtual host style urls instead of host path style by default for proxy compatibility. Proxy services may rely on the bucket in the url's subdomain for validation. Buckets with "." in their name will still default to path style for compatibility. S3 compatibles will continue to use path style urls. Path style format may be forced by adding "FORCEAWSPATHSTYLE" to .spec.transactionManager.testFlags in the DataProtectionAgent.
 

[{"Type":"MASTER","Line of Business":{"code":"LOB69","label":"Storage TPS"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSFETU","label":"IBM Fusion"},"ARM Category":[{"code":"a8m3p0000000rXCAAY","label":"SW"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.11.0"},{"Type":"MASTER","Line of Business":{"code":"LOB69","label":"Storage TPS"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSXEFDS","label":"IBM Fusion HCI Appliance Software"},"ARM Category":[{"code":"a8m3p0000000rX7AAI","label":"HW"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.11.0;2.11.1"}]

Document Information

Modified date:
06 March 2026

UID

ibm17246631

Page Feedback