Windows 2003 Enterprise
Hello, I've searched for this even in EE, and I understand what causes it, however I have a twist to the problem:
The following has occured twice to us recently:
-A full backup is running on our Exchange 2003 server.
-event ID 1159 is logged and Stores in one Storage Group go offline:
Database error 0xfffffd9a occurred in function JTAB_BASE::EcUpdate while accessing the database "SG3\PVT10".
Both of our incidents occurred when the following was happening:
First time: we were moving a lot of mailboxes, and a Full backup was running.
Second time: It was a busy day for Exchange activity in general, a Full backup was running.
This article, although dated for Exch 2000 explains it: http://support.microsoft.com/kb/905801
Also in that document it points to this link which gives a tad more information: http://support.microsoft.com/kb/819771/
In summary, the stores go offline when the number of uncommitted transaction logs in one Storage Group reach 1008 files.
Here is the thing, in our environment, we have had backup issues in the past where our transaction logs did not commit for days. For us this can amount to over 80gigs of transaction logs (we have a lot of disk space for transaction logs). The total number of transaction logs are definitely in the thousands for each of our 4 stores. The Mailbox Stores DO NOT go offline when this happens. everything is fine, we just fix the full backup and get those logs committed.
The two occurrences of this event 1159 happened when a FULL backup is in progress, AND the number of transaction logs exceeds 1008. I followed the backup progress in the event log from this past weekend before the last event 1159 and it is progressing fine. It just did not seem to complete before the store went offline because the amount of transaction log files created during this backup period breached the limit.
I'm looking for anyone with experience in this issue using Exchange 2003, since the articles I find are for Exch 2000.
Which one of the following statements are true?
1. While an Exchange Storage Group backup is in progress, regardless of how many uncommitted Transaction Logs there are in total for that Storage Group, there is a limit to how many uncommitted Transaction logs can be produced while the backup is in progress. That limit is 1008.
2. There is a limit to how many uncommitted Transaction Logs in total for each Storage Group. That limit is 1008.
Because of the size of our centralized environment, full backups can take 3 days to complete an entire Exchange server, maybe 14hours per Storage Group.
Thanks for any comments, suggestions.