Backup & Restore (Legacy)

Protect your data with application-centric backups. Use local snapshots for quick recovery or transfer backups to external object storage for safe keeping.

Before you begin

Go through the following information for prerequisites and planning:
  • In IBM Storage Fusion, if Global Data Platform service is not enabled already and your platform is Bare Metal, then do these steps:
    Note: This step is not applicable for IBM Storage Fusion HCI System.
    Note: You can ignore this step if you are on OpenShift® Container Platform version 4.11 or higher.
    Ensure a minimum of 4096 pidslimit is set on Bare Metal compute nodes before you enable the Backup & Restore (Legacy) service.
    1. Run the following command to label compute nodes:

      For example:

      oc label machineconfigpool worker spplimit=pidslimit
      Note: In this example, machineconfigpool is the label for compute nodes. You can have a label of your choice, however, same label must be used in next step for matchLabels value.
    2. Create container runtime config:

      Create crc-worker-pidslimit.yaml with following information:

      kind: ContainerRuntimeConfig
       name: "pidslimitforspp"
           spplimit : pidslimit
         pidsLimit: 4096
    3. Run the following command to apply the YAML:
      oc apply -f crc-worker-pidslimit.yaml
  • Ensure S3 is not in the same cluster or namespace as IBM Storage Fusion or Backup & Restore (Legacy) service.
  • You can plan to use cluster services like MinIO or NooBaa but ensure to host them on different clusters. If your backups are in the same place as your primary data, then the data is not protected.
  • Important: If you plan to install or upgrade Backup & Restore (Legacy) IBM Storage Fusion service, then ensure that you do not apply the ICSP of Backup & Restore IBM Storage Fusion service. Apply Backup & Restore ICSP only whenever you plan to install the Backup & Restore IBM Storage Fusion service.
  • Support for Backup & Restore (Legacy) service on Amazon web services ROSA is using native storage class - gp2-csi, gp3, and gp3-csi. The native storage classes gp2-csi, gp3 and gp3-csi are supported if you create a new class based on those that has volumeBindingMode Immediate. The gp3 and gp3-csi classes are clones of each other, one can be used as a base to create a new class with immediate binding.
  • Support for Backup & Restore (Legacy) service on Microsoft Azure ARO is using managed-csi storage class. The managed-csi storage class is CSI compliant, but does not have volumeBindingMode Immediate. You can create a new storage class based on managed-csi and set Immediate binding mode.


  1. Go to Services page in IBM Storage Fusion or IBM Storage Fusion HCI System user interface.
  2. In the Available section, click Backup & Restore (Legacy) tile.
  3. In the Backup & Restore (Legacy) window, go through the details about the service and click Install.
    The internal data catalog requires a minimum of 420 GB for ReadWriteOnce storage.
  4. In the Install service message box, select a Storage class. If there are failures, go through the downloaded logs to understand the cause of the failure and fix the issue. For more information about service issues in IBM Storage Fusion, see Troubleshooting installation and upgrade issues in IBM Storage Fusion services.
  5. Click Install.
  6. Validate the installation.
    • IBM Storage Fusion user interface:

      After you enable the Backup & Restore (Legacy), you can view the service version and health status. From the ellipsis menu, you can download logs and view documentation. After you successfully collect the logs, a success notification gets displayed. The notification disappears automatically after some time.

    • OC CLI commands and OpenShift Container Platform web console to check the successful startup of various services and pods, which got added to the cluster as a result of this service:

      To validate IBM Storage Fusion installation, see Validating IBM Storage Fusion installation.

      To validate IBM Storage Fusion HCI System installation, see Validating IBM Storage Fusion HCI System installation.

What to do next

  • The spp-connection secret exists only once when you upload the SPP.lic file. The first time you log in to Backup & Restore (Legacy) user interface, use the default credentials. Change the values and upload the SPP.lic file to create the spp-connection secret with your own credentials.

    Verify whether the spp-connection secret exists with the new credentials for the Backup & Restore (Legacy) user interface console. Before you log in with the default credentials, run the following command to verify:

    oc get secrets -n ibm-spectrum-fusion-ns|grep spp
    Example output of the command:
    spp-dp-controller-manager-dockercfg-52jp5                              1      23h
    spp-dp-controller-manager-service-cert                                       3      23h
    spp-dp-controller-manager-token-6d29d                      4      23h
    oc get secrets -n ibm-spectrum-fusion-ns|grep spp-connection 
    To extract the credentials anytime, run the following command:
    oc -n ibm-spectrum-fusion-ns extract secret/spp-connection  --to=-
  • If a backup fails only for the policies fusion_backup, clusterscope_backup, and openshift_backup, then do the following steps:
    1. Log in to IBM Spectrum Protect Plus user interface.
    2. Go to Manage Protection > Policy overview.
      1. In the Policies tab, click the Edit icon.
      2. Go to the Backup Policy tab and select Object Storage from the Target Storage Type.
      3. Select Target from the drop-down list.
      4. Select Use existing access key checkbox.
      5. Click Select a key drop-down and select the key.
      6. Click Save.
  • You can now protect your IBM Storage Fusion applications.
    1. Add location to determine whether the network verification is needed. For the procedure to add a location, see Backup storage locations.
    2. Assign an application to the backup policy
    3. Adding backup policy
    For more information about backup, see Backup and restore application resources.