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?