I think you need to adjust your time travel machine. We are now in 2026

Btw., does it still have this issue? sh: 1: lsb_release: not found · Issue #12 · uroni/urbackup-client-docker · GitHub

However, I have run into a critical issue with restores/mounting:

Web Interface: When I try to mount a VHDX image via the Web UI, it fails with: “Mounting image failed. Please see server log file for details.” Interestingly, the server logs (urbackup.log) do not show any specific errors related to the mount failure.

CLI Access: Previously, with RAW incremental images, I could mount them manually via the console. Now, with VHDX incrementals, every mounting attempt (even using loop devices) fails. The OS reports that no file system is found on the device, or the partition table is unreadable.

Environment & Setup:

UrBackup Server Version: 2.5.35

Backend Filesystem: BTRFS

Image Format: VHDX (Incremental)

How can I correctly mount these incremental VHDX images via the CLI when the Web UI fails?

bB

I don’t think I’ll pursue this any further.

Many thanks for your help

Using rsync and/or SSH is no good for server using btrfs because all of the space saving done by btrfs’s sub-volumes and snapshots will be lost as neither rsync or (various) SSH methods don’t understand btrfs snapshots etc.

You could try and backup only the top-level of each client’s folder/s which would give(at least) one copy for (exmple) offline backup.

I myself have been working on a shell script that will copy upto a depth of X for a given start date of Y for all clients in the server database. This script “knows” how to deal with btrfs parent/child relationships that are implemented by urbackup as sub-volumes and snapshots.

One thing ….that may help if you want to investigate btrfs replication is that the folders that are named after the client/virtual sub client….are NOT sub-volumes or snapshots ….it is the contents of these folders that contain the snapshots etc.

If you would like a copy of the script thus far (it’s incomplete) then let me know a way to send it to you.

Best of luck

David

services:
  urbackup:
    image: uroni/urbackup-server:latest
    command: ["run", "-v", "info", "-g", "20971520", "-b", "enp2s0"]
    container_name: urbackup
  [...]

Arguments for the command can be identified with

urbackupsrv run --help

after opening a terminal inside the container.

I think using the configuration file with the image would be a more common approach as it is used in the non-docker implementations of urbackup.

Version: 2.5.35

Issue: When assigning a user permissions to multiple clients via Settings → Users, the user can only see one client when logged in, despite permissions appearing correctly in the UI.

Steps to reproduce:

1. Create a user

2. Assign permissions to Client A (e.g. browse_backups, status, logs, etc.)

3. Use the navigation trick to assign the same permissions to Client B

4. Log in as the user — only one client appears

Database findings: Looking at backup_server_settings.db, the si_permissions table stores permissions like this:

clientid | t_right | t_domain
5        | 6       | browse_backups
5        | 7       | browse_backups

Where t_right contains the client machine ID from the clients table in backup_server.db. When two different client IDs exist for the same user and domain, only one client appears in the user’s view.

Workaround: Setting t_right to all for all domains shows all clients, but this removes per-client access restrictions entirely, which defeats the purpose.

Expected behavior: A user with permissions for multiple clients should be able to see all assigned clients, or group-based permissions should work as an alternative.

Hopefully this explains my issue a little clearer? I even tried to delve into manually assigning with sqlite in the cli. Maybe i need a fresh install or something?

#This is a key=value config file for determining the scripts/programs to create snapshots

create_filesystem_snapshot=/usr/local/share/urbackup/dm_create_snapshot
remove_filesystem_snapshot=/usr/local/share/urbackup/dm_remove_snapshot
create_volume_snapshot=/usr/local/share/urbackup/dm_create_snapshot
remove_volume_snapshot=/usr/local/share/urbackup/dm_remove_snapshot

The scripts are at the pointed at location.

The script needs to output

SNAPSHOT=/foo/bar

pointing at the created snapshot.

For image backups it also reads the backing device from the file $SNAPSHOT-dev (in this case /foo/bar-dev) – you don’t actually need to have the snapshot mounted – see recent changes to dm_create_volume_snapshot

the UI allows you to assign multiple clients to a user but the backend permission system breaks when you actually do it, only ever showing one client. The only workaround is all which defeats the purpose of per-client restrictions.

I have the server installed as a docker image on an OpenMediavault installation. Works like a charm.

Now the server inform me that the new 2.5.36 version of the server is available.

I use WatchTower to auto update my docker containers, but this update is not done.

I also tried to manually update without success. I’m still working with 2.5.35

I don’t understand the reason why the update do not install? Any ideas?

I only changed it in latest. You could use the 2.5.x tag. I don’t think that has the arguments

Next server release would be the image for urbackup-server 2.5.36 or 2.5.37? Currently the image is 2.5.35.

I think it would be easy to change the bash scripts to support this, but someone needs to do the work and testing.

I run the server inside a VM and the backupdir on the host for many years, but now that I updated to a fresh setup I’m getting this problem.

I’m posting part of the debug log below:

 
03/06/26 17:08  	DEBUG  	HT: Hardlinking failed (unkown error) Source="/mnt/offsite/urbackup/offsite/260306-1744/.symlink_x86_64-linux-gnu-cpp-13" Destination="/mnt/offsite/urbackup/hero/260306-2258/.symlink_x86_64-linux-gnu-cpp-13" -- Operation not permitted (code: 1)
03/06/26 17:08  	DEBUG  	HT: Copying file: "/mnt/offsite/urbackup/hero/260306-2258/.symlink_x86_64-linux-gnu-cpp-13" (id=8965)
03/06/26 17:08  	DEBUG  	HT: Renaming file to "/mnt/offsite/urbackup/hero/260306-2258/.symlink_x86_64-linux-gnu-cpp-13"
03/06/26 17:08  	INFO  	Waiting for file hashing and copying threads...

Does anyone have any ideas? Is this just a bug with this version of the server since I never had any problems with my 2.4.x versions?

Thanks in advance.

Brady

I am a complete beginner and have the following question: I have a Debian client and would like to create an image backup. Lvm is set up. I have already tried a few things, but unfortunately I keep getting the message “not supported”. What exactly do I need to set up to make it work?

Many thanks for your help

Thanks for your support and for this great software!!!

I do not see the setting in the GUI.

Thanks

jayrehme:

doesn’t work on intel machines

As I mentioned in the MacOS thread, I don’t have an Intel one to test with. Could you perhaps elaborate what exactly does not work on Intel machines?

The path for urbrackupclientctl is /Applications/UrBackup\ Client.app/Contents/MacOS/bin/urbackupclientctl - should allow you to configure via the command line.

I’ve not had chance to try the 2.5.29 release yet - but I’d be surprised if it doesn’t work on Intel systems…