Backups fail with "Device not found" after Update to V3

[ibschreiber]

Hi,
after the update to V3, I can't backup a disk of mine since the update.
the log states:

Code: Select all

[24.01.2019 12:35:50] <139709019645696> lpbcore|       Found device: [/dev/dm-5]. Device number: [253:5]; Type: [dm].
[24.01.2019 12:35:50] <139709019645696> lpbcore|         Slave of: [8:33].
[24.01.2019 12:35:50] <139709019645696> lpbcore|         Link: [/dev/dm-5].
[24.01.2019 12:35:50] <139709019645696> lpbcore|         Link: [/dev/block/253:5].
[24.01.2019 12:35:50] <139709019645696> lpbcore|         Link: [/dev/mapper/daten-linux].
[24.01.2019 12:35:50] <139709019645696> lpbcore|         Link: [/dev/disk/by-label/Daten_Linux].
[24.01.2019 12:35:50] <139709019645696> lpbcore|         Link: [/dev/disk/by-uuid/5e5d0610-2d00-4922-aed8-e3ca43f8b736].
[24.01.2019 12:35:50] <139709019645696> lpbcore|         Link: [/dev/disk/by-id/dm-uuid-CRYPT-LUKS1-4ca47e3681504f7bb6331ce0ce185b0d-daten-linux].
[24.01.2019 12:35:50] <139709019645696> lpbcore|         Link: [/dev/disk/by-id/dm-name-daten-linux].
[24.01.2019 12:35:50] <139709019645696> lpbcore|         Filesystem uuid: [5e5d0610-2d00-4922-aed8-e3ca43f8b736]; Type: [ext4]; Mount points: [/mnt/Daten_Linux].

so the device is found.

later on it fails:

Code: Select all

[24.01.2019 12:35:50] <139709019645696> vmb    |     [SessionLog][error] Unable to backup object: DEV__dev_dm-5(not found).
[24.01.2019 12:35:50] <139709019645696> lpbcore|   Enumerating backup objects. Failed.
[24.01.2019 12:35:50] <139709019645696> lpbcore| BackupJobPerformer: Creating backup. Failed.
[24.01.2019 12:35:50] <139709019645696> vmb    | [SessionLog][error] Failed to perform backup.
[24.01.2019 12:35:50] <139709019645696> vmb    | [SessionLog][error] Some objects were not processed.

Any Idea what's going on? Tried to select the mountpoint, same here.

Thank you very much,
Michael

[PTide]

Hi,

You should contact the support team directly, as there is no way of troubleshooting that sort of issues via forum board. Best effort support is available even if you don't have a subscription. Please post your case ID once you do that.

Thanks!

[ibschreiber]

Thank you! Case ID: #03379978

[PTide]

Hi again,

Development team got the logs, the troubleshooting is in progress.

Thank you!

[ibschreiber]

So, the answer is: not supported anymore. I can't believe this worked for so long and now I can't use the veeam backup anymore. I have veeam up and running with multiple customers of mine, saving linux servers, too. Locked the client version there to prevent bricking the backup mechanism.

I did some testing today and downgraded to an older version of the client. Works perfectly with all my disks. No matter if they are ext4 -> lvn -> luks, ext4 -> luks or plain ext4. I can backup and restore without any problems.

So what is the solution here? Migrating back to unencrypted disks? For 20+ servers which have been running perfectly for years? That's weeks of work, loosing encryption and just because of the backup system?

Why would you break a mechanism which has been working for so long...?

It's truely a black day for Linux and Veeam.

[PTide]

So, the answer is: not supported anymore.

We as a company never had an intention to cut off or break the support for LUKS. We certainly want to have it fixed, and the fix is being prepared.

Thanks!

[ibschreiber]

Is there a timeline when the fix will be available?

[ibschreiber]

If you need someone to test a new version, feel free to contact me.

[PTide]

Thank you for volunteering! New version will be provided via support as soon as QA finishes all mandatory internal test procedures (we simply cannot let a new build out without those).