The mc ls command lists buckets and objects on an AIStor deployment. You can also use mc ls to list objects on S3-compatible services. Syntax Example The following command lists all objects in a bucket on the myminio deployment:

The mc support top disk command displays current drive statistics. Syntax Example The following command displays the current disk usage and performance on the alias myminio.

The mc support diag command generates a health report for an AIStor deployment. The command generates and uploads the health report to SUBNET for analysis. Automated with Call Home The report is automatically generated and uploaded every 24 hours with callhome, which can be disabled or enabled at any time. The resulting health report is intended for use by AIStor Engineering through SUBNET and may contain internal or private data points. Exercise caution before sending a health report to a third party or posting the health report in a public forum.

The mc license register command connects your deployment with your AIStor SUBNET account. The registration process collects the following information about the cluster for upload to SUBNET: Deployment ID Cluster Name Used capacity AIStor Object Store version Number of server pools Number of servers Number of drives Space on each drive Space used on each drive Number of buckets Number of objects After registration, you can upload deployment health reports directly to SUBNET using the mc support diag command.

The mc support telemetry replay command replays a file of telemetry data to an OpenTelemetry collector. You can record a file to replay later with mc support telemetry record. Syntax Example The following command replays a local file of telemetry data to a localhost OTLP server.

Syntax The mc legalhold info command returns the current legal hold setting for an object or objects. mc legalhold requires that the specified bucket has object locking enabled. You can only enable object locking at bucket creation. See mc mb --with-lock for documentation on creating buckets with object locking enabled.

Use the mc support perf command to review the performance of the S3 API (read/write), network IO, and storage (drive read/write). The resulting tests can provide general guidance of deployment performance under S3 GET and PUT requests and identify any potential bottlenecks. For more complete performance testing, consider using a combination of load-testing using your staging application environments and the AIStor WARP S3 benchmarking tool.

The procedure on this page creates a new object lifecycle management rule that transition objects from an AIStor bucket to a remote storage tier on the storage backend. This procedure supports use cases like moving aged data to low-cost public cloud storage solutions after a certain time period or calendar date. Requirements Install and configure mc This procedure uses mc for performing operations on the AIStor cluster. Install mc on a machine with network access to both source and destination clusters. See the mc Installation Quickstart for instructions on downloading and installing mc.

Use the following checklist when planning the software configuration for a production, distributed MinIO deployment. AIStor pre-requisites Description ☐ Servers running a Linux operating system with a kernel of 6.6.x or later for access to critical performance features.Red Hat Enterprise Linux (RHEL) 10 and Ubuntu Server 24.04 LTS use appropriate kernel versions by default. ☐ A method to synchronize time servers across nodes, such as with ntp, timedatectl or timesyncd.The method to use varies by operating system.Check with your operating system’s documentation for how to synchronize time with a time server. ☐ Disable system services that index, scan, or audit the filesystem, system-level calls, or kernel-level calls.These services can reduce performance due to resource contention or interception of AIStor operations.MinIO strongly recommends uninstalling or disabling the following services on hosts running AIStor:- mlocate or plocate- updatedb- auditd- Crowdstrike Falcon- Antivirus software (clamav)The above list represents the most common services or softwares known to cause performance or behavioral issues with high performance systems like AIStor.Consider removing or disabling any other service or software which functions similarly to those listed above on AIStor hosts.Alternatively, configure these services to ignore or exclude the AIStor process and all drives or drive paths accessed by AIStor. ☐ System administrator access to the remote servers ☐ A management tool for distributed systems, such as Ansible, Terraform, or Kubernetes for orchestrated environments.Kubernetes infrastructures should use the MinIO Operator for best results. ☐ Load balancer to handle routing of requests (for example, NGINX) ☐ Prometheus or a Prometheus-compatible setup for monitoring and metrics ☐ Grafana or similar Prometheus-compatible visual dashboard ☐ (Optional) mc installed on the local host system AIStor install Install a matching version of AIStor across all nodes in the deployment.

This section documents steps for running AIStor as a container. Procedure Pull the latest stable image of AIStor Server Docker docker pull quay.io/minio/aistor/minio Podman podman pull quay.io/minio/aistor/minio Create a data directory for use with the server