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

Database backup

I already talked about backing up your Drupal installation in my posts about updating Drupal.

Backing up the code is pretty easy – just copy your whole Drupal installation – and done.

But how do you backup the database nice and easy?

The easiest way I found was the Module Backup and Migrate.

You can easily back up the database just with a click or setup automatic backups for your systems (either saved on a server or send by mail).

You can also setup the backup to be compressed (which is handy, when you need to restore and the Server will not let you do it with a big file)

And the module also restores the database.

You can also update the Database directly with these files (outside of Drupal – useful if your provider let’s you not update the whole database via Restore – I had the problem once :/ )

Of cause there are more cool options waiting in the module (I just never used them 😉 ) and if you search for Backup on drupal.org you find some more Backup and Restore projects not part of the main project (I’ve seen some backup to Dropbox once)