Skip to main content
Solved

WORM Storage Lock retention / also for GFS


Nikos.Kyrm
Byte
Forum|alt.badge.img+13

Hello Commvault,

Lets assume we have a Primary Storage Policy with 14 days retention and extended rules, 90 days for Weekly Full.


 

In case of 2nd aux copy, to Storage Policy (Azure Storage Account) with WORM Storage Lock enabled and 30 days of retention, I am wondering what happened with the GFS backup?


OK, I see the retention is for 30 days (initial configuration), but the extended retention for Weekly Full are missing (from Primary Storage policy)!

So, what happened with them? WORM Storage Lock has only 1 retention?

How you are going to protect the rest GFS backup jobs?


Please for your feedback,
Nikos

Best answer by Collin Harper

Hello @Nikos.Kyrm 

As mentioned above, Extended Retention is not supported for WORM storage because of the way the data held and aged. Since the data is deduplicated and locked by WORM, we cannot prune the data until all of it has aged. This would mean that the data with normal retention wouldn’t age until the Jobs with Extended retention have aged. Once every job has aged, all of the data gets pruned.

Additionally, you cannot use “inherit retention from the source”. Each copy associated to the WORM StoragePool must have the same retention to avoid pruning issues.

 

Configuring WORM Storage Mode on Cloud Storage - https://documentation.commvault.com/2023e/expert/configuring_worm_storage_mode_on_cloud_storage_01.html
 

Configuring WORM Storage Lock and Compliance Lock - https://documentation.commvault.com/2023e/expert/configuring_worm_storage_lock_and_compliance_lock.html

 

Thank you,
Collin

View original
Did this answer your question?

2 replies

Forum|alt.badge.img+12
  • Vaulter
  • 173 replies
  • March 11, 2024

@Nikos.Kyrm,

If you enable worm storage lock on the storage pool you can no longer enable extended retention cause of how worm storage lock works. If you are looking to setup GFS you would need to implement Compliance Lock at the storage policy copy level.

 

Regards,

Edward J Holowienka


Forum|alt.badge.img+14
  • Vaulter
  • 490 replies
  • Answer
  • March 11, 2024

Hello @Nikos.Kyrm 

As mentioned above, Extended Retention is not supported for WORM storage because of the way the data held and aged. Since the data is deduplicated and locked by WORM, we cannot prune the data until all of it has aged. This would mean that the data with normal retention wouldn’t age until the Jobs with Extended retention have aged. Once every job has aged, all of the data gets pruned.

Additionally, you cannot use “inherit retention from the source”. Each copy associated to the WORM StoragePool must have the same retention to avoid pruning issues.

 

Configuring WORM Storage Mode on Cloud Storage - https://documentation.commvault.com/2023e/expert/configuring_worm_storage_mode_on_cloud_storage_01.html
 

Configuring WORM Storage Lock and Compliance Lock - https://documentation.commvault.com/2023e/expert/configuring_worm_storage_lock_and_compliance_lock.html

 

Thank you,
Collin


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings