Configuring Commvault Cloud With Wasabi

  • Updated on Sep 17, 2025
  • Published on Sep 17, 2025
  • 2 minute(s) read
Prev Next

Commvault Cloud (formerly Metallic) has been validated for use with Wasabi. Follow the steps outlined below to use Commvault Cloud with Wasabi.

Prerequisites

Configuring Wasabi as a Cloud Storage Target

  1. Log in to the Commvault Cloud account.

  1. Navigate to Storage and click Cloud.

  1. Click Add to add a new storage target.

  1. In the Add Cloud Storage window, expand the Type drop-down menu. Search for Wasabi and select Wasabi Hot Cloud Storage.

  1. Provide the following details:

    1. Name — Provide a name for the cloud storage.

    2. Service Host — Provide the endpoint URL of the region where the bucket is located.

    3. Media agent — Select the desired media agent.

      Click + sign under Credentials to add the credentials for your Wasabi account.

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.

  1. In the Add Credential dialog box, 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

  1. Select the added Wasabi credential and provide a bucket name. Enable deduplication and add a location for the Deduplication DB location. Click Save.

  1. The Cloud tab displays the newly added Wasabi storage location.

Creating a Backup Plan

  1. Navigate to Manage and click Plans.

  1. Click Create Plan and select Backup.

  1. In the Create Backup Plan wizard, select Create a new plan and provide a name in the Plan name field. Click Next.

  1. In the Storage Policy tab, we will configure the storage targets. Click Add Copy.

  1. Wasabi can be configured as a Primary storage or as a target for a secondary copy of the backup data.

5.1. Configuring Wasabi as a Primary Copy

5.1.1.  In the Add copy dialog box, provide the following details and click Save.

  • Name — Provide a name for the destination

  • Storage — Select the Wasabi storage location configured earlier

  • Retention period — Configure the desired retention period

5.1.2. Click Next to configure the Schedule Policy.

5.2. Configuring Wasabi as a Secondary Copy

5.2.1.  To configure Wasabi as a secondary storage target, configure the desired storage as primary storage and click Save.

5.2.2. Click Add Copy to add Wasabi as a secondary copy.

5.2.3. Provide the required information and click Save.

5.2.4. Click Next to configure the Schedule Policy.

  1. Configure the desired schedule policy 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 Cloud supports object lock in Compliance mode.

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/saas/worm_storage_and_retention_for_cloud_storage.html

Follow the steps below to make your backups immutable.

  1. Create an object lock enabled Wasabi bucket. For more information, refer to Object Lock: Enabling.

  2. Configure the object lock enabled bucket as a cloud storage server location following the steps in section, Configuring Wasabi as Cloud Storage target.

  3. Click on the cloud storage location and navigate to Configuration. Under the WORM section, enable WORM Storage Lock and configure the desired retention period.

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