Replication fails: Failed to connect to service 'ASN'. Destination host 'x.x.x.x' is unreachable or a firewall may be blocking the connection.

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

Hello,

I'm having a hard time to implement an offsite replication with Acronis Backup Advanced 11.7.50064

We set up an Acronis storage node on a offsite backup server, where backups shall be replicated after completing the local backup. According to the network documentation only TCP port 9876 is needed for this, and also the replication will be carried out by the local storage node (not by the Client on the backed-up machines).

Looking into the communication with Wireshark only TCP 9876 seems to be used between the local backup Server and the offsite storage node - as expected, and so it is configured in our firewalls. But still every replication fails, either as a second step in a regular backup job, or in a manual replication/cleanup task.

The tasks run for a long time before this is stopped, and the jobs can't really be stopped manually.

Adding the offsite storage node went fine, creating the offsite vault in the storage node, too. I can browse and refresh the offsite vault, and I can see the folder structure created on the offsite storage node.

But why the heck can't Acronis replicate anything to the offsite storage node?

I also tried using an SMB share instead of a storage node. Same story, creating the vault was fine, replication failed.

Log shows:

Command 'Running backup plan '[jobname]'' has failed.
Additional info:
--------------------
Error code: 61
Module: 309
LineInfo: 4a8728dc8a1c9510
Fields:  $module : mms_vs_50064
Message: Command 'Running backup plan '[jobname]'' has failed.
--------------------
Error code: 41
Module: 307
LineInfo: e6792a5ee190de98
Fields:  $module : agent_protection_addon_vs_50064
Message: Failed to execute the command.
--------------------
Error code: 53
Module: 309
LineInfo: 2e7e9e174f1fb70e
Fields:  $module : agent_protection_addon_vs_50064
Message: Several activities have not succeeded. Details:
346D5717-3ACD-45C1-85C7-0D30C9FF3258:
Error 0x1350016: TOL: Failed to execute the command. The 'Replication' command initiates backup replication.
| line info: 0x8d165e86fb819666
| TraceLevel: 0x1
| $module: staging_command_addon_vs_50064
|
| error 0x175000b: Failed to resolve the secondary location. Location: 'arl:/ECF81237-C38E-4262-9142-E1AA6A28FDFA/2E40D79E-463A-47BD-BFD6-D0D5B1E83BF4'; Archive: '[archivename]'.
| line info: 0xdfd7515541030cee
| $module: staging_command_addon_vs_50064
|
| error 0x1350016: TOL: Failed to execute the command. This command resolves the secondary location for the backup replication.
| line info: 0x8d165e86fb819666
| TraceLevel: 0x1
| $module: staging_command_addon_vs_50064
|
| error 0xa100d4: Failed to find archive '[archivename]'.
| line info: 0xb320396adfe3da3
| IsReturnCode: 0x1
| $module: disk_bundle_vs_50064
|
| error 0xad0003
| line info: 0x1fb741a8992b2bd0
| $module: disk_bundle_vs_50064
|
| error 0xad0026: Failed to connect to service 'ASN'. Destination host 'x.x.x.x' is unreachable or a firewall may be blocking the connection.
| line info: 0x1c13eceb383289c1
| ServiceID: 0x22
| $module: mms_vs_50064

CEA6349A-AEEA-4A4C-977F-E9AEB674103D:
Error 0x1350016: TOL: Failed to execute the command. The 'Replication' command initiates backup replication.
| line info: 0x8d165e86fb819666
| TraceLevel: 0x1
| $module: staging_command_addon_vs_50064
|
| error 0x175000b: Failed to resolve the secondary location. Location: 'arl:/ECF81237-C38E-4262-9142-E1AA6A28FDFA/2E40D79E-463A-47BD-BFD6-D0D5B1E83BF4'; Archive: '[archivename]'.
| line info: 0xdfd7515541030cee
| $module: staging_command_addon_vs_50064
|
| error 0x1350016: TOL: Failed to execute the command. This command resolves the secondary location for the backup replication.
| line info: 0x8d165e86fb819666
| TraceLevel: 0x1
| $module: staging_command_addon_vs_50064
|
| error 0xa100d4: Failed to find archive '[archivename]'.
| line info: 0xb320396adfe3da3
| IsReturnCode: 0x1
| $module: disk_bundle_vs_50064
|
| error 0xad0003
| line info: 0x1fb741a8992b2bd0
| $module: disk_bundle_vs_50064
|
| error 0xad0026: Failed to connect to service 'ASN'. Destination host 'x.x.x.x' is unreachable or a firewall may be blocking the connection.
| line info: 0x1c13eceb383289c1
| ServiceID: 0x22
| $module: mms_vs_50064

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

 

Any help appreciated! EN or DE

Tue, 07/04/2017 - 13:34
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

Unfortunately the documentation on this seems to be wrong: in the userguide for Acronis Backup Advanced 11.7, chapter 4.5.1 Supported Locations it is written:

Which machine performs the operation?

Copying, moving or deleting a backup from any location is initiated by the agent that created the backup, and is performed:　

 By that agent, if the location is not a managed vault.

 By the corresponding storage node, if the location is a managed vault. However, copying or moving the backup from the managed vault to the cloud storage is performed by the agent that created the backup.

As follows from the above description, the operation will be performed only if the machine with the agent is powered on. If the operation is scheduled, the schedule will use that machine's date and time.

---------

While both our first backup location is a managed vault AND the offsite storage node vault is a managed vault, I was supposing that the operation of replication does NOT need any interaction with the original backup source / client on that machine.

A test with starting a "Replication/cleanup 1st location" definately interacts with the client on the backed up Server, as one can clearly see at the now active task monitor icon on that machine:

image

This leeds to the additional requirement in this scenario to open TCP 9876 from all clients to the offsite backup location - clearly unwanted, also unnecessary, technically doubtful and potentially dangerous in my opinion.

Why is this so?

Is the documentation wrong or at least very misunderstandable?

Is this a bug?

Can this be avoided?

Wed, 07/05/2017 - 11:34
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello Ulrich,

The article Acronis Backup: Troubleshooting Replication or Staging Issues will provide more information on the replication algorithm and potential issues. 

When the source location of replication is Managed vault then the storage node performs replication. However Agent that was doing the backup initiates this process and monitors it.

Thu, 07/13/2017 - 08:59
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 1
Comments: 2

Hello Ekaterina,

thanks for link. Indeed section #5 under "About replication" explains what I was observing:

"When the source location of replication is Managed vault then the storage node performs replication. However Agent that was doing the backup initiates this process and monitors it."

However, I will not pursue this any further, as I have upgrade to v12.5 in the meantime.

Still having some troubles there, but I'm already investigating this with Acronis support.

 

Thu, 07/13/2017 - 09:10