Case ID# 03124279
I'm having intermittent problems with a Veeam linux repository. This repository is shared between a Veeam Backup and Replication server and a separate Veeam Cloud Connect server. I understand that you can share a repository in this way, but must take into account the number of concurrent tasks configured for this repository on each Veeam Backup server. And that the two servers obviously can't know how many tasks the other is running. I understand that the recommendation is for 1 task per core.
The repository in question is a physical machine with 2 CPUs, 12 cores and 96GB of RAM. I'm seeing intermittent backup copy job failures with the error No connection could be made because the target machine actively refused it 10.x.x.x:2514.
Is there a way to debug this issue on the linux repository server itself? When the problem is happening I can't find any issues on the linux server. It has plenty of free RAM, CPU and disk IO. It's clear that at some point the backup repository is refusing backup copy job data for some reason, but I've searched the syslog and auth logs for issues related to ssh or anything else and can't find any problems. I also notice that each backup copy job even when idle maintains a running process in the form /tmp/VeeamAgentxxxx, so I'm not sure how to work out if I'm exceeding the recommended number of tasks at a given time.
In short, does Veeam log anything on the linux repository that could help me determine why it seems to be refusing connections some of the time? How can I identify which processes to count to ensure I'm not exceeding 1 task per core?