04-29-2016 09:42 AM
We had Symantec 2012 when the error started about a week ago, since then we have upgraded to Symantec 15. It seems that about a week ago we added another instance to our DB for a test environment. After that the Backup Exec started throwing communication errors. Of course none of the credentials or IPs have changed. I wouldn't think that adding another instance to the DB would not cause this kind of issue. I'd appreciate any ideas you may have. Thanks.
From the backup log:
Job ended: Friday, April 29, 2016 at 2:02:32 AM
Completed status: Failed
Final error: 0xe0000f25 - A communication failure occurred when attempting to connect to this server. Some common causes for this error are: the computer name is typed incorrectly, the computer is not powered on, a Backup Exec agent is not installed, or the network is improperly configured.
Final error category: Job Errors
05-01-2016 11:08 PM
Would recommend the following -
1) First, try recreating the backup job (specifically reselect the data which is to be backed up)
2) If this doesn't help, then readd the SQL Cluster to the Backup & Restore tab and create a new backup job.