This page documents all requirements of bucket replication configurations, including: Active-Passive Active-Active Data Resynchronization Ensure you meet the following prerequisites before you set up any of these replication configurations. Permissions required for setting up bucket replication Bucket replication requires specific permissions on the source and destination deployments to configure and enable replication rules.

MinIO AIStor Quality of Service is enforced at two layers: API QoS — per-bucket / per-prefix / per-API request rate (rps) and concurrency controls, enforced inside the MinIO AIStor server. See Bucket-level Quality of Service. Network QoS — per-bucket / per-prefix and per-access-key bandwidth (bytes per second) and request-rate controls, enforced by minwall, the network-layer component of AIStor that runs in front of (or co-located with) each MinIO AIStor server. The two layers stack and complement each other. This page covers Network QoS.

MinIO AIStor bucket notifications allow administrators to send notifications to supported external services when events occur on objects or buckets, similar to Amazon S3 Event Notifications. This page lists supported event types that trigger notifications, including bucket-level and object-level S3 events. Supported notification targets MinIO AIStor supports publishing event notifications to the following targets:

Production Delta Sharing deployments place MinIO AIStor behind a reverse proxy, ingress controller, or load balancer. Because the Delta Sharing protocol emits streamed responses and returns presigned data-file URLs, the proxy must be configured for streaming and its hostname must match the configured Delta Sharing endpoint. This page describes those requirements and the streaming and pagination model behind them. Stream responses through the proxy The Delta Sharing metadata and query endpoints return newline-delimited JSON (application/x-ndjson) that MinIO AIStor streams to the client as it enumerates the files that make up a table. A proxy or load balancer that buffers the full response before forwarding it overflows its buffers or times out on large tables, because the complete response is never held in memory at once on the server side.

This page documents the steps necessary to remove a peer site from existing Site Replication configuration. Removing site replication invalidates any existing Security Token Service (STS) session tokens. In a site replication configuration, STS tokens are signed with the site replicator service account credentials. When you remove site replication, those tokens become invalid. After removal, clients must regenerate their STS tokens as usual.

MinIO AIStor requires an active and unexpired MinIO Software License. Use mc license info to check your current license status. Accessing your license The license is available in MinIO SUBNET. Log in to SUBNET. From the Deployments screen, select License Key.

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.

The following procedures decommissions one or more pools on a Linux bare-metal deployment. Review the MinIO AIStor deployment topology The mc admin decommission command returns a list of all pools in the MinIO AIStor deployment: mc admin decommission status myaistor The command returns output similar to the following: ┌─────┬──────────────────────────────────────────────────────────────────┬──────────────────────────────────┬────────┐ │ ID │ Pools │ Capacity │ Status │ │ 1st │ https://aistor-{01...04}.example.com:9000/mnt/disk{1...4}/aistor │ 10 TiB (used) / 10 TiB (total) │ Active │ │ 2nd │ https://aistor-{05...08}.example.com:9000/mnt/disk{1...4}/aistor │ 60 TiB (used) / 100 TiB (total) │ Active │ │ 3rd │ https://aistor-{09...12}.example.com:9000/mnt/disk{1...4}/aistor │ 40 TiB (used) / 100 TiB (total) │ Active │ └─────┴──────────────────────────────────────────────────────────────────┴──────────────────────────────────┴────────┘ The example deployment above has three pools. Each pool has four servers with four drives each.

