Blog · 24 October 2026

Website failover vs backup: what's the difference and which do you need?

People often use "backup" and "failover" as if they meant the same thing. They don't. Both protect your website, but they solve different problems, and choosing the wrong one can leave you with a site that is down for hours or a plan that costs far more than it needs to.

This guide explains each in plain terms, shows how recovery time and recovery point apply to both, and helps you decide what your site needs.

What is a website backup?

A backup is a saved copy of your website: files, database, settings and content, stored somewhere safe. It does nothing while your site is healthy. It sits quietly until something goes wrong, then you use it to rebuild.

Backups are what you reach for when:

• a bad update breaks your site
• you delete something by mistake
• malware or a hack corrupts your files
• your hosting is lost and you need to start again somewhere else

The key point is that a backup does not serve visitors. If your site goes down, visitors see an error until someone restores the copy. That restore takes time: finding the right version, setting up somewhere for it to run, loading it and checking it works.

What is website failover?

Failover means keeping a second, standby copy of your site ready to go. When the main site stops responding, traffic is automatically (or quickly) redirected to the standby, which serves visitors in its place.

Think of it as a spare engine already running, rather than a spare part in a cupboard. Visitors may barely notice a problem, because the switch happens in seconds or minutes rather than hours.

A standby copy is only useful if it is reasonably up to date, so failover setups usually involve ongoing syncing between the main site and the standby. That is also why they cost more and take more setting up than backups alone.

Two terms that make the difference clear

Two measurements are used to compare recovery plans. They sound technical, but the ideas are simple.

Recovery time objective (RTO)

How long can your site be down before it hurts? RTO is the target time between the site failing and it being back in service.

Recovery point objective (RPO)

How much recent data can you afford to lose? RPO is the gap between your last good copy and the moment of failure. If your last backup was at 2am and the site fails at 4pm, you could lose up to 14 hours of orders, comments, bookings or edits.

How backup and failover compare

The figures below are typical examples to show the pattern, not promises from any particular provider.

That fourth row matters. Failover is excellent for outages, such as a server crashing or a hosting problem, but it can faithfully copy a mistake or an infection to the standby. A backup lets you go back in time. Failover keeps you online. They answer different questions.

A worked example

Imagine a small business with an online booking form, backed up nightly.

• Server fails at 3pm. With backups only, the owner restores last night's copy. The recovery time might be a few hours, and every booking made since midnight is lost. That's a recovery point of about 15 hours.
• With failover as well, the standby takes over within minutes and is only a short sync behind. Almost no bookings are lost.

If that same site is a brochure with five pages that rarely change, the picture is different. A few hours offline and a day-old copy might cost nothing noticeable, and failover would be money spent on a problem you don't have.

Which do you need?

Start with a simple question: what does an hour of downtime cost you?

Work it out roughly:

1. Average sales or enquiries per hour through the site
2. Plus any cost to your reputation, such as customers who give up and go elsewhere
3. Plus staff time spent dealing with the fallout

Then use this as a guide.

Backup alone is usually enough if:

• your site is mainly informational
• content changes infrequently
• a few hours offline is an inconvenience rather than a crisis
• you want to be protected against mistakes, hacks and data loss at a sensible cost

Add failover if:

• the site takes orders, bookings or payments
• downtime directly loses you money or customers
• you have promised availability to clients
• your content or data changes constantly, so a day-old copy would hurt

Never rely on failover alone. A standby is not a substitute for a proper history of backups. If something corrupts your site, you need an older, clean version to return to.

Setting your own recovery targets

Before you buy anything, write down two numbers:

• Your RTO: "We need to be back online within [X minutes or hours]."
• Your RPO: "We can afford to lose no more than [X minutes or hours] of data."

Those two numbers tell you what to ask for. A target of "within a day, losing up to a day" points to regular backups. "Within minutes, losing almost nothing" points to failover on top.

Also check that you've actually tested recovery. A backup you've never restored, or a standby you've never switched to, is an assumption rather than a plan.

Where DRSite fits

DRSite is built around website backup and disaster recovery, so you can protect your online presence and have a route back when something goes wrong. For details on how recovery works with DRSite, including [confirm: whether a standby/failover option is offered, and typical restore times], see [link to DRSite features page] or compare options on [link to DRSite pricing page].

The short version

• A backup is a saved copy you restore from. It protects your data and lets you roll back, but recovery takes time.
• Failover is a live standby that keeps visitors served during an outage. It cuts downtime sharply but costs more.
• RTO is how long you can be offline. RPO is how much recent data you can lose.
• Most sites need good backups first. Add failover when downtime costs more than the standby does.

If you're unsure where your site sits, start by putting a figure on one hour of downtime. The answer usually makes the decision for you.