Skip to content

[enterprise-4.18] OADP-5636: After OADP update to 1.4.2 no backups found #91101

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
Mar 26, 2025
Merged

[enterprise-4.18] OADP-5636: After OADP update to 1.4.2 no backups found #91101

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
1 change: 1 addition & 0 deletions ...nd_restore/application_backup_and_restore/installing/about-installing-oadp.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
29 changes: 29 additions & 0 deletions modules/oadp-support-backup-data-immutability.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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.