Migration

Now I talked about updating and backups.

Now on to what you can do with your backups: *drumroll*

Migration

While building your page, fixing bugs or testing updates – it’s logical to actually work on a local host and not on your real life website…

But then comes the day of migration (finally)

The way I like to do migration:

  1. update the Drupal core (or find the version of your site)
  2. install the Drupal core normally on the other server
  3. migrate the sites folder (and activate one or two modules for the next step)
  4. migrate the database (using Backup and Migrate)

I like to install the Drupal core normally as it is easier than changing the settings manually in the settings file (but you could do that as well if you are sure of what you are doing)

To make a transition from online to offline and back as smooth as possible I always do one of the following to be sure the will be database working correctly:

  • update both sites at the same time – if by chance you know there will be no problems… which you don’t – or I have a test site running on a server (group projects…)
  • test the update on the test site and afterwards update the productive site 

Always be careful to migrate the database when you have the same versions running otherwise you could get errors (especially if the database was change with the update)

And of cause backup both you test site and your productive site before you do the migration!

And done 🙂

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s