Object Replication: Overview

What is Object Replication?

Object replication enables you to replicate or copy your data between Wasabi regions to protect against ransomware attacks, malicious data manipulation, natural disasters, or even accidental deletion. Object replication enables you to replicate/copy objects from an active storage bucket (source) to one or more different buckets (destination) with these conditions:

• The source and destination buckets must have the same owner.
• The source and destination buckets must have the same versioning status (enabled or disabled).
• While the buckets may be in different Wasabi regions, they must be within the same geographic continent.

You can replicate objects across different buckets in:

• The same account, as described in Object Replication in the Same Account, or
• Different accounts, as described in Object Replication Across Different Accounts.

In either case, Wasabi fully manages object replications. For you, this involves two simple steps:

1. With the source bucket active, begin by giving the replication job a unique name.
2. Select a destination bucket and create the job.

Wasabi will automatically run the job and replicate all objects from the source to the destination bucket. As long as the job is running, objects in the source bucket will be copied to the destination bucket. 

Replicating to More Than One Bucket

Create a replication job for each destination bucket if you want to replicate to more than one bucket.

Bidirectional Synchronization

Wasabi can replicate buckets bidirectionally. Simply create a replication job for both directions. For example:

1. Create a replication job with Bucket-A as the source and Bucket-B as the destination.
2. Create another replication job with Bucket-B as the source and Bucket-A as the destination.

As long as both replication jobs are running, objects in the buckets will copy and synchronize bidirectionally.

FAQs for Object Replication

Does the replication create any new buckets in my Wasabi account?

Configuring and scheduling the replication job will not create any new buckets.

Which use cases are not a good fit for Wasabi replication?

Buckets with mixed versioning statuses are not good for replication:

• Replication from a versioned bucket to an unversioned bucket.
• Replication from an unversioned bucket to a versioned bucket.

Can I replicate versioned or object lock buckets?

You can configure:

• Replication from a versioned bucket to a versioned bucket.
• Replication from a bucket with object lock to another bucket with object lock. In this case, only objects are replicated and not the modes associated with the objects. For example, if an object in the source bucket has Governance mode, only the object is replicated and not the mode.

  The object replicated to the destination receives the mode based on the destination bucket. For example. if the destination bucket is configured with Compliance mode, the object is replicated with that mode assigned.

How long does it take to complete the replication job?

There is no estimated time of completion. Finishing a job will depend on various factors such as the number of objects in the source bucket and the current load being handled by the replication server.

How do I check the status of my replication jobs?

Status is displayed for each replication job. For example:

How do I get email notifications for my replication jobs?

Currently, Wasabi does not send email notifications for replication scheduling, failure, or completion.