We recently updated our BackupExec to 2010 R3 from version 12. Our Exchange server is running Windows Server 2008 R2 and our Media server is running on a Winders Server 2008 box.
We are able to get full backups, jobs are running fine. But the Exchange logs are not committing - running NTBackup on the Exchange box does commit the logs successfully though.
We have the Exchange license installed on BackupExec with the remote agent installed on the Exchange box.
The setting for the job is Full Backup and Commit logs.
Any ideas what might be going on?
If you carried those jobs over, try creating a new one and see what happens. Just make it a stand-alone job, run it, and then check and make sure the logs are clearing.
Post back with an update!
Do you have the Exchange 2010 Management tools installed on your Backup Exec server ?
As this is a requirement for exchange 2010 backups.....
Also the MAPI CDO tool need to be installed on the Exchange server.
Hi, any update here? I have the same problem. The LastFullBackup property is blank for all databases, unless I use NT Backup and then it will update the date (but still won't flush the logs). Interestingly, Circular Logging does not work at all. No obvious VSS errors in the Event Logs.
Server is Exchange 2010 SP1 RU5. It's not the AOFO thing, I've tried installing the latest MAPI CDO and I have the Management Tools installed.
Backups are working fine, just not flushing the logs. I have had to resort to manually deleting logs to buy time while I troubleshoot.
I've seen the problem before - last time I applied Exchange SP1 RU3 which sorted it out. But it resurfaced and unfortunately applying RU5 didnt have the same effect as before.
It would be great to learn how you fixed it. I have tried everything short of calling Microsoft!