The mc ilm tier ls command shows the remote tiers configured on a deployment. The mc ilm tier list command has equivalent functionality to mc ilm tier ls. Syntax Example The following example outputs a list of the existing remote tiers on the myaistor deployment.

The mc idp ldap accesskey ls displays a list of LDAP access key pairs. mc idp ldap accesskey ls is also known as mc idp ldap accesskey list. This command works against access keys created by an AD/LDAP user after authenticating to AIStor. Create AD/LDAP service accounts with the mc idp ldap accesskey create command. Authenticated users can manage their own long-term Access Keys using the AIStor Console. AIStor supports using AssumeRoleWithLDAPIdentity to generate temporary access keys using the Security Token Service.

The mc support perf client command measures the network throughput from the local device running the AIStor Client to the server. The command displays results in a terminal user interface (TUI) with a spinner during testing and a tabular output showing TX (transmit) statistics for each server. Use this command to identify potential network performance bottlenecks between the client and server. Syntax Example The following command tests the network throughput from the local device to the server with alias myaistor.

The mc ilm tier add command creates a new remote storage tier to a supported storage services. See Object Transition for a complete list. Syntax Example The following example creates a new remote tier called WARM-MINIO-TIER on the myaistor deployment. The command creates a tier for a remote AIStor deployment located at the hostname https://warm-minio.example.com.

Metrics and alerts AIStor Server publishes point-in-time metrics using the Prometheus Data Model. You can use any scraping tool which supports that data model to pull those metrics into a database for populating historical views, performing query/analysis of metrics data, or creating alerts on preferred data points.

This section provides documentation for operating and maintaining AIStor Object Store deployments. Use this documentation for Day 2 and ongoing operational tasks in production environments, including monitoring, scaling, troubleshooting, and managing production AIStor deployments. Core concepts Core concepts explain the foundational technologies that underpin AIStor. Understanding topics like erasure coding, distributed architecture, and data protection mechanisms provides a foundation for effectively operating your cluster.

Sets or replaces the cluster name for an AIStor deployment. This command cannot override a cluster name set with the MINIO_SITE_NAME environment variable. Syntax Example The following command sets the cluster name for the deployment at alias myaistor:

Distributed AIStor deployments rely on Erasure Coding to provide built-in tolerance for multiple drive or node failures. Depending on the deployment topology and the selected erasure code parity, AIStor can tolerate the loss of up to half the drives or nodes in the deployment while maintaining read access (“read quorum”) to objects. For Kubernetes deployments, you can further enhance fault tolerance by configuring spread zones to distribute pods across different failure domains, such as racks or availability zones.

Lists the entities associated with a policy, user, or group on a target AIStor deployment. This command only returns minio-managed users and groups. To list entities associated with an Active Directory or LDAP (AD/LDAP) configuration, use mc idp ldap policy entities.

The mc admin cluster iam import command imports IAM metadata as created by the mc admin cluster iam export command. You can use this command to manually restore IAM metadata settings for an AIStor deployment. The command outputs the results of the import, including the following: count of individual entities imported by entity type list of policies imported by entity type they imported to list of entities that failed to import Syntax Example The following command imports the IAM metadata of the specified file onto the myaistor deployment.