Hi All,
This is more an FYI to the community to check Veeam pre requirements/release notes before doing upgrades so that you don't have old servers which are no longer supported.
I found with a client today who did not do this. However the v13 precheck didn't notify that they had a ESXi server that was not supported.
The end result was the upgrade occured but the Veeam Backup Service would not start.
In this specific case the old ESXi server was running ESXi6 and was managed by vCenter 7 with multiple DCs under the vCenter.
Additionally, as a reminder take a snapshot prior to upgrading for rollback.
In this case they tried to remove all the Veeam and PostgreSQL components but after this the v12 installer would not load.
As such we had to rebuild the backup server, install v12.3, restore the config, remove the effected vCenter (as the vcenter had been replaced, but not removed from Veeam) and then upgrade the server.
R&D, Might be something to look into to ensure these pre checks are working as they have previously.
It could be in this case that as it was a non supported ESXi server under a managed vcenter it may not work, but I would have assumed it would.
-
richardbradley
- Service Provider
- Posts: 38
- Liked: 4 times
- Joined: Dec 06, 2021 11:31 pm
- Full Name: Richard Bradley
- Contact:
-
HannesK
- Product Manager
- Posts: 15981
- Liked: 3598 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: v13 Upgrade Pre Check Issue
Hello,
thanks for sharing. The ESXi topic is something I will discuss internally. Normally we should check all connected components for compatibility, but there are exceptions (e.g. unmanaged database plugins).
I must admit, that I cannot follow the second scenario
What was the idea of uninstalling Postgres and then try the V12 (or is this a typo?) installer and replace VCenter at the same time?
Best regards
Hannes
thanks for sharing. The ESXi topic is something I will discuss internally. Normally we should check all connected components for compatibility, but there are exceptions (e.g. unmanaged database plugins).
I must admit, that I cannot follow the second scenario
Best regards
Hannes
-
richardbradley
- Service Provider
- Posts: 38
- Liked: 4 times
- Joined: Dec 06, 2021 11:31 pm
- Full Name: Richard Bradley
- Contact:
Re: v13 Upgrade Pre Check Issue
So the client was using v12 previously and wanted to rollback to v12 to revert as they didn't take a snapshot.
I also tried this after the fact for testing and found the exact same behaviour.
I wanted to test this as when upgrading particularly on physical VBR servers I cannot take a snapshot, so if there is an issue like this I can rollback fix it and then upgrade again.
Not that I would even hope to see anything like this, but wanted to confirm what options I have as I still have a few clients with physical VBRs.
I also tried this after the fact for testing and found the exact same behaviour.
I wanted to test this as when upgrading particularly on physical VBR servers I cannot take a snapshot, so if there is an issue like this I can rollback fix it and then upgrade again.
Not that I would even hope to see anything like this, but wanted to confirm what options I have as I still have a few clients with physical VBRs.
Who is online
Users browsing this forum: Amazon [Bot], Bing [Bot], Google [Bot], Semrush [Bot] and 89 guests