Skip to content

Commit bf4d59a

Browse files
committed
OADP-4677 updated restic to nodeAgent
1 parent 92b8ca4 commit bf4d59a

File tree

2 files changed

+13
-6
lines changed

2 files changed

+13
-6
lines changed

modules/oadp-restic-issues.adoc

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,16 +23,21 @@ You can resolve this issue by creating a supplemental group for `Restic` and add
2323

2424
. Create a supplemental group for `Restic` on the NFS data volume.
2525
. Set the `setgid` bit on the NFS directories so that group ownership is inherited.
26-
. Add the `spec.configuration.restic.supplementalGroups` parameter and the group ID to the `DataProtectionApplication` manifest, as in the following example:
26+
. Add the `spec.configuration.nodeAgent.supplementalGroups` parameter and the group ID to the `DataProtectionApplication` manifest, as shown in the following example:
2727
+
2828
[source,yaml]
2929
----
30+
apiVersion: oadp.openshift.io/v1alpha1
31+
kind: DataProtectionApplication
32+
# ...
3033
spec:
3134
configuration:
32-
restic:
35+
nodeAgent:
3336
enable: true
37+
uploaderType: restic
3438
supplementalGroups:
3539
- <group_id> <1>
40+
# ...
3641
----
3742
<1> Specify the supplemental group ID.
3843

modules/oadp-restic-timeouts.adoc

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@
66
[id="restic-timeout_{context}"]
77
= Restic timeout
88

9-
`timeout` defines the Restic timeout. The default value is `1h`.
9+
The `spec.configuration.nodeAgent.timeout` parameter defines the Restic timeout. The default value is `1h`.
1010

11-
Use the Restic `timeout` for the following scenarios:
11+
Use the Restic `timeout` parameter in the `nodeAgent` section for the following scenarios:
1212

1313
* For Restic backups with total PV data usage that is greater than 500GB.
1414
* If backups are timing out with the following error:
@@ -19,7 +19,7 @@ level=error msg="Error backing up item" backup=velero/monitoring error="timed ou
1919
----
2020
2121
.Procedure
22-
* Edit the values in the `spec.configuration.restic.timeout` block of the `DataProtectionApplication` CR manifest, as in the following example:
22+
* Edit the values in the `spec.configuration.nodeAgent.timeout` block of the `DataProtectionApplication` custom resource (CR) manifest, as shown in the following example:
2323
+
2424
[source,yaml]
2525
----
@@ -29,7 +29,9 @@ metadata:
2929
name: <dpa_name>
3030
spec:
3131
configuration:
32-
restic:
32+
nodeAgent:
33+
enable: true
34+
uploaderType: restic
3335
timeout: 1h
3436
# ...
3537
----

0 commit comments

Comments
 (0)