---
title: "Migrate Veeam v12 Backup Copy Job From AWS S3 to Wasabi Using WCSM"
slug: "migrate-veeam-v12-backup-copy-job-from-aws-s3-to-wasabi-using-wcsm"
updated: 2026-08-22T16:40:53Z
published: 2026-08-22T16:40:53Z
canonical: "docs.wasabi.com/migrate-veeam-v12-backup-copy-job-from-aws-s3-to-wasabi-using-wcsm"
---

> ## 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.

# Migrate Veeam v12 Backup Copy Job From AWS S3 to Wasabi Using WCSM

Wasabi is a member of Veeam's cloud partner ecosystem. We have worked closely with Veeam to deliver 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 migrate a non-immutable Veeam v12 repository from AWS S3 to Wasabi using Wasabi Cloud Sync Manager (WCSM). WCSM is a paid managed service that performs cloud-to-cloud migration without requiring the customer to download and re-upload backups.

This article covers only Backup Copy Jobs. Reference the articles listed below for **Direct to Object Storage** and **Scale-Out Backup Repositories (SOBRs).**

[How do I migrate Veeam v12 Direct to Object Storage from AWS S3 to Wasabi using WCSM?](https://docs.wasabi.com/docs/migrate-veeam-v12-direct-to-object-storage-from-aws-s3-to-wasabi-using-wcsm)

[How do I migrate Veeam v12 SOBR from AWS S3 to Wasabi using WCSM?](https://docs.wasabi.com/docs/migrate-veeam-v12-sobr-from-aws-s3-to-wasabi-using-wcsm)

To use the Veeam v12 Move capability, which also works with immutable backups, review [Migrate Veeam Backups From AWS S3 to Wasabi on Veeam v12](https://docs.wasabi.com/docs/how-do-i-migrate-veeam-backups-from-aws-s3-to-wasabi-on-veeam-v12). Using Veeam Move requires you to download and upload your backups.

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 or higher, installed and licensed. This solution was tested with v12.2.
- Active AWS S3 cloud storage account.
- An AWS S3 non-Object-Locked (non-immutable) bucket with access keys.
- An active VBR repository.
- Active Wasabi Cloud Storage account.
- A Wasabi non-Object-Locked (non-immutable) bucket created with access keys.

## **High-Level Migration Steps**

Follow the high-level steps below to migrate from AWS S3 to Wasabi.

Backup copies reside initially only in the AWS S3 bucket.

1. The WCSM team performs an initial copy from AWS S3 to Wasabi.
2. The customer disables Veeam backup activities (backup jobs) before the final sync.
3. The WCSM team performs a final sync.
4. The customer adds a Wasabi repository.
5. The customer does a test restore using a migrated backup.
6. Finally, the customer points the backup jobs to Wasabi and enables the jobs.

## **Wasabi Cloud Sync Manager Configuration**

Wasabi Cloud Sync Manager (WCSM) is a paid, managed migration service. Refer to [Getting Started With Wasabi Cloud Sync Manager](https://docs.wasabi.com/docs/wasabi-cloud-sync-manager-wcsm-getting-started) for more information.

1. Request a WCSM Account by either completing the [WCSM Questionnaire](https://info.wasabi.com/wcsm-questionnaire) or reaching out to your Wasabi Sales contact.
2. Upon approval and notification of account creation, you will be able to log in to the [WCSM Portal](https://wcsm.wasabisys.com/). Follow the steps outlined in [2—Entering Credentials for Cloud Migration](https://docs.wasabi.com/docs/entering-credentials-for-cloud-migration).
3. This will require you to enter your AWS S3 storage account credentials and Wasabi account credentials, along with your bucket information.

**After the data has been initially copied to Wasabi, proceed with the next sections.**

## Disable Backup Activities Before Final Sync is Performed

1. Navigate to the Home tab. Click **Backup** under Jobs and select the primary backup job. Click **Disable**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1718656829634.png)
2. Navigate to the Home tab, click **Backup Copy** under Jobs, select the **Backup Copy** job you wish to disable, then click **Disable**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1718721402330.png)

## Final WCSM sync will be performed on the agreed-upon date

The final WCSM data sync will occur on the date agreed upon by the customer and the Wasabi WCSM team. This will sync any new backups performed to AWS S3 and any Veeam backup cleanup activities/deletions from AWS S3 to ensure the same data resides in Wasabi. For a definition of the WCSM sync operation, review [Migration Types](https://docs.wasabi.com/docs/wasabi-cloud-sync-manager-wcsm#migration-types).

**After the final sync has been performed, proceed to the next section.**

## Creating the Wasabi Repository

1. Navigate to the Backup Infrastructure tab. Click **Backup Repositories,** then click **Add Repository**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717780067590.png)
2. Click **Object Storage**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717780180292.png)
3. Click **Additional Providers**. Note: this step is new for VBR version 12.2. Previously, Wasabi was located directly under **Object Storage**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724967586267.png)
4. Click **Wasabi Cloud Storage**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724967647237.png)
5. Give the repository a Name. Click **Next**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717780364979.png)
6. Specify the Wasabi region that your Wasabi bucket is located in. Click **Add to add your Wasabi account access and secret key** credentials.

