After Health Check of Backup Copy Job Verification Fails

[manofbronze]

Opened a ticket with Veeam on this issue (#01904913), but never got to a satisfactory resolution, so I thought I would share with the community to see if anyone has encountered, and successfully resolved, this issue.

When our backup copy jobs perform a "health check", they always fail when they get to the "verification of files" stage. Here is a sample of the error:

Backup Copy job: Sample1
Created by VEEAMBACKUP\Administrator at 6/4/2016 8:37 AM.Error
5 of 5 VMs processed
Thursday, January 12, 2017 12:00:19 AM
Success5Start time12:00:19 AMProcessed30.1 GBBackup size13.1 GBBackup files health check has been completed
Failed to perform backup file verification Error: ChannelError: ConnectionAborted
Warning0End time4:35:32 AMRead30.1 GBDedupe1.0x
Error0Duration4:35:12 Transferred13.1 GB (2.3x)Compression2.3x
Details
NameStatusStart timeEnd timeProcessedReadTransferredDurationDetails
sampleDC01Success3:40:58 AM3:48:17 AM1.1 GB1.1 GB698.7 MB (1.7x)0:06:29
sampleEX01Success3:40:59 AM4:03:59 AM18.3 GB18.3 GB5.2 GB (3.5x)0:22:14
sampleFile01Success3:41:04 AM3:59:13 AM1.5 GB1.5 GB975.3 MB (1.6x)0:15:43
sampleRB01Success3:41:05 AM3:54:11 AM2.9 GB2.9 GB1.7 GB (1.7x)0:12:16
sampleRDS01Success3:41:06 AM4:02:54 AM6.3 GB6.3 GB4.5 GB (1.4x)0:21:08

Veeam Backup & Replication 9.5.0.711

The backup copy job itself completes, but the health check always fails with this error. I have checked all the usual suspects: Windows firewall - disabled on all Veeam systems, Anti-virus - Not installed on any Veeam Systems, Network Connectivity - excellent, Available disk space - healthy, rebooted repository, rebooted WAN accelerators, applied latest MS patches to all Veeam systems, etc... No luck.

Anyone else have an idea where else to look, tricks to try?

[foggy]

I see that the case was closed back in September, since the error didn't show up after "applying the most recent Windows patches AND disabling Windows firewall on the repository servers". Are you seeing the same issue again? I then recommend re-opening the case for further investigation (escalation will probably be required). Thanks.

[manofbronze]

Yes. Seeing the same issue again. Re-opening the case.