Installing and upgrading help

There are multiple posts on how to do this but it is a multiple step process.

You will have to copy your entire environment and create that exact environment on the new server.

Then you will need to upgrade to the last 1.9.x version, which I think is 1.9.14+

Then you will have to follow the steps to upgrade PHP, Apache, etc and upgrade Moodle to v2.

Once you are v2, then I think you may be able to go directly to 2.5+.

Please search prior posts for the exact details but this is the general overview.

http://docs.moodle.org/19/en/Moodle_migration

Gives step-by-step instructions for moving Moodle to a new server. Some of it won't apply if the URL is staying the same. I would recommend trying this with a test url first to make sure everything works for you before doing it on your live site. You can follow those same instructions to create a test site on the new server first.

The jump for 1.9 to 2.5 is very large. You will need to upgrade to the latest 1.9 release, then to the latest 2.2 release, then to 2.5. I would recommend using the command-line upgrade tool as that eliminates issues with timeouts. See: http://docs.moodle.org/25/en/Administration_via_command_line

^David,

You can't just copy over the data and database, so you will need to do an upgrade at some point. Unless you can set up a test/development area somewhere, your best course of action would be to clone your existing site to the new server (copy code, moodledata and database) then customise for the new domain name (see http://docs.moodle.org/23/en/Moodle_migration ). Make sure it works and then try the upgrade process. If successful, then great, but if it fails, you only have to re-copy the information and start again.

Be warned: the upgrade from 1.9 to 2.x is not always easy - I have found that it really depends upon how many customised modules you have and how early you started using moodle.

If you are happy just to move the resources (so not bothered about taking grades etc across) and you don't have too many courses, then the cleanest method of moving the site would be to install a fresh Moodle 2.5 system on the new server, then backup courses on the old server and restore them to the appropriate place on the new server. This method has the advantage of clearing out accumulated garbage and also means that legacy course files are not created, keeping the system 'fully 2.x compliant.

I hope this helps: I'm in the same position and am about to upgrade our fairly large site (500GB) from 1.9.19-2.5 so I know your dilemma!

graham

Just to add to what others have already said ... there are things to consider when making the successful jump from 1.9.highest to 2.2.highest.

Is the 2.2 site in Legacy mode?  Are all the courses using 'legacy" file system?  Answer to both: yes.

Can you 'live' with 'legacy'?  Maybe ... maybe not.  For it is my understanding that once a course is in Legacy, it's forever.  And that might/will affect that course backup ability to restore to a 2.6, or a 2.7, or a 2.8 (don't know that for sure but at this juncture, I'd say there is a pretty good bet that will be true). Never known anyone/thing to support legacy forever and ever!

2.2.highest is the ONLY version left that will allow restoring a 1.9.highest course AND by using a special method of restore, rid the course of the Legacy file system.

Not taking care of legacy at the 2.2.highest hop, means the next hop will remain legacy ... site + courses.

Just my 2 'sense' ... nope, spelled it correctly thank you! ;)

'spirit of sharing', Ken