Hi,
We have a severe problem with Urbackup clients (Windows).
When taking image backup, we see UrBackup Client absorbing all available memory within a minute and after a while the PC becomes veeerrrrry slow (e.g. 3 minutes to open the start menu).
This happens exactly when the image backup starts and keeps as long as the backup is in progress. If we stop the backup, the PC gets responsive again.
I have tried installing older client versions in 2 PCs, same behavior (2.5.24, 2.5.23, 2.5.21).
I have not found anything in the forum for Windows clients, except of a few unanswered posts.
What I have found is that for linux clients, we could edit the /usr/lib/systemd/system/urbackupclientbackend.service file to set specific values on a few MemoryXYZ variables, e.g.:
MemoryAccounting=true
MemoryHigh=2G
MemoryMax=3G
MemorySwapMax=512M
Is there any similar configuration option for Windows Clients?
We have checked and the bottleneck is not the server. The same thing happens either with a maximum of 1 concurrent backups or more. Server resources seem normal.
I have also tried disabling windows swap file, same results.
All client PCs are on Windows 10 or 11, on Gigabit Ethernet, last version 2.5.25
Urbackup Server 2.5.33 runs on Linux, 10Gb Ethernet.
Thanks for the question, I am not sure for that, but I tried at least 10 times to start image backup on 4 different clients. All had 16 or 32 GB of RAM and went from ~“6GB used” to maximum in about 1 minute since the image backup started.
Also, some times this excessive memory usage just does not happen. It may depend on some Windows System state.
Is it possible to alter configuration to send maximum of memory usage in Windows Urbackup clients, as it is with Linux clients?
Same problem here. Had this issue for over a year now. Just upgraded to 2.5.28 but it’s still happening. UrBackupClientBackend.exe will eat all available memory after starting backup. And it’s not directly visible in Task Manager, but you can find out in Process Explorer as “private bytes”. Not sure if it happens always, on which type of backup etc, but it happens quite offten. You will notice other programms will start to crash (due to lack of memory) and I’ve to kill UrBackupClientBackend then. Sadly, it makes UrBackup unusable
Please find some screenshots below. Those were taken once backup has been completed. Usually, working set / value visible in Task Manager is a much smaller value (not suspicious at all), so even if your PC is behaving wired, you might not notice it’s a UrBackup issue, but Private bytes are always high (and your general RAM usage drops from 97% to 50% if you kill UrBackupClientBackend.exe).
Let me investigate further, as I’ve a feeling it’s not happening on regular basis. I’ve run incremental file backup now, 1h after backup has finished, this is the memory usage (high, but Windows still behaves normally):
Then, without restaring, I’ve run incremental image backup, after that:
I’m not 100% sure what’s happening, but quite often my PC lacks RAM and then I’ve to kill UrBackupClientBackend.exe in order to make Windows usable again.
To throw an alternate view… Win10 Pro PC Client => Linux Server here with a Incremental File backup running at the moment and nothing even noticeable. 66% complete. I run Image and File backups and don’t notice hiccups.
I’m the only user on this PC. Eset AV on this here. Multiple drives (SSD and Spinning) and all kinds of mess of files scattered across those drives.
Just noticed the client is 2.5.25, server 2.5.33. Will update after the backup has completed and compare later.
One thing I have done in here is to tell Eset AV to exclude UrBackupClient.exe and UrBackupClientBackend.exe from being checked. Though I also have PCs installed elsewhere that I don’t bother doing that and don’t seem to have an issue.
