Dataverse Migration - need advice

[Ayu Widi]

Hi There,

We are currently running Dataverse 4.20 in our production environment(CENTOS 7), and now for some reason we will migrate the dataverse into a new VM server (Rockylinux), and we want to upgrade the dataverse to 5.10 version.

We need advice if there's some best practices to do this, is it better to upgrade the current dataverse into the latest release before migrating it, or we can install a new fresh dataverse 5.10 in the new server (need advice on how to move the database)?

--

Regards,

Ayu

BRIN-Indonesia

Phone /SMS/ Whatsapp : +62 818 0778 6675

[Philip Durbin]

You need to install each release one after another (5.0, 5.1, 5.1.1, 5.2, etc.) so I would recommend doing this on a test server and then on your production server. Once you are on the latest version, you could migrate to your new server.

I hope this helps,

Phil

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CAO2JCMxzJx82qQphaYt06LXiWj5COVSVphB9et-zUMHKUu-UKA%40mail.gmail.com.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[Ayu Widi]

Thank you, 

We will try to upgrade it first then migrate to new server as suggested, i will reach you if there's any problem in our migration phase. 

Regards

On 21 May 2022, at 04.43, Philip Durbin <philip...@harvard.edu> wrote:



To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8EBENF5hFbr4DR6dboF1Ps_HKu%3D0JoXtn03eK7%2B8wE39g%40mail.gmail.com.

[juan...@gmail.com]

We just migrated e-cienciaDatos from v4.19 to v5.10.1 two weeks ago. We needed one work day for the production server migration.

Our dataset files are in a disk server (not S3 or similar) out of the main Dataverse server.

- At first we migrated our Dataverse instance in the test server and put here our customization and translation.

- We have write a little migration guide at the same time. This guide is more specific for our particular case that the general guide and we detailed here the problems found.

- We created a war with our v5.10.1 customization.

- We advice to our librarians to not create datasets the day of the production server migration (only librarians can create datasets in our installation)

- The migration day, we connected the disk server to the test server to avoid stop the service for 6-8 hours (we profited to make several operating system updates). We changed the main e-cienciaDatos url to point to the test server. The only problem of this approach is that we loss the usage statistics of the time that the production server was out of service.

- Before the production server migration, we had all needed files organized for Dataverse version (payara versions, solr, tsv files, dataverse war files, ....)

- After the migration and customization, we connected the disk server to the production server, we had changed the e-cienciaDatos url to point the production server, and we had said to the librarians that they can create datasets.

  Tell me if you want more information.

Regards,

Juan