Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v9.5.4b to v10a upgrade does not properly upgrade all components #14

Open
lenaertswouter opened this issue Sep 2, 2020 · 0 comments
Open

Comments

@lenaertswouter
Copy link
Contributor

Hello Goodrum,

Thanks for all the work to support v10a! I just wanted to report an issue I ran into while testing the upgrade process from v9.5.4b to v10a.
To make the upgrade it seems this cookbook installs the package found in the v10 ISO’s “update” folder. Initially this process seems work for major version upgrades like v10 but has some underlying issues when I look closer.

When making the jump from v9.5.4b to v10a not all components get properly upgraded. See screenshot. Also the “add and remove programs” list now shows components that shouldn’t be there. It seems to be residue from the previous version that now cannot be uninstalled anymore.

veeam_upgrade_1
veeam_upgrade_2

Interestingly the Veeam documentation tells us in case of unattended upgrades we need to uninstall all Veeam packages and reinstall connecting to the old configuration SQL database.
Source (see bottom section): https://helpcenter.veeam.com/docs/backup/vsphere/upgrade_vbr.html?ver=100

unattendedupgrade

Would it be wise to stick to the Veeam recommendation? I think we could solve this by making the upgrade.rb resource be able to distinguish between major version upgrades or minor version updates and have it uninstall all Veeam components when an older major version is detected.

I am curious what you think about this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant