Agent backup job is stuck on one Workstation

[broth-itk]

Dear Veeam Support Team!

In a customers installation (VBR 11.0.0.837 P20210525, Standard, SQL 2016) we configured agent backup for some workstations.
Among all six workstations, only one is having troubles with the backup as data transfer is hanging at a given time (obviously the one from the CEO)

The windows task manager is showing no data transfer on the network anymore, backup status is stuck at

22.07.2021 06:47:52 :: (C:) (475,6 GB) 33,4 GB read at 136 MB/s

All the other workstations in the same LAN segment are working fine.
I checked network connections, drivers, firmware, windows updates on the target workstation and no problems were found. All is up to date.

Is there any log file from the client agent which we could analyze to find the root cause of the non-working backup job?
What action plan do you recommend?

Thanks and best regards,
Bernhard

[Egor Yakovlev]

Hi Bernhard.

Veeam Support rarely shows up on R&D Forums.
As it states when creating a new topic, with technical issues you need to provide a support case ID for this issue.

Log files are under C:\ProgramData\Veeam.

/Thanks!

[broth-itk]

Hi Egor,

thanks!

Your help already made me to progress on the issue:

Code: Select all

[22.07.2021 07:17:40] <01> Info     [AP] Waiting for completion. Id: [0x3bf8826], Time: 00:30:00.0186726
[22.07.2021 07:22:15] <91> Info           [AP] (21c5) output: --asyncNtf:Pipeline timeout: it seems that pipeline hanged.
[22.07.2021 07:22:15] <90> Info           [AP] (0055) output: --asyncNtf:Pipeline timeout: it seems that pipeline hanged.
[22.07.2021 07:22:15] <48> Info           [AP] (7fff) output: --asyncNtf:Pipeline timeout: it seems that pipeline hanged.
[22.07.2021 07:22:16] <42> Info           [AP] (afb4) output: --asyncNtf:Pipeline timeout: it seems that pipeline hanged.
...

I will investigate possible causes and eventually, if required, will open an official suppot request.

Best regards,
Bernhard

[PetrM]

Hi Bernhard,

The error message is quite generic, basically it means that the source Data Mover stopped to send data blocks to the target one. There are many possible causes of such a problem and I strongly recommend to let our support team to work on it otherwise troubleshooting might take significant time.

Thanks!