This page documents the steps necessary to remove a peer site from existing Site Replication configuration. Remove the Peer Site using AIStor Console In a browser, access the Console for one of the existing replicated sites.

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.

The procedure on this page creates a new object lifecycle management rule that transitions objects from a bucket on a primary AIStor deployment to a bucket on a remote AIStor deployment. This procedure supports cost-management strategies such as tiering objects from a “hot” AIStor deployment using NVMe storage to a “warm” AIStor deployment using SSD. Requirements Install and configure mc This procedure uses mc for performing operations on the AIStor cluster. Install mc on a machine with network access to both source and destination clusters. See the mc Installation Quickstart for instructions on downloading and installing mc.

You can suspend bucket versioning at any time using the AIStor Console, the AIStor mc CLI, or using an S3-compatible SDK. Behavior While versioning is suspended, AIStor does the following in the bucket: Objects created while versioning is suspended are assigned a null version ID. Any changes to an object while versioning is suspended result in overwriting that null versioned object. AIStor does not remove or otherwise alter existing versioned objects as part of suspending versioning. Clients can continue interacting with any existing object versions in the bucket. Procedure To disable versioning, select whether you want to use the AIStor Console or the AIStor Client (mc).

AIStor Server’s support site replication for both synchronous and asynchronous replication of data between independent AIStor Server deployments. Deploy AIStor Server peer sites in different racks, datacenters, or geographic regions to support functions like BC/DR (Business Continuity / Disaster Recovery) or geo-local read/write performance in a globally distributed AIStor Server AIStor Server. An AIStor Server multi-site deployment with three peers. Write operations on one peer replicate to all other peers in the configuration automatically

This procedure downloads and installs the AIStor Server onto baremetal hosts running Red Hat Enterprise Linux Review the Hardware and System Requirements to ensure your target infrastructure meets our guidance. You can also open a SUBNET issue to request an architecture review or assistance during deployment. MinIO strongly recommends using only RHEL releases in the Full Support lifecycle with Long-Term Support (LTS) Kernels in the 6.12 or later release series, such as RHEL 10. These Linux kernels include support for critical performance features.

AIStor supports deploying resources onto macOS hosts for local development and evaluation. For the purposes of evaluation or local development, MinIO recommends using a machine released in the last 4 years with at least 8 GB of RAM. You can use any supported version of macOS. For testing or local development using a virtualized environment, use a machine with a higher number of cores and 16 or 32GB of RAM.

Install on Red Hat Enterprise Linux Deploy AIStor onto RHEL 10+

This procedure provides guidance for enabling Server-Side Encryption (SSE) using AIStor Key Manager as the Key Management Service (KMS). Enabling SSE on an AIStor deployment automatically encrypts the backend data for that deployment using the default encryption key selected during the setup process. AIStor requires access to the Key Manager to decrypt the backend and start normally. You can neither disable nor reset encryption of the backend.

Use the mc support proxy command to configure a proxy to use to communicate with MinIO SUBNET. Syntax mc support proxy set Create a proxy URL for the AIStor deployment to use when communicating with MinIO SUBNET.