Rescan and VAL jobs fail after B&R upgrade from 11 to 12

[gothaggis]

I have a ticket open with Veeam - case 07115374

VAL 5 was working on RHEL 9.2 and our B&R server was running 11. We upgraded the B&R server to 12 - now all VAL jobs are failing (unable to process, host rescan is required). When I go to rescan the physical RHEL host under the Manually Added protection group - it fails with the error:

"Installing Installer service Error: Error: package veeamdeployment-12.1.0.2131-1.x86_64 does not verify: no digest; Exit code 1
Failed to connect to <myservername> Details: Error: package veeamdeployment-12.1.0.2131-1x86_64 does not verify: no digest"

No other changes other than the upgrade from 11 to 12 have happened (I booted to RHEL 9.3 from 9.2 to test, same result). If I edit the protection group (Manually Added) and test the username and password used for the VAL backup jobs, they test successfully, so that isn't the problem.

Has anyone run into this problem?

one more thing - I am able to run veeamconfig ui from the linux server and successfully restore files from previous backup jobs

[gothaggis]

Figured out 1 problem - the server is running in FIPS mode - this was preventing the rescan. I disabled FIPS and now it successfully rescans, however ran into a new problem when upgrading the agent to 6.1

2/2/2024 8:52:34 AM Failed [prc1] Failed to update veeam-6.1.0.1498-1.el9.x86_64.rpm, veeam-libs-6.1.0.1498-1.x86_64.rpm and kmod-blksnap-6.1.0.1498-1.el9.x86_64.rpm packages: error: Failed dependencies: veeamsnap conflicts with kmod-blksnap-6.1.0.1498-1.el9.x86_64 Failed to invoke rpc command 0:00:01

[rovshan.pashayev]

Hello Geoff,

Please ensure you provide the latest information and details about the new error to our support team for a more accurate analysis and resolution.

Rovshan.

[gothaggis]

It seems the resolution is that VAL (veeamblksnap specifically) doesn't support 5.14.0-362.18.1.el9_3.x86_64 - will have to fall back to an earlier version.

[PTide]

Hi,

Actually there is a patch to support 5.14.0-362.18.1.el9_3 kernel. Please let me conduct that info to the support team and do not close the case so that they can give you the bits.

Thanks!