File backup size Unknown or "-1 bytes", nightly cleanup won't run

Server
1

There’s a strange problem with the server on one specific windows 11 pc. It shows file backup size as Unknown or “-1 bytes”, for all backups and all clients. Plus, the nightly cleanup won’t run (no “cleanup” word in the logs, clients scheduled for removal remain).

I tried the simplest setup possible:

Clean install of the server - no “C:\Program Files\UrBackupServer” dir, empty backup storage dir, all defaults except for:

  • set the Backup storage path
  • check Do not do image backups

Clean install of the client on the same pc, chose some test folder to backup.

Server and client find each other and do the first full backup, and its size is shown as Unknown (on Activities tab) or “-1 bytes” (on Backups tab).

What doesn’t help:

  • waiting - nothing changes on next day
  • changing folder(s) to backup
  • using remote client

What helps:

  • changing the pc - the problem doesn’t occur on a vm, for example
  • running cleanup.bat - fixes backup sizes and does the cleanup

So I guess the pc is to blame, but what exactly is wrong? Any ideas?

urbackup.log (16.4 KB)
client.log (484 Bytes)
UrBackup Server 2.5.34 Rev. 65c5000eb3
Windows 11 IoT Enterprise LTSC 24H2 26100.7171

2

Okay, problem solved. Hopefully. Here’s what I did:

  • stopped the server and manually cleared the backups folder
  • replaced the “C:\Program Files\UrBackupServer” folder with a copy from another machine (one without the issue) - binaries, database, settings - the whole thing.
  • run remove_unknown.bat
  • started the server
  • added clients, adjusted settings

A few days passed and everything seems to work as it should: backups have sizes, statistics updates correctly, cleanup runs every night (“Cleaning up …” in logs, scheduled for removal clients disappear) and Download client for windows/linux buttons on Status tab are visible (they weren’t before - I didn’t mention it in the initial post). So what was that anyway - a consistent incorrect creation/initialization of the database during the setup/first run? Beats me.