Acronis Backup & Recovery 11 advanced Server fails to connect to storage node

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 4

I am trying to do a backup to my external USB hard drive. I have it as a "managed" vault. It was working fine and all of a sudden I get the following error and the backups fail now - yet I can see & connect to the node when editing the backup plan. I tried the suggestions here (http://forum.acronis.com/forum/17615) but no luck. Any thoughts?

--------------------
Log Entry Details
--------------------
Type: Warning
Date and time: 2/10/2012 1:25:33 PM
Backup plan: [None]
Task: [None]
Managed entity type: [None]
Managed entity: [None]
Machine: lhfilesvr2.LH.local
Code: 10,551,313(0xA10011)
Module: 161
Owner: Acronis Agent User
Message:
Failed to connect to the storage node.
Additional info:
--------------------
Error code: 17
Module: 161
LineInfo: cbaf98c283a3b031
Fields: host : lhvhsvr1.lh.local, $module : C:\Program Files\Acronis\BackupAndRecovery\DiskBundle.dll
Message: Failed to connect to the storage node.
--------------------
Error code: 3
Module: 173
LineInfo: 67e2725e54112c8e
Fields:
Message:
--------------------
Error code: 17
Module: 173
LineInfo: 1c13eceb38328974
Fields:
Message: Error: Invalid address was specified.
--------------------
--------------------

Fri, 02/10/2012 - 23:32
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 24
Comments: 3268

Hello Don,

Thank you for finding time to open a thread regarding this question. 

There can be several possible reasons,  like the address can't be resolved from this machine, might be the lack of connectivity, damaged USB port, or a service is not started.  We have this issue described in this KB article alongside with the solutions. Please follow the instructions, and let us know if the problem remains.

Should you have any questions or concerns, let us know,  we  will  be glad to help.

Thank you.

Wed, 02/15/2012 - 17:37