Skip to main content

Failed to connect to storage node

Thread needs solution
Beginner
Posts: 5
Comments: 3

Dear Acronis Support,

After several days we receive an error regarding 2 specific servers.
Please see below:

 

------------------------------------------------------------------------------------------------------------------------------------------------------

Command 'Backing up' has failed.
Additional info:
--------------------
Error code: 61
Module: 309
LineInfo: 4a8728dc8a1c9510
Fields:  $module : service_process_vs_50058
Message: Command 'Backing up' has failed.
--------------------
Error code: 22
Module: 309
LineInfo: 8d165e86fb819666
Fields:  TraceLevel : 1, $module : gtob_backup_command_addon_vs_50058
Message: TOL: Failed to execute the command. The 'Backing up' command backs up the specified data to the specified location.
--------------------
Error code: 200
Module: 161
LineInfo: b320396adfe3b54
Fields:  IsReturnCode : 1, $module : disk_bundle_vs_50058
Message: Failed to get archive URIs from location 'arl:/337FB62D-B2B5-4D3D-BF17-A95A635DD0B5/83BBB502-FA52-48D6-8F6C-06A7B567432A'.
--------------------
Error code: 8
Module: 154
LineInfo: f9cb46cc20081f0c
Fields:  $module : disk_bundle_vs_50058
Message: Failed to connect to the storage node.
--------------------
Error code: 3
Module: 173
LineInfo: 67e2725e54112c89
Fields:  $module : disk_bundle_vs_50058
Message:
--------------------
Error code: 3
Module: 173
LineInfo: 1fb741a8992b2bd0
Fields:  $module : disk_bundle_vs_50058
Message:
--------------------
Error code: 3
Module: 173
LineInfo: 90fb8a255b1df5a1
Fields:  ServiceID : 34, $module : service_process_vs_50058
Message: Failed to establish connection.
--------------------
Error code: 20
Module: 4
LineInfo: 4d5187f54acfdb00
Fields:  $module : service_process_vs_50058
Message: Authentication has failed.
--------------------
Error code: 1078
Module: 3
LineInfo: a3cdb7a26e18c8d9
Fields:  $module : service_process_vs_50058
Message: Authentication has failed.
--------------------

------------------------------------------------------------------------------------------------------------------------------------------------------

- We already removed an added the Storage node from the management server, did not work
- We already restarted the Acronis Services from the failing servers, did not work
- We restarted the failing servers, did not work
- A colleague of mine also re-deployed the Acronis agent on one of these servers, did not work
- we also wanted to be sure if the issue was not because of the Backup Job. After creating a testjob, we received the same error when only backupping the failing servers.
 

Any ideas?
Thanks in advance,
David Dahles

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi David,

The issue is likely to be related to outdated credentials cache on the agents side, e.g. the credentials used to access the managed vault (on Storage Node) are no longer valid. One thing to try to confirm is to create a new backup plan for one of the affected machines by connecting to it directly from Acronis Backup Management Console (do not create plan while connected to Acronis Management Server) and providing credentials to access Storage Node (if possible create a new vault administrator and use its credentials). If this doesn't help then the issue should be investigated with help from our support team.

Thank you.

Beginner
Posts: 5
Comments: 3

Dear reader,

Thank you for you information. It seems indeed that it was asking for the credentials when connecting directly to the affected host.
The strange thing is when creating a new backup job from within the machine, and run that job, it is now indicating
"The operation was interrupted due to a problem with network connection to the required file. Time trying to connect to the location: ......

When looking this up at this forum, people are also sometimes referring that these are issue's regarding the vault.
It this also regarding the vault, or is this really a different issue/subject that I am now talking about.

Many thanks again,

David

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi David,

The problem could be lack of connectivity between the agent and Acronis Storage Node (ASN), e.g. there is proper connection between Acronis Management Server (AMS) and ASN (which is why there are no errors when you create a backup plan while connected to AMS), but since the backup is performed by the agent - it requires to have connection. The connection is established using the registration address of ASN in AMS: which in practice means that the hostname of ASN (if it was registered by hostname) must be properly resolved to IP from the agent side and there is no firewall blocking the connection.

Thank you.