The procedure on this page creates a new object lifecycle management rule that transitions objects from a bucket on a primary MinIO AIStor deployment to a bucket on a remote MinIO AIStor deployment. This procedure supports cost-management strategies such as tiering objects from a “hot” MinIO AIStor deployment using NVMe storage to a “warm” MinIO AIStor deployment using SSD. Requirements Install and configure mc This procedure uses mc for performing operations on the MinIO AIStor 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 AIStor provides multiple replication strategies to ensure data availability, support disaster recovery, enable geographic distribution, and facilitate data migration between clusters. Each replication method serves different use cases and operates at different levels, from entire cluster to individual objects. Replication methods MinIO AIStor supports four distinct replication and synchronization approaches:

CONTENTS | PREV | NEXT Example Alternate Implementation of java.io.File C.1 Example Alternate Implementation of java....

You can suspend bucket versioning at any time using the MinIO AIStor Console, the MinIO AIStor mc CLI, or using an S3-compatible SDK. Behavior While versioning is suspended, MinIO AIStor does the following in the bucket: Objects created while versioning is suspended are assigned a null version ID. Any changes to an object while versioning is suspended result in overwriting that null versioned object. MinIO AIStor does not remove or otherwise alter existing versioned objects as part of suspending versioning. Clients can continue interacting with any existing object versions in the bucket. Procedure To disable versioning, select whether you want to use the MinIO AIStor Console or the AIStor Client (mc).

CONTENTS | PREV | NEXT Overview Goals Assumptions Who’s Responsible for Versioning of Streams Compatible Java Type Ev...

contributing: Report issues](reporting_issues. md).

NEWS-2.7.0: NEWS for Ruby 2. This document is a list of user visible feature changes made between releases except for bug fixes.

dtrace_probes: DTrace Probes A list of DTrace probes and their functionality. Module" and "Function" cannot be defined in user defined probes (known as USDT), so th

MinIO AIStor provides tools for scaling your cluster capacity by adding or removing server pools. These tools allow you to expand storage capacity or retire aging hardware without disrupting ongoing operations. Planning for growth MinIO recommends initially sizing clusters for at least 2-3 years of anticipated data growth. This approach minimizes the frequency of expansion operations and simplifies long-term capacity management.

Description The mc admin cluster bucket command and its subcommands provide tools for manually importing and exporting MinIO AIStor bucket metadata. This metadata includes configurations related to features like lifecycle management rules. You can use this metadata as a snapshot of the bucket configuration for restoration later, such as part of or backup/restore operations.