Configuring Immutability on Disk Libraries

Commvault offers two types of WORM functionality: Storage lock and Compliance lock.

Storage Lock

You can use the Storage lock option for both deduplicated and non-deduplicated data in disk libraries. Storage lock provides data security at the physical (hardware) level.

Notes

  • For WORM-protected storage, only backup data files are locked. Commvault internal metadata files aren't locked, and deleting these metadata files doesn't affect the ability to restore backup data.

  • If you enable the Storage lock, the Compliance lock is automatically enabled. Also, you can enable only the Compliance lock.

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

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

    If a WORM-optimized deduplication database (DDV) remains offline for more than 5 days, the software stops running backups to that DDB.

Compliance Lock

Compliance lock is a security control that provides protection from destructive tasks such as deleting backups, storage, apps, servers, and backup destination copies, and reducing retention for disk storage vendors within the CommCell Console interface. You can enable the Compliance lock at the storage level, and all associated backup destination copies will be locked and protected.

Compliance lock provides data security only at the software level (within the Commvault user interface) by protecting data against rogue users that use compromised credentials.

The combination of Storage lock and Compliance lock features results in immutable backups that neither the storage administrator nor the Commvault administrator can delete.

×

Loading...