This article discusses an issue that only occurs when non-persistent Veeam Data Movers are used. The non-persistent data movers are only used when the account provided to Veeam Backup & Replication to connect to a Linux server does not have root or root-equivalent permissions.
To enable the persistent Veeam Data Mover service, edit the credential used to add the Linux server to Veeam Backup & Replication and enable the Elevate account privileges automatically checkbox.
Certain SSH operations involving non-persistent Veeam Data Movers time out after 100 seconds.
The following error message is present, either in the job statistics or the debug logs:
Call execution timeout (100000 ms) (Veeam.Backup.SSH.PerlSoapException)
This error may occur when communicating with any Linux-based server that Veeam Backup & Replication deploys the non-persistent data mover.
Veeam Backup & Replication implements timeouts to protect from application hangs. This timeout may indicate that the non-persistent data mover has become unresponsive or that a performance problem with the operation that was in progress when the timeout occurred.
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.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case