KB1976: Jobs fail with “Error: Completion Timeout Occurred”
www.veeam.com › kb1976Dec 12, 2014 · The IP connection timeout itself can also be increased by adding the following registry key to HKey_local_machine\software\Veeam\veeam backup and replication\. ConnectByIPsTimeoutSec. Type: REG_DWORD. value: 1200. Click here to send feedback regarding this KB, or suggest content for a new KB. To report a typo on this page, highlight the typo ...
KB1857: Unable to allocate processing resources
https://www.veeam.com/kb185713.02.2014 · Too many jobs are running at a time for the number of concurrent tasks set across all proxies available to the job that failed. Proxies may be unavailable (Shutdown, not connected to the network, etc.). The existing set of backup proxies does not have enough resources to process the backup jobs in a timely manner.
KB1857: Unable to allocate processing resources
www.veeam.com › kb1857Feb 13, 2014 · Too many jobs are running at a time for the number of concurrent tasks set across all proxies available to the job that failed. Proxies may be unavailable (Shutdown, not connected to the network, etc.). The existing set of backup proxies does not have enough resources to process the backup jobs in a timely manner.
KB1982: Release Notes for Veeam Backup & Replication 8.0 Patch 1
www.veeam.com › kb1982Dec 25, 2014 · If a Hyper-V cluster node goes offline during backup from shared volume snapshot, and does not recover until the Veeam job fails, CSV volume backup infrastructure resource will not be released by the scheduler. As the result, other jobs waiting to process VMs from the same volume may remain hanging in the "Resource not ready: Snapshot" state.