MinIO AIStor supports decommissioning and removing server pools from a deployment with two or more pools. To decommission, there must be at least one remaining pool with sufficient available space to receive the objects from the decommissioned pools. MinIO AIStor supports queueing multiple pools in a single decommission command. Each listed pool immediately enters a read-only status, but draining occurs one pool at a time. Decommissioning is designed for removing an older server pool whose hardware is no longer sufficient or performant compared to the pools in the deployment. MinIO AIStor automatically migrates data from the decommissioned pools to the remaining pools in the deployment based on the ratio of free space available in each pool.

MinIO AIStor supports publishing an audit log of all operations to a remote receiver. The audit logging feature meets security and compliance requirements around granular tracking of operations within an MinIO AIStor deployment. MinIO AIStor does not by default publish audit logs to any destination. Audit logs can contain private and internal details such as hostnames, IP addresses, and object names. The remote receiver takes responsibility for processing, storing, and securing all incoming audit logs.

This page describes how to upgrade MinIO AIStor Helm clusters that use public registries and have direct internet access to helm.min.io and quay.io. If your cluster uses a private container registry or is in an airgapped environment, see: Upgrade with Private Registry Upgrade in Airgapped Environment Overview MinIO AIStor Helm upgrades involve updating two components:

The AIStor Client (mc) is a drop-in replacement for the Open Source MinIO client. MinIO AIStor mc has exclusive functionality intended to support licensed AIStor Server deployments. mc has the following syntax: mc [GLOBALFLAGS] COMMAND --help See Command quick reference for a list of supported commands. Command name Some operating systems bundle another software tool that uses mc as its command name. In those cases, the AIStor Client uses the command mcli instead. Swap mcli in for mc in all reference documentation if this is your situation.

AIStor Server publishes its server logs to the system console. These logs can include errors, information output, or other information useful during troubleshooting or debugging. Server logs do not emit for all operations and cannot support audit trail or similar compliance requirements. If you require such a trail, configure and use audit logging instead. You can read the server logs using any of the following methods: Run journalctl -u minio from any host machine. Run mc admin logs against the MinIO AIStor deployment. Publish server logs to HTTP webhook MinIO AIStor supports publishing logs to a webhook consumer through an HTTP PUT operation, where the body of the request is the log as a JSON document.

Overview Starting with RELEASE.2025-12-20T04-58-37Z, MinIO AIStor supports creating inventory reports on objects and related metadata in a bucket. The MinIO AIStor inventory feature provides a fully-integrated solution with equivalent utility to the previously announced MinIO AIStor Catalog while expanding functionality with improved scheduling, filtering, and integration options.

MinIO AIStor supports expanding an existing distributed cluster by adding a new server pool. Each pool expands the total available storage capacity of the cluster. MinIO AIStor does not support increasing storage through logical volume expansion, rolling drive replacement, or other filesystem-level approaches. Expansion does not provide Business Continuity/Disaster Recovery (BC/DR)-grade protections. While each pool is an independent set of servers with distinct erasure sets for availability, the complete loss of one pool results in MinIO stopping I/O for all pools in the cluster. Similarly, an erasure set which loses quorum in one pool represents data loss of objects stored in that set, regardless of the number of other erasure sets or pools.

This page covers settings for the AIStor Client mc. You can establish or modify settings by defining: an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable. a configuration setting using mc admin config set. If you define both an environment variable and the similar configuration setting, MinIO AIStor uses the environment variable value.

Learn how to use Docker Debug to troubleshoot Docker Hardened Images (DHI) locally or in production.

Learn how to use Extended Lifecycle Support with Docker Hardened Images.