Backup Exec 2010 R3 - Communications failure between Job Engine and Remote Agent
Hi,
I just set up a new Backup Exec 2010 R3 installation with a tape loader and partitions and etc.. all the good stuff. The machine backs itself up, an AD server and an MSX2010 server. The credential test for the job reports all success connecting to the resources.
The job log itself shows stuff being backed up from the local machine, the AD server and the Exchange Server (Information Stores, etc..) which all goes fine. Its only at the end of the Job log in a seperate section that this communication failure error is reported as follows:
Completed status: Failed
Final error: 0xe00084f9 - A communications failure has occurred between the Backup Exec job engine and the remote agent.
Final error category: Resource Errors
I follow the support link to here:
http://www.symantec.com/business/support/index?page=content&id=TECH28737&actp=search&viewlocale=en_US&searchid=1334281890371
But in my Logon Account Management screen I already have a System Logon Account which is my backupexec service account. Note that the system itself is logged on as another user (console user for the machine).
I restarted all the BE services but this did not help.
Do I perhaps not have enough permissions assigned to the backupexec service account (it is a domain administrator)? I assume since it does not fail to backup any of the remote machines, that this problem is referring to the remote agent installed on the BE server itself?
Anyway I am puzzled, so if anyone can help it would be appreciated.
Cheers,
Luke
Hi Luke,
Check the TN below for the BESA requirements in order to backup Exchange 2010.
http://www.symantec.com/business/support/index?page=content&id=HOWTO21796
If you're getting that error message though, it could be that a RAWS agent is stopping on a particular server.
In this case, up the level of logging for a backup run and see where it fails.
You can also check each server's RAWS event log to see if the RAWS agent is failing, and once you find it, make sure that the AV or firewall isn't blocking it from running for whatever reason.
Thanks!