OADP offline backup fails with pod timeout error

You are unable to create an offline backup because of a timeout error when the OADP utility is creating the cpdbr-vol-mnt pod.

Symptoms

In the CPD-CLI*.log file, you see an error like in the following example:

Warning Failed   84s    kubelet   Error: kubelet may be retrying requests that are timing out in CRI-O 
due to system load. Currently at stage container volume configuration: context deadline exceeded: error reserving ctr name k8s_main_cpdbr-vol-mnt_app00236429-wkc-cpd-instance_82731acb-274a-458c-abc9-b6761639b32d_1 
for id 807520332fba35129161065cefd09de779284d91579c664d80d61628fee8e29e: name is reserved

Resolving the problem

Do the following steps:

  1. In the DataProtectionApplication (DPA) configuration, increase the Restic timeout (spec.configuration.restic.timeout) to 4 hours.

    For more information, see Installing IBM® Software Hub OADP backup and restore utility components.

    Tip: You can also try running the backup command with the --try-skip-volume-selinux-label option set to true. For more information about this option, see tenant-backup create.