Grouper Users - Open Discussion List

["Hyzer, Chris" <>]

I changed the wiki:

 

I added a link to the upgrade instructions: https://spaces.at.internet2.edu/display/Grouper/v2.4+Upgrade+Instructions+from+v2.3

 

Also, I changed:

 

FROM:

 

We have to keep whats there and make a new env in a new tomcat and new database

 

TO:

 

On the demo server we want 2.3 to persist as an example, so we have to keep whats there and make a new env in a new tomcat and new database.  On an typical upgrade you will not keep the old env up and running like we do on the demo server, so ignore steps: 1, 2, 5, 8, 9, 10

 

Ok?

 

Thanks

Chris

 

From: <> On Behalf Of O'Dowd, Josh
Sent: Wednesday, September 19, 2018 3:45 PM
To:
Subject: [grouper-users] 2.3 to 2.4 upgrade import/export vs dump?

 

Hi,

 

Not long ago you helped me with a data migration where we wanted to move a v2.3 oracle registry to a v2.3 postgres.  Your recommendation was to try a new export/import option recently added to gsh.  I had a smooth successful go of that.

 

Now we are looking to upgrade to v2.4 and I am reading a recent post by Chris,

https://spaces.at.internet2.edu/display/Grouper/Grouper+upgrade+demo+server+from+2.3+to+2.4

.. which begins by creating a new database for v2.4, but then goes on to suggest doing an SQL dump from v2.3, to use as a primer for v2.4.

 

Does that mean that a gsh export file from v2.3 could not be imported using v2.4 gsh?

 

Thanks.

 

Josh O’Dowd

Software Systems Engineer / Identity Access Management

University of Montana