Backup proxy Configuration for VMware VSAN - doesn't work

[Vlajko007]

Hi,

I wanted to optimize Veeam configuration for use with VMware VSAN and I deployed proxies for each of 6 ESXi nodes within the cluster. I deployed proxies on Windows Server 2019. I configured everything based on this article: https://www.veeam.com/kb2273
After that, a lot of backup jobs were failed, but every time the same VMs.
I restored the old configuration with 3 proxies on Windows Server 2012 R2, without affinity rules, and it works fine.

We have the latest version of Veeam Backup an Replication.

What can be a potential issue here?

Thank you.

[PetrM]

Hi Vladimir!

Welcome to our Community Forum!

Which error message do you see in the job statistics window for failed VMs or in the html report?

Anyway, it would be challenging to say what is the reason of failures without debug logs analysis so it makes sense to create a support case and let our support team to investigate the issue.

Thanks!

[Vlajko007]

Hi,

These are the most usual errors I get. These errors are from different backup tasks.

I didn't have these errors before I deployed proxies.

Code: Select all

"Error: VDDK error: 14009 (The server refused connection). Value: 0x00000000000036b9
Failed to upload disk.
Agent failed to process method {DataTransfer.SyncDisk}.
Exception from server: VDDK error: 14009 (The server refused connection). Value: 0x00000000000036b9
Unable to retrieve next block transmission command. Number of already processed blocks: [28795].
Failed to download disk.

Code: Select all

Error: Data error (cyclic redundancy check).
Asynchronous read operation failed
Failed to upload disk.
Agent failed to process method {DataTransfer.SyncDisk}.

Code: Select all

Error: An unexpected network error occurred.
Failed to write data to the file [\\NAS\veeam_folder\Vm's Backup\Vm's BackupD2019-09-16T4566870_6ff5.vib].
Failed to download disk.
Reconnectable protocol device was closed.
Failed to upload disk.
Agent failed to process method {DataTransfer.SyncDisk}."

[wishr]

Hi Vladimir,

There are several possible root causes of such errors, so I'd suggest you reach out to our technical support team directly for further investigation. Please, do not forget to post your case ID here for our reference.

Thank you