Dental checkups. Cleaning the gutters. Computer backups.
Some things are all too easy to put off even though we know we should do them.
I can’t help you with your teeth, and I won’t help with your gutters, but I have advice about backups. Specifically, WordPress backups.
Every day more organizations trust WordPress as their website platform. I do too, and I often recommend it to clients. That’s great. The problem is that some organizations take trust a little too far by assuming nothing will ever go badly wrong.
WordPress makes it especially easy to lapse into backup avoidance since it doesn’t provide a straightforward built-in backup capability. In fact, unless you study the issue a bit you can think you’re backing up your site (for example, by using the Export function from the administrative menu) when you’re really only capturing part of it.
This article should clarify the situation and help you understand your options.
Some people believe you don’t really need to back up WordPress. This is not a good belief for our non-ideal world.
Though I don’t agree with the argument, it’s worth explaining since it highlights a couple of layers of protection that you already have in place.
If you’re working with a reputable web host, the web host maintains a backup of your site and can restore it in case of emergency. This is convenient in case of a catastrophic failure at your web host: for example, if the web server itself crashes. In that case your web host should restore your site from backups for you.
WordPress also buffers you from the the need for backups by providing two supporting features.
When you edit a post or page, WordPress keeps a history of that revision. You can view earlier versions or restore them directly from WordPress. Just edit the page in question and scroll down below the editor to see earlier revisions.
If a page or post has been accidentally (or intentionally) deleted, check the trash. There’s a good chance you’ll find it there waiting to be restored. You can find the trash by going to your list of posts or pages in the WordPress administrator menu.
That’s absolutely right if you live in an ideal world.
For the rest of us, here are a few reasons to make your own backup:
Your WordPress site has two components:
Your WordPress database (which is mainly text-based information) will be vastly smaller than the files on your web server (which include things like your photos and documents). For this reason a typical backup approach includes frequent backups of the WordPress database, and less frequent backups of the files.
Up until recently I did it the hard way. The hard way isn’t awful, but it’s cumbersome since it involves backing up the two components in different ways.
Your database is the heart of your site. It has all of the text from your pages and posts, your menu definitions, categories, comments, and settings.
As described in the WordPress Codex, there are many methods of backing up your database. One tool I’ve used for this is the WP-DB-Backup plugin. Once you install and activate the plugin, your Tools menu will have a new Backup option. To back up your WordPress database, go to the Backup option, and in the Backup Options section select Download to your computer and click Backup now! This will generate a file that you can save on your computer.
Regardless of how you back up the database, it’s best to retain more than the most recent backup in case of a long-standing problem that you want to correct. For example, if you back up your site weekly you might keep the most recent 4 weeks available, then also retain another copy every 3–6 months for long term archival.
Unfortunately the best method for backing up your files varies from web host to web host.
The be completely safe you should back up your entire WordPress directory. However, especially in the third scenario above, that can be very slow. If you can’t stand the wait you can just back up the folders that are most likely to have WordPress files specific to your installation, understanding that it’s conceivable you’ll be omitting something you’ll want later:
If you thought backing up the hard way was a pain, wait until it’s time to restore. Even if you have all the backup files, restoration isn’t practical for typical WordPress end users. You really need help from a WordPress expert.
Until recently I did it the hard way. Then several weeks ago as part of bringing a client’s WordPress site live, I decided to try a plugin I’ve heard good things about: BackupBuddy.
In short, BackupBuddy is the easy way.
My disclosure is that I have nothing to disclose. I paid the same price as anybody else for BackupBuddy and I’m getting no benefit from them for writing this. I wouldn’t do that. It would be icky.
You create your backups from an intuitive menu within WordPress. You can back up just the database or your entire site including all your WordPress files and WordPress itself. About to upgrade WordPress or add a theme or plugin? If something goes wrong you can restore not only your content but WordPress itself to its earlier state.
As with the hard way, it makes sense to back up your database more frequently than your entire site. Ask yourself how much content you can stand to lose and recreate, then pick your backup period based on that.
It lets you do backups on demand or schedule them to happen automatically, and either way it’ll email to tell you how the backup went.
Once you’ve made a backup you can leave it on your web host or, for more protection, download it to your computer. You can also have the backups automatically sent to other servers if you’d like; it currently supports transfers to Amazon S3, Dropbox, and Rackspace, as well as transfers via email and FTP.
As much as I’d love a one-button restoration process, BackupBuddy doesn’t provide that. However, its restoration process is much, much simpler than the hard way.
If you’re a little technically inclined you can follow their instructions and probably do it yourself. And if you prefer to hire a WordPress expert, it’ll almost certainly take them much less time than most other restoration methods.
I’ve used BackupBuddy several times in the last few weeks and it’s worked very well, saving me a lot of time and fuss.
The least expensive license right now is for two sites, currently $75: probably not of interest for hobbyists, but (in my opinion) a good investment for a nonprofit or small business. I went for the developer license that lets me use it on any website I develop for $150, but was lucky enough to find a 25% discount code online.
So for me at least, it’s has been well worth the money. And that’s not even taking into account its website malware scanning, excellent Server Information utility, or wonderful support for (be still my heart!) migrating your WordPress site from one web server or address to another.
When something goes wrong you want things to be as uncomplicated as possible. Knowing you have your own backup and a clear path to restoring it avoids all kinds of stress and tragedy.