CommVault Backup & Recovery software can be easily configured to use S3 compatible object storage such as DataCore Swarm for backups. For additional safeguards against ransomware and accidental deletions, backups can be object locked using their WORM option.

Prerequisites

• CommVault 11.36 or higher

• DataCore Swarm object storage v17 or above

• DataCore Swarm Gateway v8.2.1 or above

• CommVault requires TLS connections to object storage. See our KB article https://caringo.atlassian.net/wiki/spaces/KB/pages/36930810/Configuring+haproxy+SSL+offloading+with+a+Self+Signed+Certificate+on+Content+Gateway)

• S3 Access Key and Secret Key for the bucket. CommVault will create the needed bucket if it doesn’t exist.

Setting up an S3 compatible object store for CommVault

Swarm Content Portal

To generate an access token, navigate to the Swarm storage domain and select settings, then tokens sub-menu

Open

On the domain settings view, press the “+Add” button to generate a new S3 token

Copy the Token ID and Secret Key to the clipboard for later pasting into the Commvault form.

Commvault Console

Setup credentials for Cloud Account

Go to the Manage -> Security -> Credentials Vault in the Web UI

Open

then click Add

For Account Type, choose Cloud Account, for Cloud vendor type choose S3 Compatible Storage.

Enter the Credential name, Access Key ID, and Secret Access Key. The Access Key ID is the Swarm Token ID generated in the earlier step.

Open

Click the Save button to add the credentials.

That’s it. At this point you can use the DataCore Swarm as an s3 object storage destination for Commvault backups.

You can find this information on the official CommVault documentation here:

https://documentation.commvault.com/v11/essential/configuring_cloud_storage.html

Example steps to setup a new backup job

Navigate to Manage → server groups → Media Agents → Configurations → Settings

Add the configuration parameter called “Cloud Storage Server Certificate Identity Check” and set it to “VERIFY SELF-SIGNED CERTIFICATE (NOT WITH ROOT CA)

Example:

Open

Navigate to Storage → Cloud and press Add

Open

Create a Storage Policy ( now called a new Plan ) by navigating to Manage → Plan and press Create Plan → server backup

Open

Define the backup destination

Open

Define the RPO

Open

Once completed it will look like this

Open

Now we need to enable WORM if you want to use the new immutability features.

This is now done via the UI natively; you no longer need a workflow for this functionality.

Enable Policy Versioning for the Swarm Cluster first

1. In the Swarm UI (not the Content Portal), select Settings from the side navigation bar.

2. Select “allowed” corresponding to policy.versioning then click Save.

   Open

   

3. Then you need to enable versioning at the domain level as well. Navigate to the domain properties and unclick “Apply Evaluated Policy” then toggle Content Versioning to “Enabled”

   Open

   

Navigate to Storage → Cloud → Plan → Configuration Tab and edit the Worm Section.

Open

This is what enabling WORM storage lock looks like:

Open

Choose what you want to protect, in my example test environment I selected VM’s in a specific resource group on a VMware vCenter 7.0

Open

Once you have added your source you can start backing any VM assigned to your VM Group.

Don't forget to assign the storage plan to the VM Group.

Example backup job , as seen in the gateway audit log

Tuning parameters

Navigate to Manage -> server groups -> media agents

Add a setting called “configure number of upload threads”

Open