minio/docs
1
0
Fork 0
mirror of https://github.com/minio/docs.git synced 2025-11-03 05:13:12 +03:00
Code Activity
Files
30d2fd90d0bc45d66e12fe49f8b77b38b6cb1723
docs/source/object-retention/minio-object-retention.rst
Ravind Kumar ea01909527 SDK import, Nav cleanups, DOCS-417
2022-02-08 16:38:35 -05:00

2.0 KiB
Raw Blame History

MinIO Object Retention

minio

Table of Contents

By default, each new write operation to a unique object name results in overwriting that object. You can configure MinIO to instead create versions <minio-bucket-versioning> of each object mutation, preserving the full history of that object. MinIO also supports Write-Once Read-Many (WORM) locking <minio-object-locking> versioned objects to ensure complete immutability for a specified duration or until the lock is explicitly lifted.

Both versioning and object locking features are available only with distributed MinIO deployments <minio-installation-comparison>.

Bucket Versioning

MinIO keeps each mutation to an object as a full "version" of that object.

Bucket with multiple versions of an object

Clients by default retrive the latest version of an object and can explicitly list and retrieve any other version in the object's history.

WORM Object Locking

MinIO enforces Write-Once Read Many (WORM) immutability on versioned objects. Clients cannot delete a WORM-locked object until the configured locking rules expire or are explicitly lifted.

Bucket with multiple versions of an object

MinIO supports setting bucket-default or per-object WORM locking rules with either duration-based or indefinite lock expirations. MinIO object locking is feature-compatible with AWS S3 object locking.

Object Versioning </object-retention/bucket-versioning> Object Locking </object-retention/minio-object-locking>