How to get rid of WORM copy in primary DR policy

Question

Hi all!as time went by, the disk space on the disk library associated with CommServerDR policy is full. Unfortunately, on the Primary copy of the CommServerDR policy WORM Copy settings has been enabled. Even worse, the retention period has been set to infinite.Would it be feasible to move the mount path/the disk library to the different disk and then concurrently create new policy copy in CommServerDR policy, that could be set as primary instead of current one?Or is just the only solution either reinstall all CV environment (as it is DR policy) or to ask support for eliminating the WORM copy?Any suggestions would be greatly appreciated!

Sheri Balzarano · Accepted Answer

Hi @drPhil:After FR21.61, WORM is automatically configured on the primary copy of a Commserve DR storage policy to prevent accidental deletion of the DR data.If the retention was previously set to infinite before this change was added in, then it is now maintained that way.To have the WORM configuration removed from the DR storage policy’s primary copy, we require an authorization request be submitted with specific information from your environment that we can review and process on our end to provide authorization to disable the WORM attribute.You can open a case with support to proceed with this since there is site specific information from your environment that is needed to process this request and support can provide you with the authorization form and let you know what details are needed.After the WORM configuration is removed from the copy, you could then modify and lower the retention, manually delete jobs from the copy, or if preferred change the data path to use a new target location or other solution.Creating an entirely new CommserveDR storage policy copy would again automatically configure WORM again on the new copy, however by default retention on a primary copy of a new Commserve DR policy is only 15 days & 15 cycles.

drPhil · Answer

Hi @Sheri Balzarano ! Thank you so much for your input. Now, I understand, that only one reasonable solution is to get in touch with the support to remove WORM configuration from the storage policy copy. Followingly, it is possible to modify and lower the retention, manually delete jobs from the copy, or if preferred change the data path to use a new target location as you have stated.

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded