Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1352
  • Last Modified:

Exchange 2010 - Backup - Transaction Logs aren't getting flushed.

I have an Exchange 2010 server that I'm having problems with.. The backup fails with the error below.. I've also tried with just Windows 2008 server backup and it fails as well..

The problem is with the failing the logs aren't being truncated / flushed..

Error category: Resource
Error: e000032d - The consistency check of the snapshot for the Microsoft Exchange transaction log has failed.  You should check for possible data corruption in the transaction log that is online.

For additional information regarding this error refer to link V-79-57344-813

Things I've tried:

Enabled circular logging on both DB's, dismount and remounted the databases. Log files did not clear. Restarted the information store service. Logs still did not clear. Turned circular logging off and rebooted the server again. Verified databases were mounted.

Logs continue to grow.. 82,000 for my one DB and the other DB has 14,000+

There are some jumps in log files too.. Oldest are 1/21/13 but then the next ones go to 1/29/13..

When I reboot it I get the attached error (Note it's a VM).

Thanks
ExchangeError.PNG
0
TBIRD2340
Asked:
TBIRD2340
1 Solution
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Maybe a sequence break or corruption in some Transaction log .... so one good try could be Enable Circular logging restart Information store service and then try with backup again

- Rancy
0
 
AmitIT ArchitectCommented:
Do you see event ID 55 in system logs, as this error indicates disk issue. I faced this recently and after running check disk db size went to 0 KB and finally i have to restore it from back. If DB is up, i better suggest you to create db on another drive and move the mailbox ASAP and then run check disk on this drive.
0
 
TBIRD2340Author Commented:
There actually is numerous ID 55 event's.. What's strange is this is a VM with virtual disks on a SAN.

The DB's are on another logical disk on the VM and there are no errors for it... Just the logs disk..

I know I can right click and say to move the database but am I able to just move the logs without providing another DB location?

Can this be done hot? (IE: without unmounting the databases) ?
0
Microsoft Certification Exam 74-409

VeeamĀ® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
No if you move DB or Logs Database will be dismounted .... only way is to delete all logs older than an hour or move to some additional location to gain free space

- Rancy
0
 
TBIRD2340Author Commented:
"only way is to delete all logs older than an hour or move to some additional location to gain free space"

Only way to what? I want to fix the problem not bandaid it.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Look either Dismount DB and flush all logs and let it create or enabled\disable Circular logging as i said earlier and try backup

- Rancy
0
 
I QasmiCommented:
1) check whether exclusions for exchange folders and  your backup folder has been added to antivirus , if you have any
2) check for any log which is corrupt , check the ESE events in eventviewer you will find if any.
3) no need to enable circular logging,
    check the drive where the exchange database and logs reside for errors using chkdsk
if it is a virtual disk on the SAN , then check the SAN drive for errors, if errors persisrt then fix it with CHKDSK/F/R and then perform that backup with windows server backup.

And make sure you have the vss plugin for exchange 2010 full backup, then only it will purge the logs to the database,

If will allow you to select the complete drive where the database and the logs resides
and will take the successful backup

http://www.msexchange.org/articles-tutorials/exchange-server-2010/high-availability-recovery/uncovering-new-exchange-2010-volume-snapshot-vss-plug-in-part1.html
0
 
TBIRD2340Author Commented:
Checkdsk won't run on it. It gives the error I attached in my OP..

Tonight I tried to simply move the logs to a different virtual disk that I added. I tried via the exchange shell.. I got "Error1" attached..

Then I tried a move database path (but only choosing logs) via the gui. Cancelled it after waiting 30 minutes and the progress bar not even moving. When I cancelled it I got the message:

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:30:18


Exch2010-db-02
Failed

Error:
Sending data to a remote command failed with the following error message: The WS-Management service cannot complete the operation within the time specified in OperationTimeout. For more information, see the about_Remote_Troubleshooting Help topic.

Exchange Management Shell command attempted:
move-DatabasePath -Identity 'Exch2010-db-02' -EdbFilePath 'N:\exchange2010\database\Exch2010-db-02\Exch2010-db-02.edb' -LogFolderPath 'W:\Logs\DB02'

Elapsed Time: 00:30:18

Then I looked in my eventvwr and see some bad stuff..

At '2/9/2013 1:16:02 AM' the Exchange store database 'Exch2010-db-01' copy on this server detected corruption on the active copy of the database. To help identify the specific failure, consult the Event log on the server for other storage and "ExchangeStoreDb" events.  Service recovery was attempted by failover to another copy, which was unsuccessful in restoring the service. Error: There is only one copy of this mailbox database (Exch2010-db-01). Automatic recovery is not available.

AND

Log Name:      Application
Source:        ESE
Date:          2/9/2013 1:16:02 AM
Event ID:      467
Task Category: Database Corruption
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER
Description:
Information Store (5740) Exch2010-db-01: Database M:\Exchange2010\databse\exch-db-01\exch-db-01.edb: Index CI PropStore Failed Items MailboxNum Index of table CI PropStore Failed Items-2-2 is corrupted (0).


Not sure what to do at this point as I don't want to eff things up more..
Error1.jpg
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Database corruption so i would simply create a new database and move all mailboxes across

- Rancy
0
 
TBIRD2340Author Commented:
I ended up opening a case with Microsoft.. They had me dismount the databases and then go to ASDI Edit and change the log paths manually and then remount the databases..

I changed the paths and verified the logs were being created there and then I was able to also successfully run a backup..

Next step I'm going to create numerous new databases on a new virtual disk and migrate mailboxes..
0
 
TBIRD2340Author Commented:
Called Microsoft and they walked me through the fix.
0

Featured Post

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

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