Object Management on SILO

Bucket Versioning

Mon, 01 Jan 0001 00:00:00 +0000

Overview

MinIO supports keeping multiple “versions” of an object in a single bucket.

When enabled, versioning allows MinIO to keep multiple iterations of the same object. Write operations which would normally overwrite an existing object instead result in the creation of a new versioned object. MinIO versioning protects from unintended overwrites and deletions while providing support for “undoing” a write operation. Bucket versioning is a prerequisite for configuring object locking and retention rules.

Transition Objects to Remote MinIO Deployment

Mon, 01 Jan 0001 00:00:00 +0000

The procedure on this page creates a new object lifecycle management rule that transitions objects from a bucket on a primary MinIO deployment to a bucket on a remote MinIO deployment. This procedure supports cost-management strategies such as tiering objects from a “hot” MinIO deployment using NVMe storage to a “warm” MinIO deployment using SSD.

Requirements

Install and Configure `mc`

This procedure uses mc for performing operations on the MinIO cluster. Install mc on a machine with network access to both source and destination clusters. See the mc Installation Quickstart for instructions on downloading and installing mc.

MinIO Object Locking

Mon, 01 Jan 0001 00:00:00 +0000

Overview

MinIO Object Locking (“Object Retention”) enforces Write-Once Read-Many (WORM) immutability to protect versioned objects from deletion. MinIO supports both duration based object retention and indefinite legal hold retention.

MinIO Object Locking provides key data retention compliance and meets SEC17a-4(f), FINRA 4511(C), and CFTC 1.31(c)-(d) requirements as per Cohasset Associates.

Bucket Without LockingMinIO versioning preserves the full history of object mutations. However, applications can explicitly delete specific object versions.

Bucket With LockingApplying a default 30 Day WORM lock to objects in the bucket ensures a minimum period of retention and protection for all object versions.

Delete Operations in Locked BucketDelete operations follow normal behavior in versioned buckets, where MinIO creates a DeleteMarker for the object. However, non-Delete Marker versions of the object remain under the retention rules and are protected from any specific deletion or overwrite attempts.

Versioned Delete Operations in Locked BucketMinIO blocks any attempt to delete a specific object version held under WORM lock. The earliest possible time after which a client may delete the version is when the lock expires.

MinIO object locking is feature and API compatible with AWS S3. This page summarizes Object Locking / Retention concepts as implemented by MinIO. See the AWS S3 documentation on How S3 Object Lock works for additional resources.

Transition Objects from MinIO to S3

Mon, 01 Jan 0001 00:00:00 +0000

The procedure on this page creates a new object lifecycle management rule that transition objects from a MinIO bucket to a remote storage tier on the Amazon Web Services S3 storage backend or an S3-compatible service. This procedure supports use cases such as tiering objects to low-cost or archival storage after a certain time period or calendar date.

Requirements

Install and Configure `mc`

Object Deletion

Mon, 01 Jan 0001 00:00:00 +0000

Overview

This page summarizes how a DELETE operation affects objects depending on the configuration of the bucket that contains the object.

Any combination of the following factors may impact how DELETE operations function:

Permissions

MinIO uses a policy based access control system for access management. The user or service account must provide the correct policy action and conditions to allow a DELETE for the bucket and object.

Transition Objects from MinIO to GCS

Mon, 01 Jan 0001 00:00:00 +0000

The procedure on this page creates a new object lifecycle management rule that transition objects from a MinIO bucket to a remote storage tier on the Google Cloud Storage backend. This procedure supports use cases like moving aged data to low-cost public cloud storage solutions after a certain time period or calendar date.

Requirements

Install and Configure `mc`

Transition Objects from MinIO to Azure

Mon, 01 Jan 0001 00:00:00 +0000

The procedure on this page creates a new object lifecycle management rule that transition objects from a MinIO bucket to a remote storage tier on the Azure storage backend. This procedure supports use cases like moving aged data to low-cost public cloud storage solutions after a certain time period or calendar date.

Requirements

Install and Configure `mc`

Automatic Object Expiration

Mon, 01 Jan 0001 00:00:00 +0000

Each procedure on this page creates a new object lifecycle management rule that expires objects on a MinIO bucket. This procedure supports use cases like removing “old” objects after a certain time period or calendar date.

Requirements

Install and Configure `mc`

Data Compression

Mon, 01 Jan 0001 00:00:00 +0000

Overview

MinIO Server supports compressing objects to reduce disk usage. Objects are compressed on PUT before writing to disk, and uncompressed on GET before they are sent to the client. This makes the compression process transparent to client applications and services.

Depending on the type of data, compression may also increase overall throughput. Write throughput for a production deployment is generally 500MB per second or greater per available CPU core in the system. Decompression is approximately 1 GB per second or greater for each CPU core.

Object Management on SILO

Bucket Versioning

Overview

Transition Objects to Remote MinIO Deployment

Requirements

Install and Configure mc

MinIO Object Locking

Overview

Transition Objects from MinIO to S3

Requirements

Install and Configure mc

Object Deletion

Overview

Permissions

Transition Objects from MinIO to GCS

Requirements

Install and Configure mc

Transition Objects from MinIO to Azure

Requirements

Install and Configure mc

Automatic Object Expiration

Requirements

Install and Configure mc

Data Compression

Overview

Install and Configure `mc`

Install and Configure `mc`

Install and Configure `mc`

Install and Configure `mc`

Install and Configure `mc`