Documentation Index

Fetch the complete documentation index at: https://docs.wasabi.com/llms.txt

Use this file to discover all available pages before exploring further.

Configuring Commvault With Wasabi Using the Command Center

Prev Next

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.

Requirements

  • Commvault v11sp19 (or later) has been installed and configured. This article details the configuration of v11.42.100.

  • 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 details on the configuration using the Commcell Console, refer to Configuring Commvault With Wasabi Using the Commcell Console. Note that Commcell console cannot be used for versions FR30 and later.

Configuring Wasabi as a Cloud Storage Target

  1. Log in to the Commvault Command Center.

  2. Navigate to the Storage tab.

  3. Click Cloud.

  4. Click Add.

  5. Configure the following.

    • Type—Select Wasabi Hot Cloud Storage from the drop-down menu.

    • Name—Provide a name for the cloud storage.

    • MediaAgent—Select a Media-agent associated with Commcell.

    • Server host—Provide the endpoint URL for 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.

  6. In the Add Credential window, provide the following details. 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.

  7. Select the added Wasabi credential and provide a bucket name.

  8. Enable deduplication and add a location for the Deduplication DB location.

  9. Click Save.

    The Cloud tab displays the newly added Wasabi storage location.

Backing Up a Virtual Machine

  1. Navigate to Manage.

  2. Select Plans.

  3. Click Create Plan and select the desired plan type. In this example, we will be configuring a Backup.

  4. In the Create Server Backup Plan wizard, input the following.

    • Plan Name—Provide a name for the plan

    • Configure backups—Click the checkbox to enable Configure backups.

    • Storage—Select the Wasabi cloud storage location created in the previous section.

    • Frequency—Choose how often the backup should occur.

    • Retention rules—Select the retention period.

    Click Save.

    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.

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, refer Commvault’s documentation: Configuring Storage Lock.

As of version 11.44 of Commvault, a new feature has been added to improve storage reclamation efficiency, you can enable WORM Storage Optimization, which uses micro-pruning to reclaim eligible data at the job level while maintaining WORM immutability protections.

  1. Log in to your Commvault Console Dashboard.

  2. Search “Commcell” in the search bar at the top of the dashboard.

  3. Click Manage > Commcell.

  4. In the Settings panel, click Add.

  5. Input the following values.

    • Name—EnableOptimizedWORMStorageLock

    • Type—Integer

    • Path—CommServDB.GxGlobalParam

    • Value—1 (or 0 to disable)

    • Click Save.

  6. Commvault Optimized WORM Storage Lock will be enabled for newly created storage locations.

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

  8. Configure the object lock enabled bucket as a cloud storage server location by following the steps in Configuring Wasabi as a Cloud Storage Target.

  9. Select the cloud storage location and navigate to Configuration.

  10. Under the Immutability section, enable Storage Lock and configure the desired retention period.

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

Restoring a Backup

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.

  1. Navigate to the VM and select the desired date from the calendar in the Recovery points section.

  2. Click Restore.

  3. Select the desired Restore type (in this example, we choose Full virtual machine).

  4. In the Destination tab, select the Type and Access node.

  5. Click Next.

  6. In the Virtual Machines tab, click Next.

  7. In the Restore Options tab, configure the desired options.

  8. Click Next.

  9. In the Summary tab, review the settings. Click Submit to start the restore job.