The mc tree command lists all prefixes inside an AIStor bucket in a tree format. The command optionally supports listing all objects inside of bucket at each prefix, including the bucket root. You can also use mc tree against a local filesystem directory to produce similar results to the tree commandline tool. Syntax Example The following command prints a complete tree of all objects at any depth in the mydata bucket on the myminio AIStor deployment:

mc support profile runs a system profile for your deployment. The results of the profile can provide insight into the Object Store process running on a given node. The resulting report is intended for use by AIStor Engineering. You can upload the report to AIStor SUBNET. Independent or third-party use of these profiles for diagnostics and remediation is done at your own risk.

AIStor automatically creates remote targets based on a given file path or resource location (such as an IP or DNS address). Users defining a remote target no longer need to determine an ARN for the remote bucket. Syntax The mc replicate add command creates a new server-side replication rule for a bucket on an AIStor deployment.

Description The mc support callhome command allows the enabling or disabling of sending diagnostic reports from a deployment to AIStor SUBNET. With Call Home, AIStor automatically sends a deployment’s diagnostic information to SUBNET. This makes it easier and quicker for the AIStor team to respond to questions and issues.

The mc support top api command summarizes the real-time API events on an AIStor deployment server. Syntax Example The following command displays the current in-progress S3 API calls on the alias myminio.

Description The mc admin update command updates all AIStor servers in the deployment. The command also supports using a private mirror server for environments where the deployment does not have public internet access. After running the command, a prompt displays to confirm the update. Type y and [ENTER] to confirm and proceed with the update.

AIStor can make the loss of an entire site, while significant, a relatively minor incident. Site recovery depends on the replication option you use for the site. Replication type Restoration method Site Replication Total restoration of IAM configurations, bucket configurations, and data from the healthy peer site(s) Bucket Replication Data restoration of objects and metadata from a healthy remote location for each bucket configured for replication mc mirror Data restoration of objects only from a healthy remote location with no versioning Site replication healing automatically adds IAM settings, buckets, bucket configurations, and objects from the existing site(s) to the new site with no further action required.

This section documents best practices and tutorials for updating the AIStor server on Linux and Kubernetes infrastructure to a newer release. All AIStor software supports non-disruptive upgrades with zero downtime. In optimal environments, cluster-wide upgrades typically complete in under 500 milliseconds with large clusters (1000+ nodes) completing in less than 5 seconds. Applications using MinIO or S3 SDKs can rely on the built-in transparent retry to ensure continuous operations during the update procedure.

AIStor supports scaling deployments by expanding or decomissioning server pools. Ideally, deployments should plan for 3 years of data growth at installation.

Description The mc admin prometheus command and its subcommands provide access to MinIO Prometheus metrics. Subcommands Subcommand Description generate The mc admin prometheus generate command generates a metrics scraping configuration file for use with Prometheus. metrics The mc admin prometheus metrics command prints Prometheus metrics for a cluster.