Blog · 24 October 2026

WordPress backup plugin: what to look for beyond "it makes a zip file"

Nearly every WordPress backup plugin can produce a zip file. That is the easy part. The hard part comes on the day your site goes down, when you need to know whether that zip file will get you back online quickly, completely and without a long, stressful afternoon.

This guide sets out four criteria worth checking before you choose a plugin, then explains how the DRSite plugin fits and how to set it up.

Why "it makes a zip file" isn't enough

A backup is only useful if it survives the problem you're backing up against. Sites go down for ordinary reasons: a failed update, a hacked login, a hosting fault, an accidental deletion. In several of those cases, a zip file sitting on the same server as your site is lost along with everything else.

So the question to ask of any plugin isn't "does it back up?" but "what happens when I need it?"

Criterion 1: Is the backup stored off the server?

If your backups live in the same hosting account as your website, one incident can take out both. A server failure, a suspended account or a compromised login can remove your site and your safety net together.

Look for:

• Storage separate from your host. The backup should be kept somewhere your web server can't overwrite or delete.
• Clarity about where it goes. You should be able to find out where copies are held and for how long.
• No reliance on manual downloads. Backups you have to remember to download are backups that eventually don't happen.

Questions to ask: If my hosting account disappeared tomorrow, where would my backup be? Could I get to it without logging in to my host?

Criterion 2: How fast can you restore?

People tend to judge backup tools by how they back up. The restore matters more, because that's when your site is offline and customers can't reach you.

Consider:

• How many steps a restore takes. Is it one guided process, or do you have to unpack files, upload them and edit settings by hand?
• Whether you can restore without a working WordPress admin. If the site is broken, you may not be able to log in to use the plugin.
• Whether partial restores are possible. Sometimes you only need to roll back a single file or one table, not the whole site.
• Whether you've ever tested it. A restore you've never rehearsed is a guess.

For a small business, the practical measure is simple: how long could you afford to be offline, and does the tool's restore process fit inside that?

Criterion 3: Is there a standby copy?

A backup is a stored copy of your site. A standby copy goes a step further: a ready version of the site you can switch to when the live one fails, rather than rebuilding from scratch.

This is the difference between backup and disaster recovery. A backup says "your data exists". Disaster recovery says "your site can be back up and running again, and here's how".

When comparing tools, ask:

• Does the service offer a standby or recovery option, or only file storage?
• If the live site is unavailable, is there a way to keep a version of it reachable while you fix the problem?
• Does it work even if your host is the thing that has failed?

If you take online bookings, sell products or rely on enquiries from your site, a standby copy can be the difference between a short interruption and a lost day of trade.

Criterion 4: Does it include the database?

This one catches people out. WordPress files (themes, plugins, uploads) are only half of your site. The database holds your posts, pages, settings, user accounts, orders and form entries. Restore the files without the database and you have an empty shell.

Check that the plugin:

• Backs up the database as well as the files, every time, not as an optional extra.
• Keeps the two in step, so a restore doesn't pair last week's files with last month's content.
• Covers custom tables created by plugins such as shops, bookings or membership tools.
• Backs up often enough to match how often your content changes. A shop taking orders daily needs a different schedule from a brochure site updated twice a year.

A quick checklist

Before you commit to any WordPress backup plugin, you should be able to answer yes to these:

1. Are backups stored away from my web server?
2. Can I restore without a working WordPress dashboard?
3. Is there a standby or recovery option, not just a download?
4. Are the files and the database included every time?
5. Are backups automatic, with a schedule that suits my site?
6. Have I actually tried a restore?

Where DRSite fits

DRSite is built around website backup and disaster recovery, so the criteria above are the ones it's designed to address, rather than backup being a side feature. The WordPress plugin connects your site to your DRSite account, so protection is managed from one place instead of being tied to your hosting.

For the specifics of what is included on each plan, such as [backup frequency], [retention period] and [storage location], see the DRSite pricing page [replace with the exact pricing URL].

Setting up the DRSite plugin with your API key

The plugin links to your account using an API key, so there's no need to share your password with the plugin. The setup looks like this:

1. Create or log in to your DRSite account at drsite.app.
2. Generate an API key in your account area: [exact menu path in the DRSite dashboard].
3. Install the plugin on your WordPress site: [plugin name and install method, such as the WordPress plugin directory or a zip upload].
4. Open the plugin's settings in your WordPress admin: [settings page name].
5. Paste in your API key and save. The plugin will confirm the connection: [confirmation message or status].
6. Choose what to protect and how often, and check the database is included: [option names].
7. Run a first backup and confirm it appears in your DRSite account.

Treat your API key like a password. Don't paste it into emails or shared documents, and if you think it has been exposed, generate a new one and update the plugin: [key regeneration steps].

Test it before you need it

Whichever tool you choose, set a reminder to test a restore, ideally on a staging copy or a spare domain, once a quarter. Ten minutes of rehearsal will tell you more about your backup than any feature list.

If you'd like to see how DRSite handles backup and recovery for your WordPress site, start at drsite.app.