Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Nach BackupExec Upgrade zu 2012 - Remote Agent konnte keine Verbindung herstellen

Created: 24 Jun 2013 • Updated: 27 Jun 2013 | 13 comments
This issue has been solved. See solution.

Hallo zusammen,

nachdem ich von BE 2010 auf 2012 SP1 gewechselt habe, bekomme ich bei 90% der Backupjobs die Fehlermeldung, dass der Agent den Server nicht erreicht.

Jedoch kann ich mit der Konsole den Server durchsuchen, ein beidseitiger Ping ist ebenfalls möglich.

Die Firewall sperrt nichts.

 

Was kann ich hier tun?

 

Ich danke im Voraus.

Operating Systems:

Comments 13 CommentsJump to latest comment

CraigV's picture

Hi,

Did you also upgrade the RAWS agents on the remote servers via a push-install?

If not, do so and then try again.

Otherwise try to re-establish the trust between the media and remote servers:

http://www.symantec.com/business/support/index?pag...

Thanks!

Alternative ways to access Backup Exec Technical Support:

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

cr1zz's picture

Hey CraigV,

thanks for you answer.

I'm getting the following error when I try to re-establish the trust (please notice that I pushed the new agent before and there were no errors).

 

2013-06-25 08_34_24-Symantec Backup Exec 2012.png

pkh's picture
Check the following
 
1) on the remote server, check that the remote agent service is running
 
2) open the remote agent utility and make sure that it is publishing correctly to the media server
 
3) make sure that you can ping from the media server to the remote server and vice-versa
 
4) make sure that there is no firewall blocking port 10000
 
5) on the remote server, check that there are no other applications using port 10000.
cr1zz's picture

I deactivated the anti virus -> same error

I set permission at firewall to any -> same error

I restarted the media server -> same error

Funny thing is, that BE can view the properties of the media server and all authentication test succeeded.

2013-06-25 09_23_56-Symantec Backup Exec 2012.png2013-06-25 09_24_14-Symantec Backup Exec 2012.png

VJware's picture

Is there any specific reason for re-establish trust manually since a push install of remote agent automatically establishes trust.

Secondly, does the actual backup job fail ?

CraigV's picture

Yes there is...I've had to do this on the instruction of 1 of your tier 1 support engineers. It's worth trying just to eliminate this as a possible issue.

 

Alternative ways to access Backup Exec Technical Support:

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

cr1zz's picture

All are converted jobs... With BE 2010 I had no problems.

I tried with the actual jobs in testmode.

pkh's picture

I tried with the actual jobs in testmode.

Have you actually run the jobs?  If not, you should run the actual jobs and not the test.

CraigV's picture

cr1zz: What happens if you recreate 1 of the jobs? Does it run then?

If so, try a repair of the BEDB using BEutility.exe and see if this fixes any issues.

Thanks!

Alternative ways to access Backup Exec Technical Support:

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

SOLUTION
CraigV's picture

...could have been corruption in the installation/upgrade even though it went through successfully. Wouldn't be the first time this has happened.

Glad it is now sorted out!

Thanks!

Alternative ways to access Backup Exec Technical Support:

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