Description The mc admin scanner commands provide information about the scanner process. Subcommands mc admin scanner includes the following subcommands:

The mc admin accesskey create command adds a new access key and secret key pair for an existing AIStor user. Syntax Example The following command creates a new access key associated to an existing AIStor user:

Object tiering is the moving of the data of an object from one set of hardware to another set of hardware. This is often done as a cost-saving measure, keeping more expensive and performant hardware for the newest or most accessed objects while placing other objects to less expensive and less performant storage solutions. Retrieving a tiered object When AIStor moves an object to another tier, the object’s metadata remains on the primary tier while the object’s data moves to the secondary tier. When AIStor needs to serve a tiered object, it transparently retrieves the object from the secondary tier.

Memory primarily constrains the number of concurrent simultaneous connections per node. MinIO recommends at least 256GiB of RAM per host. Caching memory usage By default, deployments have caching enabled. The AIStor Server allocates up to 75% of host memory as a drive-level per-shard cache for supporting GET operations.

This page covers settings that control Information Lifecycle Management (ILM) for the AIStor process. 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.

mc support upload copies a file from the local file system to a SUBNET ticket. Syntax The command has the following syntax: mc [GLOBALFLAGS] support profile \ ALIAS \ FILE \ [--comment "string"] \ [--enc] \ [--issue integer] Parameters ALIAS Required

The mc update command automatically updates the mc binary to the latest stable version. Running this command is equivalent to manually downloading the latest stable binary and using it to replace the existing mc installation on the host machine. Syntax Example The following command updates the mc binary on the local host:

The mc retention clear command removes the Write-Once Read-Many (WORM) locking settings for an object or object(s) in a bucket. You can also remove the default object lock settings for a bucket. To change the retention status of an object under legal hold, use mc legalhold clear. Syntax Example The following command removes the default object lock configuration for the mydata bucket on the myaistor AIStor deployment:

The mc idp openid update command modifies an existing set of configurations for an OIDC provider. Example and syntax Example The following example changes two of the configuration settings for the myaistor deployment as defined in the test-config setup for Dex integration.

The mc mirror command synchronizes content to an AIStor deployment, similar to the rsync utility. mc mirror supports filesystems, AIStor deployments, and other S3-compatible hosts as the synchronization source. The target synchronization site file names are normalized using the shortest equivalent name. For example, s3/miniocloud//this/./object becomes miniocloud-backup/this/object. mc mirror only synchronizes the current object without any version information or metadata other than tags. To synchronize an object’s version history and other metadata, consider using mc replicate for bucket replication or mc admin replicate for site replication.