09-18-2012 03:27 AM
We had a SEV1 for our mail system due to running out of exchange transaction log sequence number. We are using Backup Exce 11 for the backup which takes Exchange Full Backup with "Full - Database & Logs (flush committed logs). The logs are flushing after each backup.
My Query is why exchange could not reset the sequence numer. Is any Backup solution has ability to reset exchange transaction log sequence number.
- SREEVNAIR
Solved! Go to Solution.
09-18-2012 03:42 AM
Hi,
Backup Exec won't reset log numbers. All it does is backup the Information Store, and then commit the logs before flushing them. Exchange would handle log numbering.
That said, make sure you're not using Advanced Open File Option in your job, and if you are, turn it off and see if this makes any difference.
Also, if you're not using BE 11d rev. 7170, consider downloading and upgrading to that with SP5 and any subsequent patches. Then push-install these updates to any remote servers you might have.
Download link below:
https://www4.symantec.com/Vrt/offer?a_id=30140 |
Thanks!
09-18-2012 03:42 AM
Hi,
Backup Exec won't reset log numbers. All it does is backup the Information Store, and then commit the logs before flushing them. Exchange would handle log numbering.
That said, make sure you're not using Advanced Open File Option in your job, and if you are, turn it off and see if this makes any difference.
Also, if you're not using BE 11d rev. 7170, consider downloading and upgrading to that with SP5 and any subsequent patches. Then push-install these updates to any remote servers you might have.
Download link below:
https://www4.symantec.com/Vrt/offer?a_id=30140 |
Thanks!
09-18-2012 03:42 AM
As far as I know no backup tools are able to reset the exchange transaction log sequence number.
This is a limitation in Exchange, not in Backup Exec.
09-18-2012 04:44 AM
Hello Shree,
You have already got the answer that Backup Exec or for that matter no backup solution will reset the Exchange Trnsaction log sequence number.
You can refer to the following link to do so. Ii would recommend that you check with Microsoft Support before performing the steps (if Microsoft still support Exchange 2003 ..??)
http://technet.microsoft.com/en-us/library/aa998701(v=exchg.80).aspx
Thanks,
-Sush...