Forgot To Mention Friday is a different error, but i think that is to do with the tape needing to be reformatted, will feedback on this later

Thanks,

please update me the Service Packs installed of Windows, Symantec BEWS, Exchange.
Please verify that you have not selected AOFO option to backup Exchange databases.
Verify the prerequisuites to backup Exchange server.

Find the below link to configure Exchange backup
http://seer.entsupport.symantec.com/docs/288777.htm

Please let me know any queries,

Regards
KK

Windows SBS2003 SP2
Backup Exec 12.5 Rev 2213
Exchange 2003 6.5.7638.1

You'll have to explain what AOFO is sorry.

That link you have sent seems to pertain only to Exchange 2007?

Seems odd that the exchange backup would work ok on the other days

thanks

Mark

Thanks for the information.

Your Exchange is 2003.
BE 12.5 with service pack / hotfix ??????????
If backup would work ok on other days then also there is some problem hence not work entire week.
Is same job runs for all days i.e from monday to sunday?

Regarding AOFO:

Server - CCBSBS
AOFO: Started for resource: "C:". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7).

You are backuping up Exchnage database and volume in same selection list, its not recommended.
Create different job for database and other for file level backups.

Find the below technote that would explain few points to backup exchange database :

http://seer.entsupport.symantec.com/docs/326305.htm

Let me know any queries,

regards
KK

SP2 Latest hotfix installed - 324947

I've got numerous clients that back up Exchange and file volume on the same job with absolutely no problem.

My suspicion with this problem is that exchange is doing something on a Wednesday that is stopping the backup job from getting access to the database but I'm not sure what operations could be doing this.

Since reporting the Problem I have had no problems with the Backup job running on Monday or Tuesday

I'm still not sure what AOFO means

It happened on Friday last week, but not on Wednesday, I thought it had gone away.

Exactly the same error as I had posted in the original log

Anyone have any ideas?

TIA
Mark

and what about other big network based processes on Friday (and Wednesday)?

That's what I'm trying to find out, there are a few scheduled tasks called
C:\WINDOWS\system32\vssadmin.exe Create Shadow /AutoRetry=5 /For=\\?\Volume{99585c31-4ce8-11d9-b544-806e6f6e6963}\

that all run on a daily basis but I'm not actually sure what they do? they are scheduled to run @ 4am, 5am and 7am so unless they are taking all day to complete on Fridays and Wednesdays I canlt be sure that they are causing the interference.

What could exchange be doing/running that woudl interfere with Backup Exec?

update. it failed last night too, same error. I'm confused as to why it is trying to connect to a remote server as it is all in 1 server, nothing remote at all

does backup exec require that the Microsoft Exchange MTA stacks service be running?

I think I've found what's causing the problem.

I have events on the days when the backups fail saying that the local admin account failed to log on to MSSQL$BKUPEXEC.

So i thiught, great, I'll find the service and update it with the correct admin password, but the service isn't showing in services.

Anyone got any clues as to where it might be?

HI,

Can anyone shed any light on this one?

I thought I had it cracked but then it failed again last Fridahy with exactly the same errors as the first post.

It keeps telling me to check for Network issues but the exchange store is on the same server as the backup job!!

Please help, this is driving me crazy

Mark