This will only work for offline backups otherwise you have to keep 10 years of log files for you oldest backup.
My 10 cents... Jacques van den Berg TSM / Storage / SAP Basis Administrator Pick 'n Pay IT Email : [EMAIL PROTECTED] Tel : +2721 - 658 1711 Fax : +2721 - 658 1676 Mobile : +2782 - 653 8164 Dis altyd lente in die hart van die mens wat God en sy medemens liefhet (John Vianney). -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Herrmann, Boris Sent: 27 June 2008 10:55 AM To: [email protected] Subject: Re: [ADSM-L] Different db2 retention periods Hi Wanda, thanks for your answer. >Use multiple nodenames, e.g: >DB2client >DB2client-monthly >DB2client-yearly >Then they can use different management classes with different retentionvalues. But that is exactly my problem. TSM doesn't control the backup versions via tsm management classes. There is only a "db2adutl" tool to control the TSM Backup versions. With that tool you can do: db2adutl delete full older than <x> days or db2adutl delete full keep <n> (means to keep the last n versions) With both options I can't fulfill the requirements. How do other handle this issue? (One thought of me was to EXPORT the TSM Node to tape, or to dump the db2 backup to a file and then backup up this file with tsm and use different management classes). Any ideas or thought are appreciated. With kind regards, Boris Read our disclaimer at: http://www.picknpay.co.za/pnp/view/pnp/en/page5093? If you don't have web access, the disclaimer can be mailed to you on request. Disclaimer requests to be sent to [EMAIL PROTECTED]
