The following procedure adds a server pool to an existing AIStor deployment running on baremetal infrastructure. Each pool expands the total available storage capacity of the cluster while maintaining the overall availability of the cluster. All commands provided below use example values. Replace these values with those appropriate for your deployment. Review the Prerequisites before starting this procedure. Complete any planned hardware expansion prior to decommissioning older hardware pools. 1) Install AIStor on each node in the new server pool Follow the instructions to install the appropriate AIStor Object Store package for your architecture and operating system on each node of the new pool.

AIStor server-side bucket replication is an automatic bucket-level configuration that synchronizes objects between a source and destination bucket. AIStor server-side replication requires the source and destination bucket be two separate AIStor clusters running the same Object Store version. For each write operation to the bucket, AIStor checks all configured replication rules for the bucket and applies the matching rule with highest configured priority. AIStor synchronizes new objects and object mutations, such as new object versions or changes to object metadata. This includes metadata operations such as enabling or modifying object locking or retention settings.

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 AIStor Batch Framework allows you to create, manage, monitor, and execute jobs using a YAML-formatted job definition file (a “batch file”). The batch jobs run directly on the AIStor server to take advantage of the server-side processing power without constraints of the local machine where you run the AIStor Client. The expire batch job applies Automatic Object Expiration behavior to a single bucket. The job determines expiration eligibility based on the provided configuration, independent of any configured expiration rules.

AIStor supports publishing bucket notification events to a MySQL service endpoint. AIStor supports MySQL 5.7.8 and later only. Prerequisites MySQL 5.7.8 and later AIStor relies on features introduced with MySQL 5.7.8. The AIStor mc command line tool This procedure uses the mc command line tool for certain actions. See the mc Quickstart for installation instructions.

AIStor supports configuring a single Active Directory or LDAP (AD/LDAP) service for external management of user identities. Enabling AD/LDAP integration for identity management disables the internal identity provider. Steps to integrate your AD/LDAP service: Configure your AIStor cluster for AD/LDAP integration. Access the AIStor console with AD/LDAP credentials. Generate temporary credentials for application access with the AssumeRoleWithLDAPIdentity Security Token Service (STS) API See the documentation for your AD/LDAP provider for detailed information about configuring user identities.

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.

The AIStor Console is a rich graphical user interface that provides similar functionality to the mc command line tool. This page provides an overview of the AIStor Console and describes configuration options and instructions for logging in. Overview You can use the AIStor Console for administration tasks like Identity and Access Management, Metrics and Log Monitoring, or Server Configuration.

Syntax Example The following command retrieves the anonymous access policy for the mydata bucket on the myminio AIStor deployment:

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: