Veeam Known Issues: Network Failure and SSL Errors

Veeam Known Issues: Network Failure and SSL Errors

Veeam Known Issues: Error Observed by Underlying BIO

Issue

Discontinuous network failures may occur when communicating with the VMware host. This is accompanied by errors such as:

“Error observed by underlying BIO: No such file or directory Detail: ‘SSL connect failed in tcp_connect()’, endpoint:”

Error Illustration

In many cases, the backup process continues successfully on a subsequent attempt.

Cause

This error often arises due to unsupported network configurations in VMware. Specifically:

  • A VM Kernel NIC with management enabled is set on a port group that is no longer suitable for the VM.
  • Even if the VM port management option is added to a network, VMware may display warnings.

In Veeam backup, discontinuous alerts are triggered, such as:

“Error observed by underlying BIO: No such file or directory tail: ‘SSL connect failed in tcp_connect()’, endpoint:”

Despite the alerts, Veeam's configuration often allows backup jobs to succeed after a few retries.

Solution

To resolve this issue:

  • Remove the Management VMKernel port from the VM network.
  • Alternatively, move the VM to a network without a management VMKernel port.

These actions will eliminate the errors and allow backups to complete without interruptions.

Popular posts from this blog

How to Import Azure Wiki Contents into a JSON File

How to Resolve VSS Writer Errors Without Rebooting