{"id":1814,"date":"2020-03-02T12:31:07","date_gmt":"2020-03-02T17:31:07","guid":{"rendered":"http:\/\/newmediaproduction.mynmi.net\/?page_id=1814"},"modified":"2026-10-27T15:28:28","modified_gmt":"2026-10-27T15:28:28","slug":"backing-up-wordpress","status":"publish","type":"page","link":"https:\/\/nmi.cool\/webdev\/backing-up-wordpress\/","title":{"rendered":"Backing up WordPress"},"content":{"rendered":"\n
\"\"
Photo by Markus Spiske<\/a><\/figcaption><\/figure>\n\n\n\n

Because a) we’ll be doing all of our WordPress work on our server, not locally in this class and b) WordPress isn’t just a set of files, but a set of files plus<\/em> a database, it’s important to back up WordPress.<\/p>\n\n\n\n

Unlike the static websites we’ve built so far, WordPress stores much of your content and configuration in a database. That means simply downloading your WordPress files through SFTP won’t give you everything you need to restore your site. A complete backup needs to include both your files and your database.
<\/p>\n\n\n\n

Server-side back-ups<\/h2>\n\n\n\n

Because Reclaim Hosting is a nice company to work with, our WordPress starter steps<\/a> should automatically configure server-side back-ups. However, it’s always a good idea to verify that your backups are working as intended.<\/p>\n\n\n\n

To create a backup, log in to Reclaim Hosting, open cPanel, and click on WordPress. Locate your WordPress installation and click the Backup button. Follow the prompts to create a backup of your site.<\/p>\n\n\n\n

To check your automatic backup schedule, open the installation’s Edit\/Settings controls and look for the automatic backup settings. Ideally, backups should be scheduled at reasonable intervals, such as one weekly and one monthly.<\/p>\n\n\n\n

You can also visit My Backups in Installatron to see your available backups.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Scroll down and click “Backups” to verify that back-ups are enabled on a reasonable schedule, such as 1 weekly + 1 monthly:<\/p>\n\n\n\n

\"Installatron<\/figure>\n\n\n\n

A Note About Backup Limits<\/strong><\/p>\n\n\n\n

Reclaim Hosting may limit the number of Installatron backups you can store. For example, your account might allow only two backups per WordPress installation.<\/p>\n\n\n\n

If you reach that limit, Installatron may automatically remove an older backup to make room for a new one. This process is called pruning<\/em>.<\/p>\n\n\n\n

That’s another reason it’s important to download and store your own backups outside your hosting account. Server-side backups are convenient, but they aren’t intended to be your only long-term copies.<\/p>\n\n\n\n

Local back-ups<\/h2>\n\n\n\n

Completing the above steps to verify that your remote, server-side backups are working is a great first step. But, it’s not sufficient. If something goes wrong with your server, you’ll have no way to restore your WordPress site. <\/p>\n\n\n\n

(The thing that most frequently goes wrong with student servers, by the way? Forgetting to renew your hosting after your initial year passes. Reclaim Hosting is a great company, but they’re not a charity, and all the data on your server will<\/em> be deleted if you don’t pay annually for hosting.)<\/p>\n\n\n\n

Thankfully, simple tools exist for creating remote back-ups of a WordPress site. A great one is All-in-One WP Migration and Backup<\/a>. Though billed as a migration tool (for moving a WordPress install from one place to another), it’s also a great back-up tool.<\/p>\n\n\n\n

Install and activate it as you would any other plugin. Then, once it’s active, click on it in the menu bar and select Export To > File:<\/p>\n\n\n\n

\"All-in-One<\/figure>\n\n\n\n

Wait a bit, then click the obnoxiously bouncing Download button when the file’s ready and store the .wpress file somewhere safe.1<\/a><\/p>\n\n\n\n

You’ll want to repeat this process periodically, especially after you’ve made major changes or addition to your site.<\/p>\n\n\n\n

Troubleshooting: What If Your Backup Won’t Download?<\/h3>\n\n\n\n

Occasionally, All-in-One WP Migration will successfully create your backup, but clicking the Download button won’t actually download the file. If this happens, don’t panic! Your backup may already exist on your server.<\/p>\n\n\n\n

First, try a couple of simple fixes:<\/p>\n\n\n\n

    \n
  1. Open your WordPress dashboard in a private or incognito browser window and try downloading the backup again.<\/li>\n\n\n\n
  2. Try a different browser. For example, if Chrome isn’t working, try Safari or Firefox.<\/li>\n\n\n\n
  3. Check your browser’s download settings or temporarily disable extensions that might interfere with downloads.<\/li>\n<\/ol>\n\n\n\n

    If those steps don’t work, you can try downloading the backup directly through cPanel:<\/p>\n\n\n\n

      \n
    1. Log in to Reclaim Hosting and open cPanel \u2192 File Manager.<\/li>\n\n\n\n
    2. Navigate to the folder containing your WordPress installation.<\/li>\n\n\n\n
    3. Open wp-content\/ai1wm-backups\/<\/code>.<\/li>\n\n\n\n
    4. Locate the .wpress<\/code> file created by your export.<\/li>\n\n\n\n
    5. Select the file and use File Manager’s Download option to save it to your computer.<\/li>\n<\/ol>\n\n\n\n

      Remember, a backup stored on your server is not the same as a backup stored on your computer. Make sure you’ve actually downloaded your file!<\/p>\n\n\n\n

      Restoring<\/h3>\n\n\n\n

      Should you find yourself in the position of needing to restore from a All-in-One WP Migration backup, get your new WordPress install up and running<\/a>, install the plugin as above, and this time choose Import, and upload the .wpress file you exported earlier.<\/p>\n\n\n\n

      Be careful! Importing a backup can overwrite the destination WordPress installation’s existing content, settings, and database. Make sure you’re importing into the correct location on your server.<\/p>\n\n\n\n

      You may also encounter a file-size limit when importing a .wpress<\/code> backup. These limits depend on your hosting configuration and the migration plugin’s capabilities. If your file is too large, you may need to adjust your server’s upload settings or use an alternative import method. Don’t assume that installing another plugin will automatically resolve the problem.<\/p>\n\n\n\n

      We’ll explore how this same export-and-import process can be used to move a WordPress website in Moving WordPress lesson.<\/p>\n\n\n\n

      <\/p>\n

      1. You are backing up your local machine, too, right? ?↩<\/a><\/p><\/li><\/ol><\/div>","protected":false},"excerpt":{"rendered":"

        Because a) we’ll be doing all of our WordPress work on our server, not locally in this class and b) WordPress isn’t just a set of files, but a set of files plus a database, it’s important to back up WordPress. Unlike the static websites we’ve built so far, WordPress stores much of your content […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-1814","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/nmi.cool\/webdev\/wp-json\/wp\/v2\/pages\/1814","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nmi.cool\/webdev\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/nmi.cool\/webdev\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/nmi.cool\/webdev\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nmi.cool\/webdev\/wp-json\/wp\/v2\/comments?post=1814"}],"version-history":[{"count":16,"href":"https:\/\/nmi.cool\/webdev\/wp-json\/wp\/v2\/pages\/1814\/revisions"}],"predecessor-version":[{"id":6786,"href":"https:\/\/nmi.cool\/webdev\/wp-json\/wp\/v2\/pages\/1814\/revisions\/6786"}],"wp:attachment":[{"href":"https:\/\/nmi.cool\/webdev\/wp-json\/wp\/v2\/media?parent=1814"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}