# Configuring Storage Lock

You can configure Storage lock in Commvault using the following procedure.

## Before You Begin

Before configuring Storage lock, make sure to perform the following:

### Create or configure the following in cloud storage:

Note

For information on permissions to configure cloud storages, see Creating a Cloud Storage Library.

Vendor | Before You Begin Tasks
--- | ---
Amazon S3 | Create a bucket in Amazon S3 cloud storage, with object lock enabled. Create a lifecycle rule to clean up previous versions of the deleted objects. For more information, see Deleting Object Versions and Managing your storage lifecycle. Note Disable default retention when object lock is enabled. Verify that the PutObjectRetention permission is assigned to the bucket along with the other permissions needed to configure Amazon S3. For more information about the other permissions, see the Amazon S3 pages. Commvault uses Compliance mode with object lock on AWS S3. For a bucket with versioning enabled, you must have the DeleteObjectVersion permission to delete versioned objects.
S3 Compatible | Same tasks as Amazon S3 Commvault uses Compliance mode with object lock on S3 Compatible. Disable default retention when object lock is enabled or set retention days to 0. Additionally, you should configure life cycle policy to remove delete markers.
Google Cloud Storage | Create a bucket in Google Cloud Storage. Notes From Commvault Platform Release 2024 (11.34), Commvault supports object lock on Google Cloud Storage, but only for new storage buckets. Upgraded storage buckets remain bucket lock enabled. For object lock supported Google Cloud Storage buckets, enable object lock during bucket creation. You cannot enable object lock on existing buckets or through the Google Cloud Console. You must use the command line interface. Verify that the storage.objects.setRetention permission is assigned to the IAM Service Account along with other permissions needed to configure Google Cloud Storage. For information about the other permissions, see Google Cloud Storage.
Microsoft Azure Storage | Create a storage account and a container with version-level immutability support in Microsoft Azure Storage. Create a lifecycle rule to clean up previous versions of the deleted objects. For more information, see Blob versioning and Optimize costs by automatically managing the data lifecycle. Verify that the Storage Blob Data Contributor role is assigned in Azure.
Oracle Cloud Infrastructure (OCI) | Commvault supports Bucket Lock on Oracle Cloud Infrastructure (OCI). OCI does not support object lock, but bucket-level retention is available through Bucket Lock. When you enable WORM storage lock from the Command Center on an OCI storage, Commvault automatically configures the corresponding bucket settings: A retention lock policy is applied to the OCI bucket. The retention period (in days) matches the WORM lock duration set in Commvault.

### (Optional) Set retention cycles to zero on storage pool:

If you want the jobs running on a client to be aged according to the defined days retention rule, set retention cycles to zero (0) on storage pool.

1. Download the Update_BasicRetention.xml file and save it on the computer from where the command will be executed.

2. Execute the following command.

       qoperation execute -af $[downloaded location]\Update_BasicRetention.xml -storagePolicyName $[StoragePoolName] -retainBackupDataForCycles 0 -retainBackupDataForDays $[required days retention] -copyName $[StoragePoolCopyName]

For more information, see How does zero cycle retention work?.

## Procedure

1. From the Command Center navigation pane, go to Manage > Storage > Cloud.

   The Cloud page appears.

2. Click the cloud storage for which you want to configure WORM storage mode.

   The cloud storage page appears.

3. On the Configuration tab, in the Immutability section, do the following:

   a. Move the Storage lock toggle key to the right.

   The Retention rules page appears.

   Notes

   - This action also enables Compliance lock on all associated backup destinations.

   - This action is irreversible and you cannot lower the retention.

   - If you enabled Storage lock unintentionally, we recommend you to create a new storage pool with a new storage pointing to a new container or bucket.

   - Enabling Storage lock requires additional storage to retain immutable backup data during the retention period.

     WORM storage optimization uses micro-pruning to improve storage reclamation for deduplicated data stored on WORM-enabled cloud storage, allowing eligible data to be reclaimed at the job level while continuing to enforce retention and WORM lock requirements.

     To enable WORM storage optimization, add the EnableOptimizedWORMStorageLock additional setting on the CommServe database and set its value to 1.

   - Warning: Associating Index backups and DDB backups to WORM copies is not recommended. Doing so can result in deletion attempt errors. Ensure these backups are not configured on WORM copies to avoid operational issues.

   b. In the Retention period option, specify the amount of time to retain the backups, and then click OK.

   The Do you want to enable storage lock? dialog box appears.

   c. Select the options to confirm your agreement, type Confirm in the confirmation box, and then click CONFIRM.

×

Loading...