2 Replies Latest reply on Jul 31, 2017 9:03 AM by walter.gildersleeve

    Jive 7 to 9 on premises migration

    jcampbell

      Hello, we are in the process of upgrading from Jive 7 to Jive 9 and we are following the "lift and shift" method of creating a fresh Jive 9 installation on a clean server and then migrating our Jive 7 content over.

       

      There is some confusion as to whether we should be running the initial Jive 9 installation using a blank database or a copy of our Jive 7 database. Do we:


      1. Run the initial Jive 9 installation on a clean OS and during the wizard setup point it to a copy of our Jive 7 database
      or
      2. Run the initial Jive 9 installation on a clean OS and during the wizard setup point it to a blank database, then once the installation is complete restore our Jive 7 database over top of the new Jive 9 database

       

      Thank you,
      Jonathan

        • Re: Jive 7 to 9 on premises migration
          pushpendra.paliwal

          Jive Upgrade essentially involves change in database structure. It is not possible to run Jive 9 pointing to Jive 7 database schema.

          • Re: Jive 7 to 9 on premises migration

            Hi,

             

            Typically I completely install Jive to the new version, then test it to make sure everything is working. Once that's done, you can nuke the newly-created dB and copy your Jive 7 data over. On startup, Jive will detect that the dB version is old and kick you into the upgrade console.

             

            Completely installing and successfully testing the higher version eliminates a lot of problems during the actual data upgrade. That way, you don't have to worry during upgrade that errors you are seeing are environmental, and can be sure they're data-related.

             

            Hope this helps,

             

            Walter