Hardened Repository broken after upgrade to VIA

[EKo_BEOFG]

### Regarding Case # 08201927 ###

Hello,

during upgrade from Veeam 13.0 to 13.1 the installer shows a message that I should upgrade the Veeam Hardened Repository to the new Veeam Infrastructure Appliance.

After installation of 13.1 was finished, it could not connect anymore to the existing VHR and it could not be updated remote by the Veeam Server because of insufficent permissions.
Providing new single use SSH credentials did not changed anything.

So I decided to upgrade the VHR to Veeam Infrastructure Appliance immediately. I downloaded the ISO, mounted it to the server and started the setup.
Unfortunately, during the setup the connection to the ISO got lost, the setup-process stuck and I had to do an hard reboot. The bootloader was broken and the server did not boot anymore.
My attempts to reinstall or upgrade again was failing.

I opened Case # 08201927. I was suggested to do an repair installation of the old VHR version.
It seems that this was successfull, but the server has no network connection anymore. I used the previous, working IPv4 settings.
The VHR setup said "Connected" on this interface but I cant ping or connect to SSH.

This case is opened since 18th of August without a solution.
The primary backup repository of our customer is affected and they can´t create new backups.

Any help is appreciated.
Thank you.

Best Regards,
Emil

[vnikiforov]

Hello, Emil,

I'm sorry to hear you are experiencing this situation.
From what I see in the internal communications, the case is now getting ready to be escalated.
I understand the urgency, so I would also recommend you to use talk to manager option, which should help you to clarify the issue.

[longwoodeng]

Same here (sort of).

Case #08208815

Veeam B&R 13.1 is complaining that the Data Mover Service on the VIA is out of date.

When running the Updated from B&R I have.. Failed to Upgrade Host components. Error: No connection could be made because the target machine actively refused it.

I did not attempt anything else as yet...