Migrate Veeam v12 SOBR From AWS S3 to Wasabi Using WCSM

How do I 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.

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?

How do I 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. Using Veeam Move requires downloading and uploading your backups.

Prerequisites

• 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 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 for more information.

1. Request a WCSM Account by either completing the WCSM Questionnaire or reaching out to your Wasabi Sales contact.
2. Upon approval and notification of account creation, you will be able to log into the WCSM Portal. Follow the steps outlined in 2—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.

Disable Backup Activities Before Final Sync is Performed

Disable the backup job(s) currently pointed to AWS S3.

1.  Navigate to the Home tab.  Click Jobs, then select the job backing up to AWS S3.  Click Disable.

Final WCSM sync will be performed on 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.

Creating the Wasabi Repository

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

   

2. Click Object Storage.

   

3. Click Additional Providers.  Note this step is new for VBR version 12.2.  Previously Wasabi was located directly under Object Storage.
   
4. Click Wasabi Cloud Storage.

   

5. Give the repository a Name. Click Next.

   

6. Specify the Wasabi region that your Wasabi bucket is located in. Click Add... to add your Wasabi access and secret key account credentials.
   This configuration example discusses the use of Wasabi's us-east-1 storage region. Use the region your bucket is located in.  For a list of regions, see Available Storage Regions.

   

7. Enter your Wasabi Access Key and Secret Key. Click OK.

   

8. Click Next.

   

9. Under Bucket, click Browse.

   

10. Select the Wasabi bucket that data was migrated to and click OK.

    

11. Under Folder, click Browse.

    

12. Select the existing top-level folder in the bucket and click OK. Do NOT create a new folder.

    

13. Click Next.

    

14. On the next screen, click Next.

    

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

    

16. Click Next.

    

17. Click Finish on the Summary screen.

    

18. Once the Status shows "Success" on the next screen, click Close.

    

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

   

2. Click Next.

   

3. On the Performance Tier screen, click Next.

   

4. On the next screen, click Next.

   

5. Under "Extend scale-out backup repository capacity with object storage", click Choose.

   

6. Select the previously created Wasabi Repo and uncheck the AWS S3 one. Click OK.

   

7. On the Capacity Tier screen, click Next.

   

8. On the pop-up window, click OK.  This will NOT download your previous backups to the local server.

   

9. On the next screen, click Apply. 

   

10. On the Summary screen, click Finish.

    

11. After the following screen has a status of Success, click Close.

    

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 it will show that they are in the Wasabi repo.  In the following example, there was one restore point that was migrated to Wasabi using WCSM.
2. Right-click on server name. Click Restore entire VM. 

   

3. Click Point....

   

4. Expand the backup job shown. You will see the available restore points. In the case shown in the following screen, there is one restore point.  Select a restore point and click OK. 
5.  On the Virtual Machines screen, click Next.
6.  Select "Restore to a new location, or with different settings" and click Next.
7.  Optionally click Host to change the host the VM is restored to.  Click Next.
8.  Optionally select the VM and click Pool to change the Resource Pool.  Click Next.
9.  Optionally change the Datastore.  Click Next.
10.  Select the VM and click Name.
11.  Change the name of the VM to be different from the original VM and click OK.
12.  Click Next.
13. Select the network under the VM and click Disconnect to avoid any IP address conflicts on the network. Repeat for any other networks.
14. Click Next after the network for the restored VM has been disconnected.
15. Optionally enter a restore reason.  Click Next.
16. Check the "Power on target VM after restoring" checkbox and click Finish.
17. Verify the restore job completes successfully.  Click Close.
18. Verify you can login to the restored VM on the VM's console, such as in 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).
   
2.  The job will now show that it is enabled.