MinIO generates a unique and immutable identifier for each versioned object as Removes all versions of an object older than the specified calendar date. Mc rm -versions - Removes all versions of an object. You can alternatively perform manual removal of object versions using the

no longer the “latest” version of that object).

For example, you can configureĪ rule to automatically expire object versions 90 days after they become Object versions and free up storage capacity. MinIO supports configuring configuring object lifecycle management rules to automatically expire or transition aged Than 14GB of data associated to a single object. This process every day for 10 days, the bucket would eventually contain more MinIO would then containīoth the 1GB and 1.1GB versions of the object.

An applicationĪppends 100MB of data to the log and uploads to MinIO. Mutation-heavy workloads, this may result in substantial drive usage byįor example, consider a 1GB object containing log data. MinIO does not perform incremental or differential-type versioning. MinIO only enforces versioning with a specific namespace and thereforeĬonsiders each object.blob above as distinct and unique. While object.blob might be the same binary across all namespaces,

Download the new version Bucket Knight