Skip to content

[enterprise-4.17] OADP-4677 updated restic to nodeAgent #80806

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 22, 2024
Merged

[enterprise-4.17] OADP-4677 updated restic to nodeAgent #80806

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions modules/oadp-restic-issues.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,16 +23,21 @@ You can resolve this issue by creating a supplemental group for `Restic` and add

. Create a supplemental group for `Restic` on the NFS data volume.
. Set the `setgid` bit on the NFS directories so that group ownership is inherited.
. Add the `spec.configuration.restic.supplementalGroups` parameter and the group ID to the `DataProtectionApplication` manifest, as in the following example:
. Add the `spec.configuration.nodeAgent.supplementalGroups` parameter and the group ID to the `DataProtectionApplication` manifest, as shown in the following example:
+
[source,yaml]
----
apiVersion: oadp.openshift.io/v1alpha1
kind: DataProtectionApplication
# ...
spec:
configuration:
restic:
nodeAgent:
enable: true
uploaderType: restic
supplementalGroups:
- <group_id> <1>
# ...
----
<1> Specify the supplemental group ID.

Expand Down
10 changes: 6 additions & 4 deletions modules/oadp-restic-timeouts.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,9 @@
[id="restic-timeout_{context}"]
= Restic timeout

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

Use the Restic `timeout` for the following scenarios:
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:
Expand All @@ -19,7 +19,7 @@ level=error msg="Error backing up item" backup=velero/monitoring error="timed ou
----

.Procedure
* Edit the values in the `spec.configuration.restic.timeout` block of the `DataProtectionApplication` CR manifest, as in the following example:
* 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]
----
Expand All @@ -29,7 +29,9 @@ metadata:
name: <dpa_name>
spec:
configuration:
restic:
nodeAgent:
enable: true
uploaderType: restic
timeout: 1h
# ...
----