Veeam error transmission pipeline hanged aborting process

Veeam R&D Forums

Technical discussions about Veeam products and related data center technologies

Pipeline timeout. Transmission pipeline hanged.

Pipeline timeout. Transmission pipeline hanged.

Post by JohnGG » Jun 28, 2016 3:01 am this post

I have been getting something very similar (Processing SQLServer Error: Transmission pipeline hanged, aborting process.), and also (Processing SQLServer Error: Shared memory connection was forcibly closed by peer. Failed to upload disk. Agent failed to process method . ). I replicate to a server first with ESXi on it and then replicate to a Synology 1815+ NAS and it only ever happens when replicating tot he NAS and with the sqlserver, mailserver and all others work fine.
Running latest version of Veeam as well.

Re: Pipeline timeout. Transmission pipeline hanged.

Post by veremin » Jun 28, 2016 6:56 am this post

Re: Pipeline timeout. Transmission pipeline hanged.

Post by JohnGG » Jun 28, 2016 10:27 pm this post

The thing is it doesnt do it all the time, maybe once a week.
Anyway i have updated the NAS and also changed the settings so it seeds to the nas and then remapped the servers to the nas.
Replicating to the server never misses a beat but replicating tot he nas can have issues so i will see when it fails again and then contact support.

Who is online

Users browsing this forum: Google [Bot] and 213 guests

• Main
• All times are UTC
• Delete cookies
• Members
• The team
• Contact us

DISCLAIMER: All feature and release plans are subject to change without notice.

Powered by phpBB® Forum Software © phpBB Limited

Источник

Veeam R&D Forums

Technical discussions about Veeam products and related data center technologies

