---
title: "Wasabi Object Replication With Cohesity DataProtect"
slug: "wasabi-object-replication-with-cohesity-dataprotect"
updated: 2026-04-10T16:07:42Z
published: 2026-04-10T16:07:42Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wasabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Wasabi Object Replication With Cohesity DataProtect

[Cohesity DataProtect](https://www.cohesity.com/products/dataprotect/) is a high-performance, secure backup and recovery solution. Wasabi is validated to be used as an External Target for Cohesity DataProtect. To learn more about the Cohesity + Wasabi solution, refer to our solution brief, [Comprehensive Enterprise Data Protection and Fast, Cost-effective Cloud Storage with Wasabi and Cohesity](https://cdn.brandfolder.io/BFD8NB05/at/cjsp55bf4pth7m666hcpz/Cohesity_Solution_Brief.pdf).

This article describes the procedure to use Wasabi [Object Replication](https://docs.wasabi.com/docs/bucket-replication) to replicate objects from one region to another within the same continent. This can be used to recover from natural disasters or other events in a region.

> In the case of a disaster, a second, licensed Cohesity DataProtect cluster will be required to recover from your “destination” bucket that contains replicated data.

> The data restoration process is handled by your specific backup software application. As there are many potential variables that will affect your unique environment, Wasabi strongly recommends that you seek the guidance of your backup software's technical support team in the event that you encounter difficulty or have application-specific inquiries.

## Requirements

- Cohesity DataProtect is installed and licensed. This solution was tested with 7.3_release-20251021_a422614d.
- A second, licensed Cohesity DataProtect cluster.
- An active Wasabi Hot Cloud Storage account.
- Access to the Wasabi Console as your account’s root user or with equivalent IAM permissions.
- An active Cohesity DataProtect external target pointing to a Wasabi bucket.
- Access to your Cohesity DataProtect portal as an administrator.
- Login credentials to your VM hypervisor will be required in order to recover a VM.

## High-Level Steps

Follow the high-level steps below to implement Object Replication from a source bucket to a destination bucket in another region with Cohesity. These are detailed further in the sections below.

1. Sign up for notifications to be sent to your account email address.
2. Create a Wasabi "destination" bucket where the source bucket will be replicated to.
3. Configure an object replication job on the source bucket pointing to the destination bucket.
4. In the case of a disaster:
  - A second Cohesity DataProtect cluster will be required.
  - On this second cluster, a Cohesity external target pointing to the destination bucket may be created and a restore performed.

## Signing Up for Object Replication Notifications

Signing up for notifications will allow you to receive information about any object replication failures as well as when the initial replication has finished.

1. Log in to the [Wasabi Console](https://console.wasabisys.com/).
2. Navigate to **Settings**, then click **Notifications**. Next to Object Replication, enable email notifications. Enter your Multi-Factor Authentication (MFA) code, and click **Save Changes**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-03-24_at_7_48_48%E2%80%AFAM(2).png)

## Creating the Wasabi Destination Bucket

The destination bucket is the bucket that the source bucket will replicate to.

1. Navigate to **Buckets** and search for the source bucket. Select the bucket name.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-04-09_at_10_04_31 AM.png)
2. Note the name, region, Versioning, and Object Lock settings of the source bucket. In this example, we are using an “mt-cohesity-replication-source” source bucket in Wasabi's us-east-1 region that has Versioning and Object Lock disabled (Object Lock would appear next to Versioning if it was enabled).

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-04-09_at_10_04_57 AM.png)
3. Choose a region within the same continent for the destination bucket.

