Workflow to Configure WORM Storage Mode on Disk Libraries, not Cloud Libraries

Steven, Thank you, I need some clarification here. 

Documentation from ver. 11.30: 

Enabling WORM Storage and Retention for Disk Libraries

https://documentation.commvault.com/2023/expert/157131_enabling_worm_storage_and_retention_for_disk_libraries.html

Configuring WORM Storage Mode on Disk Libraries

https://documentation.commvault.com/2023/expert/146623_configuring_worm_storage_mode_on_disk_libraries.html

What is the difference?

It seems to me that the Configuring WORM Storage Mode on Disk Libraries page is specific to environment where disk storage vendors support the WORM (Write Once Read Many) functionality and on those cases the CommVault provides the workflow Enable Retention Lock Workflow. But how It works? Do I need to provide the IP address of the disk storage’s admin console? Is there any kind of exposed API? The workflow will set up the WORM parameters on storage side? 

Documentation from ver. 11.28 (the ver. I’m running now):

Configuring WORM Storage Mode on Disk Libraries

https://documentation.commvault.com/2022e/expert/146623_configuring_worm_storage_mode_on_disk_libraries.html

This workflow didn’t work on my environment. It didn’t complete and I said after executing the workflow (Enable WORM Storage) the workflow got stuck in a pending state. Error Code: [19:857] Description: Parse error at line 5, column 1. Encountered: workflow Source: cvault-cs, Process: Workflow

I took a look inside the script and It seems to me that this workflow is specific to cloud libraries, not traditional disk Libraries. 

What are my options? Update to ver. 11.30 and download the Enable WORM Storage workflow to configure the WORM storage mode for disk storage vendors that support the WORM (Write Once Read Many) functionality or keep the ver. 11.28 and download the Enable Retention Lock Workflow, but Do I need to set up something at Commvault side? 

I'm pretty disappointed with the way Commvault documents some of its functionality.

I’ve ran into the same problem today (we’re on 11.28) and can confirm your suspicion as to why the workflow is not working on Disk Libraries.

In the SQL Statement that is parsing the associated Mount Paths there’s an “AND” filter fixed onto “MountPathTypeId” = 7, which is for Cloud Libraries. Disk Libraries have the Type 4.

Hence it’s not returning any valid Mount Paths and the workflow fails/gets stuck there.

If you modify that value in the workflow from 7 to 4 you should be able to run it successfully.

I’m also curious about the correct procedure for this in regards for Disk Libraries.

 

Thank you, ChrisK. It's too late for us. I decided to run the Enable Retention Lock workflow and apply a set of adjustments manually. Here they are: 

• Hardware WORM lock should be set to twice as long as copy retention. (Ok) See Screencaps from Tela 1 to Tela 4
• All dependent copies of the DDB must have same retention. (Ok) Screencaps from Tela 5 to Tela 7
• DDB seal frequency will be set to same as copy retention in days value (Ok) ScreencapTela 8
• Micro pruning will be disabled on all mount paths. (don’t know how to confirm that)

More here:

• Disable the CV option “Prevent Accidental Deletion” as the storage may throw errors when CV tries to modify permissions on the file before deletion. (Ok) Screencap Tela 9
• Additionally, as a general rule to prevent aux copies from causing secondary copies to be larger than the source copy, you will want to have Scalable Resources enabled during the aux copy job. (Ok) Screencap Tela 10
• Lastly, when creating the secondary copy and DDB, if the source copy has large amounts of SQL data, there is a chance for data bloat on destination copy. To prevent this from happening, follow the steps here before running the first aux copy. This will ensure even SQL data will be aligned on destination copy and there will not be any increased disk utilization. (I don't know how to do it and I don't even know if I still need to do it since my version is much more recent than the version described in the documentation)