asked on

Failed to backup Exchange Server 2007

Hi Everyone,

I'm having emergency problem here in our CCR Exchange Server 2007, the Log partition is currently almost full - less than 1 GB and I got the attached error message as follows.

is there any permanent fix to prevent his to happens again ?

my only solution is just restart the STORE.exe process during the business hours and pray that it will back up again as soon as possible. (http://support.microsoft.com/?kbid=930800) my OS is Windows Server 2008 not 2003 and the Exchange Server 2007 version is 8.1 build 240.6

If anyone here know how to fix this issue, please share it here.

Thanks.

#############################################################################################
"Microsoft Exchange Server (Microsoft Information Store)"  Time: 25/01/2011 3:41:05 PM
ESE subsystem or operating system reported error for SG10:
0x50d: Either the target process, or the target thread's containing process, is a protected process.
#############################################################################################
Log Name:      Application
Source:        MSExchangeIS
Date:          25/01/2011 3:41:05 PM
Event ID:      9840
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EXC01-VM.domain.com
Description:
An attempt to prepare the storage group 'SG10' for backup failed because the storage group is already in the process of being backed up. The error code is 1293. (Note that if a backup was recently aborted, then it may take several minutes for the system to detect the aborted backup and initiate backup cleanup procedures, so this message may be generated if an attempt was made to backup a storage group before a previous backup attempt had fully terminated.) 
#############################################################################################
Information Store (3796) Callback function call ErrESECBPrepareInstanceForBackup ended with error 0x0000050D Either the target process, or the target thread's containing process, is a protected process.
#############################################################################################

Open in new window

eugene20022002

Your log files will fillup unless it is backed up with an Exchange aware application.

Trying using the native Windows Server backup feature and use that to run a full backup. This will automatically remove the log files that could be filling up the drive. Instructions here

What are you currently using to backup the exchange server?

jjoz

ASKER

i'm using HP data protector but as at yesterday it failed and then the log files gets accummulated.

I tried using Windows Server 2008 - backup utility (not NTBackup) it seems that it doesn't support it at all.

AFAIK the only way to flush down the log files is by performing the full VSS-aware backup unless there is any other way around ?

eugene20022002

Hi Im running exchange 2010 and do daily backups (images) with Acronis. It however does not flush the log files because it is not exchange aware.
i use the Windows Server Backup (not ntbackup) and yes it has to be a VSS Full Backup

jjoz

ASKER

Hi eugene, but from the Windows Server backup application I can't drill down the IS objects ?

ASKER CERTIFIED SOLUTION

eugene20022002

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

jjoz

ASKER

thanks man.

jjoz

ASKER

by the way is there any permanent fix in order to avoid this problem again in the future ?

eugene20022002

Hi
Thanks for the points.
As a permanent solution we do windows backups on a weekly basis to get rid of the built up logs. We schedule the windows backups to run every weekend while still doing 3rd party(acronis)backups on a daily basis.
I havent used HP data protector myself but they may have some exchange specific modules or add ins ,that may also require an additional license, but that could allow you to backup your exchange server once and not have to use windows backups and data protector.

More Info