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:

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).

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.

Each MinIO AIStor server process exposes unauthenticated endpoints for probing server uptime and deployment high availability for simple healthchecks. These endpoints return an HTTP status code indicating whether the underlying resource is healthy or satisfies read/write quorum. The server exposes no other data through these endpoints. MinIO AIStor liveness Use the following endpoint to test if the specified MinIO AIStor server is up and ready to serve requests:

This section documents best practices and tutorials for updating the MinIO AIStor server on Linux and Kubernetes infrastructure to a newer release. All MinIO AIStor software supports non-disruptive upgrades with zero downtime. In optimal environments, cluster-wide upgrades typically complete in under 500 milliseconds with large clusters (1000+ nodes) completing in less than 5 seconds. Applications using MinIO or S3 SDKs can rely on the built-in transparent retry to ensure continuous operations during the update procedure.

The mc admin cluster bucket export command exports bucket metadata for use with the (mc admin cluster bucket import) command. You can use this command to manually back up the metadata for the specified MinIO AIStor bucket. The command always saves the output as cluster-metadata.zip. If you specify only the deployment as the target, this command backs up all bucket metadata on the target deployment.

MinIO AIStor can make the loss of an entire site, while significant, a relatively minor incident. Site recovery depends on the replication option you use for the site. Replication type Restoration method Site Replication Total restoration of IAM configurations, bucket configurations, and data from the healthy peer site(s) Bucket Replication Data restoration of objects and metadata from a healthy remote location for each bucket configured for replication mc mirror Data restoration of objects only from a healthy remote location with no versioning Site replication healing automatically adds IAM settings, buckets, bucket configurations, and objects from the existing site(s) to the new site with no further action required.

Upgrade MinIO Community Edition clusters on Linux to MinIO AIStor by replacing binaries, adding license files, and restarting the cluster.

Run a set of prompts with variables or function calls with an imported or synthetically generated dataset towards the selected models and parameters.