Replicating S3 data between datacenters

Virtuozzo Hybrid Infrastructure can store replicas of S3 cluster data and keep them up to date in multiple geographically distributed datacenters. Geo-replication reduces the response time for local S3 users accessing the data in a remote S3 cluster, or remote S3 users accessing the data in a local S3 cluster, as they do not need an Internet connection.

Geo-replication schedules the update of the replicas as soon as any data is modified. Its performance depends on the Internet connection speed, the redundancy mode, and cluster performance.

If you have multiple datacenters with enough free space, it is recommended to set up geo-replication between S3 clusters residing in these datacenters.

Prerequisites

S3 clusters are created, as described in Creating the S3 cluster.
Each cluster has its own SSL certificate signed by a global certificate authority.

To set up geo-replication between S3 clusters

In the admin panel of a remote datacenter, open the Storage services > S3 > Geo-replication screen.
In the section of the home S3 cluster, click Token. On the Get token panel, copy the token.
In the admin panel of the local datacenter, open the Storage services > S3 > Geo-replication screen, and then click Add datacenter.
Enter the copied token, and then click Done.
Configure the remote S3 cluster the same way.

After you enable geo-replication for the clusters, you can replicate their data per bucket.

To replicate a bucket

Open the Storage services > S3 > Buckets screen, and then select the bucket.
Click Enable geo-replication on the right pane.

The Geo-replication column for this bucket will display Enabled and the bucket will be copied to the connected cluster.

To disable geo-replication of a bucket

Open the Storage services > S3 > Buckets screen, and then select the bucket.
Click Disable geo-replication on the right pane.

The Geo-replication column for this bucket will display Disabled. After geo-replication is disabled for a bucket, the data copied beforehand will remain, but the changes to it will no longer be replicated to the other S3 cluster.