Learn how to a build a cloud-first strategyRegister Now

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

Exchange not deleting logs after a full backup.

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
Logix3
Asked:
Logix3
  • 5
  • 5
1 Solution
 
DenverRickCommented:
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
 
Logix3Author Commented:
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
 
DenverRickCommented:
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
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

 
DenverRickCommented:
One other thing...I assume there are more than 7 Exxxxxxx.log files, correct?
0
 
Logix3Author Commented:
Yes way more than 7.
0
 
DenverRickCommented:
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
 
Logix3Author Commented:
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
 
DenverRickCommented:
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
 
Logix3Author Commented:
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
 
Logix3Author Commented:
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

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

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