12.3.1 strange setup experiences

[karsten123]

Hi,
I updated a VBR 12.2 to 12.3.1 and something strange and unexpected happened.

First splash screen was „install“ and not the usual „upgrade“ button. After that i was able to click on upgrade VBR, select license and after prerequisite check, the setup installed straight away. No service account and database selection as I know it.
Is this the new way or is it a bug?

I am confused. Setup was successful, so nothing to worry about. I am just curious.
Karsten

[mjr.epicfail]

Yeah saw the same, looks just cosmetic to me.

[Gostev]

@Egor Yakovlev

[Egor Yakovlev]

Hi guys.

Yes, that is expected - we have restricted the ability to change the service account and database during upgrade.
Both operations can be performed on a live product before\after upgrade.

[Gostev]

@Egor Yakovlev I believe, discussed here is the new.name of the button that used to say Upgrade before (when executed on the existing backup server) but now says Install, which leaves users with an impression that the existing install is not detected and therefore something might go wrong with the upgrade.

[Egor Yakovlev]

Got it, surely we can tune it.

[mjr.epicfail]

next page will show the 3 install options (VBR, console only, enterprise manager) and shows upgrade. Its just strange that the splash screens shows install instead of upgrade as like in previous versions of the ISO.

[karsten123]

It would be great to check SSPI authentication with the postgresql database while pre checking. If there is something wrong, setup will fail.
Before 12.3.1, you get the warning after selecting database but before installing the upgrade.

[apolloxm]

We would like the service account and database can be selected.

[Egor Yakovlev]

Options to change the service account and database during upgrade process lead to additional setup complexity.

If upgrade fails due to account\DB connection issues, that means upgrade is being performed on a corrupted installation that has those problems outside upgrade sequence.

Both options can be changed on a live product, outside of upgrade process, any time of a day, with same validations in place, using services.msc and Configuration Database Connection Utility.

[roland]

I experienced the same behaviour during upgrade.
I also have a failed upgrade because of "SSPI authentication failed for user" on postgresSql database and i find usefull information here https://www.veeam.com/kb4542
Finally i restart the upgrade with the same user used during first veeam installation and the upgrade was successful .