backup fails - invalid snapshot configuration

[bkc]

I have a Ubuntu 14.04.5 system with 2-disk software raid, LVM on top of that. I tried 'backup entire computer' and the backup failed immediately 'invalid snapshot configuration'.

For some reason Veeam seems to want to backup both physical disks rather than just backing up the md arrays

BIOS bootloader on [/dev/sda] will be backed up.
Disk [/dev/sda] will be backed up.
BIOS bootloader on [/dev/sdb] will be backed up.
Disk [/dev/sdb] will be backed up.

I will pm a link to logs, including dmesg output taken right after the backup failed.

I'm not sure if this shows up in the logs

cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md2 : active raid1 sdb1[0] sda1[1]
497856 blocks [2/2] [UU]

md3 : active raid1 sda2[1] sdb2[0]
1953013952 blocks [2/2] [UU]

[bkc]

I have pm'd link to logs to PTide

[PTide]

Thank you for the logs, the issue is being investigated. Does it work fine if you manually select md arrays instead of selecting "entire machine"?

[PTide]

UPDATE:

Also please provide the following info:

blkid and libblkid versions, and output of

Code: Select all

blkid -p /dev/sda1

and lsblk

(run them as root).

Thanks!

[bkc]

blkid from util-linux 2.20.1 (libblkid 2.20.0, 19-Oct-2011)

# dpkg-query -l libblkid1
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=========================-=================-=================-=======================================================
ii libblkid1:amd64 2.20.1-5.1ubuntu2 amd64 block device id library
ii libblkid1:i386 2.20.1-5.1ubuntu2 i386 block device id library

# blkid -p /dev/sda1
/dev/sda1: VERSION="0.90.0" UUID="42e3d5b8-c145-0c51-af69-2555e97c8e96" TYPE="linux_raid_member" USAGE="raid" PART_ENTRY_SCHEME="dos" PART_ENTRY_TYPE="0xfd" PART_ENTRY_FLAGS="0x80" PART_ENTRY_NUMBER="1" PART_ENTRY_OFFSET="63" PART_ENTRY_SIZE="995967" PART_ENTRY_DISK="8:0"

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
├─sda1 8:1 0 486.3M 0 part
│ └─md2 9:2 0 486.2M 0 raid1 /boot
└─sda2 8:2 0 1.8T 0 part
└─md3 9:3 0 1.8T 0 raid1
├─VGFire00-opt (dm-0) 252:0 0 12G 0 lvm /opt
├─VGFire00-home (dm-1) 252:1 0 128G 0 lvm /home
├─VGFire00-usr_local (dm-2) 252:2 0 4G 0 lvm /usr/local
├─VGFire00-usr (dm-3) 252:3 0 18G 0 lvm /usr
├─VGFire00-usr_media (dm-4) 252:4 0 32G 0 lvm /usr_media
├─VGFire00-var (dm-5) 252:5 0 8G 0 lvm /var
├─VGFire00-tmp (dm-6) 252:6 0 7G 0 lvm /tmp
├─VGFire00-vmware (dm-7) 252:7 0 100G 0 lvm
├─VGFire00-root (dm-8) 252:8 0 4G 0 lvm /
├─VGFire00-swap (dm-9) 252:9 0 6G 0 lvm [SWAP]
├─VGFire00-marimba_archive (dm-10) 252:10 0 20G 0 lvm /marimba_archive
├─VGFire00-vmware2 (dm-11) 252:11 0 164G 0 lvm /vmware
├─VGFire00-wikimedia (dm-12) 252:12 0 16G 0 lvm /wikimedia
├─VGFire00-zimbra (dm-13) 252:13 0 180G 0 lvm
└─VGFire00-server1 (dm-14) 252:14 0 750G 0 lvm
sdb 8:16 0 1.8T 0 disk
├─sdb1 8:17 0 486.3M 0 part
│ └─md2 9:2 0 486.2M 0 raid1 /boot
└─sdb2 8:18 0 1.8T 0 part
└─md3 9:3 0 1.8T 0 raid1
├─VGFire00-opt (dm-0) 252:0 0 12G 0 lvm /opt
├─VGFire00-home (dm-1) 252:1 0 128G 0 lvm /home
├─VGFire00-usr_local (dm-2) 252:2 0 4G 0 lvm /usr/local
├─VGFire00-usr (dm-3) 252:3 0 18G 0 lvm /usr
├─VGFire00-usr_media (dm-4) 252:4 0 32G 0 lvm /usr_media
├─VGFire00-var (dm-5) 252:5 0 8G 0 lvm /var
├─VGFire00-tmp (dm-6) 252:6 0 7G 0 lvm /tmp
├─VGFire00-vmware (dm-7) 252:7 0 100G 0 lvm
├─VGFire00-root (dm-8) 252:8 0 4G 0 lvm /
├─VGFire00-swap (dm-9) 252:9 0 6G 0 lvm [SWAP]
├─VGFire00-marimba_archive (dm-10) 252:10 0 20G 0 lvm /marimba_archive
├─VGFire00-vmware2 (dm-11) 252:11 0 164G 0 lvm /vmware
├─VGFire00-wikimedia (dm-12) 252:12 0 16G 0 lvm /wikimedia
├─VGFire00-zimbra (dm-13) 252:13 0 180G 0 lvm
└─VGFire00-server1 (dm-14) 252:14 0 750G 0 lvm
sdc 8:32 0 2.7T 0 disk
└─sdc1 8:33 0 2.7T 0 part /archive
sdd 8:48 0 477G 0 disk

[PTide]

Thanks, finally we've reproduced the issue. One last question - do you have a license installed on the machine? If so then please open a support case and post your case ID in this thread.

Thanks

[bkc]

I deleted the default job, created a new job , volume level and selected md3

backup failed, link to logs have been pm'd to you.

I do not have a license.. Eventually will be using this with 9.5 on another machine with similar configuration.

[PTide]

Hi,

I'm aware that you don't have the license, nevertheless, please open a case with support team so they can provide you with the fix. Don't forget to post your case ID.

Thanks