Command quick reference The following table lists mc commands: The below table does not include those commands. Command Description mc alias The mc alias S3-compatible hosts that [mc`](#command-mc) can connect to and run operations against. mc anonymous The mc anonymous command supports setting or removing anonymous policies to a bucket and its contents. Buckets with anonymous policies allow public access where clients can perform any action granted by the policy without authentication. mc batch The mc batch commands allow you to run one or more job tasks on an MinIO AIStor deployment. mc cat The mc cat command concatenates the contents of a file or object to another file or object. You can also use the command to display the contents of the specified file or object to STDOUT. cat has similar functionality to cat. mc cp The mc cp command copies objects to or from an MinIO AIStor deployment, where the source can MinIO AIStor or a local filesystem. mc diff The mc diff mc computes the differences between two filesystem directories or MinIO AIStor buckets. mc diff lists only those objects which are missing or which differ in size. mc diff does not compare the contents of objects. mc du The mc du command summarizes the disk usage of buckets and folders. You can also use du against the local filesystem to produce similar results as the du command. mc encrypt The mc encrypt commands set, update, or disable the default bucket Server-Side Encryption (SSE) mode. MinIO AIStor automatically encrypts objects using the specified SSE mode. mc event The mc event command supports adding, removing, and listing bucket event notifications. mc find The mc find command supports searching for objects on an MinIO AIStor deployment.You can also use the command to search for files on a filesystem. mc get The mc get command downloads an object from a target S3 deployment to the local file system. mc head The mc head command displays the first n lines of an object, where n is an argument specified to the command. mc idp ldap The `mc idp /mc-idp-ldap commands allow you to manage configurations to 3rd party Active Directory or LDAP Identity and Access Management (IAM) integrations. mc idp openid The `mc idp commands allow you to manage configurations to 3rd party OpenID Identity and Access Management (IAM) integrations. mc idp ldap policy The `mc idp mc-idp-ldap-policy/" commands show the mapping relationships between policies and the associated groups or users. mc ilm rule The mc ilm commands manage object lifecycle management rules on an MinIO AIStor deployment. mc ilm tier The mc ilm commands manage tiering on an MinIO AIStor deployment. mc legalhold The mc legalhold command sets, removes, or retrieves the object legal hold (WORM) settings for object(s). mc license The mc license commands work with cluster registration for MinIO SUBNET. Use the commands to register a deployment, display information about the cluster’s current license, or update the license key for a cluster. mc ls The mc ls command lists buckets and objects on MinIO AIStor or another S3-compatible service. mc mb The mc mb command creates a new bucket or directory at the specified path. mc mirror The mc mirror command synchronizes content to MinIO AIStor deployment, similar to the rsync utility.mc mirror supports filesystems, MinIO AIStor deployments, and other S3-compatible hosts as the synchronization source. mc mv The mc mv command moves an object from source to the target, such as between MinIO AIStor deployments or between buckets on the same MinIO AIStor deployment. mc mv also supports moving objects between a local filesystem and MinIO AIStor. mc od The mc od command copies a local file to a remote location in a specified number of parts and part sizes. The command outputs the time it took to upload the file. mc ping The mc ping command performs a liveness check on a specified target. mc pipe The mc pipe command streams content from STDIN to a target object. mc put The mc put uploads an object from the local file system to a bucket on a target S3 deployment. mc rb The mc rb command removes one or more buckets on MinIO AIStor or another S3-compatible service.To remove only the contents of a bucketaistor-mc/mc-event, use mc rm instead. mc ready The mc ready command checks the status of a cluster and whether the cluster has read and write quorum. mc replicate The mc replicate-add command configures and manages the Server-Side Bucket Replication for an MinIO AIStor deployment, including active-active replication configurations and resynchronization. mc retention The mc retention 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. mc rm The mc rm command removes objects from a bucket on an MinIO AIStor deployment. To completely remove a bucket, use mc rb instead. mc share Use the mc share commands to manage presigned URLs for downloading and uploading objects to an MinIO AIStor bucket. mc sql The mc sql command provides an S3 Select interface for performing sql queries on objects in the specified MinIO AIStor deployment. mc stat The mc stat command displays information on objects in an MinIO AIStor bucket, including object metadata. You can also use it to retrieve bucket metadata. mc support The inIO Client [`m/mc-support commands provides tools for analyzing deployment health or performance and for running diagnostics. You can also upload generated health reports for further analysis by MinIO AIStor engineering. mc tag The mc tag command adds, removes, and lists tags associated to a bucket or object. mc tree The mc tree command lists all prefixes inside an MinIO AIStor bucket in a tree format. The command optionally supports listing all objects inside of bucket at each prefix, including the bucket root. mc undo The mc undo command reverses changes due to either a PUT or DELETE operation at a specified path. mc update The mc update command automatically updates the mc binary to the latest stable version. mc version The mc version commands enable, disable, and retrieve the versioning status for an MinIO AIStor bucket. mc watch The mc watch command watches for events on the specified MinIO AIStor bucket or local filesystem path. For S3 services, use mc event add to configure bucket event notifications on S3-compatible services.

The following procedures add a server pool to an existing MinIO AIStor cluster running on bare-metal infrastructure. Each pool expands the total available storage capacity of the cluster while maintaining the overall availability of the cluster. A new pool is a set of new nodes and drives that meet the cluster’s erasure set requirements and parity levels. You can use MinIO’s Erasure Code Calculator to check the Erasure Code Stripe Size (K+M) of your new pool to confirm that it meets the EC:M value of current cluster. MinIO strongly recommends seeking an architecture review from MinIO Engineering through SUBNET to analyze potential performance impacts before committing to a new pool for your cluster.