Enable Two-Way Server-Side Bucket Replication

1) Create a New Bucket Replication Rule on Each Deployment

1. Log in to the MinIO Console for the deployment

2. Select the Manage button for the bucket to replicate

   

3. Select the Replication section

   

4. Select Add Replication Rule +

5. Complete the requested information:

   Field	Description
   Priority	Enter a number value to indicate the order in which to process replication rules for the bucket. 1 indicates the highest importance.
   Target URL	The URL of the deployment to replicate data to.
   Use TLS	Leave the toggle in the ON position if the destination deployment uses TLS. Otherwise, move the toggle to the OFF position.
   Access Key	The user name to use on the destination deployment. The user must have write access to the bucket to replicate to.
   Secret Key	The password for the provided Access Key.
   Target Bucket	The bucket at the destination to write the data to. The target bucket may have the same name as the origin bucket, depending on the destination bucket location.
   Region	The AWS resource region location of the destination deployment.
   Replication mode	Leave the default selection of Asynchronous to allow MinIO to replicate data after the write operation completes on the origin ment. Select Synchronous to attempt to complete the replication of the object during its write operation. While synchronous replication may result in more reliable synchronization between the origin and destination buckets, it may also increase the time of each write operation.
   Bandwidth	Specify the maximum amount of bandwidth the replication process can use while replicating data. Enter a number and select a data unit.
   Health Check Duration	The maximum length of time in seconds MinIO should spend verifying the health of the replicated data on the destination bucket.
   Storage Class	The class of storage to use on the destination deployment for the replicated data. Valid values are either STANDARD or REDUCED_REDUNDANCY.
   Object Filters	Limit which objects to replicate from the bucket by Prefix or tags. If you enter multiple tags, the objects must match all tag values.
   Metadata Sync	Leave selected to also replicate the object’s metadata file. Otherwise, move the toggle to the Off position.
   Delete Markers	Leave selected to also replicate MinIO’s indication that an object has been deleted and should also be marked deleted at the action bucket. Otherwise, move the toggle to the Off position to prevent marking the object as deleted in the destination bucket.
   Deletes	Leave selected to allow replication of the deletion of versions of an object. Otherwise, move the toggle to the Off position to not replicate deletion of object versions.

6. Select Save to finish adding the replication rule

Repeat the above steps to create a rule in the other direction.

1. Go to the Console for the destination deployment used above.

2. Create a replication rule from the second deployment back to the first deployment. The first deployment becomes the target deployment for the rule on the second deployment.

2) Validate the Replication Configuration

1. Go to the Buckets section of the MinIO Console

   

2. Select the Browse button for the bucket you added replication to

   

3. Select the Upload button to add a new object to the bucket

4. Select Upload File

5. Use the interface to add a new object to the bucket

6. Go to the other deployment’s console and select the destination bucket defined in the replication

1) Create a New Bucket Replication Rule on Each Deployment

Use the mc replicate add command to add a new replication rule to each MinIO deployment.

mc replicate add ALIAS/BUCKET \
   --remote-bucket 'https://USER:PASSWORD@HOSTNAME:PORT/BUCKET' \
   --replicate "delete,delete-marker,existing-objects"

• Replace ALIAS with the alias of the origin MinIO deployment. The name must match the bucket specified when creating the remote target in the previous step.

• Replace BUCKET with the name of the bucket to replicate from on the origin deployment.

• Replace the --remote-bucket to specify the remote MinIO deployment and bucket to which the ALIAS/BUCKET replicates.

  The USER:PASSWORD must correspond to a user on the remote deployment with the necessary replication permissions.

  The HOSTNAME:PORT must resolve to a reachable MinIO instance on the remote deployment. The BUCKET must exist and otherwise meet all other replication requirements.

• The --replicate "delete,delete-marker,existing-objects" flag enables the following replication features:

  • Replication of Deletes

  • Replication of existing Objects

  See mc replicate add --replicate for more complete documentation. Omit any field to disable replication of that component.

Specify any other supported optional arguments for mc replicate add.

Repeat this step on the other MinIO deployment. Change the ALIAS and --remote-bucket values to correspond to the first deployment.

You should have two replication rules configured at the conclusion of this step - one created on each deployment that points to the bucket on the other deployment. Use the mc replicate ls command to verify the created replication rules.

2) Validate the Replication Configuration

Use mc cp to copy a new object to the replicated bucket on one of the deployments.

mc cp ~/foo.txt ALIAS/BUCKET

Use mc ls to verify the object exists on the destination bucket:

mc ls ALIAS/BUCKET

Repeat this test by copying another object to the second deployment and verifying the object replicates to the first deployment.

Once both objects exist on both deployments, you have successfully set up two-way, active-active replication between MinIO buckets.