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...

[vnikiforov]

Hello, Stephen,

That seems like something else, please continue with support.

[Origin 2000]

Same problem here. Upgrade process tries to deinstall it packages and than complaining that it is unable to install what ever is needed.

IIRC i fixed it buy clicking through the Linux Server entry rather than under repository and provide a new Single Credential. The Wizard listet that half of the components are there and install the missing ones. Ofter that the repository was back.

Regards,
Joerg

[Didi7]

There seems to be some significant problems with VIA-based Hardened Repositories since 13.1.x !!!

Every time new updates are available our physical Hardened Repositories stop communicating and they have to be rebooted in order to work again.

It looks like NIC communication is broken, but it may be a bigger problem => even the console is not reacting any more, so a hard reboot is necessary, same phenomena on each physical hardened repository system. I noticed this since we upgraded from 13.0.x to 13.1.x and it continues to be a problem with every new update available within the VSA-environment.

The consequences => Hardened repositories are no longer available, backups fail! Updates don't run smooth, as those Hardened Repository sytems are no longer available.

Correction:
Some consoles react, other do not react. In any case the NIC communication is lost, so you need to at least reboot the system. Never was a problem in 13.0.x

[vnikiforov]

Hello @Didi7,

If you face technical difficulties with the product, please open a support case per problem and attach full relevant logs.
The issue you are describing is too broad to be advised on - it could be anything. I'm not aware of any known issues with this behavior at this time

[EKo_BEOFG]

Hello,

The problem is resolved.
We completely deleted the repository server and installed it from scratch using the latest Veeam Infrastructure Appliance ISO.
This was possible, because we had other backups on copy repository and tape.

Regards,
Emil

[vnikiforov]

Hello, Emil,

Thank you for the update. Good to hear that is resolved.

[Didi7]

Interesting EKo_BEOFG !

We currently have eleven Veeam Hardenened Repository systems, on which we see the Veeam Host Management screen and the only button 'Sign in'. This systems are all HPE based with the latest BIOS, firmware and Intelligent Provisioning.

We can see that the time in the Veeam Host Management screen is updating but on most of this systems we cannot 'Sign In' anymore. Ping is possible to all those systems and they all interact with the VBR server as well (all updates done on every system as well). We are currently in the process to check if all virtual VIA-based systems work properly, so far they do.

So it probably has something to do with the new version 13.1.1.18 and/or the hardware BIOS or firmware versions, as this did not happen with 13.0.x at all.