You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users might wish to enable the bucket lock mechanism for their objects stored in buckets to use write-once-read-many(WORM) model. As the storage providers exhibit varying functionality for bucket lock, we need to adapt our approach based on each provider's specific bucket lock implementation.
To support the bucket lock mechanism, the following features of the backup-restore process need to be enhanced:
Garbage collection of backups.
The ability to skip certain snapshots during restoration, if required.
Feature (What you would like to be added):
Users might wish to enable the bucket lock mechanism for their objects stored in buckets to use write-once-read-many(WORM) model. As the storage providers exhibit varying functionality for bucket lock, we need to adapt our approach based on each provider's specific bucket lock implementation.
To support the bucket lock mechanism, the following features of the backup-restore process need to be enhanced:
Bucket Lock
immutable objects support for AWS S3 #818Bucket Lock
immutable object support for Google Cloud Storage. #776Container level WORM
immutable object support for Azure Blob Storage. #781Motivation (Why is this needed?):
Approach/Hint to the implement solution (optional):
The text was updated successfully, but these errors were encountered: