Backup & Restore service installation and upgrade issues

Backup & Restore service installation may hang at 75%

If the provided custom install namespace exceeds 24 characters in length, then the Fusion Backup & Restore service installation may hang at 75% completion. To resolve this issue, provide a custom namespace that is no more than 24 characters in length.

Application information not repopulated after service reinstallation

Problem statement

The application information gets removed during Backup & Restore service uninstallation. It does not get repopulated in MongoDB after the service reinstallation. Restore jobs validation fail with the following error message.

postJobRequest: Application Info not returned from application service for applicationId

Resolution

The workaround is to restart the isf-application-operator-controller-manager pod in the IBM Fusion namespace.

Backup & Restore server installation displays an Invalid Input error

Problem statement

The Backup & Restore service deployment fails with the following error in the IBM Fusion user interface:

Install Error: Invalid Input: Both the api Server and bootstrapToken fields need to be populated

Resolution

As a resolution, try with a private browser window.

Backup & Restore hub service in a custom namespace

Problem statement

In general, the Backup & Restore service is installed or upgraded to the default ibm-backup-restore namespace. To avoid issues during the installation or upgrade of the service with custom namespace, do the resolution steps.

Resolution

1. Go to Operators > Installed Operators > Fusion Service Definition.
2. Open the ibm-backup-restore-service CR and go to the YAML tab.
3. In spec.onboarding.parameters, search for parameter with name as namespace and change the defaultValue to the custom-namespace where the service must be installed.
   Example:

   
   parameters:
         - dataType: string
           name: namespace
           defaultValue: <custom-namespace>
           userInterface: false
           required: true
           descriptionCode: BMYSRV00003
           displayNameCode: BMYSRV00004

4. Store the following YAML in server-fsi.yaml, and replace <custom-namespace> with the namespace where the service must be installed.

   
   apiVersion: service.isf.ibm.com/v1
   kind: FusionServiceInstance
   metadata:
     name: ibm-backup-restore-service-instance
     namespace: ibm-spectrum-fusion-ns
   spec:
     parameters:
       - name: doInstall
         provided: false
         value: 'true'
       - name: namespace
         provided: false
         value: <custom-namespace>
       - name: storageClass
         provided: true
         value: lvms-lmvg
     serviceDefinition: ibm-backup-restore-service
     triggerUpdate: false
     enabled: true
     doInstall: true

5. Run the following command to apply the changes:

   oc apply -f server-fsi.yaml 

6. For the upgrade procedure, upgrade the IBM Fusion operator, repeat step 1 of the resolution, and then upgrade the service.

Pods in Crashloopbackoff state after upgrade

Problem statement

The Backup & Restore service health changes to unknown and two pods go into Crashlookbackoff state.

Resolution

In the resource settings of guardian-dp-operator pod that is in ibm-backup-restore namespace, set the value of IBM Fusion operator memory limits to 1000 mi.

Example:

resources:    
          limits:    
            cpu: 1000m    
            memory: 1000Mi    
          requests:    
            cpu: 500m    
            memory: 250Mi 

Backup & Restore service goes into unknown state

Problem statement

This Backup & Restore service might go into unknown state when you upgrade IBM Fusion from 2.6.x to 2.8.0.

Resolution

It automatically shows healthy on the IBM Fusion user interface after you upgrade the Backup & Restore service.

MongoDB pod crashes with CrashLoopBackOff status

Problem statement

The MongoDB pod crashes due to an OOM error.

Resolution

To resolve the error, increase the memory limit from 256Mi to 512Mi. Do the following steps to change the memory limit:

1. Log in to the Red Hat® OpenShift® web console as an administrator.
2. Go to Workloads > StatefulSet.
3. Select the project ibm-backup-restore.
4. Select the MongoDB pod, and go to the YAML tab.
5. In the YAML, change the memory limit for MongoDB container from 256Mi to 512Mi.
6. Click Save.

Backup & Restore service installation and upgrade issue with the IBM Storage Protect Plus catalog source

Problem statement

The backups can fail with a FailedValidation error after you install or upgrade the IBM Fusion and Backup & Restore service to 2.8.0.

validationErrors': ['an existing backup storage location wasn't specified at backup creation time and the default guardian-minio wasn't found.

Error: BackupStorageLocation.velero.io "guardian-minio" not found'

It occurs when the IBM Storage Protect Plus catalog exists in the OpenShift Container Platform clusters.

Resolution

The workaround is to upgrade the OADP, installed in the ibm-backup-restore namespace, to version 1.3.