Hi Zoltan, In this case, I recommend you place a call with IBM support. The IBM service team can gather a trace and find out exactly which backup is keeping the logs from inactivating. (If that is indeed the problem.)
If you are adventurous, you can turn on tracing like this: domdsmc inactivatelogs /traceflag=service /tracefile=trace.txt and peak through it. It's not for the faint of heart... Thanks, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <[email protected]> wrote on 12/07/2009 10:35:55 AM: > [image removed] > > Re: Force/purging Domino transaction logs > > Zoltan Forray/AC/VCU > > to: > > ADSM-L > > 12/07/2009 10:37 AM > > Sent by: > > "ADSM: Dist Stor Manager" <[email protected]> > > Please respond to "ADSM: Dist Stor Manager" > > I tried this 2-ways on one Domino instance. > > "incremental" did nothing. > "selective" forced a backup > > 11/23/09 10:45:46 13.50MB I Yes Julie R Zubris > mail/usermail8/zubrisjr.nsf > 11/16/09 12:19:35 13.50MB I Yes Julie R Zubris > mail/usermail8/zubrisjr.nsf > 11/09/09 10:33:55 13.50MB I Yes Julie R Zubris > mail/usermail8/zubrisjr.nsf > 11/02/09 07:44:36 13.50MB I Yes Julie R Zubris > mail/usermail8/zubrisjr.nsf > 12/07/09 10:30:32 13.00MB A Yes Domino MailTrac > mtdata/mtstore.nsf > 05/27/08 19:49:38 13.00MB I Yes Domino MailTrac > mtdata/mtstore.nsf > > "inactivatelogs" did nothing (0-purged/released/inactivated)
