An object is binary data, such as images, audio files, spreadsheets, or even binary executable code. The term “Binary Large Object” or “blob” is sometimes associated to object storage, although blobs can be anywhere from a few bytes to several terabytes in size. Object Storage platforms like AIStor provide dedicated tools and capabilities for storing, listing, and retrieving objects using a standard S3-compatible API. AIStor Object Storage uses buckets to organize objects. A bucket is similar to a top-level drive, folder, or directory in a filesystem (/mnt/data or C:\), where each bucket can hold an arbitrary number of objects.

The mc support perf net command measures the network throughput of all nodes in a cluster. The command displays results in a terminal user interface (TUI) with a spinner during testing and a tabular output showing per-server RX (receive) and TX (transmit) statistics. Use this command to identify potential network performance bottlenecks in your deployment. Syntax Example The following command runs a network throughput test on a cluster with alias myaistor.

The mc replicate command configures and manages per-bucket Server-Side Bucket Replication for an AIStor deployment, including active-active replication configurations and resynchronization. For site-level replication, see mc admin replicate. Subcommands mc replicate includes the following subcommands: Subcommand Description add Create a new server-side replication rule for a bucket on an AIStor deployment. backlog Show a list of unreplicated new or deleted objects. export Export the JSON-formatted replication rules for an AIStor bucket to STDOUT. import Import JSON-formatted replication rules for an AIStor bucket from STDIN. ls List all replication rules on an AIStor bucket. resync Resynchronize all objects in the specified AIStor bucket to a remote replication target. resync-backlog Trigger replication for backlogged objects with PENDING or FAILED status. rm Remove a replication rule from an AIStor bucket. status Display the replication status of an AIStor bucket. The status also lists the remote target path or location. update Modify an existing bucket replication rule.

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 command configures the Write-Once Read-Many (WORM) locking settings for an object or object(s) in a bucket. You can also set the default object lock settings for a bucket, where all objects without explicit object lock settings inherit the bucket default. Subcommands mc retention includes the following subcommands:

mc inventory suspend suspends a running inventory job and prevents all future scheduled executions. Suspension pauses both the current execution and prevents the scheduler from starting any future runs. The job remains in the suspended until you explicitly resume it using mc inventory resume. Resuming a job does not rerun any missed executions regardless of scheduling confugratoin. To cancel a job once, use mc inventory cancel. To remove a job permanently, use mc inventory delete.

mc inventory cancel cancels a running inventory job. The behavior of cancelling a job depends on the schedule of the job: once: The job never runs again after cancellation. All other values: The job runs at the next scheduled time. To fully stop a periodic job, either suspend or delete it: mc inventory suspend: Pause the job and prevent future scheduled runs. mc inventory delete: Completely remove the job’s configuration. This command requires the admin:InventoryControl permission.

The mc legalhold set command enables legal hold Write-Once Read-Many (WORM) object locking on an object or objects. mc legalhold requires that the specified bucket has object locking enabled. You can enable object locking at bucket creation. See mc mb --with-lock for documentation on creating buckets with object locking enabled. Version changed Beginning with RELEASE.2025-05-20T20-30-00Z, AIStor allows setting object locking and retention rules on any existing bucket. Earlier versions of AIStor only allowed setting retention rules for buckets at the bucket’s creation.

The mc inventory status command displays the execution status of an inventory job. The command shows comprehensive information about the job’s current state, progress, and execution history. You can optionally watch the status in real-time as the job progresses. Syntax Example The following command displays the status of an inventory job:

The mc idp ldap accesskey rm deletes the specified access key from the local server. mc idp ldap accesskey rm is also known as mc idp ldap accesskey remove. This command works against access keys created by an AD/LDAP user after authenticating to AIStor. Create AD/LDAP service accounts with the mc idp ldap accesskey create command. Authenticated users can manage their own long-term Access Keys using the AIStor Console. AIStor supports using AssumeRoleWithLDAPIdentity to generate temporary access keys using the Security Token Service.