AIStor provides tools for scaling your cluster capacity by adding or removing server pools. These tools allow you to expand storage capacity or retire aging hardware without disrupting ongoing operations. Planning for growth MinIO recommends initially sizing clusters for at least 2-3 years of anticipated data growth. This approach minimizes the frequency of expansion operations and simplifies long-term capacity management.

The procedure on this page creates a new bucket replication rule for one-way synchronization of objects from one AIStor bucket to another AIStor bucket. The buckets can be on the same AIStor deployment or on separate AIStor deployments. Requirements Replication requires all participating clusters meet the bucket replication requirements. This procedure assumes you have reviewed and validated those requirements.

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.

AIStor requires an active and unexpired MinIO Commercial License. Use mc license info to check your current license status. Accessing your license The license is available in MinIO SUBNET. Log in to SUBNET. From the Deployments screen, select License Key.

Description The mc admin cluster bucket command and its subcommands provide tools for manually importing and exporting AIStor bucket metadata. This metadata includes configurations related to features like lifecycle management rules. You can use this metadata as a snapshot of the bucket configuration for restoration later, such as part of or backup/restore operations.

The mc admin cluster bucket export command exports bucket metadata for use with the (mc admin cluster bucket import) command. You can use this command to manually back up the metadata for the specified AIStor bucket. The command always saves the output as cluster-metadata.zip. If you specify only the deployment as the target, this command backs up all bucket metadata on the target deployment.

AIStor supports publishing bucket notification events to a NATS service endpoint. Prerequisites The AIStor mc command line tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions. Add a NATS endpoint to an AIStor Server The following procedure adds a new NATS service endpoint for supporting bucket notifications in an AIStor Server.

AIStor supports publishing bucket notification events to NSQ service endpoint. Prerequisites The AIStor mc Command Line Tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions. Add an NSQ endpoint to an AIStor Server The following procedure adds a new NSQ service endpoint for supporting bucket notifications in an AIStor Server.

The procedure on this page creates a new bucket replication rule for two-way “active-active” synchronization of objects between AIStor buckets. Requirements Replication requires all participating clusters meet the bucket replication requirements. This procedure assumes you have reviewed and validated those requirements.

You can use the AIStor Console to perform several of the identity and access management functions available in AIStor, such as: Create and manage user credentials or groups with the built-in AIStor IDP, connect to one or more OIDC providers, or add an LDAP provider for Single Sign On. Configure single sign on workflows using either OpenID Connect or AD/LDAP. View, manage, and create access policies. Create child access keys that inherit the parent’s permissions. IAM Users The IAM Users section provides a management interface for AIStor-managed users.