Full backup & incremental backup not purging logs in Exchange 2007 SCR
Hi Experts, We have an Exchange 2007 Environment with 2 sites. Site1 is having 8 Mailbox servers and Site B is the DR of Site A with SCR configured. We use HP DP for backups. From a month we have problems with Full and incremental backup, they are failing and even if they succeed getting errors and log files are not purging. Due to this we are facing disk space issue and database dismounts. I have checked the DR log drive and found many ignored logs with M0o,2lw,ivf...extensions. As per my understanding if log files are not successfully replayed in the DR site backup will not purge it. From exchange server we are able to find the error event Event ID 459 Description: MSExchangeIS (2508) MB: The file C:\Logs\SG12\E2D000131B4.log is missing and could not be backed-up. Can you tell me whether i have to diagnose with the SCR log shipping or do i need to check with any other configurations. Please provide your suggestions.
May 4th, 2012 4:42pm

You're going to have to bring this up with HP, I'm sorry to have to advise you.Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
Free Windows Admin Tool Kit Click here and download it now
May 5th, 2012 8:45pm

Not sure why that log file is missing, however a full backup should work. If you've tried a full backup and it still fails, try the native WSB and test, if it works, then your issue is most likely related to DPM.Sukh
May 6th, 2012 4:17pm

On Sun, 6 May 2012 20:17:34 +0000, Sukh828 wrote: >Not sure why that log file is missing, however a full backup should work. Not if there's a missing log file. >If you've tried a full backup and it still fails, try the native WSB and test, if it works, then your issue is most likely related to DPM. If the log file is missing, it's missing. What difference does it make what software you use? If you must (assuming only one database per storage group), dismount the database and verify that it's in a clean state. Then remove all the *.log files and *.chk files associated with that database/storage group. Remount the database to start a new log file generation. Then make a full/normal backup immediately -- don't wait, do it now . . . yes, RIGHT NOW! --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP
Free Windows Admin Tool Kit Click here and download it now
May 6th, 2012 5:09pm

On Sun, 6 May 2012 20:17:34 +0000, Sukh828 wrote: >Not sure why that log file is missing, however a full backup should work. Not if there's a missing log file. >If you've tried a full backup and it still fails, try the native WSB and test, if it works, then your issue is most likely related to DPM. If the log file is missing, it's missing. What difference does it make what software you use? If you must (assuming only one database per storage group), dismount the database and verify that it's in a clean state. Then remove all the *.log files and *.chk files associated with that database/storage group. Remount the database to start a new log file generation. Then make a full/normal backup immediately -- don't wait, do it now . . . yes, RIGHT NOW! --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP I've used HP DPM, and when log files have been moved from the last incremental backup they fail, the only way to get a successful back is to perform a Full backup.. In terms of the software, well, the logs aren't purging, so to simply rule out backups software, using the WSB is worth while doing. I've seen cases where WSB will truncate logs and not 3rd party product due to software updates needed, this may not be the case here as there isn't much detail but is a possibility.Sukh
May 6th, 2012 6:43pm

How is the issue now?Xiu Zhang TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
May 8th, 2012 3:34am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics