Solved

Exchange 2010 Database log problem

Posted on 2012-03-29
8
5,550 Views
Last Modified: 2012-04-10
Hello all and thanks to anyone who can give me some assistance.

Our exchange setup:

Exchange 2010 SP1 - 2 sites with all roles installed - connected via 100m circuit.  We have 5 databases setup on a DAG.

The server with the passive copies crashed yesterday - showing the following in the eventlogs

RPC request to the Microsoft Exchange Information Store service for log truncation failed for database store2\EXCHANGE2. Error: 4294965485.

I deleted this particular databases passive copy, and reseeded.  Everything looked okay until the backup ran on the active databases and crashed trying to delete the logs for this db.

Any advice?

Thanks again

Pat
0
Comment
Question by:techlinden
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
8 Comments
 
LVL 24

Expert Comment

by:Rajith Enchiparambil
ID: 37782477
0
 

Author Comment

by:techlinden
ID: 37782514
RPC traffic is passing fine - 4 other databases are truncating logs without trouble.
0
 
LVL 43

Expert Comment

by:Amit
ID: 37782618
First, you should be taking backup for Active database, always take backup for passive db. Second, check the AV exclusion, if AV exclusion is set properly. I guess this db might be in a separate lun, so you might need to check AV exclusion, don't forget to exclude SAN physical path from AV. Normally admin exclude the logical path, but AV still scans the physical path.
0
Raise the IQ of Your IT Alerts

From IT major incidents to manufacturing line slowdowns, every business process generates insights that need to reach the people required to take action. You need a platform that integrates with your business tools to create fully enabled DevOps toolchains.

You need xMatters.

 
LVL 43

Expert Comment

by:Amit
ID: 37782627
Ignore typo error

First, you should not be taking backup for Active database, always take backup for passive db. Second, check the AV exclusion, if AV exclusion is set properly. I guess this db might be in a separate lun, so you might need to check AV exclusion, don't forget to exclude SAN physical path from AV. Normally admin exclude the logical path, but AV still scans the physical path.
0
 

Author Comment

by:techlinden
ID: 37782652
Thanks much for the help

No AV on either box - no SAN - all local storage

We are attempting backup now with symantec, and it is hanging at consistency check
0
 

Author Comment

by:techlinden
ID: 37782677
Also seeing the following in the event log during the backup

Content Indexing function 'CISearch::EcGetRowsetAndAccessor' received an unusual and unexpected error code from MSSearch.
Mailbox Database: nystore2
Error Code: 0x80041606
0
 
LVL 43

Accepted Solution

by:
Amit earned 500 total points
ID: 37782691
Looks like index is corrupt. Here your options:

1) Fix the corrupt index
2) Repair the db
3) Create new db, move the mailboxes to new db, remove old db.

All 3 options are ok, you need to check how long you can take the down time. Option 3 has zero downtime.
0
 
LVL 43

Expert Comment

by:Amit
ID: 37782697
0

Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A hard and fast method for reducing Active Directory Administrators members.
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …

717 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question