How to Backup WordPress the Right Way

I wouldn’t trust a plugin to do a WordPress backup, but if you must, try UpDraft and cross your fingers. First of all, how will you ever know that the plugin is secure? How will you know if the plugin is working correctly? Finally, you’ll need the plugin to restore the backup–what if the plugin isn’t updated for the current version of WordPress?

To Backup WordPress the Right Way, Do a Direct Database Backup

A WordPress installation is composed of two separate but integrated components–and a full backup requires you to backup both components. First (and easiest) is the php and script files that run the installation and the template. These are files that exist on your web server/hosting account. You back up these files with an FTP program like FileZilla. An FTP backup is the easy part of backing up a WordPress installation–but won’t represent a complete backup.

Simple Steps to Backup WordPress’ FTP Files

First look at the following photo, it’s what a WordPress installation looks like in an FTP program (you want to backup the folders and files you see here):

wordpress-backup

 

So here are the steps to backup:

  1. You need an FTP program installed on your local PC, we recommend open source FileZilla.
  2. Use your web hosting password and log into FTP using FileZilla.
  3. Download the files described above to your local machine.

Part 2: The Database Backup

The second component of a WordPress installation is the WordPress database, and backing up this part is a bit more difficult. The database stores user information, all the text of your pages and posts, and your plugin settings. Your WordPress database runs within software that runs on your webserver–it isn’t a file or set of files that is easy to just copy to your local PC.  In 99% of cases, you can get to your database by logging into the admin area for your web hosting account. For a Hostgator or Bluehost account you simply point your browser to yoursite.com/cpanel (cpanel is common web hosting management software). For GoDaddy and some other hosts that use their own administration software, you’ll need to hunt a bit to get to your database.

Step 1: Log in to Cpanel

If I go to tastyplacement.com/cpanel, I get to this screen. From there I use my account password; pretty darn easy.

cpanel-login

Step 2: Find phpMyAdmin and Get In!

If you have cPanel, your phpmyadmin is in there somewhere…find it and click to enter the program.

find-phpmyadmin

Then you’ll see the phpMyAdmin software interface, and your databases will be listed in the left column. You want to keep your server name and database names private, so I’ve grayed out mine here. Click on the name of your WordPress database to enter the database.

phpmyadmin

 

And here it is, your WordPress database. Here’s an important distinction: your WordPress installation has ONE database and within that database is 15 or more tables. In the example below, the tables (like “wp-commentmeta”) are listing in the main column:

wp-database

 

Step 3: Export the Database to Your Local PC and Save as a Backup (and Promise You’ll Go Slowly and Carefully)

You need to make sure you backup ALL the tables, because phpMyAdmin will certainly let you backup some, one, or all of the tables within a database. It’s easy: from the view above, scroll to the bottom of the table and “Check All”, and then select “Export” from the drop-down like so:

wp-export

Here’s a safety note, as you might imagine, the selections on that drop-down menu “drop” and “empty” would be very bad, as in your site would be totally destroyed. And so here is the last screen:

final-export

I would use these options without customizing anything. You might be tempted to change the “Format”, but don’t. SQL backup format is going to be the most universal and will cause the fewest problems when restoring your backup.  Just click “Go” and download the file to a safe place.

Questions? Post ’em up in the comments! Your WordPress backup will be your savior if your WordPress site gets hacked.

 

1 reply
  1. Rob says:

    Hi!

    Thanks for the good info above. It confirms that I did the right thing when I backed up a site which is now gone completely but could be restored.

    Although I have backed up the site, have you any tips or potential pitfalls on restoration? I’m also thinking in terms of a transition from one host to another.

    Reply

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *