Since UrBackup can’t copy all files from my disk at once (the speed is extremely low — estimated backup time is more than 7 days), I decided to split the backup into several parts using multiple virtual clients.
One client with a simple configuration
works fine and successfully starts copying.
However, clients with more complex configurations
do not start the backup process.
When the backup starts, the client first spends a long time (about 30 minutes) reading the file
C:\Program Files\UrBackup\urbackup\backup_client.db
and writing to
C:\Program Files\UrBackup\urbackup\backup_client.db-wal.
Currently, backup_client.db is about 120 MB, and backup_client.db-wal is about 180 MB.
After that, the client seems to hang (I waited up to 20 hours before stopping the service).
During this time, there is a constant CPU load of about 17%, but according to monitoring, there is no disk or network activity, no new debug log entries, and no attempt to create a shadow copy (VSS).
At the same time, the server log shows the following messages:
2025-10-30 13:51:27: Error sending ‘running’ (2) ping to client
2025-10-30 13:51:27: Timeout: Error sending ‘running’ (2) ping to client
2025-10-30 13:51:27: Error sending ‘running’ (3) ping to client
2025-10-30 13:51:47: Error sending ‘running’ (2) ping to client
2025-10-30 13:51:47: Timeout: Error sending ‘running’ (2) ping to client
2025-10-30 13:51:47: Error sending ‘running’ (3) ping to client
2025-10-30 13:52:07: Error sending ‘running’ (2) ping to client
2025-10-30 13:52:07: Timeout: Error sending ‘running’ (2) ping to client
2025-10-30 13:52:07: Error sending ‘running’ (3) ping to client
However, according to the web interface , the server still sees the client as “online”.
What could be the problem and how can I fix it?
Server version 2.5.33
Clien version 2.5.26