In this article we take a look at server migration. The term server migration might sound fanciful and technical, like you need an IT degree just to look at a server. But with the help of this article and a few of the other resources, you will see that given the right knowledge, even you could migrate your own MEX data.
You first have to understand why you are migrating your server. Typical cases are:
If your reason is for testing, you probably don’t even need to migrate servers at all. Here is a tech tip to help you set up a test instance: Creating a New Instance of MEX Tech Tip
There are two parts to a complete MEX server migration:
Depending on your situation you may only need to migrate one or the other but let’s start with Database Migration.
Before even beginning a database migration you have to check if the server you are migrating to has the same version of SQL or has a higher version installed. You won’t be able to continue if the new server has a lower version.
To do this, simply open the SQL Server Management Studio and got to Help -> About. This will tell you exactly what version of SQL you are running.
SQL Server Version Example.
Once you’ve checked this, migrating a database only consists of three steps.
Once you’ve finished these steps, your database migration is done.
It is highly recommended to set up an automatic backups which we’ve explained in a tech tip found here: Schedule Automatic SQL Database Backup
To ensure that the new server is capable of running your MEX data. A few things will need to be set up correctly.
The database connection details are usually found in the following format:
Now run through the Data Server installer on the new server and follow the prompts. Eventually it will ask you to put in the connection details to your newly migrated database, as explained above.
At the end of the installation process it will give you a link to run MEX in your browser which you should pass onto your MEX Users.
Your Link to access MEX will be provided at the end of the install
With MEX successfully installed on your new server, it’s a good idea to copy the MEX Documents folder from the old server into the new one.
Now you’re done, but with a few final considerations: MEX on the old server must be turned off.
This is so users don’t waste time using an out of date instance.
It’s always a good idea to put in place a redirection HTML file to cater for any user who still ends up on the old server through an old MEX link.
Here is an example:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>MEX Redirection Notice</title>
<meta http-equiv="refresh" content="0; URL=&rsquohttp://NewServerIPAddress/MEXData&rsquo" />
<h1>MEX Redirection Notice</h1>
<p><strong>MEX is no longer hosted at this address.</strong></p>
<p>You will be redirected shortly to the new server. </p>
<p><a href="http://NewServerIPAddress/MEXData" title="New MEX Server">Click Here</a> if you are not redirected in 10 seconds.</p>
Just copy and paste this code into notepad and do the following
Of course, it’s a good idea to send an email out letting everyone know the new address of MEX. As I said before, the address can be found in the last screen of the data server installer (as pictured above).
Configuring and migrating servers isn’t for everyone and that’s not something to feel bad about. In fact, it’s exactly why we provide an online hosting service.
Let us manage all the IT for you! MEX Data Hosting provides you with
We’ll do it for you. For more information go to the MEX Data Hosting Information Page
If you have any questions or issues with notifications please contact MEX Support at firstname.lastname@example.org or call +61 7 3392 4777.