CMOD ERM + TSM

[Justin Derrick]

Hey everyone. 

I'm looking for some insight regarding CMOD Enhanced Retention Management and TSM/Spectrum Protect.

We're building Application Groups with implied holds, and storing the data long-term in TSM.  We've got the TSM hierarchy set up, but we're wondering if we've got the config right...

We've set retinit=event, but we're not sure exactly how to set everything else. 

The config is that an upstream system will deliver a file to us with a list of documents expiring that day, and we'll process that and tell CMOD which documents to expire -- so... do we set the retention to one day, so that the documents are deleted the day after we get the permission from the upstream system to dispose of the file? 

It's my first time setting up ERM this way, so any info / insight / wisdom would be greatly appreciated. 

Thanks.

-JD.

[rjrussel]

Sounds like you are on the right track. I would set the retention to be the minimum it has to be. It very well might be one day but it just may be longer. It really just depends on the legal needs. I have seen customers who chose to make it slightly longer, just in case. Keep in mind that the CMOD retention value is typically based on load date(or field designated as expire date). Or more specifically, not when you remove the hold.

You also have retmin and retver in TSM. What are you planning setting for those? In the scenario you are describing, I would typically have them set to 0.

Thanks,
Rob