Video Screencast Help

Backup Exec 2010/2012 SP4 Remote Agent for Windows ...

Created: 17 Jun 2014 | 6 comments

... or Exchange Agent causes Runtime Errors on Windows Server 2003 SP2 x86, resulting in communication failure between the media server BE 2010 SP4 and the remote server on which the backup remote agent fails and gets stopped or like in BE 2012 SP4 the performance gets drastically reduced.

We still have a lot of Exchange 2003 Server (SP2) installed on Windows Server 2003 SP2 x86. Those system (if rebooted) work fine for a couple of days but suddenly Runtime Errors occur that reduce the performance of the backup of those Exchange servers under Backup Exec 2012 SP4 or which stop the Remote Agent on the Exchang Server under Backup Exec 2010 SP4 and doesn't let the running job end until you logon to the corresponding Exchange server, acknowledge the Runtime Errors by pressing OK and restart the Remote Agent for Windows.

This is really annoying and only happens on Windows Server 2003 SP2 x86 paired with Exchange Server 2003 SP2. There are no Runtime errors on Windows Server 2008 R2 paired with Exchange Server 2010 SP3.

Anybody has the same problem and knows a solution?

Regards,

DiWi

 

 

Operating Systems:

Comments 6 CommentsJump to latest comment

CraigV's picture

Hi,

 

Have you checked the Known Issues section to see if this is listed there or not?

https://www-secure.symantec.com/connect/backup-and-recovery/issues

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

DiWi's picture

I've checked that, but couldn't find the right solution. There are a couple of Hotfixes I like to test. Shouldn't this help, I have another idea as a work-around.

Will keep you informed.

Regards

DiWi

VJware's picture

Would recommend to log a formal support case as we would need to enable debugging and investigate further.

Laurie_Downey's picture

Just so I am clear, are there two versions of Backup Exec backing up the same Exchange server? Or just the BE 2010R3 version  is backing up the 2003 Exchange databases, and BE 2012 backing up another version of Exchange?

Runtime errors can be caused by a few different possibilities. Try referring to the links below, and the first link listed, could possibly resolve the issue:

 

http://www.symantec.com/docs/TECH61177

 

http://support.microsoft.com/kb/911816

 

http://www.microsoft.com/en-us/download/search.aspx?q=Windows%20Script%205.6

 

Laurie Downey

Backup Exec

Advanced Tech Support

Symantec Corporation

www.symantec.com

 

 

DiWi's picture

Not really! We have Backup Exec 2010 media server backupping Exchange 2003 Server with an Backup Exec 2010 remote agent and we have Backup Exec 2012 media server backupping other Exchange 2003 Server. With both versions of Backup Exec (2010 and 2012), we have Runtime Errors only on Exchange 2003 Servers running on Windows 2003 SP2 x86 Servers.

We also have Backup Exec 2010 servers backupping Exchange 2010 servers running on Windows 2008 R2 servers (there without any runtime errors).

Now, last weekend I upgraded all Backup Exec 2010 SP4 and Backup Exec 2012 SP4 servers with the latest Hotfixes available and upgraded all remote agents accordingly.

Now, only time will tell, whether those runtime errors will re-occur or not! Will keep you informed here.

 

Regards,

DiWi

 

DiWi's picture

Ok, here are some important news to know ...

On the 26th of June I updated 7 Backup Exec 2012 media server with HotFix 217347 on top of SP4. I also updated all remote agents on the relevant servers.

These 7 media servers are in different locations and all of them do backup local servers.

This night, the 7 Windows 2003 Servers with Exchange 2003 and the latest remote agents spit out a Runtime Error message and the Backup Exec Remote Agent was stopped.

These 7 Exchange 2003 servers are in different locations and are backupped by a different Backup Exec 2012 media server.

Now, I really wonder what's going on here? Is there a time bomb in the Backup Exec Remote Agent that stops the agent on Exchange 2003 servers and spit out a Runtime error?

This is really a strange behaviour, especially since those 7 servers have no relationship at all.

Regards,

DiWi