Failed v8 upgrade

[SteelContainer]

Hi there,

We recently tried to upgrade from v7a to v8. The main 365 server seemed to upgrade fine, but we had issues getting the remote proxies to update. They seemed to just timeout during the upgrade process in the Veeam console. Then if you try to upgrade the remote proxies again, they will say the upgrade is currently running although there was no visible processes or disk access on the proxies to confirm anything was still happening.
We eventually had to roll back to v7a via VM backups which caused it's own set of issues with some of the JetDBs (JetError -501, JET_errLogFileCorrupt, Log file is corrupt) see case #07434172 for reference.

Now we are back in a stable state running v7a and are planning the upgrade again.
Listed in the v8 release notes for the 365 server and proxies are the following:
Microsoft .NET Runtime 8.0.7 or later.
Windows PowerShell 7.4.2 or later is required.
In the past the Veeam installers have installed requirements and features, do we need to install these manually on the proxies now? We tried installing these manually during the last upgrade but want to make sure this is the correct process.

Are there any new patches coming soon that would change our upgrade experience? We provided our v8 logs in our support case and asked if there was anything obvious that was caused the upgrade issues but support were only keen to make sure v7a was working and noted we could just log another case next time.
I am a bit hesitant to attempt the upgrade again given the issues we experienced with both the upgrade and the roll back to the older version, although this is the first time we have had issues upgrading.
We also have 30+ organisations under the one multi-tenant console so we need to add all of the new graph permissions and do the repository upgrades following the version upgrade so it is a bit more of an undertaking than normal.

Appreciate any advice, Thanks!

[Mike Resseler]

Hi,
Normally we will release another (big) patch next week. So you might want to wait for that specific one.

That said, installing the prerequisites manually should be a good thing. Out of the issues I have seen the last few weeks, I am guessing there is an issue and you will need to open more firewall ports (check the requirements, with NATS in play, there is additional networking config to do).

But in essence, when you go through the upgrade again, it should be a smooth experience and I am a bit disappointed with the response that you received for support. Is that the same case # as you mentioned above or another one?

[Seve CH]

Hi

If you are not forced by contract to update in a specific time frame and you are happy with v.7, I would stay in v.7 for at least 2-3 months.

The new v.8 architecture is IMHO much better and professional, but it's at the moment a complete mess at least for medium to big installations.

Best regards
Seve

[SteelContainer]

Thanks Mike, I'll hold off until that patch is released.

Yeah I noticed extra ports required between the remote proxies and the V365 server for Nats and Postgres and I'll intstall the .NET and powershell requirements ahead of time for the next attempt. Hopefully things will go smoother.

Yeah the response was at the end of the case mentioned above, I had uploaded the logs from the failed upgrade before rolling back the version and just wanted to know if there were any insights into why the proxies failed to upgrade.
I'll try again after the next patch and log another case if I run into more issues.

Thanks!