> Expert > Storage > Libraries > Cloud Storage > Setting up Basic Components for Cloud Storage

Configuring WORM Storage Mode on Cloud Storage

You can use the Enable WORM Storage workflow to configure the WORM storage mode for cloud storage vendors that support the WORM (Write Once Read Many) functionality.

Note

Once applied, the WORM functionality is irreversible.

The following agents are not supported for WORM:

  • Dynamics 365

  • Azure Active Directory

  • Exchange Online Agent

  • OneDrive for Business

  • SharePoint Online

  • Laptop IDA

  • Microsoft Teams

  • Exchange Mailbox Agent

  • File System Archiver Agent (Windows, Unix, NAS)

  • Any Object Store (Edge Drive, third-party migration, and so on) and hybrid file

  • Snap copy (job-based retention)

The workflow can enable WORM storage mode for the following cloud storage vendors:

  • Vendors who support object-level retention:

    • Amazon S3

    • Microsoft Azure Storage

    • NetApp StorageGRID (version 11.5)

    • Hitachi Content Platform for Cloud Scale

    • HPE GreenLake for File Storage MP

    • VAST Data Universal Storage

    • Dell ECS

  • Vendors who support only bucket/container level retention:

    • Google Cloud Storage

    • Oracle Cloud Infrastructure Object Storage

Note

This workflow does not support Metallic Recovery Reserve (MRR) and stand-alone policies.

The workflow automates the following settings:

  • Enables WORM option on cloud library.

  • Enables the WORM Copy option on all the associated storage policy copies of the selected storage pool.

  • For deduplication enabled storage pools, the seal frequency of the deduplication database (DDB) is set to the same number of days as retention set in the storage policy copies of selected storage pool, with a maximum of 365 days. For example, if the retention is set for 60 days in the dependant copies of the storage pool, the seal frequency for the DDB is also set to 60 days. For retention higher than 365 days, the seal frequency is set to 365 days.

    In addition, micro pruning is disabled at the mount path level.

  • Optionally, by default, workflow sets WORM retention at the cloud bucket/container level for vendors who support only bucket/container level retention as follows:

    Note

    The workflow does not set anything on the cloud bucket/container for vendors who support object-level retention. Retention is set during backup jobs at each object-level for these vendors.

    • For dependant copies of the deduplication enabled storage pools, retention (or the WORM lock days) at the bucket/container level is set to the retention value set at the dependant copies of the storage pool plus the seal frequency of the deduplication database (DDB). The DDB seal frequency is maximum of 365 days.

    • For dependant copies of the non-deduplicated storage pools, retention will be set to the same number of days in the bucket/container as that of the dependant copies of the storage pools. For example, if retention is set for 60 days in the dependant copies of the storage pool, then retention at the bucket/container is also set to 60 days.

      Note

      You can set custom values for WORM retention.

  • When you delete a file, a delete marker is created due to versioning. Though the file exists in storage, the application cannot access the file.

Before You Begin

  • Create or configure the following in cloud storage:

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.

Google Cloud Storage
  • Create a bucket in Google Cloud Storage.

Microsoft Azure Storage

  • Configure the bucket/container in Commvault software as follows:

    1. Configure a cloud storage pool using the cloud bucket/container.

    2. Configure a storage policy with the configured cloud storage pool.

      If you have multiple storage policies/copies created using the cloud storage pool, make sure to set the same number of days as retention in all the copies.

  • Configure an internal mail server.

  • We recommend not to use extended retention on WORM-enabled storage pools.

Note

WORM workflow supports object locking in object storage platforms that support standard S3 implementations. If object lock support is not available on an object storage, the WORM workflow will default to bucket level locking.

For non-standard S3 implementations, such as Alibaba Cloud, the WORM workflow will only help with setting the DDB seal frequency based on retention of the storage pool. You should manually set the object locking or bucket locking from the cloud platform dashboard.

Procedure

  1. Download the workflow Enable WORM Storage from the Commvault Store using the instructions in Download Workflows from Commvault Store.

  2. From the CommCell Browser, go to Workflows.

  3. Right-click Enable WORM Storage, and then click All Tasks > Deploy.

  4. Right-click Enable WORM Storage again, and then click All Tasks > Execute.

    The Enable WORM Storage Options dialog box appears.

  5. Click OK.

    The Select Storage Pool dialog box appears.

  6. From the Storage Pool list, select the cloud storage pool that you want to configure the WORM storage mode on.

  7. Perform one of the following actions:

    • Click Continue to run the workflow.

    • Click Modify to modify the WORM lock days. By default, the WORM lock is set to twice the retention set at the storage pool.

      The Modify WORM lock dialog box appears.

      1. In the WORM Lock Days box, enter the number of days for the WORM lock.

      2. Click Save.

    Whether you continue to run the workflow or modify the WORM lock days, a message appears that warns you that WORM requires more storage capacity and it cannot be reversed after enabling.

  8. Click Yes.

    The Summary dialog box appears.

  9. Click Submit.

Result

  • In the Library Properties dialog box, the WORM Storage Lock option will be displayed as Enabled.

  • Retention settings for subsequent backup jobs will be set as follows:

    • For vendors that support a WORM policy at the object level

      For each object uploaded to the cloud, Commvault software will set the retention settings based on the retention settings in the dependant copies of the storage pool, and the DDB seal frequency at the time of the upload.

    • For vendors that support a WORM policy at the bucket / container level

      Commvault software uploads the data to the cloud and the software vendor will set the retention time, based on the retention settings established at the bucket/container level.

  • Data aging and pruning (both the object level, and bucket / container level) will be performed as follows:

    • For deduplicated data, the data will be pruned from the cloud when the DDB is sealed and all the jobs in the DDB are aged. By this time, the WORM retention time in the cloud vendor side will expire, so the deletion will be allowed.

      For non-deduplicated data, the data will be pruned from the cloud when the job is aged.

Enable Retention Lock Workflow

Loading...