Server 2.5.13 beta/Client 2.5.7 beta

New settings handling

The major change with server 2.5.x and client 2.5.x is a complete redesign how settings are handled. The goal is to make it more explicit and consistent.

  • Each setting has a button next to it which switches between inheriting the setting from the group, using the configuration value on the configuration page and using the value from the client, and for some setting merging client and server settings together
  • File backup paths are now a normal setting just like any other. No more separation between paths to backup configured on the client and default directories to backup

This is a critical area of UrBackup and as such needs a lot of testing. Focus should be on if the 2.4.x client still more or less works with the 2.5.x server (and especially doesn’t loose its connection settings for Internet servers).


  • Implement new URL scheme for connection settings in the client settings GUI

Connect via web sockets

With 2.5.x clients can connect via web sockets to the server. Setup should be easy. Instead of “Internet server name/IP” of e.g. “” use “ws://”. The real advantage comes into play if a real web server with SSL is setup in front. Either proxy the whole page, or serve the files and only proxy “/x” via FastCGI (see manual), additionally proxy “/socket” via web socket to “ws://”. Then setup the clients to connect to “Internet server name” “wss://”. Basic authentication, a different name and a different port should also work, e.g. “wss://”.

Linux image backups

2.5.x can backup Linux clients (via dattobd or Linux device mapper snapshots). The use case is e.g. backing up a DigitalOcean instance. It is explicitly not to create image backups of all possible configurations e.g. LVM, mdraid, btrfs, …
It can “live restore” a root volume, i.e., overwrite the root volume of a currently running machine. So one can image backup e.g. a DigitalOcean droplet. To restore create a new instance (tested with Debian 10/buster) then run the restore script which overwrites the current instance with the backed up instance using a trick to put the currently running system files into (compressed) memory.
Dattobd and the Linux device mapper supports Changed Block Tracking (CBT), so image (and file) backups are done with CBT.

The Linux device mapper snapshots scripts are currently only tested on Debian 10 and with the root volume. It needs to hook into the boot sequence (initramfs) to backup the root volume. For other volumes it probably needs to hook into udev. Help getting it running on other distributions/with non-root volumes would be welcome!

Linux image backup howto


  • To only backup used space install partclone (e.g. apt install partclone). This is currently supported for ext* and xfs. If partclone is not present it’ll backup unused space.
  • Install the (binary) client and select either dattobd or the Linux device mapper for snapshotting
  • If you are using dattobd: Install dattobd


  • On the server browse to the image backup to restore
  • Click on “Restore Linux image”
  • Copy & paste the command into a new instance and follow the instructions (the command has a timeout (token), so after a while it should not work anymore)

Testing (image backup + file backup with CBT)

To test if CBT works correctly with file backups please enable Debugging: Verify file backups using client side hashes (for Internet clients with client-side hashing) or Debugging: End-to-end verification of all file backups in the advanced settings.

To test image backups enable md5sums creation on the client via touch /usr/local/var/create_md5sums_imagebackup. The client will then create a file (with date+time in the name) at /usr/local/var/md5sums-* for each image backup listing all files in the image plus their md5sum. Copy that file to server, mount the image backup then verify the md5sums with cd /backup/client/image_mnt; md5sums --quiet -c /path/to/md5sums-file.txt. The only files with checksum errors should be the .datto-*/.overlay-* files in the root directory and swap files (those get automatically excluded from backup).

Thanks for any help with testing and feedback!

Upgrade process

As always: Replace the executables (via the installers) and the database of the server/client will be updated on first running it.

Place the files from the update directory into C:\Program Files\UrBackupServer\urbackup or /var/urbackup to auto-update clients. Disable Download client from update server in the server settings to prevent the server from downloading the current version.

On Linux e.g. with this update script:

Downgrade process (server)

Stop the UrBackup server, restore C:\Program Files\UrBackupServer\urbackup or /var/urbackup from a backup before upgrade and then install the previous version over the beta release.

On testing beta/WIP versions

Please see Having problems with UrBackup? Please read before posting for what kind of information to add when reporting issues with the beta/WIP version. Reports such as “X does not work” are useless. In general, at the very least, think about what kind of information one would need to reproduce the problem in a different environment. Also a reminder that this is a community project which depends on your contribution and help. Testing is a way to contribute, but without detailed reports on the issues you are finding, you might as well wait for the final release. Best case you debug the problem yourself and then post the fix.

I’ll ignore any issue reports that don’t follow minimum reporting standards.

Changes with server 2.5.13 beta

  • Fix SQL issue with updating client settings
  • Correctly initialize global settings if client is in a group

Changes with client 2.5.7 beta

  • Add new Linux device mapper based snapshot method


The new Linux device mapper based snapshotting might look a bit complicated:

Hi, really what i think for images backup is that you should allow users to create bash plugins that can display menu and stuff in the gui and deploy scripts to clients (ie, not deploy the files separately per client).

In bash because there are so many linux admins.
So i can create a script that snapshot then dd some partition , or use btrfs send.
And that script would be added to the menu as “backup full/inc btrfs image”.
And same thing to restore partitions and partition table.

So for you it is less work , and i am pretty sure it will engage users in the developpement.
And at one point you ll get a working script for every partitions scheme

I know right now it is almost possible , but it is not very well documented and a bit cumberstone.
I think a suggestion i made at some point was to allow something like custom components, for linux, with a server side gui to manage the component, where you can select them and stuff.

Ie for the client, i think if it was a bash only client with a text menu that call urbackupclientctl (press 1 to start a full, press 2 to list backup, press 3 to restore a file, etc …)
It i think it would be more developed, instead of the gui that’s broken since years.

I think like 1-2 years ago , i tried to develop such things but gave up , i don’t remember the limitations i encountered

That would be valuable information. I don’t mind adding new commands/output modes to e.g. urbackupclientctl, for example.

Otherwise your idea is a bit too bare-bones to be actionable.

in “Interval for full file backups:” some settings are storing “NaN” instead of 24 , and that prevent me from saving.
Even if i try to cycle through all settings types (local, group, etc) to input a number

Field format wrong. (update_freq_image_full). Sorry, problem finding error message (translation)

Field format wrong. (update_freq_full). Sorry, problem finding error message (translation) <-- and others.

Everything on the file backups tab seems broken.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.