mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
31 lines
1.4 KiB
Plaintext
31 lines
1.4 KiB
Plaintext
// 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 support for backup data immutability
|
|
|
|
[role="_abstract"]
|
|
Starting with {oadp-short} 1.4, you can store {oadp-short} backups in an {aws-short} S3 bucket with enabled versioning. The versioning support is only for {aws-short} S3 buckets and not for S3-compatible buckets.
|
|
|
|
See the following list for specific cloud provider limitations:
|
|
|
|
* AWS S3 service supports backups because an S3 object lock applies only 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.
|
|
|
|
* {oadp-short} backups are not supported and might not work as expected when you enable immutability on Azure Storage Blob.
|
|
|
|
* {gcp-short} storage policy only supports bucket-level immutability. Therefore, it is not feasible to implement it in the {gcp-short} environment.
|
|
|
|
|
|
Depending on your storage provider, the immutability options are called differently:
|
|
|
|
* S3 object lock
|
|
* Object retention
|
|
* Bucket versioning
|
|
* Write Once Read Many (WORM) buckets
|
|
|
|
The primary reason for the absence of support for other S3-compatible object storage is that {oadp-short} initially saves the state of a backup as _finalizing_ and then verifies whether any asynchronous operations are in progress.
|
|
|
|
|