We have 2 protection groups, each with jsut ~50 agents. Every day we have a couple of errors (Failed to establish connection...) for the first backup attempt of some agents. Usually the first retry is then successful. Those are critical SAP systems and we do not see any general connection, timeout or latency issues.
Support feedback:
"From the behavior you described a few agents failing initially but succeeding on the first retry this does not look like a persistent connectivity problem, but rather a temporary resource or connection slot contention when multiple agents start at the same time."
This is the first time we use Veeam for agent backups and from support if feedback it sounds that even out low number of agents in one protection group (=backup job) is already too much for Veeam. This is unexpected. We also do not want to split up agents in very small PGs of just 10.
Is there any other way to debug this or any easy way to add some delay to the start of individual agent backups? I thought about a pre-script that jsut adds some delay but this requires application aware backup which we currently not use.
[27.08.2025 21:30:06.013] <140732681350976> cli | Thread [Establish connect to VBR xxxx:10006; xxxx:10006; 10.11.38.20:10006 by certificate.]. Failed.
[27.08.2025 21:30:06.013] <140732681350976> | ERR |Thread [Establish connect to VBR xxxx:10006; xxxx:10006; 10.11.38.20:10006 by certificate.](140732681350976) failed.
[27.08.2025 21:30:06.013] <140732681350976> | >> |Reconnectable protocol device was closed.
[27.08.2025 21:30:06.013] <140732681350976> | >> |--tr:Failed to read data from throttled device.
[27.08.2025 21:30:06.013] <140732681350976> | >> |--tr:in virtual std::streamsize io::CThrottledIoDev::read(byte_t*, size_t) at /mnt/Sources/CommonLib/io/ThrottledIoDev.cpp:37
[27.08.2025 21:30:06.013] <140732681350976> | >> |--tr:IoDevBIO: I/O error occurred during read operation.
[27.08.2025 21:30:06.013] <140732681350976> | >> |--tr:Failed to establish SSL connection.
[27.08.2025 21:30:06.013] <140732681350976> | >> |Failed to establish SSL connection (Unexpected error).
[27.08.2025 21:30:06.013] <140732681350976> | >> |--tr:in io::io_dev_ptr_t crypto::openssl::CSslContext::Connect(io::io_dev_ptr_t, bool, bool) at /mnt/Sources/CommonLib/crypto/openssl/SslContext.cpp:200
[27.08.2025 21:30:06.013] <140732681350976> | >> |Unable to authenticate on backup server xxxx:10006; xxxx:10006; 10.11.38.20:10006.
[27.08.2025 21:30:06.013] <140732681350976> | >> |--tr:in io::io_dev_ptr_t vmbplatform::vbr::CSslVbrConnection::Authenticate(io::io_dev_ptr_t) at /mnt/Sources/VmbPlatformLib/vmbplatform/vbr/conn/SslVbrConnection.cpp:179
[27.08.2025 21:30:06.013] <140732681350976> | >> |Failed to establish connection to xxxx:10006; xxxx:10006; 10.11.38.20:10006
[27.08.2025 21:30:06.013] <140732681350976> | >> |--tr:in void vmbplatform::vbr::CSslVbrConnection::EstablishConnectProc(io::io_dev_ptr_t) at /mnt/Sources/VmbPlatformLib/vmbplatform/vbr/conn/SslVbrConnection.cpp:143
[27.08.2025 21:30:06.013] <140732681350976> | >> |An exception was thrown from thread [140732681350976].
[27.08.2025 21:30:06.013] <140734174654272> alg | Traffic history max size: [6].
[27.08.2025 21:30:06.022] <140734157745984> alg | Reconnectable protocol stop request was received on {0e8fad7f-a7ba-456c-84eb-3711a88750d5}.