Update 2009 Drupal post.

1 files changed, 32 insertions, 0 deletions

diff --git a/_posts/2009-04-17-how-to-backup-your-drupal-site-using-backup-migrate.markdown b/_posts/2009-04-17-how-to-backup-your-drupal-site-using-backup-migrate.markdown
new file mode 100644
index 0000000..648916b
--- /dev/null
+++ b/_posts/2009-04-17-how-to-backup-your-drupal-site-using-backup-migrate.markdown
@@ -0,0 +1,32 @@
+---
+layout: post
+title: How to backup your Drupal site using Backup & Migrate
+tags: [ development ]
+published: true
+---
+
+Back from the dead; I mean, my hosting has been dead for more than a week.
+That's why I finally decided to back my Drupal website up just in case I get
+screwed again. The magic tool: [Backup &
+Migrate](http://drupal.org/project/backup_migrate")!
+
+Backup & Migrate is a Drupal module that, once installed, allows you to
+easily backup your entire database into one single file. It also has the
+ability to:
+
+* Restore that backup in any Drupal installation.
+* Schedule backup generation.
+* Generate backups under gzip, bzip or zip format.
+* Select only the tables you want to backup and even the table structure (no content).
+
+The only thing I found missing is file backup, such as images, themes and other
+modules. I honestly hope it knows what modules were installed so the only thing
+I need to do is paste the entire <code>sites</code> folder, install this
+module, import the database and _wham!_, the site is up and running. Oh and by
+the way, Drupal core version is something to consider, since it depends heavily
+on the database configurations. Just make sure the version you currently use is
+the same to the one you're importing the database to.
+
+If you know Drupal, you know portability is a serious issue of his. Well, at
+least you know how to back it up and even set boundaries between your
+development and production environments!