Depending on the situation, it may be necessary to troubleshoot an unresponsive server, troubleshoot a performance issue, or extend the timeout.
When the error refers to an SSH connection to a Linux Repository, the most common resolution is to reboot either the repository server, or the storage device (such as a NAS mounted via NFS) connected to the underlying Linux server. A repeated need to reboot to work around this error may indicate insufficient resources allocated to the repository server.
To extend the timeout, create the following registry value on the Veeam Backup & Replication server:
Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: MaxPerlSoapOperationTimeout
Value Type: DWORD (32-Bit) Value
Value Data [DEC] (Default): 100000
Time out value is in milliseconds, so the default is 100 seconds. Increase the value as needed, a good starting point is to double the value.
The new timeout value will be used the next time a non-persistent data mover agent is deployed on a remote linux server.