[ID #03954027] Transmission pipeline hanged

[ID #03954027] Transmission pipeline hanged

Post by KamSandhu44 » Jan 15, 2020 8:54 am this post

I am having issue’s backing up two of my HyperV hosted VMs. I have the latest version of Veeam Backup & Replication (the community edition).

Two Vms are failing with Transmission pipeline hanged, aborting process. (Veeam.Backup.Common.CCppComponentException).

Snipet of the log: —

I am logging to a local NAS, my other seven VMs backup fine.

Any guidance would be great.

Re: [ID #03954027] Transmission pipeline hanged

Post by PetrM » Jan 15, 2020 6:18 pm this post

Generally, this message means that data transmission between Data Mover components is stopped by some reason but connection still exists.

According to log snippet, there is an issue with writing data to a NAS which seems to be overloaded:
— May be you run too many tasks in parallel to the NAS and it would make sense to reschedule backup of 2 problematic VMs
and backup these VMs in a separate job or to decrease concurrent tasks number at the level of repository settings
— There is a hardware issue with NAS itself which affects data write process

Anyway, let’s wait for results of troubleshooting from our support team.

Who is online

Users browsing this forum: No registered users and 4 guests

• Main
• All times are UTC
• Delete cookies
• Members
• The team
• Contact us

DISCLAIMER: All feature and release plans are subject to change without notice.

Powered by phpBB® Forum Software © phpBB Limited

Источник

Veeam R&D Forums

Technical discussions about Veeam products and related data center technologies

Full backup to tape fails with «Transmission pipeline hanged, aborting process»

Full backup to tape fails with «Transmission pipeline hanged, aborting process»

Post by glenn_ » Apr 12, 2021 8:29 am this post

We are trying to do a full backup of a Windows server and this is by now failing with the error «Transmission pipeline hanged, aborting process» and I don’t know why.

What could be the reason for this? Full backup was working for a long time without problems.

But with Veeam 11 I’m experiencing these issues.

Re: Full backup to tape fails with «Transmission pipeline hanged, aborting process»

Post by Natalia Lupacheva » Apr 12, 2021 9:10 am this post

This message can be caused by different reasons, so it’s hard to find the real issue without the logs.
Please keep working with Support and keep us informed.

Re: Full backup to tape fails with «Transmission pipeline hanged, aborting process»

Post by glenn_ » Apr 25, 2021 11:56 pm this post

Re: Full backup to tape fails with «Transmission pipeline hanged, aborting process»

Post by PetrM » Apr 26, 2021 11:13 am this post

The error message is quite generic and informs us that data traffic coming from source Data Mover to a target one is suddenly stopped, it can occur due to many different reasons. We provide support on a «best effort» basis for customers using Community licensed products. You may open a request again, every single attempt increases the chances to get technical support.

Who is online

Users browsing this forum: No registered users and 4 guests

• Main
• All times are UTC
• Delete cookies
• Members
• The team
• Contact us

DISCLAIMER: All feature and release plans are subject to change without notice.

Powered by phpBB® Forum Software © phpBB Limited

Источник

Veeam R&D Forums

Technical discussions about Veeam products and related data center technologies

Error: Transmission pipeline hanged, aborting process.

Error: Transmission pipeline hanged, aborting process.

Post by Wad4iPod » Apr 27, 2022 1:38 pm this post

Error: Transmission pipeline hanged, aborting process.
Windows 10 Pro (10.0.19044)
Veeam Agent for Windows Version 5.0.0.4301
Greetings,
We have one of eight Dell computers that fail to complete a full image backup. It will complete a volume of C: backup.
Near as I can tell the only difference in configuration on this particular pc in the hard drive partition includes an EFI. The partitions are such — EFI (System Partition), OS NTFS, Recovery Partition, Recovery Partition.
The failure seems to occur between after the EFI partition and at the start of the OS C: begins.
The failure occurs when the backup target is a NAS or local PC attached storage.

I have noted a few other posts with this error. The solutions were to log a support case. Does anyone have a resolution to this issue based on a support case or self-resolve?

There is a new Veeam for Windows Agent available (5.0.3). We have yet to install this and test to see if it will resolve this issue.

Re: Error: Transmission pipeline hanged, aborting process.

Post by PetrM » Apr 27, 2022 2:00 pm this post

Thanks for pasting your support case ID but I believe you should wait for the conclusion from your support engineer as the error is quite generic and just says that data flow has ceased. This error can have different root causes and a solution from another case could be useless in your case, anyway the precise examination of debug logs is needed.

Who is online

Users browsing this forum: No registered users and 8 guests

• Main
• All times are UTC
• Delete cookies
• Members
• The team
• Contact us

DISCLAIMER: All feature and release plans are subject to change without notice.

Powered by phpBB® Forum Software © phpBB Limited

Источник

Veeam R&D Forums

Technical discussions about Veeam products and related data center technologies

Veeam agent error — Transmission pipeline hanged, aborting process.

Veeam agent error — Transmission pipeline hanged, aborting process.

Post by jrbaumann » Apr 27, 2021 3:40 pm this post

I’ve been having some issues with Veeam agent since upgrading to VBR 10.0.1.4854. I’ve tried agent 3.02 and 4.0 and I’m having intermittent backup completion with both agents. The job may complete one day then go a few days with out completion. The errors we get are often different for each agent.

I opened case #04730406 with support, but we have not found a resolution.

The agents backup to our Exagrid repositories through a VPN to different data centers. Prior to the upgrade, had very little issues.

Jobs will complete until somewhere between 70-95% and then stop and error out. (Looking through the logs, it looks like it starts backing up to one IP address, then when it stops it looks like its trying to backup to a different ip address, and I’m not sure why)

We tried enabling backup cache, which didn’t make a difference

I was told by one rep that it could be that the repository was busy. i don’t think that is it as I’ve had all jobs paused and the dedup process completed on the SOBR and the job fails, but then the next day it completes. Very frustrating.

A couple of the errors i see are

— Transmission pipeline hanged, aborting process.
— An existing connection was forcibly closed by the remote host Failed to upload disk. Agent failed to process method .

Any help would be appreciated.

If you have any ideas, I’m willing to try as its been a couple weeks now since ive gotten a good backup on a couple of the servers.

Источник

We use Veeam Agent v5 (and v4, same error) for our backups and found we have some Windows 2019 physical servers using a Volume level backup that have recently failed in their Operating System backup with the following error.

The text of the error gives a little bit more to work with.

31/03/2021 10:00:43 AM :: Error: The device is not ready. Asynchronous read operation failed Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. Exception from server: The device is not ready. Asynchronous read operation failed Unable to retrieve next block transmission command. Number of already processed blocks: [0]. Failed to download disk ‘1140af5b-d567-46db-9b74-11c85ca1fb25’.  

So we logged a job with Veeam and their answer was to log a job with Microsoft as it was a server error. Time to have a deeper look before we went down that path.

This was a bit strange, the jobs were happy until a round of Windows Updates done some time in February. Looking at the volume picker below showed what the job was trying to back up.

If we removed the Recovery volume from the selected volumes, there is an error about an incomplete backup but the job runs successfully with the remaining two volumes. Including the Recovery volume into the backup causes it to fail again. A backup of only the Recovery volume also had the same failure.

A hunt of the Veeam forums showed that a few others had the same issue.

Hunting around with PowerShell provided this from the Recovery partition

(Get-Partition).Where({$_.type -eq "Recovery"}) | FormatList


UniqueId             : {00000000-0000-0000-0000-100000000000}600508B1001C480977D3EE56F92B41FB

AccessPaths          : {\?Volume{62480ffe-130d-4cfd-a21f-e44b531d5a34}}

DiskNumber           : 4

DiskPath             : \?scsi#disk&ven_hpe&prod_logical_volume#5&25daa67a&0&000100#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

DriveLetter          :

Guid                 : {62480ffe-130d-4cfd-a21f-e44b531d5a34}

IsActive             : False

IsBoot               : False

IsHidden             : False

IsOffline            : True

IsReadOnly           : False

IsShadowCopy         : False

IsDAX                : False

IsSystem             : False

NoDefaultDriveLetter : True

Offset               : 1048576

OperationalStatus    : Offline

PartitionNumber      : 1

Size                 : 499 MB

Type                 : Recovery

Operational Status is Offline, how about we look at that. So with

(Get-Partition).Where({$_.type -eq "Recovery"}) | Set-Partition -IsOffline $False

We set the Recovery partition to being online, run a backup job with the Recovery volume included and it works. Huzzah!

Then a reboot to test and we found that the Offline setting returns to $True after a reboot and the Veeam Agent job would fail. Setting a PowerShell script with the above line in it and making it run as a Scheduled Task on Startup ensured the Recovery volume was online. Not sure if that is best practice, but it makes the job run and our backup engineer happy.