1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00

OADP-6348-dita-vale-oadp-usecases

Signed-off-by: Shruti Deshpande <shdeshpa@redhat.com>
This commit is contained in:
Shruti Deshpande
2025-07-09 14:19:18 +05:30
committed by openshift-cherrypick-robot
parent 11f7fd293b
commit 8fff38b8a9
8 changed files with 8 additions and 0 deletions

View File

@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
toc::[]
[role="_abstract"]
Following is a use case for using {oadp-short} and {odf-short} to back up an application.
//backup

View File

@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
toc::[]
[role="_abstract"]
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}.
// include a CA cert and run a backup

View File

@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
toc::[]
[role="_abstract"]
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.
// using legacy-aws velero plugin

View File

@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
toc::[]
[role="_abstract"]
Following is a use case for using {oadp-short} to restore a backup to a different namespace.
//restore

View File

@@ -6,6 +6,7 @@
[id="oadp-usecase-backup-odf_{context}"]
= Backing up an application using {oadp-short} and {odf-short}
[role="_abstract"]
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}.
* 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.

View File

@@ -6,6 +6,7 @@
[id="oadp-usecase-include-ca-cert-backup_{context}"]
= Backing up an application and its self-signed CA certificate
[role="_abstract"]
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.
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:

View File

@@ -6,6 +6,7 @@
[id="oadp-usecase-restore_{context}"]
= Restoring an application to a different namespace using {oadp-short}
[role="_abstract"]
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.
.Prerequisites

View File

@@ -7,6 +7,7 @@
[id="oadp-using-legacy-aws-plugin_{context}"]
= Using the legacy-aws Velero plugin in the DataProtectionApplication CR
[role="_abstract"]
In the following use case, you configure the `DataProtectionApplication` CR with the `legacy-aws` Velero plugin and then back up an application.
[NOTE]