You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/oadp-installing-oadp-rosa-sts.adoc
+36-15Lines changed: 36 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ The Data Mover feature is not currently supported in ROSA clusters. You can use
24
24
25
25
.Prerequisites
26
26
27
-
* A ROSA OpenShift Cluster with the required access and tokens. For instructions, see the procedure in _Preparing AWS credentials_.
27
+
* A {openshift-rosa} cluster with the required access and tokens. For instructions, see the procedure in "Preparing AWS credentials". If you plan to use two different clusters for backing up and restoring, you need to prepare AWS credentials, including `ROLE_ARN`, for each cluster.
28
28
29
29
30
30
.Procedure
@@ -90,7 +90,7 @@ spec:
90
90
EOF
91
91
----
92
92
93
-
. Create the `DataProtectionApplication resource`, which is used to configure the connection to the storage where the backups and volume snapshots will be stored:
93
+
. Create the `DataProtectionApplication` resource, which is used to configure the connection to the storage where the backups and volume snapshots are stored:
<1> The `credentialsFile` is the mounted location of the bucket credential on the pod.
134
-
<2> The `enableSharedConfig` allows the `snapshotLocations` to share or reuse the credential defined for the bucket.
135
-
<3> Assume your Velero default for your `profile: default`.
136
-
<4> Specify `region` as your AWS region. This must be the same as the cluster region.
132
+
<1> See the first note below.
133
+
<2> The `credentialsFile` field is the mounted location of the bucket credential on the pod.
134
+
<3> The `enableSharedConfig` field allows the `snapshotLocations` to share or reuse the credential defined for the bucket.
135
+
<4> Use the profile name set in the AWS credentials file.
136
+
<5> Specify `region` as your AWS region. This must be the same as the cluster region.
137
137
+
138
+
You are now ready to backup and restore OpenShift applications, as described in the link:https://docs.openshift.com/container-platform/4.11/backup_and_restore/application_backup_and_restore/backing_up_and_restoring/backing-up-applications.html[OADP documentation].
139
+
138
140
[NOTE]
139
141
====
140
142
The `enable` parameter of `restic` is set to `false` in this configuration because OADP does not support Restic in ROSA environments.
143
+
144
+
If you are using OADP 1.2, replace this configuration:
145
+
[source,terminal]
146
+
147
+
----
148
+
nodeAgent:
149
+
enable: false
150
+
uploaderType: restic
151
+
----
152
+
with the following:
153
+
154
+
[source,terminal]
155
+
----
156
+
restic:
157
+
enable: false
158
+
----
141
159
====
142
-
+
143
-
You are now ready to backup and restore OpenShift applications, as described in the link:https://docs.openshift.com/container-platform/4.11/backup_and_restore/application_backup_and_restore/backing_up_and_restoring/backing-up-applications.html[OADP documentation].
160
+
161
+
[NOTE]
162
+
====
163
+
If you want to use two different clusters for backing up and restoring, the two clusters must have identical AWS S3 storage names in both the cloudstorage CR and the OADP `DataProtectionApplication` configuration.
.Restic, Kopia, and DataMover are not supported or recommended
29
29
30
30
* link:https://issues.redhat.com/browse/OADP-1054[CloudStorage: openshift-adp-controller-manager crashloop seg fault with Restic enabled]
31
31
* link:https://issues.redhat.com/browse/OADP-1057[Cloudstorage API: CSI Backup of an app with internal images partially fails with plugin panicked error]
0 commit comments