unable to backup ext4 partition.

[maxilee]

ehlo.a.
I'm unable to backup ext4 partition ( /dev/sdd1) on one machine.
partition is not showing up when i was tring to configure backup job via GUI so I've addess it via CLI to job.
then I've started backup but it has fallen with error :

[23.10.2018 06:30:31] <140627719628544> vmb | [SessionLog][error] Unable to backup object: /dev/sdd1(not found).
[23.10.2018 06:30:31] <140627719628544> lpbcore| Enumerating backup objects. Failed.

but device /dev/sdd1 existst

currently I've added to backup only few my volumes :

Code: Select all

   Objects for backup:
      Include Disk: md2
      Include Disk: md3
      Include Disk: sda1
      Include Disk: sdb1
      Include Disk: sdd1

Code: Select all

[root@home ~]# ls /dev/sdd1  -al
brw-rw---- 1 root disk 8, 49 10-22 18:29 /dev/sdd1

[root@home ~]# lsblk -f
NAME    FSTYPE            LABEL               UUID                                 MOUNTPOINT
sda                                                                                
├─sda1  ext4                                  e43ef57b-02c6-47ce-8067-b2c198769295 /boot
├─sda2  linux_raid_member home.inbox.eu.org:2 004df42b-d5b2-e6b5-1fc9-35c2ae089892 
│ └─md2 ext4                                  ab3b220b-454f-403e-a1a9-69cbbd31f373 /opt
├─sda3  linux_raid_member 10.254.0.102:3      2d258e9f-8cf9-63ea-308d-eda58cafa34e 
│ └─md3 ext4              root                82c494f1-0db2-4c9c-99f1-b1a42ea94624 /
└─sda4  linux_raid_member 10.254.0.102:4      1337ad9e-6329-452a-500a-aba0ced7862f 
  └─md4 swap              swap                680554d9-191b-4bca-a418-b59873880948 [SWAP]
sdb                                                                                
├─sdb1  ext4                                  e539ecc6-66a5-4ec7-a09e-067f790d9c02 
├─sdb2  linux_raid_member home.inbox.eu.org:2 004df42b-d5b2-e6b5-1fc9-35c2ae089892 
│ └─md2 ext4                                  ab3b220b-454f-403e-a1a9-69cbbd31f373 /opt
├─sdb3  linux_raid_member 10.254.0.102:3      2d258e9f-8cf9-63ea-308d-eda58cafa34e 
│ └─md3 ext4              root                82c494f1-0db2-4c9c-99f1-b1a42ea94624 /
└─sdb4  linux_raid_member 10.254.0.102:4      1337ad9e-6329-452a-500a-aba0ced7862f 
  └─md4 swap              swap                680554d9-191b-4bca-a418-b59873880948 [SWAP]
sdc                                                                                
└─sdc1  btrfs                                 d788fcea-8234-441d-8ed4-6c92e5d4c6ca 
sdd                                                                                
└─sdd1  ext4                                  a56e0394-b536-4394-958b-f2863ee4e430 /mnt/data-all
sde                                                                                
└─sde1  btrfs                                 d788fcea-8234-441d-8ed4-6c92e5d4c6ca 
sdf                                                                                
└─sdf1  btrfs                                 d788fcea-8234-441d-8ed4-6c92e5d4c6ca /mnt/backup

as you can see I'm using btrfs in my setup - maybe this is the problem and veeam can't list all partitions ?

[PTide]

Hi,

The current version of VAL should just ignore BTRFS partitions. That is, the described behaviour is unexpected - ordinary partitions should be backed up just fine. I am also curious what kernel version are you running on that machine? For some reason I expect it to be way newer than the default CentOS 7 kernel

If you are running the default 3.10 then please contact our support team directly so they can investigate.

Thank you

[maxilee]

Hello.
yes i know limitation about BTRFS.

this machine is not CentOS but Fedora 28.

[root@home ~]# cat /etc/redhat-release
Fedora release 28 (Twenty Eight)
[root@home ~]# uname -a
Linux home.inbox.eu.org 4.16.3-301.fc28.x86_64 #1 SMP Mon Apr 23 21:59:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

kernel is not the last one from fedora repo ( 4.18 ) because on newest kernel veeamsnap is not building.

[PTide]

VAL 2.0.1.665 is expected to work on Fedora 28 with 4.16 kernel installed. If suggest you to contact the support team as it is difficult to diagnose the issue without logs.
By the way, are the other machines also running the same distro and kernel?

Thanks

[maxilee]

Ok. I'll contact support for that case.

no. this other machine was running ubuntu 16.04 ( but few weeks ago I've upgraded it to 18.04 and switched one partition from btrfs to ext4, because I wanted to add that partition to backup ... ).

[maxilee]

Hello.
I've found reason of that behawior in veeam agent linux manual
"The supported file system can reside on a simple volume or LVM2 volume.

* Consider the following:

Veeam Agent for Linux does not back up volumes that reside on USB devices."

in my case sda and sdb are internal hdd ( sata ) and rest of my devices ( sdc..sdf ) are USB.

suggestion to developers : can they change error message from "not found" to "unable to backup USB drive" ?

case close ...

[PTide]

suggestion to developers : can they change error message from "not found" to "unable to backup USB drive" ?

Yes, sure. Or, alternatively, we might actually look into supporting backup of USB drives : )

Thanks!