mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
40 lines
1.1 KiB
Plaintext
40 lines
1.1 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * backup_and_restore/application_backup_and_restore/troubleshooting/oadp-timeouts.adoc
|
|
//
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="restic-timeout_{context}"]
|
|
= Implementing restic timeout
|
|
|
|
[role="_abstract"]
|
|
The `spec.configuration.nodeAgent.timeout` parameter defines the Restic timeout. The default value is `1h`.
|
|
|
|
Use the Restic `timeout` parameter in the `nodeAgent` section for the following scenarios:
|
|
|
|
* For Restic backups with total PV data usage that is greater than 500GB.
|
|
* If backups are timing out with the following error:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
level=error msg="Error backing up item" backup=velero/monitoring error="timed out waiting for all PodVolumeBackups to complete"
|
|
----
|
|
|
|
.Procedure
|
|
* Edit the values in the `spec.configuration.nodeAgent.timeout` block of the `DataProtectionApplication` custom resource (CR) manifest, as shown in the following example:
|
|
+
|
|
[source,yaml]
|
|
----
|
|
apiVersion: oadp.openshift.io/v1alpha1
|
|
kind: DataProtectionApplication
|
|
metadata:
|
|
name: <dpa_name>
|
|
spec:
|
|
configuration:
|
|
nodeAgent:
|
|
enable: true
|
|
uploaderType: restic
|
|
timeout: 1h
|
|
# ...
|
|
----
|