Solved

Exchange not deleting logs after a full backup.

Posted on 2008-10-13
10
1,426 Views
Last Modified: 2013-12-01
Hello, our Exchange Server is not deleting transaction logs after a full backup using Backup Exec, or NTBackup. The fulls complete with no errors, but the difs and incurmentals fail with access denied errors in Backup Exec

Backup- \\l3mail.logix3.com\Microsoft Information Store\First Storage Group V-79-57344-33928 - Access is denied.
Access denied to database Log files.

Backup- \\l3mail.logix3.com\Microsoft Information Store\First Storage Group WARNING: "\\l3mail.logix3.com\Microsoft Information Store\First Storage Group\Log files" is a corrupt file.
This file cannot verify.
Verify- \\l3mail.logix3.com\Microsoft Information Store\First Storage Group WARNING: "Log files" is a corrupt file.
This file cannot verify.



 and fail with NT stating missing log file

 "Backup started on 10/13/2008 at 9:18 AM.
The 'Microsoft Information Store' returned 'Some log or patch files are missing.

' from a call to 'HrESEBackupOpenFile()' additional data 'C:\Program Files\Exchsrvr\MDBDATA\E000478A.log'
The operation was ended..


After a few days on the phone with Symantec, they siad the problem was Exchange.
Any ideas on how to fix this issue?
0
Comment
Question by:Logix3
  • 5
  • 5
10 Comments
 
LVL 8

Accepted Solution

by:
DenverRick earned 500 total points
ID: 22702459
Is this SBS or Full Windows?

If SBS you may need to change permissions on MDBDATA, it won't hurt to give Backup Operators Full.

If not SBS, check the permissions, if ok, you might consider dismounting the store to ensure flushed logs and then delete all of the log file (except E00, E00tmp, res1, and res2, then remount and run a full backup after you see a couple of new logs created.  Perhaps you have some earlier log files with a problem.
0
 
LVL 1

Author Comment

by:Logix3
ID: 22702647
Sry it's Windows Server 2003 Stanard R2 SP2. Also I'm starting to think someone deleted some of the logs before the full backup was takin. Which is what some Internet searching said might have happened.
0
 
LVL 8

Expert Comment

by:DenverRick
ID: 22702656
Not a problem since you are doing full backups.  Stope the MS Exchange Information Store, delete all the .log files except the ones previously noted, then restart the IS service.
0
Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

 
LVL 8

Expert Comment

by:DenverRick
ID: 22702695
One other thing...I assume there are more than 7 Exxxxxxx.log files, correct?
0
 
LVL 1

Author Comment

by:Logix3
ID: 22702741
Yes way more than 7.
0
 
LVL 8

Expert Comment

by:DenverRick
ID: 22702760
Ok, that was to make sure you don't have Circular Logging turned on.  Go with my previous instructions.  Once you have a Full backup, you don't need those logs.  So you are ok to delete them, but the store should be dismounted or the IS service stopped (that's Information Store).  This is so there are not active logs when you delete.  Make sure to omit the ones I specified.
0
 
LVL 1

Author Comment

by:Logix3
ID: 22702860
Ok Rick thanks I'll give it a shot tonight and let you know what happened. So to clairify. I want to run the Full backup, then stop the InfoStore Service, then delete all the trans logs expect for, E00.log, E00tmp.log, res1.log, and res2.log correct?
0
 
LVL 8

Expert Comment

by:DenverRick
ID: 22703092
That is correct.

After you do the backup and deletion, you will have to wait until at least 5 MB of emails have flowed, to create some new logs.  (You could email your self a couple of 5 MB files).  Once you have some logs, try another Full Backup and see what happens.
0
 
LVL 1

Author Comment

by:Logix3
ID: 22703135
Once I have the 5MB of new emails, do I run the difs that are failing or do I need to run another Full then the diff? The Fulls finish, the difs are what fail.
0
 
LVL 1

Author Comment

by:Logix3
ID: 22711275
After stoping IS services, deleting the the old transaction logs, restarting the IS service, running the Full backup and then waiting for atleast one transaction log to generate before i ran the dif. I finally have no more errors backing up my mail server. Thanks for your help DeverRick!  
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

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

Suggested Solutions

Lotus Notes – formerly IBM Notes – is an email client application, while IBM Domino (earlier Lotus Domino) is an email server. The client possesses a set of features that are even more advanced as compared to that of Outlook. Likewise, IBM Domino is…
In-place Upgrading Dirsync to Azure AD Connect
To efficiently enable the rotation of USB drives for backups, storage pools need to be created. This way no matter which USB drive is installed, the backups will successfully write without any administrative intervention. Multiple USB devices need t…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

808 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