Skip to main content

Scenario:

Local on prem copy - 60 day retention

Aux copy to Azure - Long term retention

We would like to set compliance and worm lock on the Azure copy. 

Questions:

  1. In prior feature releases, the suggestion we were given was to have multiple libraries/storage pools that would be rotated half way through the worm lock. Example: A 30 day retention/ 60 day worm lock, at day 31 you switch jobs to a different worm library for 30 days, rinse repeat. Is this still the case?
  2. Our Azure retention is up to 7 years. Would the best option be to have the first Aux land in a hot storage bucket that’s immutable for 30 days, and a 2nd aux written to a non immutable storage account utilizing DDB for the full retention period?

 

Hi @Shane H,

 

From Fr30 and onwards, we have made significant changes in our WORM support. Now we allow user to set WORM at storage level, and it is applied to all dependent copies. Retention is also controlled from storage level.

In your case retention is going to be 7 years, so Commvault will set automatic DDB dealing for 365 days, and object lock your Azure objects for 8 years. you would not need to do any additional steps. Just enabling WORM is needed from your end.

 

Thanks

Nikhil Gupta

Reply


Terms & ConditionsCookie settings