openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Code Issues Releases Activity

OADP-5636: After OADP update to 1.4.2 no backups found

Browse Source 
Signed-off-by: A.Arnold <anarnold@redhat.com>
This commit is contained in:
A.Arnold
2025-02-18 22:47:54 +00:00
committed by openshift-cherrypick-robot
parent c106df4229
commit 4a04801bc5
2 changed files with 30 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
backup_and_restore/application_backup_and_restore/installing/about-installing-oadp.adoc
View File

@@ -61,6 +61,7 @@ include::modules/oadp-configuring-noobaa-for-dr.adoc[leveloffset=+1]
include::modules/about-oadp-update-channels.adoc[leveloffset=+1]
include::modules/about-installing-oadp-on-multiple-namespaces.adoc[leveloffset=+1]
include::modules/oadp-support-backup-data-immutability.adoc[leveloffset=+1]
[role="_additional-resources"]
.Additional resources

29
modules/oadp-support-backup-data-immutability.adoc Normal file
View File

@@ -0,0 +1,29 @@
// Module included in the following assemblies:
//
// * backup_and_restore/installing/about-installing-oadp.adoc
:_mod-docs-content-type: REFERENCE
[id="oadp-support-backup-data-immutability_{context}"]
= OADP does not support backup data immutability
Starting with {oadp-short} 1.3, backups might not function as expected when the target object storage has an immutability option configured. These immutability options are referred to by different names, for example:
* S3 object lock
* Object retention
* Bucket versioning
* Write Once Read Many (WORM) buckets
The primary reason for the absence of support is that {oadp-short} initially saves the state of a backup as _finalizing_ and then scrutinizes whether any asynchronous operations are in progress.
With versions before {oadp-short} 1.3, object storage with an immutability configuration was also not supported. You might see some problems even though backups are working. For example, version objects are not deleted when a backup is deleted.
[NOTE]
====
Depending on the specific provider and configuration, backups might work in some cases.
====
* AWS S3 service supports backups because an S3 object lock only applies to versioned buckets. You can still update the object data for the new version. However, when backups are deleted, old versions of the objects are not deleted.
* Azure Storage Blob supports both versioned-level immutability and container-level immutability. In a versioned-level situation, data immutability can still work in {oadp-short}, but not at the container level.
* GCP Cloud storage policy only supports bucket-level immutability. Therefore, it is not feasible to implement it in the GCP environment.