Upgrade from 2.5.3 to 4.1 - different servers
Greetings - I've been reading up as much as I can regarding upgrades, and the majority of responses are noting that staged upgrading would be what I need to do, however I don't want to risk breaking my current install:
I currently have Redmine 2.5.3 on a 32-bit blade. Yes, it's old. It's been running a long time. I am going to be depreciating that entire blade.
I intend to move that entire installation to a new 64-bit Debian 9 platform with Redmine 4.1 current
We have many years worth of data in the DB, and some attached files, however we do typically use a different platform as our file repo, so no real worries there. We do however have a LOT of different expanded workflows / trackers etc, as well as a couple of additional plugins installed (Agile dwarf plugin: Mark Ablovacky 0.0.3 // Redmine Dragndrop Upload plugin hiromitz 0.0.1 // Redmine Planning plugin Egbert van der Wal 0.7.6 // Redmine Worktime Log Jared Denisov 0.0.3)
Since the OS and the bare metal has such a radical change, I would prefer to cleanly install Redmine 4.1 and then restore db from a backup - however is that even possible directly? Has the db schema changed sufficiently to fail a sql_dump import? I expect I'll have to modify some configs to re-point file paths (again, straightforward), but is there a migration path for the db itself?
I haven't tried to simply restore yet (that's this afternoon once the baseline is installed) - so it could just work, but I did want to get some more directed advice before simply "going for it". Anyone who has tried this craziness before has my thanks!
Well, at least, you may try.
What is your new machine? Win 10 + MySQL db? If so:
On the new machine: Install ruby + MSYS2. Install your db server install mysql2 gem by using something as
gem install mysql2 -- '--with-mysql-lib="C:\Program Files\MySQL\MySQL Server 5.7\lib" --with-mysql-include="C:\Program Files\MySQL\MySQL Server 5.7\include" --with-mysql-dir="C:\Program Files\MySQL\MySQL Server 5.7"'Do not use MySQL 8.
Install gem bundler.
Create database 'redmine', create user that will be using it ('redmine'@'localhost') with appropriate rights.
Download and unzip redmine zip somewhere. Copy your additions there - files, themes and not plugins. Your plugins are too old for sure.
Create and edit
config/database.yml (do not directly copy these files from the old redmine)
bundle install --without test development rmagick
Enter the command line mysql client.
use redmine. Import the sql dump of the database from the old machine. Note: You must not initialize initial data as in fresh install!
Execute database migrations of the core (the commands are given in the manual here in the site). If these migrations are successful, you will be happy man.
This will be working redmine with all your data in the database. However, without the plugins. You have to find fresh versions of these plugins, compatible with new redmine version & ruby & rails. This process takes some time. May you have first to find these new versions of the plugins and then do the whole job.