Job Failed: Unable to connect to remote agent on \\server.

[Andrew_Bienhaus]

Almost that exact error, every night now.

Job Failed: Unable to connect to remote agent on \\SERVER.

And the name of the server is just the hostname, and not the FQDN.

This job ran fine with 10d/11d, it's just since the 2010 upgrade that this has cropped up.

The "server" in question, is the machine hosting BE2010. And, in fact, the RA is in fact running...

Any ideas? It seems to back the server up just fine, gathering all data from the local hard drives as before. And the server is not listed as a remote server that should be contacted...

Andrew

[Andrew_Bienhaus]

...but it flags the job as failed each day.

[mr_miyagi]

pushed out the latest agent to the remote server? is the remote agent utility running and showing the corect media server that it needs to report back to?
you say its not listed as a remote server that should be contacted - is this in the resources tab in the job properties?

Mr_Miyagi

...Wax on, Wax off.....

[Sush--- · Accepted solution]

Hello there,
    From your two statements  " This job ran fine with 10d/11d, it's just since the 2010 upgrade that this has cropped up." and " The "server" in question, is the machine hosting BE2010 " its shows that you must have performed multi-step upgrade to Backup Exec 2010. And also the backups are failing to connect to the Remote agent on the same server itself.
    In that case I would recommend you to follow this technote:

http://support.veritas.com/docs/289709

In this you just have to make a small editing in the selection list.
Thanks.

[Andrew_Bienhaus]

Thanks!