Was documenting about the WORM activation on our cloud storage, from different threads here and using the documentation.
Came across different questions, which I hope will get some answer through this topic.
1 - On the link that follows, it’s stating that “Note: Once applied, the WORM functionality is irreversible”.
Does that mean when we activate the WORM on the storage through the workflow, we cannot change the retention ? We wanted as a first time test the WORM, with the setting of the retention of one storage policy copy on the storage pool as a test with 1 day only. Does that mean that we cannot change the retention of the workflow to something else ? Let's say 15 days.
2 - Same from the link, since our storage pool is using deduplication, it’s stated that the retention on the storage will be set twice of the one on the storage pool, our copies on the storage pool will be set to 15 days, does that mean the data will remain for 30 days on the storage without being deleted, after 15 days are passed with the data aging job ? If someone can clarify to me how this will work between the CommServ and the Storage, especially regarding the data aging, we don’t want to end up with a storage filling up quickly due to this.
Best answer by Collin HarperView original