Post-restore tasks after restoring a Cloud Pak for Data online backup

Complete extra tasks for some services after you restore an IBM Cloud Pak® for Data deployment from an online backup.

Watson Knowledge Catalog metadata import jobs

After Cloud Pak for Data is restored, long running metadata import jobs might not resume. The job run status might still be Running, even though the actual import job isn't running. The job must be canceled and manually restarted. You can cancel and restart a job in Watson Knowledge Catalog or by using an API call.

To cancel and restart a job in Watson Knowledge Catalog, do the following steps.

  1. Go to a Jobs page, either the general one or the one for the project that contains the metadata import asset.
  2. Look for the job and cancel it.
  3. Restart the job.

To cancel and restart a job by using an API call, run the following command. You must have the Admin role to use this API call.

post /v2/metadata_imports/recover_task

The request payload must look like the following example:

{
  "recovery_date": "2022-05-05T01:00:00Z",
  "pending_type": "running"
}

For recovery_date, specify the date when Watson Knowledge Catalog was restored from the backup image. Any jobs that were started before the specified date are restarted automatically.

Watson Knowledge Catalog metadata enrichment jobs

After Cloud Pak for Data is restored, running metadata enrichment jobs might not complete successfully. Such jobs must be manually restarted.

To restart a metadata enrichment job, do the following steps.

  1. In Watson Knowledge Catalog, open the project that contains the metadata enrichment asset.
  2. Select the asset.
  3. Click the Button to start or delete an enrichment job. button of the asset and then click Enrich to start a new enrichment job.
Watson Knowledge Catalog lineage data import jobs

If a lineage data import job is running at the same time that an online backup is taken, the job is in a Complete state when the backup is restored. However, users cannot see lineage data in the catalog. Rerun the lineage import job.

Watson Machine Learning Accelerator

Complete additional steps to restore owner references to all Watson Machine Learning Accelerator resources. For more information, see Backing up and restoring Watson Machine Learning Accelerator.

Watson OpenScale

Complete additional steps to restore all of the Watson OpenScale features. For more information, see Completing post-restore tasks for Watson OpenScale.

Restoring Data Replication

After Cloud Pak for Data is restored, do the following steps.

  1. If you restored Cloud Pak for Data to a different cluster, stop the replication on the source cluster to avoid having two streams of data flowing from the same data source to the same destination when the service is restarted on the restored cluster.
  2. Connect to the restored Cloud Pak for Data instance.
  3. Go to the restored replications and stop them.
  4. Restart the replications.
Services that do not support online backup and restore

The following list shows the services that don't support online backup and restore. If any of these services are installed in your Cloud Pak for Data deployment, actions must be taken after an online backup is restored to make them functional.

Db2® Data Gate
Db2 Data Gate synchronizes Db2 for z/OS® data in real time. After Cloud Pak for Data is restored, data might be out of sync from Db2 for z/OS. It is recommended that you re-add tables after Cloud Pak for Data foundational services are restored.
EDB Postgres
The service must be reinstalled and then the data must be restored. For more information about restoring EDB Postgres, see Performing physical backup and restore for the EDB Postgres service.
MongoDB
The service must be deleted and reinstalled. Recreate the instance as a new instance, and then restore the data with MongoDB tools. For more information, see Installing the MongoDB service and Back Up and Restore with MongoDB Tools.
Planning Analytics
The service instance must be restored. For more information, see Restoring Planning Analytics.
Watson Assistant
The service must be cleaned up and reinstalled. Complete the following steps:
  1. Before you backed up your Cloud Pak for Data deployment, you identified the name of the Watson Assistant installation (instance) in the ${PROJECT_CPD_INSTANCE} project. Locate that information and use it to complete the next step.
  2. Set the WA_INSTANCE_NAME variable:
    export WA_INSTANCE_NAME=<instance-name>
  3. Run the following commands, and then delete the resources that are listed after each command:
    oc get wa ${WA_INSTANCE_NAME}
    oc get watsongateway,watsonassistantstore,watsonassistantdialog,watsonassistantui,watsonassistantclu,watsonassistantanalytics,watsonassistantintegrations,watsonassistantrecommends | grep /${WA_INSTANCE_NAME}
    oc get dataexhaust,dataexhausttenant,modeltraindynamicworkflow,miniocluster,redissentinel,formation.redis,cluster,elasticsearchcluster,rabbitmqcluster,kafka,etcdcluster | grep ${WA_INSTANCE_NAME}-
    oc get job,deploy,replicaset,pod,StatefulSet,configmap,persistentvolumeclaim,poddisruptionbudget,horizontalpodautoscaler,networkpolicies,cronjobs | grep ${WA_INSTANCE_NAME}-
  4. Reinstall the Watson Assistant instance.

    For more information, see Installing Watson Assistant.

Watson Discovery

The service must be uninstalled, reinstalled, then the data restored.

Watson Speech services
The service is functional and you can re-import data. For more information, see Importing and exporting data.