Skip to main content
Solved

Enable 0 cycle retention on WORM pool

  • May 20, 2026
  • 3 replies
  • 26 views

Forum|alt.badge.img+4

Hello community,

 

we used a deduplicated WORM cloud storage pool  for a while but needed to start fresh because of unexpected growth.

In the process of aging the data of the old pool we noticed an issue because of the default 1 cycle retention which required a workaround to bypass the cycle retention.

Therefore we would like to enable zero cycle retention on the new WORM pool like described here: Configuring WORM Storage Lock

When preparing the pool and assigning the first storage policy to it I noticed that the cycle retention got increased to 1 after enabling WORM despite running the command from the documentation beforehand.

So my question is: Is there more to do than described in the documentation to enable the zero cycle retention on WORM pools or is the GUI just “showing” 1 cycle but using 0 in the background?

Best answer by Marcel_RE

I tried reproducing the issue again, but now it seems like the setting was applied correctly.

The only difference as far as I can tell was that I did not have a plan already assigned to the pool before enabling WORM.
When executing the command on an empty pool with no assigned plan copies the cycle retention stays 0 on the pool and on the plan copies added afterwards.

So maybe this should be added to the documentation if my assumption is true.

3 replies

Forum|alt.badge.img+17
  • Vaulter
  • May 22, 2026

Hi ​@Marcel_RE ,

To enable zero cycle retention, you must set the number of cycles to 0 in the storage pool retention settings and the value must be set and saved.


Forum|alt.badge.img+4
  • Author
  • Apprentice
  • May 22, 2026

Hi ​@Pradeep,

we used this command in our testing and it seemingly succeeded but I was wondering if it is expected behaviour that the cycles will get increased to 1 again after enabling WORM?

Does the zero cycle retention still apply then?#

 

Thanks in advance!


Forum|alt.badge.img+4
  • Author
  • Apprentice
  • Answer
  • May 22, 2026

I tried reproducing the issue again, but now it seems like the setting was applied correctly.

The only difference as far as I can tell was that I did not have a plan already assigned to the pool before enabling WORM.
When executing the command on an empty pool with no assigned plan copies the cycle retention stays 0 on the pool and on the plan copies added afterwards.

So maybe this should be added to the documentation if my assumption is true.