Your experiences with VSA/VIA-environments updated to v13.1.x

[Didi7]

Since the release of VSA or VIA v13.0.x we had no significant problems, also not during upgrades. Everything went smooth and systems rebooted properly.

At the day when we decided to upgrade to v13.1.x we were not at the latest updates of the current week, instead we decided to upgrade to v13.1.x directly. The upgrade did not went totally smooth. We had to repeat upgrades on several machines, some went fine, some did not went fine. It took several hours to complete the update for every machine in our infrastructure.

In the upcoming days weekly updates did not went smoothly as well, we had to interfer each time.

Probably because we always had troubles with our physical Hardened Repository systems. Every time updates had been installed, systems were no longer reachable and we had to restart them, some of them the hard way, as 'Sign in' wasn't possible.

These 11 Hardened Repository systems are up-to-date now, are reachable via Ping and in the infrastructure but the Console on 8 of 11 machines can not be used. Sign in is not possible. It is probably always the same behavior ... as soon as updates are installed, all 11 sytems do not communicate externally, they have to be rebooted manually and in the end most of them can not be operated Console-wise.

The rest of the machines are virtual VMware machines and they work properly. Sign in is possible. We checked every system today.

We would be interested to hear from your update experiences, from similar effects in your environments. Are there users with 'Sign in' problems on the Veeam Host Management console on physical Veeam Hardened Repository systems, e.g. you cannot press ENTER or RETURN to sign in? Do updates for v13.1.x run smoothly on your Hardened Repository systems?

[vnikiforov]

Hello,

Please avoid creating the same questions in different threads, as I already stated previously - what needs to be done is to create a support case.
Please provide full hardware info (firmware model, NIC model and firmware, NIC configuration (bond, LACP, etc) for your physical hosts and if any of it are different from the others in terms of specs\configuration.
It might be related to an issue under investigation, related to the latest CIQ Linux kernel, which comes with the update, but every such case differs so support needs full data along with logs.
For your convenience you may refer to already investigated internal issue 1611568 - that could expedite the process for you.
Thank you in advance.

[Didi7]

Hello vnikiforov,

you know we intended to get some experiences from other environments by creating this new thread. Are there environments with Veeam Host Management consoles, where login is no longer possible, as the console does not allow to sign in anymore.

As login is no longer possible, we cannot activate Web- or SSH-access as well. How should we generate logs in this case?

Of course we could open a support case, but currently we simply see no possibility to get access to the management of those system.

May we ask, if internal issue 1611568 is related to login issues in the Veeam Host Management console?

As we need to move forward, we seriously consider moving backup data from those backup repository system to another virtual VHR system and reconstruct the original system, just in case VHR reconstruction with the VIA ISO fails and we need to reconstruct those systems from scratch.

[vnikiforov]

Hello,

That is fair, as you can't login. Anyway please do open the case and refer to the internal issue number - that should help you get to right people. The reason I'm so vague with the instructions is that I can't obviously guarantee - that is exactly your issue as well. That is why I specifically indicated what must be included in your report, as that is very important to have precise information.

What I see internally, there is very new issue discovered with some hardware systems and latest CIQ Linux kernel, which prevents NICs to operate correctly as drivers can't be loaded, BUT VMs are not affected on the same versions as vNICs use different drivers. That matches your explanation precisely that is why I recommended what I have already recommend - you may also refer to that forum post as well.

[Didi7]

I see, but the question that raises up here, is it really related to the NIC? It might be related to the NIC as well, but as those systems are still reachable from the VBR server, the communication works somehow and currently we would be able to move backup repository data somewhere else.

To us it looks more like a problem with the Veeam Host Management console and the keyboard driver.

It would be a total disaster, if communication from outside (the VBR server) would be disrupted as well, that is still not the case.

[vnikiforov]

I can't tell, Sir! Honestly, I'd love to have a direct answer to help you, but I don't have it. Keyboard driver also might be an issue (and that is a different issue) - engineer would investigate your environment based on your hardware details provided and advise further.
Support should help with that - I definitely understand the severity and you may also mention it in the case, asking to escalate right away. In that specific case that is acceptable, as it is the issue currently under active investigation. (set severity 2, not severity 1)