About to Upgrade Moodle

About to Upgrade Moodle

Chase Brown གིས-
Number of replies: 4

Hello Everyone,

I am about to go through the process of upgrading 3 different Moodle databases from 1.9x to a 2.4x build and would like to be able to keep my user data and course data.

 

My question to you all is should I start by upgrading one revision at a time and see where things break and where I need to fix them until I get to 2.4, or should I start with a fresh install at 2.4 and see what I can bring back in from my 1.9x database?

I am going to first attempt all of this in a virtual environment so I can experiment with things and revert back when I am done.

All opinions and suggestions welcome.

Thanks,

Chase

དཔྱ་སྙོམས་ཀྱི་སྐུགས་ཚུ།: -
In reply to Chase Brown

Re: About to Upgrade Moodle

Mary Cooch གིས-
Documentation writers གི་པར Moodle HQ གི་པར Particularly helpful Moodlers གི་པར Testers གི་པར Translators གི་པར

If you start with a fresh install of 2.4 you won't be able to bring in your user data from your 1.9 Moodle so if that was essential to you then you'd have to upgrade from 1.9 upwards.

In reply to Chase Brown

Re: About to Upgrade Moodle

Ken Task གིས-
Particularly helpful Moodlers གི་པར

To add the confusion ... སྐྱོ་བ།

Migration of the site is the only way users/assignments/etc. come along upwards.  But, even during a Migration, the new file system will 'cubby hole' all documents/files in a thing called 'legacy'.

Once a course files are in legacy, it's in legacy for ever.

Suggest migrating via git to 2.2.highest and stopping at that point to get courses devoid of legacy (involves backing up each course, start a new course with minimal config, then restoring the backup to the new course (the one you are in).  This will move the 'legacy' files into the new file system.  Once, having done that, one can resume the 'moodle march' upwards.  The reason for the stop ... 2.3, 2.4, and 2.5 can no longer use the 'work around' to get files out of legacy.

New courses will use the new file system with no legacy.

Also, work with a copy of your current 1.9 site ... DB, code, and data directory.  There is massive change to the data directory.

After each step up, do a complete site backup ... DB, code, data directory.  That becomes your fall back position just in case the next step up fails for some reason.

Easiest way to 'march' ... git:

http://docs.moodle.org/25/en/Git_for_Administrators

'spirit of sharing', Ken

In reply to Chase Brown

Re: About to Upgrade Moodle

Peter Wise གིས-

Hi

my 2 cents

The VM is a _very_ good idea.

Starting with a fresh install just does not work. (or at least I could never get it to work)

Do the upgrade on the vm and then move it (backup restore it) to the live environment