Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

BE 9.1 - Persistent communications error

Status
Not open for further replies.

cyberspace

Technical User
Aug 19, 2005
968
GB
Recently there have been intermittent backup failures with error:

"A communications failure has occurred between the Backup Exec job engine and the remote agent"

The error code for this is 0xa00084f9

Over the last few days though it has been happening every time there is a backup.

All the latest patches were applied (it was reinstalled a few weeks back and a few patches were missing as a result) and the remote agent has been pushed back out to the remote machine.

Any ideas? I rebooted the machines yesterday after the patches had been installed and it's still failing.

thanks in advance

'When all else fails.......read the manual'
 
Is it failing when backing up remote server?
Checked the app/system logs on all server involved.
DO you see remote agents stopping or network errors?
 
Yes - the local server is backed up just fine.

This is the only event log error message:


Event Type: Error

Event Source: Backup Exec
Event Category: None
Event ID: 34113
Date: 25/04/2006
Time: 23:00:57
User: N/A
Computer: SERVER1
Description:
Backup Exec Alert: Job Failed
(Server: "SERVER1") (Job: "Daily Backup") Daily Backup -- The job failed with the following error: A communications failure has occurred between the Backup Exec job engine and the remote agent.


For more information, click the following link:


'When all else fails.......read the manual'
 
Yes it backs up 2 servers, one of which uses the remote agent.

'When all else fails.......read the manual'
 
In the job log were is the communcication error happening on the local or remote?
 
remote.

The order of the backup was changed to do the remote first and then do the local....and this has worked twice in a row with no problems...

very strange indeed, although it may be coincidence!

'When all else fails.......read the manual'
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top