Compliance lock on storage policy

Hi @jdutro,

Compliance Lock at the Storage Policy Copy level does NOT affect other associations of the Storage Pool.

However, if the Storage Pool level has hardware WORM enabled, Compliance Lock will be forced on any Storage Policy Copy using that Storage Pool. 

Regards,
Sheri

Hi @jdutro , Compliance lock is nothing but enforcing the retention defined on the storage pool / policy. By enforcing, it means to prevent deletion of jobs prematurely, deletion of clients and even lowering of retention. It does not affect anything else with respect to storage policy.

Hi Everyone,

I enabled Compliance Lock on one of the Storage Policies, but I'm unable to delete any backup jobs for the associated subclient. What could be causing this issue? The error message states: "WORM storage enabled for selected subclient(s). Delete operation not allowed."

Thanks,

Sounds like Compliance Lock doing it’s job.  The purpose is to not allow data deletion.

Thanks,
Scott
 

​@Scott Moseman IMO, Compliance Lock is making things overly complex. IF they would have implemented it so that we could delete subclients as long as the jobs met their days of retention, then fine. But that is not how it works. Even weeks after the retention is met one still cannot prune the junk. It’s causing storage bloat beyond what should be required. Not fond of this feature. Sure, keeping things around up to the retention is obviously good but beyond that date, that’s bug, not feature.

Hi ​@downhill,

The Compliance Lock feature does not prevent jobs from aging once they have met their retention criteria.

If you notice that certain jobs have not aged even after the retention period has passed, I recommend running the Data Retention Forecast report to identify the underlying reason.

Regards,

Wasim