But I thought that the logs were uniquely named and wouldn't go away until you did an INACTIVATELOGS command?? And if my oldest backup is 35-days then the INACTIVATELOGS would only remove the logs that are older than that full backup?? Or am I missing something here...(Which wouldn't suprise me!!!)
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Del Hoobler Sent: Wednesday, July 23, 2003 9:00 PM To: [EMAIL PROTECTED] Subject: Re: TDP Domino and transaction logs Bill, How about using the INCLUDE statement to bind the log backups to a management class with different policies? For example: INCLUDE S*.TXN MGMT_CLASS_7_DAYS where MGMT_CLASS_7_DAYS has settings of VERE=NOLIM, VERD=NOLIM, RETE=7 RETO=7 Thanks, Del ---------------------------------------------------- > Client is running transaction logging for all databases. The backup schedule > is: > Sunday - Full backup followed by an INACTIVATELOGS command. > Mon-Sat - Incremental backups > every 2-hours - Archivelog backups > > The management class retention is VERE=NOLIM, VERD=NOLIM, RETE=35 RETO=35 > > Now they want to only keep the transaction logs for a week, but still keep > the full backups for the full 35-days. (They also do a monthly full backup > under a separate nodename). > > If I understand things, my logs are also kept for the same 35-days until the > oldest FULL backup rolls off and the INACTIVATELOGS expires them. Since the > logs are all uniquely named, I can't rely on TSM versioning. > > How can I only keep a weeks' worth of logs, but 35-days worth of full > backups??
