Skip to content

Commit 25f19ba

Browse files
authored
Merge pull request #96721 from openshift-cherrypick-robot/cherry-pick-95785-to-enterprise-4.19
[enterprise-4.19] OADP-6348-dita-vale-oadp-usecases
2 parents bebac9b + 850a68e commit 25f19ba

8 files changed

+8
-0
lines changed

backup_and_restore/application_backup_and_restore/oadp-use-cases/oadp-usecase-backup-using-odf.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9+
[role="_abstract"]
910
Following is a use case for using {oadp-short} and {odf-short} to back up an application.
1011

1112
//backup

backup_and_restore/application_backup_and_restore/oadp-use-cases/oadp-usecase-enable-ca-cert.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9+
[role="_abstract"]
910
You can include a self-signed Certificate Authority (CA) certificate in the Data Protection Application (DPA) and then back up an application. You store the backup in a NooBaa bucket provided by {odf-first}.
1011

1112
// include a CA cert and run a backup

backup_and_restore/application_backup_and_restore/oadp-use-cases/oadp-usecase-legacy-aws-plugin.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9+
[role="_abstract"]
910
If you are using an {aws-short} S3-compatible backup storage location, you might get a `SignatureDoesNotMatch` error while backing up your application. This error occurs because some backup storage locations still use the older versions of the S3 APIs, which are incompatible with the newer AWS SDK for Go V2. To resolve this issue, you can use the `legacy-aws` Velero plugin in the `DataProtectionApplication` custom resource (CR). The `legacy-aws` Velero plugin uses the older AWS SDK for Go V1, which is compatible with the legacy S3 APIs, ensuring successful backups.
1011

1112
// using legacy-aws velero plugin

backup_and_restore/application_backup_and_restore/oadp-use-cases/oadp-usecase-restore-different-namespace.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
66

77
toc::[]
88

9+
[role="_abstract"]
910
Following is a use case for using {oadp-short} to restore a backup to a different namespace.
1011

1112
//restore

modules/oadp-usecase-backup-odf.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@
66
[id="oadp-usecase-backup-odf_{context}"]
77
= Backing up an application using {oadp-short} and {odf-short}
88

9+
[role="_abstract"]
910
In this use case, you back up an application by using {oadp-short} and store the backup in an object storage provided by {odf-first}.
1011

1112
* You create an object bucket claim (OBC) to configure the backup storage location. You use {odf-short} to configure an Amazon S3-compatible object storage bucket. {odf-short} provides MultiCloud Object Gateway (NooBaa MCG) and Ceph Object Gateway, also known as RADOS Gateway (RGW), object storage service. In this use case, you use NooBaa MCG as the backup storage location.

modules/oadp-usecase-include-ca-cert-backup.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@
66
[id="oadp-usecase-include-ca-cert-backup_{context}"]
77
= Backing up an application and its self-signed CA certificate
88

9+
[role="_abstract"]
910
The `s3.openshift-storage.svc` service, provided by {odf-short}, uses a Transport Layer Security protocol (TLS) certificate that is signed with the self-signed service CA.
1011

1112
To prevent a `certificate signed by unknown authority` error, you must include a self-signed CA certificate in the backup storage location (BSL) section of `DataProtectionApplication` custom resource (CR). For this situation, you must complete the following tasks:

modules/oadp-usecase-restore.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@
66
[id="oadp-usecase-restore_{context}"]
77
= Restoring an application to a different namespace using {oadp-short}
88

9+
[role="_abstract"]
910
Restore a backup of an application by using {oadp-short} to a new target namespace, `test-restore-application`. To restore a backup, you create a restore custom resource (CR) as shown in the following example. In the restore CR, the source namespace refers to the application namespace that you included in the backup. You then verify the restore by changing your project to the new restored namespace and verifying the resources.
1011

1112
.Prerequisites

modules/oadp-using-legacy-aws-plugin.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@
77
[id="oadp-using-legacy-aws-plugin_{context}"]
88
= Using the legacy-aws Velero plugin in the DataProtectionApplication CR
99

10+
[role="_abstract"]
1011
In the following use case, you configure the `DataProtectionApplication` CR with the `legacy-aws` Velero plugin and then back up an application.
1112

1213
[NOTE]

0 commit comments

Comments
 (0)