I'm experiencing some troubles with one of the listed items above:
In my case, I have 2 LUKS-encrypted partitions which appear as /dev/dm-0 and /dev/dm-1 and further with some named entries in /dev/mapper/*.Volume-level backup job relies on a device name under the /dev directory and requires volumes to have their corresponding device names under the /dev directory staying persistent (e.g. /dev/md-127, /dev/dm-1). Otherwise the job will back up the wrong volume.
The problem is, that the numbering of /dev/dm-x is NOT consistent (at least in my case).
I'm running Fedora 30 and all my encrypted partitions are listed inside /etc/crypttab. This is translated to some systemd unit files when booting.
Those systemd unit files are allowed to be executed in parallel. This causes the /dev/dm-x numbering to be kind of random.
As a consequence, the veeam backup agent performs a full backup of the affected partitions every time those numbers flip (my backup targets the entire machine).
Long story short: Is there any workaround to avoid this (e.g. enforcing the enumeration of /dev/dm-x)?
Thanks a lot in advance.