You will lose the logs after 31 backups. 
Backint/TDP will give the logs the same version-number as the previous 
(br)backup. 
So after 31 full backups, these logs will be removed with the oldest full 
backup.

Archiving the logs with a different TSM-Nodename in the utl-file will secure 
your logs.  
        SERVER      TSM_SERVER   
        ADSMNODE        SAP_LONGTIME

Jeroen


-----Original Message-----
From: Eric Winters [mailto:ewinters AT AU1.IBM DOT COM]
Sent: maandag 22 december 2003 8:12
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Retention of brarchives


Team,

TDP for R/3 3.2.0.13 on AIX

I have a system which runs brarchive to archive redologs. I have a
requirement to keep some redologs which are to be 'brarchived' for an
extended period eg we normally retain logs for 31 days but for a period of
a few hours we're interested in achieving a year's retention. (The db
itself will be archived via a traditional filesystem archive).
I'm aware that retention is controlled by the BRARCHIVEMGTCLASS but need
reassurance that MAX_VERSIONS won't have any affect on my brarchived data -
can anyone provide confirmation that MAX_VERSIONS relates solely to the
retention of brbackup data (ie db backups). It's important that these
redologs won't get flushed away in 31 days (assume we run a brbackup every
night and max_versions is set to 31).

If there's any risk of losing these logs I take it by best strategy would
be to temporarily use a different BACKUPIDPREFIX to differentiate the
backups?

Thanks for any input


Eric Winters
Sydney Australia