Configuring Commvault with Wasabi using the Command Center
Commvault has been validated for use with Wasabi. Follow the steps below to configure Wasabi as a cloud storage target.
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.
Prerequisites
Commvault v11sp19 or later has been installed and configured.This article details the configuration of v11.34.
Commvault media agent has been installed and associated with Comcell server
An active Wasabi Cloud Storage account. .
Commvault recommends using Commvault Command Center web console for net new installs, while versions before sp17 will need to leverage a Java-based command center. For detail on the configuration using the Commcell Console, refer to Commvault With Wasabi. Please note that Commcell console cannot be used for versions FR30 and later.
Configuring Wasabi as a Cloud Storage Target
Log into the Commvault Command Center. Navigate to the Storage tab. Click Cloud.
Click Add.
Configure the following -
Type - Select “Wasabi Hot Cloud Storage” from the dropdown menu
Name -Provide a name for the cloud storage
MediaAgent - Select a Media-agent associated with Commcell
Server host - Provide the endpoint url of the Wasabi region where the bucket is located
Bucket - commserve-demo
Credentials - Click + to add your Wasabi credentials.
This configuration example discusses the use of Wasabi's us-east-2 storage region. To use other Wasabi storage regions, use the appropriate Wasabi service URL as described in Service URLs for Wasabi's Storage Regions.
In the Add Credential window, provide the following details and click Save.
Credential name - Provide a name for the credentials
Access key ID - Provide the Wasabi access key
Secret access key - Provide the Wasabi secret access key
Select the added Wasabi credential and provide a bucket name. Enable deduplication and add a location for the Deduplication DB location. Click Save.
.png)
The Cloud tab displays the newly added Wasabi storage location.
Backing up a Virtual Machine
Navigate to Manage —> Plans.
Click Create Plan and select the desired plan type. In this example, we will be configuring a Server backup.
In the Create Server Backup Plan wizard, select Create a new plan. Provide a plan name and click Next.
.png)
In the Backup Destinations tab, click Add Copy.
Provide a the following details and click Save.
Name - Provide a name for the destination
Storage - Select the Wasabi cloud storage location created in the earlier section
Retention rules - Select the desired Retention period
Click Next on the Backup Destinations tab.
In the Recovery Point Objective tab, configure the desired settings and click Next.
In the Options tab, select the desired options and click Submit.
The virtual machines associated with this plan will be backed up to the Wasabi storage location.
Configuring Immutable Backups Using Object Lock
You can configure immutable backups by enabling WORM functionality on the cloud storage server. Commvault supports object lock in Compliance mode.
Note: When WORM is enabled, the cloud storage utilization will be increased due to the deduplication databases used by Commvault as a part of its backup process. This applies to all cloud storage providers. For more information, please refer to Commvault documentation at https://documentation.commvault.com/2023e/essential/configuring_worm_storage_lock_01.html.
Follow the steps below to make your backups immutable.
Create an object lock enabled Wasabi bucket. For more information, refer to Object Lock: Enabling.
Configure the object lock enabled bucket as a cloud storage server location following the steps in section Configuring Wasabi as a Cloud Storage target.
Click on the cloud storage location and navigate to Configuration. Under the WORM section, enable WORM Storage Lock and configure the desired retention period.
Assign this storage server as the destination in the appropriate backup plan.
All the backups will be written to Wasabi in WORM mode following the retention period set in the backup plan.