> This configuration example discusses the use of Wasabi's us-east-1 storage region for the source and us-west-2 for the destination. For a list of regions, see [Available Storage Regions](https://docs.wasabi.com/docs/where-is-my-data-stored-and-how-are-wasabis-storage-regions-secured?highlight=regions#available-storage-regions).
4. Navigate to Buckets, then click **Create Bucket**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-04-09_at_10_09_34 AM.png)
5. Follow the instructions in [Creating a Bucket](https://docs.wasabi.com/docs/working-with-buckets-and-objects#creating-a-bucket) to create a destination bucket. The Versioning and Object Lock settings must match those of the source bucket. In our example, we are creating a “mt-cohesity-replication-dest” bucket in the us-west-2 region.

## Creating an Object Replication Job

1. Navigate to **Buckets** and click the name of the SOURCE bucket.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-04-09_at_10_04_31 AM.png)
2. Click the Settings gear wheel on the right side of the screen.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-04-09_at_10_21_35 AM.png)
3. Click the **Object Replication** tab, then click **Create Replication Job**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-04-08_at_12_48_26 PM.png)
4. Select the Replication Type. For this example, we are selecting Replicate to a bucket within this account. Give the job a name, and click in the Destination Bucket text field to select the destination bucket. Click the checkbox next to Sync Deleted Objects. This allows Cohesity to control the lifecycle of the source bucket, and older files that Cohesity deletes from the source bucket will also be deleted from the destination bucket. Then click **Create**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-04-08_at_12_49_27 PM.png)
5. The objects in the source bucket will now begin to replicate to the destination. There is no ETA for completion as this depends on many factors, such as the number of objects, and so on. Since you signed up for Object Replication email notifications, you will receive an email when the initial replication is complete.

## Appendix A - In Case of a Disaster

In the case of a disaster that affects your source bucket, proceed with this section. The example below shows how to recover a Virtual Machine (VM) from your destination bucket.

> A second licensed Cohesity DataProtect cluster must be made available for the restoral.

1. On the second cluster, add your hypervisor as a Registered Source if it hasn not already been added. See [Register or Edit a Hypervisor Source](https://docs.cohesity.com/7_3_1/Web/UserGuide/Content/Dashboard/Protection/SourceHypervisorAdd.htm) for instructions.
2. On the second cluster, click **Infrastructure**, then click **External Targets**. Click **Add External Target**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-D23ZTNUM.png)
3. Configure the following for the destination target then scroll down.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-04-08_at_12_56_33 PM.png)
  - Select the radio button next to Archival.
  - Select S3Compatible from the drop-down Storage Type menu.
  - Select Regular from the Storage Class drop-down menu.
  - Enter your destination bucket name.
  - Enter your Wasabi access key.
  - Enter your Wasabi secret key.
  - Enter the endpoint associated with your destination bucket.
  - Select Storage Optimized.
  - Ensure the slider next to Secure Connection (HTTPS) is enabled.
  - Select AWS Signature Version 4.
  - Give the external target a name.
4. If Object Lock was enabled originally (on the source Wasabi bucket), enable Archive Object Lock here. Be sure to leave encryption disabled even if it was used on the original target. We tested with non-encrypted backups and encrypted backups with a manually managed key. We did not test with the Cohesity built-in KMS service. Click **Register**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-04-08_at_12_56_51 PM.png)
5. You will now see the registered external target.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-04-09 at 11.00.13 AM.png)
6. Click **Data Protection** then **Cloud Retrieve**. Click **Start Search**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-LNY1COCF.png)
7. Select the destination external target from the drop-down menu. Set the appropriate date range, and attach a manually managed key file if encryption was used originally. Click **Search**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-04-08_at_1_02_22 PM.png)
8. When the Status shows Success, click the checkbox next to the recovered protection group. Select the Storage Domain (we selected the Default Storage Domain) and click **Download**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-04-08_at_1_03_05 PM.png)
9. Click **OK**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-H7DY9NHU.png)
10. After the Protection Group Meta-Data and Snapshot both show Success, proceed to the next step.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-04-08_at_1_06_44 PM.png)
11. Click **Data Protection** > **Recoveries**. Click **Recover**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-URA71FB2.png)
12. Click **Virtual Machines**, then click **VMs**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-FA5FUQ18.png)
13. Enter an asterisk (wildcard) in the search field and hit enter. Select the VM(s) you wish to recover and click **Next: Recover Options**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-04-08_at_1_09_00 PM.png)
14. Configure the options appropriate for your restore. In the example below, we used a Registered Source we previously configured and a New Location. Scroll down.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-277JE1NH.png)
15. Continue configuring the options. We left the network as Unattached so as to avoid IP address conflicts with the original server. Click **Recover**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-04-08_at_1_11_18 PM.png)
16. Click **Start Recovery**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-SLOVFRHZ.png)
17. You will see the Status show Succeeded when the recovery is finished. You may have to refresh the page to update the results.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-04-08 at 2.42.10 PM.png)