Exchange 2010 database transaction logs not being truncated after backup

I currently have for Exchange 2010 servers, two hub/cas and two mailbox servers in a DAG. I ran a full backup on of mailbox server #1 including OS/system state/exchange data) and on mailbox #2 of os/system state only but NOT Exchange data using Unitrends backup. According to the backup console, the backup completed successfully and I am seeing events saying the following:

1. ESE event 2001 Information Store (3464) database_name_here: Shadow copy instance 96 freeze started.
2. ESE event 2003 Information Store (3464) Shadow copy instance 96 freeze ended.
3. ESE event 225  Information Store (3464) database_name_here: No log files can be truncated.  
4. MsExchangeIS event 9827: Exchange VSS Writer (instance f8b0064b-7a70-44b7-94e2-a5c1b0adfd45:96) has successfully completed the full or incremental backup of replicated database database_name_here. The log files will be truncated after they have been replayed.

3 and 4 seem to conflict. When I do this, I am not seeing any truncation of the logs on either mailbox server. When I ran a get-mailboxdatabasecopystatus on the affected database, it is listed as "mounted" on mailbox server #1 and "healthy" on mailbox server #2. The copy queue length and replay queue length are both listed as 0. The content index state is listed as healthy on both servers for that database.

I tried dismounting and remounting the databases and that had no effect. Circular logging is currently not enabled and I do not wish to enable it.

Thanks in advance for your help.
LVL 12
Julian123Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

MbhushanCommented:
Remove affeted database from DAG, then Try to take backup. It should Truncate the aLog. Then add that database into DAG. Then Chek.
Kamalasekar ParthasarathyMessaging SupportCommented:

Please run the full backup manually and check whether the logs are getting purged or not.  Please check..

Also, Please post the error message in any related with Exchange server.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Julian123Author Commented:
It's currently happening on all DBs.

As for the comment above, I did run it on all DBs and checked the logs and they are not. No error messages in the log, just the ones above.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
the problem is related to the Microsoft Exchange Search Indexer Service.  I don't know if it is a bug in Exchange or something in my design, but I had to dismount databases, stop the Exchange Information Store Service then delete catalogs from all database copies (active and passive).  After restarting Exchange Information Store Service and remounting the databases the backs now truncate logs.  The rep said the Microsoft Exchange Search Indexer Service wasn't allowing the Replication Service to truncate logs.

In addition to this issue I am seeing problems with the ContentIndexState, upon replica creation, being set to Crawling and never coming out.  If I restart the Microsoft Exchange Search Indexer Service, the state moves to Healthy.

It appears all my issues point to the Microsoft Exchange Search Indexer Service and it's manifesting itself in different ways.  My case is in the process of being escalated so I'll post back with an update.  Hopefully someone else won't have to spend weeks fighting this too.
Julian123Author Commented:
Jordannet, thanks for the info. Were there any specific logs or errors you saw? I'd like to see if I have the same ones, meaning maybe I have the same issue.
Maen Abu-TabanjehNetwork Administrator, Network ConsultantCommented:
check the event viewer and post the events ID's and descriptions here , it will be helpful
Julian123Author Commented:
Jordannet,

I posted mine above. I'm asking for yours. :)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.