The mc mirror command synchronizes content to an MinIO AIStor deployment, similar to the rsync utility. mc mirror supports filesystems, MinIO AIStor deployments, and other S3-compatible hosts as the synchronization source. The target synchronization site file names are normalized using the shortest equivalent name. For example, s3/miniocloud//this/./object becomes miniocloud-backup/this/object. mc mirror only synchronizes the current object without any version information or metadata other than tags. To synchronize an object’s version history and other metadata, consider using mc replicate for bucket replication or mc admin replicate for site replication.

The mc replicate resync command resynchronizes all objects in the specified MinIO AIStor bucket to a remote replication target. This command requires first configuring the remote bucket target using the mc replicate add command. You must specify the resulting remote ARN as part of running mc replicate resync. This command supports rebuilding an MinIO AIStor deployment using an active-active replication remote as the “backup” source. See the following tutorials for more information on active-active replication.

The mc ilm rule add command adds an object lifecycle management rule to a bucket. Syntax The command supports adding both Transition (Tiering) and Expiration lifecycle management rules. Example The following command adds new lifecycle management rules to the mydata bucket on the myaistor deployment:

The mc license register command connects your deployment with your MinIO SUBNET account. The registration process collects the following information about the cluster for upload to SUBNET: Deployment ID Cluster Name Used capacity MinIO AIStor version Number of server pools Number of servers Number of drives Total space across all drives Space used across all drives Number of buckets Number of objects The cluster name is generated automatically unless defined by an environment variable or mc admin name set.

The mc share upload command generates a temporary presigned URL with integrated access credentials for uploading objects to an MinIO AIStor bucket. The temporary URL expires after a configurable time limit. Applications can perform a PUT to upload an object using the URL. For more information on shareable object URLs, see the Amazon S3 documentation on Pre-Signed URLs. Syntax Example The following command generates a new presigned upload URL for the mydata bucket on the myaistor MinIO AIStor deployment:

The mc retention set command configures the Write-Once Read-Many (WORM) locking settings for an object or object(s) in a bucket. You can also set the default object lock settings for a bucket, where all objects without explicit object lock settings inherit the bucket default. To lock an object under legal hold, use mc legalhold set. Object Locking on Existing Buckets Beginning with RELEASE.2025-05-20T20-30-00Z, MinIO AIStor allows setting object locking and retention rules on any existing bucket. Earlier versions of MinIO AIStor only allowed setting retention rules for buckets that allowed object locking at the bucket’s creation.

The mc support callhome command allows the enabling or disabling of sending diagnostic reports from a deployment to SUBNET. With Call Home, MinIO AIStor automatically sends a deployment’s diagnostic information to SUBNET. This makes it easier and quicker for the MinIO AIStor team to respond to questions and issues. MinIO AIStor enables this functionality by default for registered clusters. If you prefer not to automatically send these reports to SUBNET, you may disable callhome.

The mc support inspect command collects the data and metadata associated to objects at the specified path. If this information is required to diagnose a SUBNET issue, MinIO AIStor Engineering will provide the appropriate command. MinIO AIStor assembles this data from each backend drive storing an erasure shard for each specified object. For registered clusters, the file uploads to MinIO AIStor for use by the engineering team in support efforts.

The mc replicate status command displays the replication status of an MinIO AIStor bucket. The status also lists the remote target path or location. Example Syntax The following command displays the current replication status of the mydata bucket on the myaistor MinIO AIStor deployment:

mc inventory migrate-from-batch converts an existing batch catalog YAML configuration (v2 format) to the inventory YAML format (v1 format). This command enables migration from the batch catalog system to the newer inventory system. The command transforms the YAML structure by: Changing apiVersion from v2 to v1. Removing the bucket field (the bucket is specified when submitting the configuration). Adding an id field with the specified inventory ID. Preserving all comments and other configuration fields. After converting the batch catalog YAML, use mc inventory put to upload the configuration to your target bucket.