How to remove Compliance Lock (worm) on disaster recovery backup copy

This knowledge base article addresses a scenario where users are unable to change the retention settings on the CommServe disaster recovery copy due to the presence of a compliance lock (WORM - Write Once, Read Many). The compliance lock feature was introduced to the DR (Disaster Recovery) copy to ensure the availability of multiple valid copies of the CommServe disaster recovery backup key, enabling recovery in case of a disaster.

Symptoms

Users are experiencing an issue where they cannot modify the retention settings for the CommServe disaster recovery copy.

Causes

The cause of this issue is the presence of a compliance lock, also known as a WORM Copy Lock, on the DR copy. This lock is implemented to prevent data from being altered or deleted after it has been written, ensuring data integrity and compliance with regulatory requirements.

Resolution

To resolve this issue and enable the ability to change the retention settings, follow the steps below:

1. Ensure that your CommServe is running Feature Release 11.24 or a more recent version.
2. Access the Commvault documentation link provided below to learn about the specific additional setting that needs to be configured:
   • AllowUnsetComplianceLockOnDRCopy: https://documentation.commvault.com/additionalsetting/details?name=%22AllowUnsetComplianceLockOnDRCopy%22&id=13251
3. Set the additional setting "AllowUnsetComplianceLockOnDRCopy" to True. This setting will enable users to disable the compliance lock on the primary copy of a Disaster Recovery (DR) policy.
4. After making the required changes to the retention settings, ensure that you set the "AllowUnsetComplianceLockOnDRCopy" setting back to False or remove the key to re-establish the compliance lock as needed for data integrity and regulatory compliance.

By following these steps, you will be able to manage the retention settings on the CommServe disaster recovery copy while maintaining data security and adherence to compliance requirements. If you encounter any issues during this process or require further assistance, please refer to the provided documentation or contact our technical support team for prompt assistance.