[OPEN-ILS-DEV] Looking for a way to upgrade my EG 3.0 installation in less than 8 hours

[Ken Cox]

Bill and Jason,

Your advice was extremely helpful and very much appreciated.  It makes
perfect sense now for the ansible scripts to create installs from
scratch, since you might do that every week.  When I slowed down and
paid careful attention to the upgrade SQL, it made more sense and I
was able to take my DB at version 1087 and upgrade it confidently to
3.2.2.

Thank you!

Ken

On Mon, Feb 25, 2019 at 11:40 AM Jason Stephenson <jason at sigio.com> wrote:
>
> Ken, et al.
>
> I think I should add something else to the previous email.
>
> We also upgrade our training server about 6 months prior to when we plan
> to upgrade.  This keeps us about 1 release behind.  Staff get to test
> the upcoming release on the training server with close to recent/real
> data.  I also keep training up to date with recent point releases, so
> that means I'll do a mini-update from 3.2.3 to 3.2.4 later this week.
>
> We used to upgrade twice per year, but I think we're moving to just 1
> per year, which also means skipping releases.  For instance, we're going
> from 3.0.13 to 3.2.[45] at our next upgrade.
>
> And, when I talk about testing, I mean it.  It is imperative that you
> test the database upgrade script with a recent copy of your actual,
> production data.
>
> Upgrades of Evergreen are not something that you just do, they require
> planning and preparation, otherwise you could be facing days of down
> time and unhappy users.
>
> HtH,
> Jason
>
>


-- 
-Ken