Backup Failed

Thread needs solution

E.J. McNaughton

Beginner

Posts: 1

Comments: 0

Here is the error message. Any suggestions?

Had issue with authentication and resolved then got this error.

Failed to execute the command.
Additional info:
--------------------
Error code: 41
Module: 307
LineInfo: e6792a5ee190de98
Fields: $module : agent_protection_addon_vs_50064
Message: Failed to execute the command.
--------------------
Error code: 2
Module: 329
LineInfo: 8edc81ea38faba0a
Fields: TraceLevel : 1, $module : gtob_backup_command_addon_vs_50064
Message: Step 'Post-backup replication/cleanup' has failed.
--------------------
Error code: 22
Module: 309
LineInfo: 8d165e86fb819666
Fields: TraceLevel : 1, $module : staging_command_addon_vs_50064
Message: TOL: Failed to execute the command. The 'Replication' command initiates backup replication.
--------------------
Error code: 22
Module: 309
LineInfo: 8d165e86fb819666
Fields: TraceLevel : 1, $module : staging_command_addon_vs_50064
Message: TOL: Failed to execute the command. The 'Replicating backups/cleaning up archives (1st location)' command copies backups from the current location to the next secondary location.
--------------------
Error code: 22
Module: 309
LineInfo: 8d165e86fb819666
Fields: TraceLevel : 1, $module : staging_command_addon_vsa64_50064
Message: TOL: Failed to execute the command. The 'Replicating backups/cleaning up archives (1st location)' command copies backups from the current location to the next secondary location.
--------------------
Error code: 3
Module: 7
LineInfo: a65ac6a07015ab26
Fields: $module : storage_server_archive_manager_vsa64_50064
Message: Read error.
--------------------
Error code: 106
Module: 64
LineInfo: b0ed2a9ff6bee755
Fields: $module : storage_server_vsa64_50064
Message: Failed to continue the operation because session 'CC72E566-254E-4E22-A844-3907EDF42222' cannot be found.
--------------------

Mon, 02/10/2020 - 15:24

Maria Belinskaya

Support specialist

Posts: 0

Comments: 1224

Hello E.J. McNaughton,

welcome to Acronis forums!

When a backup/replication and other operations with backups are started on a managed vault, the backup session is opened on the Acronis Storage Node side. If there is no progress, then this session will be stopped by timeout (12 hours by default).

For example, when a backup/replication operation is running to the tape vault, then the tape drive will be locked by this operation and other replication/backup tasks will wait till the tape drive is unlocked. When there are multiple operations started, then the problem can appear if summary operations time is more than this timeout.

In this situation, I would recommend doing the following:

- first of all please, update the software to the latest available build in your account (there were some fixes added that should update the timeouts);

- besides that, please check if you can schedule the tasks to run at different time;

- you can also increase the timeout using the following way:

on the server with Acronis Storage Node open Start -> Run -> regedit.exe open HKEY_LOCAL_MACHINE\SOFTWARE\Acronis\ASN\Configuration\StorageNode key find and edit WorkingSessionIdleTimeOut value change it to 172800 (48 hours) then please open Start -> Run -> services.msc restart Acronis Storage Node service.

Fri, 02/21/2020 - 17:52