Troubleshooting backup and restore issues in Data Virtualization

Resolve the problems that you might encounter backing up or restoring Data Virtualization.

Online and offline backup validation fails due to missing label in dvendpoint PVC in Data Virtualization
When you upgrade your Data Virtualization instance from version 5.2.x to 5.3.x and then use the cpd-cli OADP utility to run a backup, the backup validation fails.
The restore process times out while waiting for the ibmcpd status check to complete
The Data Virtualization restore process might time out while waiting for the ibmcpd status check to complete. To workaround this issue, re-run the restore from the restore-operands.
Restore fails and displays postRestoreViaConfigHookRule error in Data Virtualization
The Data Virtualization restore fails because custom ConfigMaps are not included in the backup or restored.
Error 404 displays after backup and restore in Data Virtualization
After you run a backup and restore, you might encounter the Error 404 - Not found error message.
Backup fails due to lingering pvc-sysbench-rwo created by storage-performance health check in Data Virtualization
Backup in a Cloud Pak for Data and Data Virtualization cluster fails if a persistent volume claim (PVC) created by the storage-performance health check remains in the Terminating state. The affected PVC (pvc-sysbench-rwo) is not automatically cleaned up and blocks the backup pre-check phase.
Data Virtualization online restore post hooks time out
When you do an online restore, Data Virtualization worker pods might bypass waiting for the check that is used for an online restore. This issue leads the worker pods to fail and be removed before the online restore post hooks run.
Data Virtualization post-restore hooks fail because pods are unreachable
When you do offline restores, Data Virtualization pods might show as running, but the IP addresses that are assigned to them are invalid and the pods cannot connect to each other. The Data Virtualization post restore hooks might fail because the pods are unreachable.
Backup and restore fails in Data Virtualization
After you run a backup and restore, you might encounter a transport: authentication handshake failed: x509: certificate signed by unknown authority message in which pods are in a crash or restart loop.
Refresh dmcuser password in Db2 Data Management Console after backup and restore in Data Virtualization
After you run a backup and restore, you might encounter errors in which security processing fails because of password invalidation.
Reset a secret after backup and restore of Data Virtualization
After you run a backup and restore, you might encounter errors in which security processing fails because of password invalidation.

Parent topic: Troubleshooting the Data Virtualization service