Managing retention for decommissioned volumes/datasets

Is there a best practice for handling retention with regards to decommissioned volumes or datasets?  I've deployed OnCommand Core 5.0, and this is one question that has come up.  I assume that, if I apply a "No Protection" policy, that will stop regular backups - will it also handle retention?

Re: Managing retention for decommissioned volumes/datasets

Hi Chris,

     Can you give little more example of description around what you mean by decommissioned datasets /volumes ?

Applying No Protection policy will not help as it doesn't have any retention setting so it wont handle it.

One way of doing this is remove the schedule from the dataset or make it none and leave the dataset that the protection policy which has the retention setting will handle it.