The mc replicate command configures and manages per-bucket Server-Side Bucket Replication for an MinIO AIStor deployment, including active-active replication configurations and resynchronization. For site-level replication, see mc admin replicate. Subcommands mc replicate includes the following subcommands: Subcommand Description add Create a new server-side replication rule for a bucket on an MinIO AIStor deployment. backlog Show a list of unreplicated new or deleted objects. export Export the JSON-formatted replication rules for an MinIO AIStor bucket to STDOUT. import Import JSON-formatted replication rules for an MinIO AIStor bucket from STDIN. ls List all replication rules on an MinIO AIStor bucket. resync Resynchronize all objects in the specified MinIO AIStor bucket to a remote replication target. resync-backlog Trigger replication for backlogged objects with PENDING or FAILED status. rm Remove a replication rule from an MinIO AIStor bucket. status Display the replication status of an MinIO AIStor bucket. The status also lists the remote target path or location. update Modify an existing bucket replication rule.

The mc retention info 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. mc retention info requires that the specified bucket has object locking enabled. You can enable object locking at bucket creation. See mc mb --with-lock for documentation on creating buckets with object locking enabled.

The mc idp openid accesskey commands allow you to list, delete, or display information about OIDC access key pairs on the MinIO AIStor deployment. This command works against access keys created by an OIDC user after authenticating to MinIO AIStor. Authenticated users can create access keys with the MinIO AIStor console, with the mc admin accesskey create command, or with the mc idp openid accesskey create-with-login command. An authenticated user cannot create access keys for another OIDC user.

The mc idp openid accesskey create-with-login command uses a browser-based login flow to authenticate with an OpenID Connect provider and generate access keys for use with MinIO AIStor. The command starts a local HTTP server, opens the OpenID authentication URL in your browser, and waits for the authentication callback. After successful authentication, it creates access keys using the policies associated with the authenticated OIDC user. For details, see the authentication flow section.

The mc support perf drive command measures the read/write speed of the drives in a cluster. The command displays results in a terminal user interface (TUI) with a spinner during testing and a tabular output showing per-server statistics. Use this command to identify potential drive performance bottlenecks in your deployment. Syntax Example The following command runs drive read/write performance measurements on all drives on all nodes for the cluster with alias myaistor.

This page covers settings that control Information Lifecycle Management (ILM) for the MinIO AIStor process. 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.

The following section documents environment variables and configuration settings for customizing MinIO AIStor’s global audit event queue. These settings control all configured audit targets. Settings Audit event queue dir Environment Variable MINIO_AUDIT_QUEUE_DIR Configuration Setting audit_event_queue_dir Specify the directory path to enable MinIO AIStor’s persistent event store for undelivered messages, such as /opt/minio/audit/events.

The mc table namespace create command creates a new Iceberg namespace within a warehouse on an MinIO AIStor cluster. A namespace is an organizational unit within a warehouse that groups related tables. Namespaces can have custom properties for categorization and management. Example The following command creates a namespace named prod in the analytics warehouse on the myaistor MinIO AIStor cluster:

The mc table warehouse create command creates a new Iceberg warehouse on an MinIO AIStor cluster. A warehouse is the top-level organizational unit in the Iceberg catalog hierarchy. Creating a warehouse also creates a corresponding bucket to store Iceberg table data and metadata. Example The following command creates a warehouse named analytics on the myaistor MinIO AIStor cluster:

The mc table namespace command manages Iceberg namespaces on MinIO AIStor clusters. A namespace is an organizational unit within a warehouse that groups related tables. Namespaces provide logical separation and can have custom properties for categorization and management. Subcommands mc table namespace includes the following subcommands: