Problem: Exchange logs are not flushing after backup exec runs full backup.

The backup in backup exec 2010 R3 Is successful. It is also set to do full backup/flush logs

The logs fill up to around 50,000 files or more. How do you fix this?

ENV: exchange 2010 SP2 Rollup 4 Dag.

I see the following in the logs on database server when backup exec is complete.

Information Store (2972) Mailbox Database Faculty: The backup procedure has been successfully completed.

Information Store (2972) There were 75299 log file(s) not found in the log range (D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database Faculty\E030003BA9C.log - D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database Faculty\E030004EA5F.log) that we attempted to truncate.

Hi,

Sorry to sound silly but is there a tick in backup exec job to flush the transaction logs?

No there is not.

Backup method is set to "Full - Database & Logs (flush commited logs)

Hello,

I recommend you use windows server backup to do a full backup for your database to check the result.

If the logs are truncated, I recommend you contact symantec vendor to verify the issue.

If thses logs will not be truncated, please restart Microsoft Exchange Server Extension for Windows Server Backup service to check the result.

If the issue persists, you can choose use circular logging to truncate these logs.

If you have any feedback on our support, please click here

You can use Windows builtin backup tools to perform a back to isolate an application specific issue.

Looks like there are some missing log files and backup software is not able to flush them, although.

Run Eseutil /l path\E00.log to find whether the logs are really missing. If you see any logs missing, the best bet would be to suspend the database copies in DAG (if you have one), dismount the database, check the database shutdown state using eseutil /mh, Ensure that it is in clean shutdown state, and remove all log files after the missing transaction log number and mount the database.

Your Backup software should be Exchange aware backup software and if you did file level backup, it will not truncate the transaction log.

Hello,

Is there any update?

If you have any feedback on our support, please click here

Are you backing up the passive or active DB's in the DAG ?

Please verify that replication is working and configured correctly and that there are no issues with the information store and or the replication writers. You can do this by running the Vssadmin list writers command from the comand line and view the results.. all should reflect a state 1 and stable status. Please review the following documentation 

TECH156654

at symantec connect.. i am unable to post the link