The mc cp command copies objects to or from an AIStor deployment, where the source can be either an AIStor deployment or a local filesystem. You can also use mc cp against the local filesystem to produce similar results to the cp commandline tool. mc cp copies only the latest version or the specified version of an object without any version information or modification date.

The mc batch cancel stops an ongoing batch job. You must specify the job ID. To find the job ID, use mc batch list. Syntax Example The following command outputs the job definition for the job identified as KwSysDpxcBU9FNhGkn2dCf.

The mc alias remove command removes an alias from the AIStor client configuration. Syntax Example The following command removes the alias named myaistor:

The mc admin user sts info command retrieves information on the specified STS credential, such as the parent AIStor user who generated the credentials, associated policies, and expiration. Credentials provide temporary access to the AIStor deployment. Syntax Example The following command retrieves information on the STS credentials with specified access key:

The mc idp ldap info command outputs the current configuration for an AD/LDAP provider on a specified AIStor deployment. Syntax Example The following example outputs the AD/LDAP configuration settings on the myaistor deployment.

The mc admin user disable command disables an AIStor user on the target AIStor deployment. Clients cannot use the user credentials to authenticate to the AIStor deployment. Disabling a user does not remove that user from the deployment. Use mc admin user enable to enable a disabled user on an AIStor deployment. To manage external Identity Provider users, see OIDC or AD/LDAP. Syntax Example The following command disables user myuser on the myaistor AIStor deployment:

The mc admin user ls command lists all AIStor users on the target AIStor deployment. The mc admin user list command has equivalent functionality to mc admin user ls. mc admin user ls does not return the access key or secret key associated to a user. Use mc admin user info to retrieve detailed user information, including the user access key. To manage external Identity Provider users, see OIDC or AD/LDAP.

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

The mc idp openid enable command starts using an existing set of configurations for an OIDC provider with your AIStor deployment. Example and syntax Example The following example enables the server configurations defined as test_config on the myaistor deployment.

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.