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.

Restoring Data Replication

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

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.
Connect to the restored Cloud Pak for Data instance.
Go to the restored replications and stop them.
Restart the replications.

IBM 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.

In IBM® Knowledge Catalog, open the project that contains the metadata enrichment asset.
Select the asset.
Click the button of the asset and then click Enrich to start a new enrichment job.

IBM 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.

IBM 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 IBM Knowledge Catalog or by using an API call.

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

Go to a Jobs page, either the general one or the one for the project that contains the metadata import asset.
Look for the job and cancel it.
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 IBM Knowledge Catalog was restored from the backup image. Any jobs that were started before the specified date are restarted automatically.

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

Some Watson OpenScale features, such as scheduled or on-demand model evaluations, might not function properly after a restore. Do the following steps to verify that Watson OpenScale runs correctly:

Log in to Red Hat® OpenShift® Container Platform as a cluster administrator.
```
${OC_LOGIN}
```
Remember: OC_LOGIN is an alias for the oc login command.

Query the Watson OpenScale operator pod name with the following command:

OPERATOR_POD_NAME=$(oc get pods -n ${PROJECT_CPD_INST_OPERATORS} | grep wos | awk {'print $1'})

Run the post-restore script in the operator by specifying the required arguments with the following command:
```
instanceCRName='aiopenscale'

oc exec ${OPERATOR_POD_NAME} -n ${PROJECT_CPD_INST_OPERATORS} -- /opt/ansible/roles/service/files/post_restore.sh -c ${instanceCRName} -n ${PROJECT_CPD_INST_OPERANDS}
```
If you did not use aiopenscale as the name of the Watson OpenScale custom resource, specify the correct value in instanceCRName.
Check the status of the Watson OpenScale custom resource reconciliation with the following command:
```
oc get WOService ${instanceCRName} -n ${PROJECT_CPD_INST_OPERANDS} -o jsonpath='{.status.wosStatus} {"\n"}'
```
The status of the custom resource changes to Completed when the reconciliation finishes successfully.

watsonx Assistant

After restoring the watsonx Assistant backup, it is necessary to retrain the existing skills. This involves modifying a skill, to trigger training. The training process for a skill typically requires less than 10 minutes to complete. For more information, see the Retraining your backend model section in the IBM Cloud documentation.

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.
MANTA Automated Data Lineage: The service is functional and data can be re-imported. For information about importing data, see Managing existing metadata imports (IBM Knowledge Catalog).
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.