• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5683
  • Last Modified:

Exchange 2010 Database log problem

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
techlinden
Asked:
techlinden
  • 4
  • 3
1 Solution
 
Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
0
 
techlindenAuthor Commented:
RPC traffic is passing fine - 4 other databases are truncating logs without trouble.
0
 
AmitIT ArchitectCommented:
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
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
AmitIT ArchitectCommented:
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
 
techlindenAuthor Commented:
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
 
techlindenAuthor Commented:
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
 
AmitIT ArchitectCommented:
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

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now