mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
33 lines
1.6 KiB
Plaintext
33 lines
1.6 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="velero-default-item-operation-timeout_{context}"]
|
|
= Implementing velero default item operation timeout
|
|
|
|
[role="_abstract"]
|
|
The `defaultItemOperationTimeout` setting defines how long to wait on asynchronous `BackupItemActions` and `RestoreItemActions` to complete before timing out. The default value is `1h`.
|
|
|
|
Use the `defaultItemOperationTimeout` for the following scenarios:
|
|
|
|
* Only with Data Mover 1.2.x.
|
|
* To specify the amount of time a particular backup or restore should wait for the Asynchronous actions to complete. In the context of OADP features, this value is used for the Asynchronous actions involved in the Container Storage Interface (CSI) Data Mover feature.
|
|
* When `defaultItemOperationTimeout` is defined in the Data Protection Application (DPA) using the `defaultItemOperationTimeout`, it applies to both backup and restore operations. You can use `itemOperationTimeout` to define only the backup or only the restore of those CRs, as described in the following "Item operation timeout - restore", and "Item operation timeout - backup" sections.
|
|
|
|
.Procedure
|
|
|
|
* Edit the values in the `spec.configuration.velero.defaultItemOperationTimeout` block of the `DataProtectionApplication` CR manifest, as shown in the following example:
|
|
+
|
|
[source,yaml]
|
|
----
|
|
apiVersion: oadp.openshift.io/v1alpha1
|
|
kind: DataProtectionApplication
|
|
metadata:
|
|
name: <dpa_name>
|
|
spec:
|
|
configuration:
|
|
velero:
|
|
defaultItemOperationTimeout: 1h
|
|
# ...
|
|
---- |