Skip to main content

How to Build a WordPress Backup Strategy With Offsite Storage

  • By Md Sayfur Rahman
  • 6 min read
How to Build a WordPress Backup Strategy With Offsite Storage

Most WordPress site owners believe they have backups. Many of them only find out that the backups do not work on the day they need them. A good backup strategy is not about making copies. It is about being able to bring your website back quickly, after any problem, with very little data lost.

This guide explains how to set up a WordPress backup strategy with offsite storage. It covers why hosting backups are not enough, what recent surveys show about backup failures, how often to back up, and how to test that your backups really work.

Why Your Host's Backups Are Not Enough

Many hosting companies include daily backups, and that is useful. The problem is where those backups are kept and who controls them. In most cases, the backups are stored by the same company, often on the same server or network as your website.

This becomes a real risk when the hosting company itself has a problem. In one Reddit thread, customers of a VPS provider shared how a server failure was followed by a message that all data was lost and could not be recovered. The only people who could rebuild quickly were the ones who kept their own backups with a different provider.

Hosting terms often say the same thing in writing. Many shared hosting companies describe their backups as a "courtesy" service that is not guaranteed, and they make the customer responsible for keeping their own copies. Some also limit how many backups they keep, or charge a fee to restore one. If your hosting account is suspended, hacked or closed, you may lose access to those backups at the same time as your website.

What the Data Says About Backups

Surveys of businesses show a clear gap between having backups and being able to use them. The numbers below come from two independent studies of IT teams and business owners. They are not about WordPress only, but the same problems appear on WordPress sites every day.

FindingResultSource
Organizations that lost data and recovered all of it42%Backblaze and The Harris Poll, survey of 300 IT decision makers
Organizations that needed to restore data at least once a month39%Backblaze and The Harris Poll
Restores caused by backup software failure54%Backblaze and The Harris Poll
Organizations that believed they could recover within hoursOver 60%Unitrends State of Backup and Recovery Report, 3,000+ IT professionals
Organizations that actually recovered within hours35%Unitrends State of Backup and Recovery Report
Organizations that test disaster recovery once a year or less25%Unitrends State of Backup and Recovery Report

Two things stand out. First, more than half of the companies that lost data could not get all of it back, even though most of them had some kind of backup. Second, people expect recovery to be much faster than it really is. For a website, the lesson is simple. A backup only counts if it is complete, stored somewhere safe, and tested.

The 3-2-1 Backup Rule for WordPress

The 3-2-1 rule is a simple way to plan backups, and it works well for websites. It means you keep three copies of your data, on two different types of storage, with one copy stored offsite. For a WordPress site, it can look like this.

  • Copy 1. Your live website on your hosting server.
  • Copy 2. Your host's own backups, which are useful for quick restores.
  • Copy 3. An automatic backup sent to a separate cloud storage account that you control, such as Amazon S3, Backblaze B2, Google Drive or Dropbox.

The third copy is the most important one. It should be in a different company's system, with a different login, so a problem with your host cannot affect it. Use a strong password and two-factor authentication on that storage account, because a hacker who gets into your website should not be able to delete your backups too.

How Often to Back Up and How Long to Keep Backups

The right schedule depends on how often your website changes. A good rule is to back up as often as you add content you would not want to lose. The table below shows a practical starting point for common types of WordPress sites.

Type of websiteDatabase backupFull backup (files and database)Keep backups for
Business or brochure siteDailyWeeklyAt least 30 days
Blog or news siteDailyWeekly30 to 90 days
WooCommerce or membership siteEvery few hours, or in real timeDailyAt least 90 days
Any site, before updates or big changesManual backupManual backupUntil the change is confirmed to work

The database holds your posts, pages, orders and settings, so it changes most often. Files such as images and plugins change less often, which is why a full backup can run less frequently. Keeping backups for 30 days or more is important because some problems, like a hidden malware infection, are only found weeks after they start.

Want your backups handled for you? Every WordPress maintenance plan we run includes daily offsite backups that we check and test, plus restores when you need them.

Choosing a Backup Plugin and Offsite Storage

Most WordPress sites use a backup plugin to create backups and send them to cloud storage. Popular options include UpdraftPlus, BlogVault, Jetpack VaultPress Backup, WPvivid and BackWPup. The best choice depends on the size of your site and how often it changes.

For small and medium sites, a plugin that sends daily backups to your own cloud storage is usually enough. For larger sites and online stores, look at tools that make incremental backups. An incremental backup only saves what has changed since the last one, so it puts less load on your server and can run more often.

Large sites also need extra care when restoring. On the UpdraftPlus support forums, many users report restores that stop halfway because shared hosting servers end long processes after a time limit. Tools that restore from their own servers, instead of from inside your WordPress dashboard, avoid this problem. They also work when your WordPress admin area is broken or hacked, which is often exactly when you need a restore.

Test Your Restore Before You Need It

A backup that has never been restored is a guess, not a plan. Testing takes less than an hour, and it shows you problems while there is still time to fix them. Do it at least once every few months, and always after you change your backup plugin or storage.

  • Download a recent backup from your offsite storage, not from your host.
  • Restore it to a staging site or a test hosting account, never over your live website.
  • Check that pages, images, forms and the WordPress admin area all work.
  • If you run an online store, check that recent orders and customers are there.
  • Write down how long the restore took, so you know what to expect in a real emergency.

If the restore fails or files are missing, fix your backup settings now. It is much easier to solve the problem on a quiet day than when your website is down.

Backups Are One Part of WordPress Maintenance

Backups protect you when something goes wrong, but regular maintenance stops many problems from happening in the first place. Tested updates, security monitoring and speed checks all reduce the number of times you will need to restore a backup.

Our WordPress maintenance checklist shows how backups fit into a full daily, weekly and monthly routine. If your site has already been hacked, a clean backup can save a lot of time, and our WordPress malware removal service can clean the site and make sure the same problem does not return. Before any big update, it is also a good idea to follow the steps in our guide on updating WordPress safely.

Written by

Md Sayfur Rahman

A website that doesn't break, doesn't slow down, and doesn't get hacked. Sounds like a fantasy. But it's exactly what I build. After more than 14 years in the WordPress ecosystem, I've learned that a truly great website isn't just about how it looks on launch day. It's about how it performs under pressure, how easy it is to manage, and how secure it remains as time goes on.