How do I use Commvault Web Console with Wasabi?

Commvault has been validated for use with Wasabi. Follow the steps outlined below to configure Wasabi as a cloud storage target.

Please NoteThe data restoration process is handled by your specific backup software application. As there are many potential variables that will affect your unique environment, it is strongly recommended 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.

Table of Contents

  1. Pre-requisites
  2. Configuring Wasabi as a cloud storage target
  3. Backup a Virtual Machine
  4. Configuring immutable backups using object lock

Pre-requisites

  • Commvault v11sp19 has been installed and configured 
  • Commvault media agent has been installed and associated with Comcell server
  • Active Wasabi Cloud Storage account. 

NOTE: Commvault recommends using web console for net new installs, while versions before sp17  will need to leverage Java-based command center. Configuration via the Command Center can be found here.

 

Configuring Wasabi as a cloud storage target

1. Log in to the Commvault Command Center via web console:

mceclip0.png

2. Navigate to Storage and click on Cloud:

mceclip1.png

3. Click "Add" 

mceclip2.png

4. 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
  • Optionally enable deduplication

Note: that this config example discusses the use of Wasabi's us-east-1 storage region. To use other Wasabi storage regions, please use the appropriate Wasabi service URL as described in this article

Note: a pre-configured Wasabi bucket is required. The below example uses "commvault-backup" bucket

mceclip3.png

 

 

Backup a Virtual Machine:

5. Navigate to "Protect" -> "Virtualization" & "Hypervisors"

mceclip0.png

6. Click "Add Hypervisor" 

mceclip1.png

7. Choose the Hypervisor which would be backed up, the example below a VMware ESXi server instance is being backed up. Click "Save"

mceclip2.png

8. Click "Add VM Group"

mceclip3.png

9. Provide a name for the group, choose the VM to be backed up and click "OK"

mceclip4.png

10. Click "Backup"

mceclip5.png

11. Choose "Backup Level" and click "Save"

mceclip6.png

12. Backup job will commence:

mceclip8.png

13. Summary of a completed job:

mceclip9.png

14. Confirm backup via 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. 

Note: 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 outlined below to make your backups immutable - 

15. Create an object lock enabled Wasabi bucket. (for more information click here)

16. Add a new storage target using the bucket created above using Steps 1 - 3.

17. Login to the Commvault Commcell Console. In the CommCell Browser, navigate to Storage Resources → Libraries. Right-click on the required library and click Properties.

Picture1.png

18. In the General tab, select the check-box for Mark Archive files as Read-Only and click OK.

Screen_Shot_2021-06-01_at_11.55.58_AM.png

 

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



Have more questions? Submit a request