Dear PrivacyIdea Community,
I have a much neglected privacyidea application running on version 2.21.4 that I am considering upgrading to v3.8.1.
Can anyone please advise if the database schema upgrade scripts are able to deal with such a large gap between the start(v2.21.4) and target(v3.8.1) db schema versions?
If this is not practical or feasible, I will deploy a new clean v3.8.1 database, a new v3.8.1 application and recreate QR codes for the team.
If you are running privacyIDEA 2.21, then you most probably are running a very extremely old distribution underneath. Maybe you should set up a new one, anyways.
The schema upgrade should™ work.
However, if you have a couple of thousands tokens in your database, the migration could take a while when updating from 2.x to 3.0.
Thanks for replying Cornelius, and for the advice also.
We are currently running privacyIDEA on Red Hat 7 so the underlying distribution is not so old.
Is the databse schema upgrade simply a matter of executing the following command from the new privacyIDEA 3.8.1 application server after amending the db pointer within the pi.cfg file to point to the old 2.21 database server/schema?
The pi.cfg file currently points to the new empty db schema running at version 3.8.1 so repointing it to the old db server should be very straightforward.
Are there any ‘dummy’ or ‘trial’ upgrade runs that can be performed to see if the upgrade is likely to work or fail?
What if the upgrade fails halfway through the process? Will that leave the database corrupt requiring a restore?