Add New Peer Site

This page documents the steps necessary to add a new AIStor installation to an existing Site Replication configuration.

The procedures assumes a new AIStor installations and an existing set of deployments configured for Site Replication. The existing configuration must have all AIStor peer sites reachable and healthy. If any of the sites are unreachable or permanently lost, you must first remove the unreachable site(s) with mc admin replicate rm before expanding with the new site.

The new site must have no data and meet the following requirements:

Ensure the new peer site has a Load Balancer, Reverse Proxy, or similar network control plane component to handle routing connections to its AIStor Server nodes. Using a single node hostname for a peer site creates a single point of failure for site replication where replication can fail if that single node goes down.

Validate that all hosts have complete bidirectional network connectivity prior to configuring site replication.

Configure Site Replication using AIStor Console

  1. Deploy a new, empty AIStor site.

  2. In a browser, access the Console for one of the existing replicated sites.

    For example, https://<addressforsite>:9000

  3. Select Settings, then Site Replication.

  4. Select Add Sites +.

  5. Complete the requested information:

    Field Description
    Site Name: A name or other identifying text to associate with the site.
    Endpoint: (required) The hostname or IP of the load balancer managing connections to the site.

    Specify the URL or IP address of the site’s load balancer, reverse proxy, or similar network control plane component.
    Requests are automatically routed to nodes in the deployment.
    Access Key: (required) The user name for root to use for signing in to the site.
    Secret Key: (required) The password for root to use for signing in to the site.

    Fill out the requested data for each peer site to add to the site replication configuration.

    To add additional sites beyond two, select the + button to the side of the last Site entry.

  6. Select Save.

Configure Site Replication using mc CLI

  1. Deploy the new AIStor peer site(s) following the stated requirements.

  2. Configure an alias for the new site.

    Specify the URL or IP address of the site’s load balancer, reverse proxy, or similar network control plane component. Requests are automatically routed to nodes in the deployment.

    AIStor recommends against using a single node hostname for a peer site. This creates a single point of failure: if that node goes offline, replication fails.

    To check the existing aliases, use mc alias list.

    Use mc alias set to define the hostname or IP of the load balancer managing connections to the new site(s).

    mc alias set minio4 https://minio4.example.com:9000 adminuser adminpassword
    

    or define environment variables:

    export MC_HOST_minio4=https://adminuser:adminpassword@minio4.example.com
    
  3. Add site replication configuration.

    Use the mc admin replicate add command to expand the site replication configuration with the new peer site. Specify the alias of all existing peer sites, then the alias of the new site to add.

    For example, the following command adds the new peer site minio4 to an existing site replication configuration that includes the existing sites minio1, minio2, and minio3.

    mc admin replicate add minio1 minio2 minio3 minio4
    
  4. Query the site replication configuration to verify.

    mc admin replicate info minio1
    

    You can use the alias for any peer site in the site replication configuration.

  5. Query the site replication status to confirm any initial data has replicated to all peer sites.

    You can use the alias for any of the peer sites in the site replication configuration.

    mc admin replicate status minio4
    

    The output could resemble the following:

    Bucket replication status:
    ●  1/1 Buckets in sync
    
    Policy replication status:
    ●  5/5 Policies in sync
    
    User replication status:
    No Users present
    
    Group replication status:
    No Groups present
    
All rights reserved 2024-Present, MinIO, Inc.