I can't imagine why you would not want this.  Do you plan (somehow) to
manually roll these logs in (commit) or just let them grow forever?  There
isn't a really good interface to allow actions as a normal DBMS product like
Oracle or MS SQL et cetera.  Not doing this automatically can cause other
problems.

David Anderson
ScrippsHealth Information Services
v: (858) 678-6238
tieline: 318-6238
--__--__--

Message: 13
From: "O'Connor, Peter" <Peter.O'Connor AT drkw DOT com>
To: "'veritas-bu AT mailman.eng.auburn DOT edu'"
         <veritas-bu AT mailman.eng.auburn DOT edu>
Date: Wed, 19 Jun 2002 11:34:22 +0100
Subject: [Veritas-bu] Exchange

Guys, Has anybody ever come up against trying to run an exchange backup
(usng the exchange agent) and wanting to NOT flush the transaction logs on
exchange?
 
Like a database it appears exchange servers have transaction logs where you
can roll the db forward with.  It appears that when an exchange backup runs
using the agent,  after it's backed up the Information Store and Directory
(the 2 options available to the class) it then flushes these logs.
 
We have a requirement to stop this from happening... does anyone have any
ideas?
 
Just thought I'd ask?