Wanda I'd say definitely use server side.
Issue 1. if you keep n copies, configured client side, you always keep n copies, even if the backup frequency is changed or the node is retired. Issue 2, Some Basis guy will unilaterally decide that he wants another 10 versions, change that parameter on the client and you will have no idea that it has happened. They seem happy to change paramateres that are configured, but not ones that are not. My experience is that most basis admins have no idea how the TDP works and indeed don't seem to want to know. Regards Steve. Steven Harris TSM Admin Canberra Australia On 26/06/2012 3:23 AM, Prather, Wanda wrote:
TSM server 6.3.0 on Windows TDP for SAP 6.3 with Oracle on Linux (BACKINT, without RMAN). The TDP for SAP redbook SG24-7686 says: Backup retention control The backup retention policy can configured either on the Tivoli Storage Manager server side by the archive copy group parameter RETVER (the number of days the version is to be kept) or on the side of Tivoli Storage Manager for ERP by specifying the parameter MAX_VERSIONS in the configuration profile (init<SID>.utl). Does anybody have strong opinions or reasons to use one method over the other? (Doing it on the TSM server seems simpler to me, rather than visiting a dozen client machines to modify the .utl file.)