This configuration example uses Wasabi’s us-east-1 storage region. Use the region where your bucket is located. 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).

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717780428337.png)
7. Enter your Wasabi Access Key and Secret Key. Click **OK**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717780999129.png)
8. Click **Next.**

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717781139522.png)
9. Under **Bucket,** click **Browse**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717781263733.png)
10. Select the Wasabi bucket that data was migrated to and click **OK**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717781638759.png)
11. Under **Folder**, click **Browse.**

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717781474708.png)
12. Select the existing top-level folder in the bucket and click **OK**. Do NOT create a new folder.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717781756155.png)
13. Click **Next**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717784420300.png)
14. On the next screen, click **Next**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717784536429.png)
15. Click the two checkboxes to search the repository for existing backups and automatically import them. Click **Apply**. Note that this will NOT download your previous backups to your local server.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717784757548.png)
16. Click **Next**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717784959749.png)
17. Click **Finish.**

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717785131516.png)
18. Once the Status shows Success, click **Close**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717785287698.png)

## **Verify Restore Points are Available in Veeam and Perform Test Restore**

1. Navigate to the Home tab, click on **Object Storage (Imported)** under Backups, and select a server that was backed up previously. You will see the number of restore points, and they will be listed in the Wasabi repo. In the following example, a single restore point was migrated to Wasabi using WCSM.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1725626895857.png)
2. Right-click on the server name. Click **Restore entire VM**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1725626814215.png)
3. Click **Point.**

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717795650691.png)
4. Expand the backup copy job shown for the Wasabi repository. You will see the available restore points. In the following screen, there is one restore point. Select a restore point and click **OK**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724966927252.png)

If you do not see the repository names for the Backup Copy Jobs, refer to the [Appendix A](/v1/docs/draft-migrate-veeam-v12-backup-copy-job-from-aws-s3-to-wasabi-using-wcsm-1#appendix-a).
5. On the Virtual Machines screen, click **Next**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724259065047.png)
6. Select Restore to a new location, or with different settings and click **Next**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724259999484.png)
7. Optionally, click **Host** to change where the VM is restored to. Click **Next**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724260286619.png)
8. Optionally, select the Virtual Machine and click **Resource** **Pool.** Click **Next**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724260575902.png)
9. Optionally, change the **Datastore**. Click **Next.**

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724260820443.png)
10. Select the VM Folder and click **Name**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724260982522.png)
11. Change the VM name to something different from the original, then click **OK**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724261154499.png)
12. Click **Next.![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724261333181.png)**
13. Select the network under the VM and click **Disconnect** to avoid any IP address conflicts on the network. Repeat for any other networks.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724261790173.png)
14. Click **Disconnect** to avoid work for the restored VM has been disconnected.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724335720319.png)
15. Optionally enter a restore reason. Click **Next**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724335814522.png)
16. Check the Power on target VM after restoring checkbox and click **Finish.![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724336010996.png)**
17. Verify the restore job completes successfully. Click **Close**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724336340514.png)
18. Verify that you can log in to the restored VM via its console, such as VMware’s or Microsoft’s hypervisor console. After successfully logging in, optionally delete the restored VM. Do NOT delete the original VM.

## Modifying Existing Backup Copy Job

1. Navigate to the Home tab. Under Jobs, click **Backup Copy** and select the backup copy job in which to modify. Click **Edit**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1718657063742.png)
2. On the next screen, click **Next**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1718657213026.png)
3. On the Object screen, click **Next**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1718657314512.png)
4. In the backup repository drop-down menu, select the previously created Wasabi backup repository, then click **Next**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1718657488167.png)
5. In the pop-up window, click **Create New**. Do NOT click Move Existing.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1718657611566.png)
6. On the next pop-up window, click **Yes**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1718658948120.png)
7. On the next screen, click **Next**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1718659029382.png)
8. Click **Apply**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1718659122770.png)
9. Click the checkbox for **Enable the job when I click Finish**. Click **Finish**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1718659243039.png)
10. Navigate to the Home tab. Under Jobs, click Backup and select the previously disabled primary backup job. Click **Disable** to re-enable the job.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1718659707573.png)
11. New backups from backup copy jobs that are subsequently run will appear under Object Storage (Copy).

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1718660072511.png)

## Appendix A

If you do not see the repository names when attempting a test restore, proceed with this section.

1. If the restore point screen looks like the example below and lists no repositories for the Backup Copy Jobs, click **Cancel**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1725042985724.png)
2. Navigate to Home, then under Backups, click on **Object Storage (Copy)**. Select the Backup Copy Job going to AWS S3, press and hold the ctrl key, right-click, and select **Remove from configuration**.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1725049514695.png)
3. When the Removal screen shows Success, click **Close**.
4. Return to the [test restore section](https://docs.wasabi.com/docs/migrate-veeam-v12-backup-copy-job-from-aws-s3-to-wasabi-using-wcsm#verify-restore-points-are-available-in-veeam-and-perform-test-restore) above.
5. After the test restore, if you wish to restore your backups in AWS S3 to the Veeam configuration, go to Backup Infrastructure, Backup Repositories, select the AWS S3 repo, right-click, and select Rescan. Your previous backups will appear in Object Storage (Imported).