Unable to start file level backup

[EffortlessIs]

When I try to configure a Veeam backup, I get an error "Unable to find filesystem type for device with number [0:5]"

Situation: Server is RHEL 7 with ZFS on Linux. MDADM RAID1 for the OS, simple partitions. The ZFS pool is used primarily to backup other systems, but I want to use Veeam to backup the O/S of this system (and not the backup files from other hosts). I want the veeam backup file to be saved in the ZFS pool.

So, I've chosen file mode backup, and excluded any reference to the zfs pool including any folders that are mounted in the filesystem tree other than /zfspool. But after choosing all the files I want to back up (basically, the whole system sans the ZFS pool) I get the error mentioned above.

What other information can I provide that will help lead to resolution of this matter?

[HannesK]

Hello,
and welcome to the forums.

In general, Veeam does snapshot based backups (also for file level backups). But snapshots are not supported for ZFS. I guess, that you somehow still pointed to something that is ZFS. There is a way to do snapshot-less file level backup

In case that hint does not help, please open a support case for further debugging. Please post the case number here for reference and do not forget to upload logs to the case.

Best regards,
Hannes

[EffortlessIs]

Ok, I do find this just a tad ironic since the primary reason I'm using ZFS is for its excellent snapshot capability!!! But I presume we're talking about something different.

In any event, doing a "snapshot less" backup seems to be working. Wish I understood how I'm selecting a ZFS dir when I am unaware of doing so.

[nielsengelen]

Hi Benjamin, VAL doesn't use native snapshots but it's something we built from scratch so we can also support other filesystems. We'll consider your request noted to integrate with ZFS native snapshots.

[EffortlessIs]

Sadly, this issue isn't resolved. Disabling the snapshot allowed me to save the configuration and start the backup, but the backup itself fails. Here's the last bit of the log file:

[13.02.2020 02:55:10] <140088587106048> lpbcore| Kernel with unstable BTRFS module found.
[13.02.2020 02:55:10] <140088587106048> lpbcore| Enumerating file backup objects. snapshot required: false
[13.02.2020 02:55:10] <140088587106048> lpbcore| Initializing file backup filter.
[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{eb3daf94-3eb4-4048-816a-1c2a273a6928}] (value [/boot])
[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{18536322-8028-46d5-9e04-ce3f5a862763}] (value [/dev])
[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{05754a20-ddfa-4372-b5d7-cd7fb4e3b1f6}] (value [/etc])
[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{776856b2-e9f9-4a50-9824-4be45493ac21}] (value [/home])
[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{82101021-194f-44ff-ba4f-b2b472a4ab1e}] (value [/media])
[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{01b41285-529b-4806-8540-629c982d0478}] (value [/mnt])
[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{d76e3d21-581d-4bbf-9daf-7c6eb88f6050}] (value [/opt])
[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{24651e14-15dc-4f4c-b1a2-98dd8543fc55}] (value [/proc])
[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{107805cb-bf61-4fa1-a944-f5d9b48ca8a9}] (value [/run])
[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{f294fcdb-4089-4986-916d-17c370f2db29}] (value [/root])
[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{d865056d-289e-46e1-883e-c3730a258770}] (value [/srv])
[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{f935c6e9-072d-4ea5-aa9d-99f4318eda4f}] (value [/sys])
[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{bea84584-8700-4e6f-a093-4a23f67da3f3}] (value [/tmp])
[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{b82500ae-c28e-4028-9aa4-e52157a71c4d}] (value [/usr])
[13.02.2020 02:55:10] <140088587106048> lodev | WARN|Mount point [/var/named/chroot/etc/localtime] is not a directory.
[13.02.2020 02:55:10] <140088587106048> lodev | WARN|Mount point [/var/named/chroot/etc/named.root.key] is not a directory.
[13.02.2020 02:55:10] <140088587106048> lodev | WARN|Mount point [/var/named/chroot/etc/named.conf] is not a directory.
[13.02.2020 02:55:10] <140088587106048> lodev | WARN|Mount point [/var/named/chroot/etc/named.rfc1912.zones] is not a directory.
[13.02.2020 02:55:10] <140088587106048> lodev | WARN|Mount point [/var/named/chroot/etc/rndc.key] is not a directory.
[13.02.2020 02:55:10] <140088587106048> lodev | WARN|Mount point [/var/named/chroot/etc/named.iscdlv.key] is not a directory.
[13.02.2020 02:55:10] <140088587106048> lodev | WARN|Mount point [/var/named/chroot/etc/protocols] is not a directory.
[13.02.2020 02:55:10] <140088587106048> lodev | WARN|Mount point [/var/named/chroot/etc/services] is not a directory.
[13.02.2020 02:55:10] <140088587106048> lpbcore| /boot --> /
[13.02.2020 02:55:10] <140088587106048> lpbcore| Initializing file backup filter. Failed.
[13.02.2020 02:55:10] <140088587106048> lpbcore| Enumerating backup objects. Failed.
[13.02.2020 02:55:10] <140088587106048> lpbcore| BackupJobPerformer: Creating backup. Failed.
[13.02.2020 02:55:10] <140088587106048> vmb | [SessionLog][error] Failed to perform backup.
[13.02.2020 02:55:10] <140088587106048> vmb | [SessionLog][error] Mount point is not found for included directory '/dev'.
[13.02.2020 02:55:10] <140088587106048> vmb | [SessionLog][error] Failed to retrieve mount point for [/dev].
[13.02.2020 02:55:10] <140088587106048> vmb | [SessionLog][error] Processing finished with errors at 2020-02-13 02:55:10 GMT.
[13.02.2020 02:55:10] <140088587106048> lpbcore| ERR |Mount point is not found for included directory '/dev'
[13.02.2020 02:55:10] <140088587106048> lpbcore| >> |Failed to retrieve mount point for [/dev]
[13.02.2020 02:55:10] <140088587106048> lpbcore| >> |Backup job has failed.
[13.02.2020 02:55:10] <140088587106048> lpbcore| >> |An exception was thrown from thread [140088587106048].
[13.02.2020 02:55:10] <140088620537792> | Closing socket device.
[13.02.2020 02:55:10] <140088620537792> lpbcore| LpbManSession: Processing commands. ok.
[13.02.2020 02:55:10] <140088620537792> | Closing socket device.
[13.02.2020 02:55:10] <140088587106048> lpbcore| JOB STATUS: FAILED.
[13.02.2020 02:55:10] <140088587106048> | Thread finished. Role: 'Volume backup job execution'.
[13.02.2020 02:55:10] <140088620537792> | Closing socket device.
[13.02.2020 02:55:10] <140088620537792> | Closing socket device.
[13.02.2020 02:55:10] <140088620537792> lpbman | Application session has been finished.

[PTide]

Hi,

I can see these lines in your log:

Code: Select all

Thread finished. Role: 'Volume backup job execution'.

Are you 100% positive it's a file-level job that you've configured?

Code: Select all

[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{18536322-8028-46d5-9e04-ce3f5a862763}] (value [/dev])
[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{24651e14-15dc-4f4c-b1a2-98dd8543fc55}] (value [/proc])
[13.02.2020 02:55:10] <140088587106048> lpbcore| Including object [{f935c6e9-072d-4ea5-aa9d-99f4318eda4f}] (value [/sys])

Did you specifically include those in your backup scope, or you just selected '/' ?

Thanks!