Upgrading Solidus 2.1 >>3.0

[eriuser]

Does anybody know of a utility for Solidus to export the data from a 2.1 server and import it into a 3.0 server in the same way that XFERDATA did for CCM.

All the documentation I have read about upgrading Solidus assumes that the existing server is to be upgraded, however many customers wish to install a new server so that they can go back to the old server in case of problems with the upgrade.

If there is no utility then a few ideas for how best to do it would be appreciated.

Thanks

 

[fidde]

Well the obvious is to uppgrade the server you have installation on and then move the the new one.

Fidde

 

[eriuser]

By doing that you loose the option to go back to the original configuration if something should go wrong.

 

[Jeppedal]

Hi,

We did this some time ago, but I cant remember exactly how ...

I believe we did the following:

Set up a mirror of the existing system by copying OAS rep files and Nodelock to the new server. Export containers and move to the new server. Install OAS on the new server and point to the existing repfiles and license file. Import the containers.

Install the old version of Solidus and the licenses on the new server. Backup the old Solidus database and restore the data on the SQL server for the new system. Copy the scriptmanager files from the old system to the new. Recompile the scripts.

At this point, You should have two identical systems up and running (if You have two boards available). It should be possible to upgrade one of them by using the OAS 2.5 and Solidus 3.0 media. Remember that there is some differences in the 2.1 and 3.0 scripts, so you probably have to make some modifications.

Good luck!

Best regards
Jeppedal

 

[eriuser]

Thanks for that. That is how I thought it would have to be done.
The upgrade we are about to perform will have the scripts completely rewritten from new so we would have liked a way to export the historical data but it seems that there is no way to do this.