mc inventory resume resumes a suspended inventory job. The job transitions back to its pre-suspension state. This command requires the admin:InventoryControl permission. Syntax Example The following command resumes a suspended inventory job:

The mc replicate rm command removes a replication rule from an AIStor bucket. The mc replicate remove command has equivalent functionality to mc replicate rm. Syntax Example The following command removes the replication rule with specified id from the mydata bucket on the myaistor AIStor deployment:

The mc watch command watches for events on the specified AIStor bucket or local filesystem path. For S3 services, use mc event add to configure bucket event notifications on S3-compatible services. You can also use mc watch against a local filesystem directory to produce similar results to running the inotify -e modify,create,delete,move command. Syntax Example The following command watches for events on any object or prefix in the mydata bucket on the myaistor AIStor deployment:

Version added This command was added in AIStor Client RELEASE.2025-12-19T20-11-44Z and requires AIStor Server RELEASE.2025-12-20T04-58-37Z or later. For earlier versions, use the manual license file replacement method described in License renewal. The mc license update command updates or renews the license for an AIStor deployment.

The mc mb command creates a new bucket on an AIStor deployment. You can also use mc mb to create buckets on S3-compatible services. Syntax Example The following command creates a new bucket on the myaistor deployment:

The mc replicate import command imports JSON-formatted replication rules for an AIStor bucket from STDIN. Syntax Example The following command imports the replication configuration for the mydata bucket on the myaistor AIStor deployment:

The mc support top net command displays realtime network metrics. Syntax Example The following command displays the current realtime network metrics for the alias myaistor deployment.

AIStor supports expanding an existing distributed cluster by adding a new server pool. Each pool expands the total available storage capacity of the cluster. 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.

AIStor supports publishing bucket notification events to PostgreSQL. AIStor supports PostgreSQL 9.5 and later only. Prerequisites PostgreSQL 9.5 and later AIStor relies on features introduced with PostgreSQL 9.5. The AIStor mc Command Line Tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions.

Metrics version 2 provides metrics organized into four categories: Cluster metrics Bucket metrics Resource metrics Node metrics Each v2 endpoint returns all metrics for its category. For example, scraping the following endpoint returns all cluster metrics: http://HOSTNAME:PORT/minio/v2/metrics/cluster The base endpoint alone, /minio/v2/metrics/, returns cluster metrics. For more flexible scraping and a wider range of metrics, use version 3 metrics. Existing deployments can continue to use version 2 metrics.