BES servers by default “poll” mail databases every 20 seconds for changes. As we evaluate Transaction Logging and 8.5/daos, we believe all those events (open, read, close) may all, or in part, be written to the transaction logs. For us, with thousands of Blackberry users, this could add millions of transactions to the TL’s each day.
Can anyone with BES and TL’s running confirm that is true?
If true what are the time to complete implications of all that “log pollution” (used loosely) on incremental restores and server restarts?
If very long to do these actions, how do you handle it?
What I did not understand: Why should reads be logged as transactions? I suppose you already know the article “IBM Lotus Domino with BlackBerry Enterprise Server: Performance best practices” (IBM Developer)
Subject: I’m not familiar w/ BES but I am familiar w/ txn logging
and if it is truly open/read/close (w/ the later BES it doesn’t even do the open unless a change occurred) then there should be no impact on the txn logs. Only update activity is recorded in the txn logs (as well as a few house keeping things that aren’t affected by the open/read/close).
Even if the BES generated more update activity to the databases which would be logged, it would not affect server restart since we keep the amount of data that needs to be replayed into the databases capped based on the performance criteria selected.
If you are using/considering archive txn logging then an increase in update activity would increase the restore time for backups when applying transaction logs since there is more data in the logs to read. But that is presupposing that BES is doing updates as part of the poll.