Official Linux repository ISO - permission issue veeamsvc

[BostjanUNIJA]

Hi.
Downloaded official Veeam Linux Hardened ISO (from my.veeam.com).
Went thru the wizard. Changed vhradmin password. Started SSH.
On the VBR server I have chosen Veeam Backup Repositories and added Hardened Linux Repository.
When I put credentials for veeamsvc temporary ssh connection it connects (it askes me to confirm the fingerprint of the server) but in the next phase it throws an error
Sorry, user veeamsvc is not allowed to execute '/bin/rpm --import /tmp/VeeamUpload_20260120T051628Z/RPM-VEEAM-PUBLICKEY' as root on Linux-repo; exit code 1

What am I doing wrong?
Even if I checkbox when adding the temporary SSH user: "Use su if sudo fails" and then enter here password of a user vhradmin and the new password we have durring the linux hardened wizard, that also doesn't help.

The customer has VBR 12.x environment so we have downloaded: "VeeamHardenedRepository_2.0.0.8_20250117.iso" from my veeam site.
Before we had tried adding this repository to VBR on the Hardened VM we have also clicked on: update-all.
Maybe that did something wrong, and upgraded to 13.x which wouldn't be compatible with VBR?
No ideas why it ain't working
Please advise.

[Mildur]

Hello Bostjan,

Unfortunately, we can’t determine what’s wrong based on a forum post, as explained in our our forum rules.
Please contact our Customer Support team, as required for any technical issue, and provide the case number.

Maybe that did something wrong, and upgraded to 13.x which wouldn't be compatible with VBR?

It should be easy for you to check which version your customer is using.
If they are indeed on v13, please use our new Veeam Infrastructure Appliance ISO for the hardened repository.

However, I don’t think that’s the root cause here — the Hardened Repo ISO v2 should still work with the latest v13.0.1, even though it’s no longer the recommended option.

Best regards,
Fabian

[BostjanUNIJA]

Hi.
Since this is a new customer we are waiting so they grant us access to their support ID so we can open tickets. Will probably be resolved in next days, since the guy to which Veeam contract is linked is out of office.
While waiting to resolve above I was digging further if someone else had the same issue and found on Veeam's forum that this is/was a known issue with Veeam Hardened ISO V2.

Link: "veeam-backup-replication-f2/managed-har ... 9ded45ed6c"

I see its related to some sudo whitelist issue for veeamsvc user.

I have a few question:
If a customer has VBR currently on version 12.x is it mandatory to use V2 hardened ISO?
Or is VBR version 12.x ALSO compatible with V13 hardened ISO?

Since I have deployed Veeam appliance only in my virtual lab in a prelease/test version (I think it was in October or November last year) as far as I remember the linux appliance also had a seperated ISO for V13 for deploying hardened linux iso repository.

And since in the forum (on the other thread) they are mentioning if you are on V2 you should select: "update all" in SSH menu, I havent debugged yet if we have some network inspections limitation that it doesnt complete update properly.
Argh

[BostjanUNIJA]

I think I found a culprint.
Customer is on VBR version: "12.1.2.172" and that is not compatible with Hardened build 2.0.0.8, so it looks like the next step is to upgrade it to version 12.3 any try again.

[BostjanUNIJA]

I will report the progress.
One off topic question, whats the best practise to deal with expanding immutable linux repositories? Probably by putting them in SOBR, right?
I have never tried (yet) putting two immutable linux repositories in SOBR but looking forward to testing in VirtualLAB.

[Mildur]

Our Veeam Infrastructure ISO v13 is not compatible with Veeam Backup & Replication v12.

One off topic question, whats the best practise to deal with expanding immutable linux repositories? Probably by putting them in SOBR, right?

For v13 Infrastructure Appliance deployments, please use SOBR for now. We plan to introduce a storage expansion feature with v13.1.
For the v12 ISO, you could theoretically boot into single-user mode and use basic Linux commands to extend the storage.

I have never tried (yet) putting two immutable linux repositories in SOBR but looking forward to testing in VirtualLAB.

It works the same as every other SOBR extend. With the exception, that Immutability will affect Rebalancing, Evacuation and Capacity Tier Move Policy (+ GFS immutability period when Move is enabled).

Best,
Fabian

[BostjanUNIJA]

Hi.
Fyi:
To share the solution.
Had to upgrade VBR to latest 12.3 version which resolved the issue