Linux Client Backup Problems

client
1

Hello,

i can’t used the ALL_NONUSB for Backup of an Kubuntu Client with btrfs. He have Problems with Access and Snapshots.

He ignored the Exclusions.

Only explized Paths are working.

Log Examples:

30.04.26 18:36  	ERROR  	Creating snapshot of "/data/SMB/NAS/Public" failed
30.04.26 18:36  	ERROR  	Cannot create snapshot of file system with type cifs
30.04.26 18:36  	ERROR  	Creating snapshot of "Public" failed.
30.04.26 18:36  	INFO  	Indexing of "Public" done. 7 filesystem lookups 0 db lookups and 0 db updates
30.04.26 18:36  	ERROR  	Creating snapshot of "/run/user/1000/doc" failed
30.04.26 18:36  	ERROR  	Cannot create snapshot of file system with type
30.04.26 18:36  	ERROR  	Creating snapshot of "doc" failed.
30.04.26 18:36  	ERROR  	Cannot access path to backup: "/run/user/1000/doc" Errorcode: 13 - Permission denied
30.04.26 18:36  	WARNING  	Hint: Directory to backup ("/run/user/1000/doc") does not exist. It may have been deleted or renamed. Set the "optional" directory flag if you do not want backups to fail if directories are missing.

Fehler
	
30.04.26 19:10
	Creating snapshot of "/sys/fs/bpf" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "bpf" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/sys/kernel/tracing" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "tracing" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/snap/bare/5" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "5" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/snap/canonical-livepatch/393" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "393" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/snap/canonical-livepatch/384" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "384" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/snap/core22/2339" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "2339" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/snap/core22/2411" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "2411" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/snap/core24/1587" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "1587" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/snap/core24/1499" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "1499" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/snap/firefox/8191" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "8191" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/snap/firmware-updater/226" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "226" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/snap/firmware-updater/223" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "223" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/snap/firefox/8054" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "8054" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/snap/gnome-42-2204/226" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "226_0" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/snap/gnome-46-2404/145" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "145" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/snap/mesa-2404/1165" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "1165" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/snap/gtk-common-themes/1535" failed
Fehler
	
30.04.26 19:10
	Cannot create snapshot of file system with type
Fehler
	
30.04.26 19:10
	Creating snapshot of "1535" failed.
Fehler
	
30.04.26 19:10
	Creating snapshot of "/snap/gnome-46-2404/153" failed

Exclusions:

/sys;/proc;/dev;/run;/snap;/boot;/swap;/data/SMB;/run/user;/run/snapd;/proc/sys/fs/binfmt_misc;/sys/fs;/sys/kernel;/sys/firmware;/dev/shm;/dev/pts;/dev/hugepages;/dev/mqueue;/run/lock;/run/snapd/ns;/.cache;/.cd;/.dbus;*.tmp;*Cache*;*cache*;/mnt;/media;/data/NFS;/home/*/Mountpoints;/home/*/.local/share/gvfs-metadata;/home/*/.local/share/nautilus/tags;/home/*/.config/borg/security/*/nonce;/*sync.ffs*;/run/user/*;/run/user/1000/doc;/run/user/1000

Working Paths:

/etc/fstab;/etc/systemd/system;/home

Many Thanks!

Many Greetings

Revan335

2

answer from AI:

These logs show the most classic yet frustrating “snapshot conflict” scenario in the world of Linux backups. While the ALL_NONUSB (or ALL) parameter looks great on paper, it turns into a complete nightmare in a modern Linux distribution (like Kubuntu) due to the dozens of virtual file systems that the operating system mounts in the background.

The root cause of the problem is this: When UrBackup uses ALL_NONUSB, it attempts to back up everything currently mounted on the system. However, the paths you see in the logs—such as /snap, /sys, /run, and /data/SMB—are not actual files but rather snapshots.

Here’s what you need to do to cut these errors off at the pass:

1. Stop Using ALL_NONUSB

The logs show that UrBackup cannot check your “Exclusion list” on these virtual systems before triggering a snapshot. On Btrfs-based Linux systems, the safest approach is to specify only the main paths you actually need.

Why?

Snapshots: Packages like Firefox under /snap are actually “SquashFS” file systems. These are read-only, cannot be snapshotted, and should not be backed up in the first place.

System Files: /sys, /proc, and /dev contain hardware and kernel information; they cannot be backed up.

SMB/CIFS: These are network shares. The Btrfs snapshot mechanism only looks at the local disk and cannot take a snapshot of an SMB share on a remote server.

2. Correct “Default Directories” Setting

Instead of entering ALL_NONUSB in the “Default directories to backup” section of the Client settings, add only the following root directories:

Plaintext

/;/home

If the system has a multi-part disk structure (with different mount points), you can add the following:

Plaintext

/etc;/home;/root;/var/www

3. Revise the Exclusion List

In UrBackup, the Exclude list sometimes does not prevent the “snapshot” error; it only prevents the file from being copied after the snapshot is taken. To stop the error at the snapshot level, use the following format (pay attention to wildcards):

Excluded files (with wildcards):

Plaintext

/sys/*;/proc/*;/dev/*;/run/*;/snap/*;/data/SMB/*;/mnt/*;/media/*;/tmp/*;*.vhdz;*.bitmap

4. Critical Setting: “Backup backups across different file systems”

Make sure to keep this option OFF (unchecked) in UrBackup settings.

When this setting is off, UrBackup automatically refuses to enter a different file system (mount point) such as /snap or /data/SMB when backing up the / (Root) directory. This alone resolves 90% of the errors in the logs.

5. Symbolic Links (Symlinks)

In Kubuntu, some paths (such as /run/user/1000/doc) are temporary paths accessible only with specific permissions. The “Permission denied” error in the logs stems from this. If you don’t need to back up these folders (which you don’t), adding /run/* to the list will resolve this.

Summary Recommendation:

The method you described as “Only the specified paths work” is actually the most accurate and professional approach. Instead of trying to automatically detect everything on Linux servers, manually defining only the disk partitions containing actual data (such as /, /home, /var/lib/mysql, etc.) based on your fstab file is always more stable.

If you proceed by adding / (Root—but along with the exclusion list) to the “Mount Points” you’ve listed—/etc/fstab, /etc/systemd/system, and /home—you’ll see that the logs are completely clean.