Skip to content

Commit 8a39e2d

Browse files
committed
OADP-5636: After OADP update to 1.4.2 no backups found
Signed-off-by: A.Arnold <anarnold@redhat.com>
1 parent 5b32f8b commit 8a39e2d

File tree

2 files changed

+30
-0
lines changed

2 files changed

+30
-0
lines changed

backup_and_restore/application_backup_and_restore/installing/about-installing-oadp.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -61,6 +61,7 @@ include::modules/oadp-configuring-noobaa-for-dr.adoc[leveloffset=+1]
6161
6262
include::modules/about-oadp-update-channels.adoc[leveloffset=+1]
6363
include::modules/about-installing-oadp-on-multiple-namespaces.adoc[leveloffset=+1]
64+
include::modules/oadp-support-backup-data-immutability.adoc[leveloffset=+1]
6465

6566
[role="_additional-resources"]
6667
.Additional resources
Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * backup_and_restore/installing/about-installing-oadp.adoc
4+
5+
:_mod-docs-content-type: REFERENCE
6+
[id="oadp-support-backup-data-immutability_{context}"]
7+
= OADP does not support backup data immutability
8+
9+
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:
10+
11+
* S3 object lock
12+
* Object retention
13+
* Bucket versioning
14+
* Write Once Read Many (WORM) buckets
15+
16+
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.
17+
18+
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.
19+
20+
[NOTE]
21+
====
22+
Depending on the specific provider and configuration, backups might work in some cases.
23+
====
24+
25+
* 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.
26+
27+
* 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.
28+
29+
* GCP Cloud storage policy only supports bucket-level immutability. Therefore, it is not feasible to implement it in the GCP environment.

0 commit comments

Comments
 (0)