Description Irrevocable Data Loss This command completely and irreversibly erases any data that may exist on the selected drive(s). Volume Manager supports using the xfs_repair utility to attempt to repair managed drives that report XFS filesystem errors, faults, or corruption. This command has no guarantee of success or complete recovery.

Use AIStor Object Lifecycle Management to create rules for time or date based automatic transition or expiry of objects. For object transition, AIStor automatically moves the object to a configured remote storage tier. For object expiry, AIStor automatically deletes the object. AIStor derives its behavior and syntax from S3 lifecycle for compatibility in migrating workloads and lifecycle rules from S3 to AIStor. For example, you can export S3 lifecycle management rules and import them into AIStor or vice-versa. AIStor uses JSON to describe lifecycle management rules and may require conversion to or from XML as part of importing S3 lifecycle rules.

Description The mc ilm rule command and its subcommands configure the rules used to transition objects between storage tiers in MinIO’s Lifecycle Management. Before creating rules with this command, use mc ilm tier and its subcommands to create the tier or tiers of other object storage locations where objects move.

The mc ilm rule add command adds an object lifecycle management rule to a bucket. Syntax The command supports adding both Transition (Tiering) and Expiration lifecycle management rules. Example The following command adds new lifecycle management rules to the mydata bucket on the myminio deployment:

mc idp openid accesskey disable disables the specified access key on the AIStor deployment. Example and Syntax Example The following example disables the access key mykey on the minio deployment:

Syntax The mc admin decommission command starts the decommissioning process for an AIStor server pools. Decommissioning is designed for removing an older server pool whose hardware is no longer sufficient or performant compared to the pools in the deployment. AIStor automatically migrates data from the decommissioned pool to the remaining pools in the deployment based on the ratio of free space available in each pool.

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, AIStor uses the environment variable value.

AIStor supports decommissioning and removing server pools from a deployment with two or more pools. To decommission, there must be at least one remaining pool with sufficient available space to receive the objects from the decommissioned pools. AIStor supports queueing multiple pools in a single decommission command. Each listed pool immediately enters a read-only status, but draining occurs one pool at a time. Decommissioning is designed for removing an older server pool whose hardware is no longer sufficient or performant compared to the pools in the deployment. AIStor automatically migrates data from the decommissioned pools to the remaining pools in the deployment based on the ratio of free space available in each pool.

Syntax Example The following command outputs the status of the specified job with JobID KwSysDpxcBU9FNhGkn2dCf currently in progress on the myminio alias.

The mc batch list command outputs a list of the batch jobs currently in progress on a deployment. Syntax Example The following command outputs a list of all jobs currently in progress on the myminio alias.