by Ken Task.
The 'devil' is in the details ... I have helped entities (at least 2) restore a site to a local server coming off a MP.
Detail 1: I'd be surprised if the MP has given you a code backup. Most MP's offer an extra bell and whistle that they offer but ONLY if you host with them. So your move to your server must now deai with a minor update to the version of Moodle as close to what you had when hosted with the MP. 2.9.4+ to the highest 2.9.x available.
One could get the exact version of Moodle code, but it would mean using git and that is a level of expertise beyond OP right now. This is gonna be a problem solving project for anyone - even to those who have a lot of experience with Moodle. It can be done ... it's just not a quick and easy 1,2,3 kinda thing.
So bottom line there ... you should get the moodle 2.9.highest code downloaded to your server from:
References:
https://docs.moodle.org/dev/Releases#Moodle_2.9
https://docs.moodle.org/29/en/Upgrading
Detail 2:
The sql dump you have has to be imported into a new DB for Moodle. That requires getting MySQL running first ... with a proper superuser login and password to begin. Then another DB user that has access to the Moodle DB you re-created for it.
Detail 3: is the eaiest ...
The un-archving of what probably is a tar.gz of moodledata to the proper location on the new server. If I re-call Ubuntu 14.04 server calls the web service apache2 and it's document root is /var/www/html/
The un-archiving of the data directory should go into /var/www/
And ithe data directory ownerships/permissions need to be changed to the apache2 web service user - which is www-data on that flavor of linux, I think.
Detail 3:
Almost done ... the creation of a config.php file from config-dist.php file.
cp config-dist.php config.php
nano config.php
then add the data to the values for the DB, the wwwroot, the datadirectory location.
You do NOT need to set all that's in config.php .... just the minimums right now.
Having done all that ... time to test ... go to another workstation and attempt to access the server first by it's static IP address then by it's fully qualfied domain name ... which is yet another devil detail depending upon home network IF that's where the server physically resides now ... or if co-located on a service providers network.
The FQDN is the fullly qualfied domain name of the server ... it was hosted before with an MP and all the data in the DB refer to that domain ... to which you no longer have access.
Two options ... but there is yin/yang cause it's hosted on a home network .. ie, at the house as opposed to another provider which is already on the internet ... a home network is not, traditionally accessible by anyone on internet.
For local access on home network to begin ... just test it ...
edit the /etc/host file on your local system.
Add a line:
Static_IP_address_of_server then next to that the FQDN as it existed on the MP site.
Example:
192.168.1.22 www.tons.online www
Got the domain name from your profile in Moodle.
Then, in a work station you will use to access the new internal private IP'd moodle server, do the same with the workstation's host file.
Your workstation will then not try DNS to find www.tons.online but the host file ... which is pointed to your internal private network only right now Moodle server by an FQDN.
Uhhhh ... think you can see this will require a lot of work ... and when you finish, there's the 'last mile' to go yet ... how to get the public internet to be able to see your server by that domain name ... assuming you own that domain name.
Ok, I've left out many, many, many details ... above are only the 'devils' in such a project just to get it up and running in your private network.
'spirit of sharing', Ken