Backing up ELMOperation instance by using Kubernetes CLI

The ELMOperation instance supports the backup of Engineering Lifecycle Management applications by using the Kubernetes CLI method.

About this task

Following method is used to create a backup of ELMOperation instance by using Kubernetes CLI.

Procedure

  1. Log in to your IBM Kubernetes Service cluster on IBM cloud and connect to your cluster namespace by using kubectl
  2. Prepare the ELMOperation source manifest. Now, from the local computer create a yaml file called backup_elm_instance.yaml by using the following command.
    apiVersion: elm.ibm.com/v1
    kind: ELMOperation
    metadata:
      name: elmoperation-sample
      namespace: <namespace_name>
    spec:
      operationType: backupELMInstance
      allApplications: true
      backupLabel: latest
      selectedApplications:
        jas: false
        jts: false
        qm: false  
        dcc: false
        rm: false
        gc: false
        ccm: false
        eni: false
        ldx: false
        lqe: false
        rb: false
  3. Run the following command:
    kubectl create -f backup_elm_instance.yaml -n <namespace_name>

    Replace the placeholders: For <namespace_name>, input the name of the project, where Engineering Lifecycle Management instance is created.

  4. Verify the installation by using following command:
    kubectl get elmoperations elmoperation-sample -n <namespace_name>
    You can see the following output, when the ELMOperation is created successfully
    NAME                  AGE
    elmoperation-sample   2m27s

    The following message is displayed when the installation fails

    Error from server (NotFound): elmoperations.elm.ibm.com "elmoperation-sample" not found
    To help resolve this error, run the following command to check the ELMOperation name.
    kubectl get elmoperations -n <namespace_name>
    kubectl describe elmoperations elmoperation-sample -n <namespace_name>

    The output provides information about ELMOperation resources and status.

    Note: The exact path of the backup can be viewed from the logs section of the backup pod created.