This article describes the procedure to migrate a non-immutable Commvault backup from hyperscalers and other third party S3 compatible cloud storage providers to Wasabi using the Wasabi Cloud Sync Manager (WCSM) platform. WCSM is a managed service that performs cloud-to-cloud migration, eliminating the need for customers to download and re-upload backups.
This article documents the migration from AWS S3 to Wasabi. Please note that the procedure applies to all third-party cloud object storages
The data restoration process is handled by your specific backup software application. As there are many potential variables that will affect your unique environment, it is strongly recommended 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
Commvault v11sp19 or later installed and configured
Commvault media agent has been installed and associated with Comcell server
An active Wasabi storage account
WCSM service purchase
High-level Migration Steps
Follow the high-level steps below to migrate from third party clouds to Wasabi. These are detailed further in the sections below.
Backups reside initially only in the AWS S3 bucket.
The WCSM team performs an initial copy from AWS S3 to Wasabi.
The customer disables the backup location for future backups before the final sync.
The WCSM team performs a final migration.
The customer works with Commvault support to move the existing cloud storage mount path to Wasabi as detailed here.
Confirm the storage location has changed.
Finally, the customer enables the backup location for future backups.
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.
Request a WCSM Account by either completing the WCSM Questionnaire or reaching out to your Wasabi Sales contact.
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.
This will require you to enter your third party cloud storage account credentials and Wasabi account credentials along with your bucket information.
Disabling the backup location before final sync is performed
Before the WCSM team performs a final sync, disable the backup location for future backups.
Log in to the Commvault Command Center and navigate to the AWS cloud storage target. Click Backup Locations.

In the Bucket section, select the S3 bucket.
.png)
Under the Configuration section, move the slider to Disable backup location for future backups.
.png)
Final WCSM migration will be performed on agreed upon date
The final incremental data migration will occur on the date agreed upon by the customer and the Wasabi WCSM operations team. This will ensure any new Commvault backups or updates to an existing backup in AWS S3, since the last migration are migrated over.
After the final sync has been performed, proceed to the next section.
Work with Commvault support to move the mount path
Once the final WCSM migration has been performed, the customer works with Commvault support to move the AWS cloud storage mount path to Wasabi.
Please inform the Commvault support that you need the authorization code for Qscript from the Commvault Backend team in order to move cloud storage mount paths and provide this article as reference.
The Commvault support team will work with the customer to execute the qscript and move the storage library to Wasabi.
Confirm the storage location has changed
Next step is to login in to the Command Center and confirm the cloud storage location now points to the Wasabi bucket.
Navigate to Backup locations tab under the cloud storage and click on the bucket under the Bucket section.
.png)
The cloud access path will now display the Wasabi bucket and the region URL of the bucket.

Enabling the backup location
Enable the Wasabi storage location for future backups. Log in to the CommvaultCommand Center and disable the setting, as shown below.

This storage location is now enabled for future backups and all the future backups will now be written to the Wasabi bucket.