---
title: "Wasabi Object Replication With Veeam v12 Backup Copy Job"
slug: "how-do-i-use-wasabi-object-replication-with-veeam-v12-backup-copy-job"
updated: 2026-06-08T17:37:59Z
published: 2026-06-08T17:37:59Z
canonical: "docs.wasabi.com/how-do-i-use-wasabi-object-replication-with-veeam-v12-backup-copy-job"
---
> ## 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 Veeam v12 Backup Copy Job
###
Wasabi is a member of Veeam's cloud partner ecosystem. We have worked with Veeam closely to offer both a seamless implementation and a smooth transition to cloud storage. For more information on how Veeam works with Wasabi, refer to [Veeam and Wasabi Solution Brief](https://wasabi.com/partner/integrations/veeam).
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.
This article covers only **Backup Copy Jobs**. Reference the articles listed in the menu to the left for **Scale-Out Backup Repositories (SOBRs)** and **Direct to Object Storage****.**
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
- Veeam Backup and Replication (VBR) v12 installed and licensed. This solution was tested with v12.3.
- Active Wasabi Cloud Storage account.
- Active Veeam repository pointing to a Wasabi bucket.
- Existing backups reside in a Wasabi Object Locked (immutable) or non-Object-Locked (non-immutable) "source" bucket.
## 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 Veeam Backup & Replication. 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 Veeam repository pointing to the destination bucket may be created and the backup copy job(s) repointed to this new repository.
## Sign Up for Object Replication Notifications
Signing up for notifications will allow you to receive information about any object replication failures.
1. Login to the [Wasabi Console](https://console.wasabisys.com/).
2. Navigate to Settings, then click on **Notifications**.
3. Enable email notifications.
## Create the Wasabi Destination Bucket
The destination bucket is the bucket that the source bucket will replicate to.
1. Navigate to Buckets and click the name of the source bucket. 
2. Note the name and settings of the source bucket, including Object Lock settings. In this example we are using a source bucket in Wasabi's us-east-1 region with Object Lock (and Versioning) enabled.Enabling bucket versioning only is not a proper configuration for immutable Veeam backups and can cause problems. If you are simply using regular Veeam backups with Wasabi buckets, bucket versioning is not required.
3. Choose the 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-1 for the destination. For a list of regions, see [Available Storage Regions](https://docs.wasabi.com/docs/en/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**.
5. Enter the destination bucket name, select the region for the bucket, and click **Next**.
6. Set Versioning and Object Lock to match the source bucket settings. These settings MUST match the source bucket. In this example we are enabling Versioning and Object Lock. Click **Next**. 
7. Enable bucket logging if desired and click **Next**.
8. Leave Object Replication disabled (default setting). The replication will be configured later on the source bucket. Click **Next**.
9. Click **Next** on the Tags screen.
10. Review the bucket's settings on the next screen and click **Create Bucket**.
## Create an Object Replication Job
1. Navigate to Buckets and click the name of the SOURCE bucket.
2. Click the Settings gear wheel on the right side of the screen.
3. Click the **Object Replication** tab, then click **Create Replication Job**.
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.
5. Click on the name of the destination bucket from the list, then click **Select**.
6. Click the checkbox next to Sync Deleted Objects. This allows Veeam to control the backup lifecycle of the source bucket, and older backups that Veeam deletes from the source bucket will also be deleted from the destination bucket. Then click **Create**.
7. 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, frequency of backups, etc.
## Appendix A - In case of a Disaster
In the case of a disaster that affects your source bucket, proceed with this section.
1. Create a Veeam repository pointing to your destination bucket. Follow the steps outlined in [Create a Backup Job in Veeam v12 to Backup to Wasabi](https://docs.wasabi.com/docs/en/create-a-backup-job-in-veeam-v12-to-backup-to-wasabi#creating-wasabi-as-an-object-repository)for creating Wasabi as an object repository.
1. On the Bucket screen, select the existing top-level folder in the bucket. Do NOT create a new folder. Use the same immutability settings as your source repository.
2. On the Review screen, click the two checkboxes to search the repository for existing backups and import them automatically. Click **Apply**. Note that this will NOT download your previous backups to your local server.
2. Navigate to the Home tab. Click **Backup**under Jobs and select the primary backup job. Click **Disable**.
3. Click on **Backup Copy** under Jobs, select the backup copy job you wish to disable, then click **Disable**.
4. Click **Edit**.
5. On the next screen, click **Next**.
6. On the Objects screen, click **Next.**
7. In the backup repository drop-down menu, select the Wasabi destination repository previously created and click **Next**.
8. On the popup window, click **Create New**. Do NOT click Move Existing.
9. On the next popup window, click **Yes.**
10. On the next screen, click **Next.**
11. Click **Apply.**
12. Click the checkbox for Enable the job when I click Finish. Click **Finish.**
13. Navigate to the Home tab. Under Jobs, click Backup and select the previously disabled primary backup job. Click **Disable**to re-enable the job (there is no Enable button).
14. New backups from backup copy jobs that are subsequently run will appear under Object Storage (Copy), and replicated backups appear under **Object Storage (Imported). **