--- title: "Migrate Veeam v12 SOBR From AWS S3 to Wasabi Using WCSM" slug: "migrate-veeam-v12-sobr-from-aws-s3-to-wasabi-using-wcsm" updated: 2026-10-13T18:14:41Z published: 2026-10-13T18:14:41Z canonical: "docs.wasabi.com/migrate-veeam-v12-sobr-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 SOBR From AWS S3 to Wasabi Using WCSM ### 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 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 Scale-Out Backup Repositories (SOBRs). Reference the articles listed below for **Direct to Object Storage** and **Backup Copy Jobs.** [How do I migrate Veeam v12 Backup Copy Job from AWS S3 to Wasabi using WCSM?](https://docs.wasabi.com/docs/migrate-veeam-v12-backup-copy-job-from-aws-s3-to-wasabi-using-wcsm) [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) To use the Veeam v12 Move capability that 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 downloading and uploading 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. These are detailed further in the sections below. 1. Backups reside initially only in the AWS S3 bucket. 2. The WCSM team performs an initial copy from AWS S3 to Wasabi. 3. The customer disables Veeam backup job(s) before the final sync. 4. The WCSM team performs a final sync. 5. The customer adds a Wasabi repository. 6. The customer does a test restore using a migrated backup. 7. 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 Disable the backup job(s) currently pointed to AWS S3. Navigate to the Home tab. Click **Jobs,** then select the job backing up to AWS S3. Click **Disable**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724421092133.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 is complete, proceed to the next section. ## Creating the Wasabi Repository 1. Navigate to the Backup Infrastructure tab. Click **Backup Repositories,** then **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 credentials, including the access key and secret key. 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** on the Summary screen. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717785131516.png) 18. Once the Status shows Success on the next screen, click **Close**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717785287698.png) ## **Modifying the Scale-Out Backup Repository** 1. Navigate to the Backup Infrastructure tab, expand the Scale-out Repositories, and select the existing SOBR. Click **Edit Scale-out Repository**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717793803170.png) 2. Click **Next**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717793980662.png) 3. On the Performance Tier screen, click **Next**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717794076682.png) 4. On the next screen, click **Next**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717794166715.png) 5. Navigate to **Extend scale-out backup repository capacity with object storage,** then click **Choose**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717794312892.png) 6. Select the previously created Wasabi Repo and uncheck the AWS S3 one. Click **OK**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717794423022.png) 7. On the Capacity Tier screen, click **Next**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717794520528.png) 8. On the pop-up window, click **OK**. This will NOT download your previous backups to the local server. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717794627835.png) 9. On the next screen, click **Apply**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717794709095.png) 10. On the Summary screen, click **Finish**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717794795122.png) 11. After the following screen has a status of Success, click **Close**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717794920837.png) ## **Verifying Restore Points are Available in Veeam and Performing Test Restore** 1. Navigate to the Home tab. Under Backups, click **Capacity Tier** and select a server that was previously backed up. You will see the number of restore points, and they will be listed in the Wasabi repo. In the following example, one restore point was migrated to Wasabi using WCSM. 2. Right-click on the server name. Click **Restore entire VM**. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717795448414.png) 3. Click **Point.** ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1717795650691.png) 4. Expand the backup job shown. 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-1724345726436.png) 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 the host 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 VM and click **Pool** to change the 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 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, then click Disconnect to avoid 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. Then click **Disconnect** to avoid working for the restored VM, which 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 the 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. ## Enable Existing Backup Job 1. Navigate to the Home tab. Click **Jobs** and select an existing backup job. Click **Disable** to enable the job (there is no Enable button). ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724446118771.png) 2. The job will now show as enabled. ![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/image-1724605697043.png)