Commvault Web Console With Wasabi
    • 04 Jul 2024
    • 2 Minutes to read
    • PDF

    Commvault Web Console With Wasabi

    • PDF

    Article summary

    How do I use Commvault Web Console with Wasabi?

    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 has been installed and configured.

    • Commvault media agent has been installed and associated with Comcell server

    • Active Wasabi Cloud Storage account. .

    Commvault recommends using 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 Command Center, refer to Commvault With Wasabi.

    Configuring Wasabi as a Cloud Storage Target

    1. Log into the Commvault Command Center through the web console.

    mceclip0.png
    1. Navigate to the Storage tab. Click Cloud.

    mceclip1.png
    1. Click Add.

    mceclip2.png
    1. Configure the following and click Save.

      • Name: Wasabi Technologies

      • Type: Wasabi Hot Cloud Storage

      • MediaAgent: Media-agent associated with Commcell

      • Server Host: s3.wasabisys.com

      • Bucket: commvault-backup

      • Credentials -> Name: Wasabi Access/Secret S3 keys

      • (Optional) Enable deduplication

    This configuration example discusses the use of Wasabi's us-east-1 storage region. To use other Wasabi storage regions, use the appropriate Wasabi service URL as described in Service URLs for Wasabi's Storage Regions.

    A pre-configured Wasabi bucket is required. The example below uses the "commvault-backup" bucket.

    mceclip3.png

    Backing up a Virtual Machine

    1. Navigate to Protect -> Virtualization & Hypervisors.

      mceclip0.png
    2. Click Add Hypervisor.

      mceclip1.png
    3. Select the Hypervisor to be backed up. In the example below, a VMware ESXi server instance is being backed up. Click Save.

      mceclip2.png
    4. Click Add VM Group.

      mceclip3.png
    5. Provide a Name for the group. Select the VM to be backed up and click OK.

      mceclip4.png
    6. Click Backup.

      mceclip5.png
    7. Select the Backup Level. Click Save.

      mceclip6.png

      The backup job will commence.

      mceclip8.png

      Summary of a completed job:

      mceclip9.png
    8. Confirm the backup using the Wasabi Console.

      mceclip10.png

    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.

    To enable the WORM functionality in Commvault, you will need to use the Commvault Commcell Console. This option cannot be enabled using the Commvault Command Console.

    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. Add a new storage target using the bucket created above (Steps 1-3).

    3. Log into the Commvault Commcell Console. In the CommCell Browser, navigate to Storage Resources -> Libraries. Right-click on the required library and click Properties.

      Picture1.png
    4. In the General tab, select the checkbox for WORM Copy. Click OK.

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