Object Replication
    • 07 Mar 2024
    • PDF

    Object Replication

    • PDF

    Article Summary

    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.

    As described completely in the instructions below, 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.

    Creating a Replication Job

    1. On the Buckets list, clickfor the desired bucket. This is the source bucket.
    2. Click Settings.
    3. Click the Replications tab.

    4. You are prompted to create a replication job. And, you are reminded that buckets selected for replication must have the same owner. Click Replication Job.

    5. Enter a name for the replication job. The job name will be ComponentReplication01 in this example:

    6. Enter a name for the destination bucket. When you click in the Destination Bucket area, you are prompted with a list of buckets that match the criteria for a destination. For example:

      Click on a bucket as the destination.

      Notice that the active bucket (widget-schematics) is in red because it is the source for the replication. And, the source cannot be the same as the destination bucket.

    7. Click Select.
    8. You can select advanced options for the job:

      Replicate only new objects indicates only new data added to the source bucket will be replicated. If you do not select this option, ALL existing objects from the source bucket will be replicated in the destination bucket.

      Sync deleted objects indicates that objects deleted in the source bucket will also be deleted in the destination bucket.

    9. Optionally, you can add a prefix to filter objects that will be copied from the source bucket. In the following example, only objects in the source bucket that have a name that begins with the text, schematic, will be copied to the destination bucket.

    10. Optionally, you can add object tags on which to filter objects to be replicated. (Refer to Object Tags  for instructions on adding a tag.)
      If you select the Sync deleted objects option, you cannot filter on object tags.

      If you specify both a prefix and object tag(s), all conditions must be met for the source bucket object to be copied to the destination bucket. In the following example, only objects in the source bucket that meet the following conditions will be replicated:

      — The object name begins with schematic  AND
      — The object has tags of release: 101 and line: arrowhead.

    11. Click Create.

    The replication job panel will appear similar to:

    Reviewing the Replication Job Panel

    Each job is listed with:

    • Name of the replication job
    • Destination bucket to which objects will be copied
    • Sync Deleted Objects indication that this option was (Yes) or was not (No) selected when creating the job
    • Last Replicated date/time when objects were last replicated
    • Count, which is the number of objects replicated on the Last Replicated date
    • Replication Size, which shows the total size of the objects last replicated
    • Filters indicate a prefix and/or object tag filter was (Yes) or was not (No) specified when creating the job
    • Status will beor.
    • Action offers a menuwith options to Pause/Resume or Delete the replication job.

    The following is a sample of an actively running replication job. In this case, the last replication occurred on Nov 10, 2023, and 31 objects (totaling 2.47 MB) were replicated to widget-components-project (the destination bucket).

    if you have a long list of replication jobs, use the list options to display all jobs, only jobs that are running, or only paused jobs:

    Pausing/Resuming a Replication Job

    To pause a job:

    1. Clickfor the replication job that you want to pause.
    2. Select Pause.
    3. Click Pause to confirm that you no longer want to replicate objects.

    To resume running the replication job:

    1. Clickfor the replication job that you want to resume.
    2. Select Resume.
    3. Click Resume to confirm that you want to replicate objects again.

    Deleting a Replication Job

    1. Clickfor the replication job that you want to delete.
    2. Select Delete.
    3. Be sure you want to delete the job because it may disrupt replication that is running (in progress). Click Delete to confirm.

    FAQs for Object Replication

    Does the Replication platform create any new buckets in my Wasabi account?

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

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

    The following are use cases that 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?

    Yes. You can configure:

    • Replication from a versioned bucket to a versioned bucket.
    • Replication from a bucket with object locking to another bucket with object locking. In this case, only objects will be 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 will get the mode based on the destination bucket. For example. if the destination bucket is configured with Compliance mode, then the object is replicated with that mode assigned.

    How long will 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.