summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJosé Mota <josemota.net@gmail.com>2012-04-29 00:34:21 +0100
committerJosé Mota <josemota.net@gmail.com>2012-04-29 00:34:21 +0100
commited0567e6f6f749da16f7653b77175370f5fb32e1 (patch)
tree34008f341c0995eeaae2f4cce2f9db2f3a56e50f
parent755a63cce0b3fce361818af55a66878ff819c004 (diff)
Update 2009 Drupal post.
-rw-r--r--_posts/2009-04-17-how-to-backup-your-drupal-site-using-backup-migrate.html25
-rw-r--r--_posts/2009-04-17-how-to-backup-your-drupal-site-using-backup-migrate.markdown32
2 files changed, 32 insertions, 25 deletions
diff --git a/_posts/2009-04-17-how-to-backup-your-drupal-site-using-backup-migrate.html b/_posts/2009-04-17-how-to-backup-your-drupal-site-using-backup-migrate.html
deleted file mode 100644
index db9f008..0000000
--- a/_posts/2009-04-17-how-to-backup-your-drupal-site-using-backup-migrate.html
+++ /dev/null
@@ -1,25 +0,0 @@
----
-layout: post
-title: How to backup your Drupal site using Backup & Migrate
-tags:
-- Development
-status: publish
-type: post
-published: true
-meta:
- _edit_last: '1'
----
-Back from the dead; I mean, my <a title="CoreSP (honestly, they should know better)" href="http://coresp.com">hosting</a> 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: <a href="http://drupal.org/project/backup_migrate">Backup &amp; Migrate</a>!
-
-<!--more-->
-
-Backup &amp; 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:
-<ul>
- <li>Restore that backup in any Drupal installation.</li>
- <li>Schedule backup generation.</li>
- <li>Generate backups under gzip, bzip or zip format.</li>
- <li>Select only the tables you want to backup and even the table structure (no content).</li>
-</ul>
-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 <em>wham!</em>, 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!
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 &amp;
+Migrate](http://drupal.org/project/backup_migrate")!
+
+Backup &amp; 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!