So, this is a bit of a weird one.
tldr: Restarting the server makes the clients (
UrBackupClientBackend.exe) on all machines to load CPU to 50 % (regardless of type).
UrBackup Server 2.4.13on Debian Stretch (Jessie when it first occured)
UrBackup Client 2.4.10(Windows 7, Windows 10, Server 2008 and 2016 – ie. everywhere. No UrBackup Clients on Linux VMs which I backup up differently.)
The long story:
My UrBackup server is running on a physical Debian machine than up until November had uptime of 500+ days, and then it crashed. I went to the site, server booted up okay (it’s a HP Microserver N54L I believe), backups seemed to be working (not much else running on this server otherwise apart from some rsync scripts every now and then)…
Except, a week later users started reporting the apps on a terminal server being too slow, which was a a bit weird to me since I had just moved the terminal server VMs from old school HDDs to NVMe SSDs.
Went to Zabbix and sure enough, the CPU load was constantly high across all machines (servers and workstations), and it started the very hour I have booted the UrBackup server back up (it was down for two days). Weird.
So I logged in to Hyper-V and noticed all the Windows VMs had unusually high CPU load for the time of the day (10 pm). Long story short, I went into each one, and there it was, on every VM there it was –
UrBackupClientBackend.exe, averaging 50 % CPU - regardless of how much CPU was assigned. Roughly 50 % on all cores, even on the HyperV itself. Compounded, it made everything noticeably slower.
The solution was easy though, simply restarting the UrBackup service everywhere.
Everything worked fine for a few weeks, then I decided to upgrade the server from Jessie to Stretch (and then eventually to Buster), which of course needed yet another restart.
I’ve since tinkered with some Zabbix CPU load triggers and sure enough, within a day I got emails that the CPU load was excessively high for a long period of time. Logged into Zabbix and yet again the CPU load started almost immediately after the UrBackup server rebooted.
Restarted the services again, everything back to normal.
Now I don’t plan on restarting the server often, but anyone has any ideas what might be causing this and where to look next time I will be restarting the server (the whole physical machine?
I am not yet sure if
service urbackupsrv restart would cause the same issue, I’d assume it would, but that’s definitely an experiment for a weekend.