openSUSE

[fleamour]

Code: Select all

The destination path is a directory that is selected for backup. Please either choose a non-local destination(CIFS/USB/NFS) or exclude /.

The backup destination is mounted under /run/media/fleamour/BKF/Archive. It wont backup because; endless mirrors I assume, a backup of a backup? I do not want to exclude root, obviously.

I am running Tumbleweed which is not supported, but mad props for supporting BTRFS!

[fleamour]

At least I assume BTRFS is supported, cus no banner error message with latest version. But root is BTRFS, so maybe that the problem?!?

[PTide]

Hi,

Yes, BTRFS is supported in v3.0

What was the object that you've selected for backup, was it root subvolume, or just the whole BTRFS, or just a single device that belongs to BTRFS?
What is the destination, is it share or HDD?

Please provide some info: lsblk -af and btrfs subvolume list / outputs

P.S. Tumbleweed is supported up to kernel 4.18.

Thanks!

[fleamour]

Hi

Yes, selected to backup whole machine as recommended over to USB connected HDD;

Code: Select all

NAME            FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
sda                                              
├─sda1                             150.8M     3% /boot/efi
└─sda2                                           
  ├─system-swap                                  [SWAP]
  ├─system-root                     12.9G    65% /var/tmp
  └─system-home                    277.3G    34% /home/fleamour/lib/libvirt/images/SKYDRIVE
sdb                                              
└─sdb1                             350.2G    25% /run/media/fleamour/BKF

Code: Select all

ID 257 gen 33 top level 5 path @
ID 258 gen 40245 top level 257 path @/.snapshots
ID 260 gen 18707 top level 257 path @/boot/grub2/i386-pc
ID 261 gen 39838 top level 257 path @/boot/grub2/x86_64-efi
ID 262 gen 40162 top level 257 path @/opt
ID 263 gen 39857 top level 257 path @/srv
ID 264 gen 40273 top level 257 path @/tmp
ID 265 gen 40151 top level 257 path @/usr/local
ID 266 gen 40255 top level 257 path @/var/cache
ID 267 gen 17545 top level 257 path @/var/crash
ID 268 gen 40150 top level 257 path @/var/lib/libvirt/images
ID 269 gen 57 top level 257 path @/var/lib/machines
ID 270 gen 25 top level 257 path @/var/lib/mailman
ID 271 gen 27 top level 257 path @/var/lib/mariadb
ID 272 gen 28 top level 257 path @/var/lib/mysql
ID 273 gen 28 top level 257 path @/var/lib/named
ID 274 gen 30 top level 257 path @/var/lib/pgsql
ID 275 gen 40270 top level 257 path @/var/log
ID 276 gen 17545 top level 257 path @/var/opt
ID 277 gen 40273 top level 257 path @/var/spool
ID 278 gen 40273 top level 257 path @/var/tmp
ID 770 gen 17634 top level 258 path @/.snapshots/427/snapshot
ID 1302 gen 40273 top level 258 path @/.snapshots/900/snapshot
ID 1420 gen 39778 top level 258 path @/.snapshots/1008/snapshot
ID 1423 gen 40071 top level 258 path @/.snapshots/1009/snapshot
ID 1424 gen 40071 top level 258 path @/.snapshots/1010/snapshot
ID 1425 gen 40071 top level 258 path @/.snapshots/1011/snapshot
ID 1426 gen 40071 top level 258 path @/.snapshots/1012/snapshot
ID 1427 gen 40071 top level 258 path @/.snapshots/1013/snapshot
ID 1428 gen 40098 top level 258 path @/.snapshots/1014/snapshot
ID 1429 gen 40100 top level 258 path @/.snapshots/1015/snapshot
ID 1430 gen 40118 top level 258 path @/.snapshots/1016/snapshot
ID 1431 gen 40121 top level 258 path @/.snapshots/1017/snapshot
ID 1432 gen 40133 top level 258 path @/.snapshots/1018/snapshot
ID 1433 gen 40134 top level 258 path @/.snapshots/1019/snapshot
ID 1435 gen 40227 top level 258 path @/.snapshots/1020/snapshot
ID 1436 gen 40228 top level 258 path @/.snapshots/1021/snapshot
ID 1437 gen 40237 top level 258 path @/.snapshots/1022/snapshot
ID 1438 gen 40242 top level 258 path @/.snapshots/1023/snapshot

Many thx!

[PTide]

Would you try to reconfigure the job, please? Select volume-level, choose sda specifically, and then choose the USB device as a target. I expect that to work. Regardless of if it works or not please open a support case to let our support team can get logs from you for investigation. Since your "/" subvolume is located on a separate device, ther should be no problems backing up to USB drive.

Thanks!

[fleamour]

The job configures correctly then fails to even run. I have exported error logs but I am a community member & do not have business or business email so as to sign up for a Veeam support account .

[PTide]

Then please upload logs somewhere else and PM me the link.

The job configures correctly then fails to even run.

What error do you see?

Thanks!

[fleamour]

Code: Select all

14:08:08         Job BKF Archive started at 2019-01-23 14:08:08 GMT                                                            
      14:08:08         [warn] Backup is missing in repository                                                                        
      14:08:08         Preparing to backup                                                                                           
      14:08:08         [error] Failed to create volume snapshot                                                      00:00:00        
      14:08:08         [error] Failed to perform backup                                                                              
      14:08:08         [error] Child execution has failed. Exit code: [1]                                                            
      14:08:08         [error] Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0 s...                 
      14:08:08         [error] Processing finished with errors at 2019-01-23 14:08:08 GMT                                            

https://mega.nz/#!X10zlK6b!GAUE3SWEGS0b ... I4tRA_iJoU

Maybe I misconfigured job?

[fleamour]

Misconfigured job, but selecting all entries results in original error...

[PTide]

No, it is not a misconfigured job. This error:

Code: Select all

14:08:08         [error] Failed to load module [veeamsnap] with parameters [zerosnapdata=1 debuglogging=0 s...

It means that veeamsnap module failed to load. There are several possible reasons - the installation has gone wrong, or the kernel version that you use is not supported for Tumbleweed (4.18 is the highest). If your kernel version is ok, then please try to reinstall the agent (make sure that kernel headers that you use match your kernel version). After reinstall check if the module is loaded (lsmod | grep veeamsnap),, and if it s not, then try load it manually (modprobe veeamsnap).

Thanks!