v11.32 - Enable WORM storage lock failed while Compliance lock already enabled

Hi Nikos,

I’d recommend checking Command Center and going to Manage > Plans > VM Plan > Backup Destinations > copy-to-blob and then check on the existing “Retention Rules” and whether there is any extended retention configured.

WORM Lock requires everything to have the same retention, and cannot use any extended retention.

Since you already have Compliance Lock enabled, the action of enabling WORM Lock cannot automatically remove any extended retention that you may have already configured.

It’s possible that the Old retention: New retention as seen in the screenshot above has the same basic 1 month retention, but there could be extended retention in the background that we’re not seeing here which is preventing the option from being enabled.

If you do have extended retention configured, you’ll need a support ticket so that we can discuss how it can be temporarily removed. Once the extended retention is removed, you should be able to re-enable Compliance Lock and enable WORM Lock at the same time.

If you don’t have extended retention configured, I’d suggest logging a support ticket and we’ll need logs from the CommServe and a copy of the CommServe database so that we can further review what’s going on here.

Kind Regards,

Melissa Davies

Thank you both for your replies.

@Melissa D The extended Retention rules, for copy-to-blob, is disabled.

@Abhishek Narulkar I will try your workaround, but when click your link, Im getting the message that workflow does not exist.

Thank you in advance,
Nikos

@Nikos.Kyrm 

11.32+ you no longer need to contact support, can do it from here: https://support.commvault.com/AdditionalInfo/DisableComplianceLockRequest