Upgrade from 3.2 to 4.1

[Abhishek Rathore]

Hi

Is there stepwise guide to upgrade from V3.2 to V4.1?

Or is it possible?

Regards

Abhi

[Philip Durbin]

Hi Abhi,

To upgrade to Dataverse 4 you'll need to do to each and every upgrade in between to perform all the database migrations, which are called buildupdates. For example, buildupdate_v3_2_v3_3.sql is for upgrading from DVN 3.2 to DVN 3.3. I believe you always run the database migration *after* you deploy the war file for that release but please check the release notes for each release: http://sourceforge.net/projects/dvn/files/dvn/

That way, you'll be on DVN 3.6.2, which is what these scripts for upgrading to Dataverse 4 assume: https://github.com/IQSS/dataverse/tree/master/scripts/migration

For all assistance with these upgrades I recommend opening a support ticket via sup...@dataverse.org

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 post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/a9ff88b5-668b-4692-81cf-557ff66c0531%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

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

[Abhishek Rathore]

Thanks Phil.

This is still unclear to me.

It seems there is not any established way.

I looked at suggested page

https://github.com/IQSS/dataverse/tree/master/scripts/migration

But could not got any clue.

Is it not possible for Dataverse team to distribute some installer (rpm) which upgrade and install V4?

it is so complicated and manual process, please help.

Regards,

Abhi

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8GR0K9TsowuQUVNumDAUCPrEbi7msK2V_HGFJhu6-kGsw%40mail.gmail.com.

[Philip Durbin]

You're right. The task of migrating a DVN 3.x installation to Dataverse 4 is not yet well explained. We've done it at Harvard but we expect for now that other installations will need assistance which is why I am encouraging you to email sup...@dataverse.org to open a support ticket about this.

Unfortunately, I don't think the state of packaging Java EE applications as RPMs has advanced much in the two years since I last posted about this: https://groups.google.com/d/msg/dataverse-community/ZX6RIqbHUHk/aTl-heYLiHYJ

If anyone has tips for packaging Java EE applications as RPMs (or Debian packages, I suppose), please let us know!

Phil

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CAD0UXAnO5i2EfXyO_Nn1QFRFy4u6g2p1U-j0a9LBnWFepDDTnw%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Condon, Kevin]

We are finalizing our instructions to include some lessons learned but upgrading from v3.6.2 to v4.0 involves three major steps:

1. Create a new environment using Glassfish v4.1, Postgres 9.3, Java 1.7, according to the Installation Guide:

http://guides.dataverse.org/en/4.0.2/installation/index.html [Open URL]

2. Migrate the database and files from v3.6.2 instance to v4.0.x

-move files and point to their location, update jvm option in the Glassfish domain.xml file

-run database migration scripts according to https://github.com/IQSS/dataverse/blob/master/scripts/migration/migration_instructions.txt [Open URL]

(https://github.com/IQSS/dataverse/tree/master/scripts/migration) [Open URL]

3. Reindex all metadata

Depending on how much data you have, this can take some time. A complete reindex of our Dataverse takes between 1 and 2 days but we have 30,000 datasets.

To index all:

 -first clear the lastindextime from the dvobject table:

update dvobject set lastindextime=null;

 -next run index all by entering the following into a browser:

http://<yourhost>/api/admin/index

We recommend trying this all on a test machine first to understand how to execute all the steps. You should also record and verify the main object counts: dataverses, datasets (studies), files, and users. Last, confirm you can create new objects, update existing/ migrated objects, and review a sample of your migrated dataverses, datasets and files.

We have used these scripts and process in our own production environment so everything works but there is always some variations in data so a review is recommended.

---

From: dataverse...@googlegroups.com [dataverse...@googlegroups.com] on behalf of Philip Durbin [philip...@harvard.edu]
Sent: Saturday, July 11, 2015 12:39 PM
To: dataverse...@googlegroups.com
Subject: Re: [Dataverse-Users] Upgrade from 3.2 to 4.1

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/CABbxx8Eg8bV4v7cJ2NYeT8uq7Y0-04x_LB1UtjKaZERiTbGQDg%40mail.gmail.com.

[Abhishek Rathore]

Thanks Kevin.

We are in process of installation of V4.

Once we finish it we will start migration and may be some of you can please help us.

Regards

Abhi

To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/8552BDDD3DDE294C995A0182F32F976F016887D8A6%40HARVANDMBX02.fasmail.priv.