Entire computer, device, & volume backups fail for clients with Btrfs, even when the Btrfs array is excluded from backup

[jdrch]

I recently posted in the subreddit and opened a bug (Case #03721691) about Veeam Agent for Linux failing to backup Btrfs raid1 arrays.

Upon further review, it seems the problem is worse than originally reported. Device and volume backups from computers containing Btrfs raid1 arrays also fail, even when the arrays aren't included in the backup. Here's the log from the most recent attempt:

Code: Select all

     Backup                                         0%                                        Status: Failed



     Summary                              Data

     Duration:           00:00:30         Processed:          ---
     Processing rate:    ---              Read:               ---
     Bottleneck:         ---              Transferred:        ---

      Time             Action                                                                     Duration

      09:44:05         Job Dell OptiPlex 390-1 started at 2019-08-26 09:44:05 GMT
      09:44:06         Preparing to backup
      09:44:07         Waiting for backup infrastructure resources availability                   00:00:02
      09:44:09         [error] Failed to create volume snapshot                                   00:00:26
      09:44:35         [error] Failed to perform backup
      09:44:35         [error] Unsupported multidevice BtrFS configuration
      09:44:35         [error] Failed to convert logical extend [542303584256:13958643712] to ...
      09:44:35         [error] Failed to allocate data file for snapshot storage
      09:44:35         [error] Processing finished with errors at 2019-08-26 09:44:35 GMT

For comparison, here's the log without the Btrfs raid1 array mounted:

Code: Select all

     Backup                                        100%                                       Status: Success



     Summary                              Data

     Duration:           00:47:15         Processed:          521 GB (100%)
     Processing rate:    189.4 MB/s       Read:               521 GB
     Bottleneck:         Source           Transferred:        2.9 GB (182.4x)

      Time             Action                                                                     Duration

      03:30:01         Job Dell OptiPlex 390-1 started at 2019-08-12 03:30:01 GMT
      03:30:02         Preparing to backup
      03:30:04         Waiting for backup infrastructure resources availability                   00:00:02
      03:30:06         Creating volume snapshot                                                   00:00:01
      03:30:10         Starting incremental backup to [DellInspiron560] Default Backup Repository
      03:30:10         File system indexing is disabled
      03:30:13         Backed up sdb 757.7 MB at 84.1 MB/s                                        00:00:09
      03:30:34         Backed up DELLOPTIPLEX390-1-vg 520.3 GB at 190.6 MB/s                      00:46:35
      04:17:09         Backing up summary.xml                                                     00:00:01
      04:17:12         Releasing snapshot                                                         00:00:03
      04:17:15         Processing finished at 2019-08-12 04:17:15 GMT

Any ideas?

[PTide]

Hi (again ),

Currently VAL doesn't support BTRFS configured as RAID. Three things will be done in that matter:

1. User guide will be updated shortly

2. VAL behaviour correction will be scheduled (skip such BTRFS systems for Entire machine mode)

3. File a feature request for support for next versions

Thanks!

[einhirn]

Blast from the past, but I ran into that issue with VAL 6.1.x just now.

When googling, I came about https://www.veeam.com/kb2771 which is mostly unrelated but points to an "ignoreDevices" entry in /etc/veeam/veeam.ini

My multidevice BtrFS uses /dev/sda and /dev/sdb so I put

Code: Select all

ignoreDevices = /dev/sda;/dev/sdb

into my /etc/veeam/veeam.ini and restarted the veeamservice as instructed.

This worked insofar as I was able to create a volume based backup of the system, probably an "entire computer" backup would also have worked!?