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?

