HomeGlossaryFailover
Glossary

What Is Failover?

Failover is switching from a failed system to a redundant or standby one so work continues. Failback is the return to the original once it is repaired.

Definition

What is failover?

Failover is the switch from a failed system to a standby one so work continues, automatically or on an operator's decision. NIST defines it as the capability to switch automatically to a redundant or standby system when the active one fails. Failback is the return once the original is repaired.

Full guide: Disaster recovery vs high availability Service: Disaster Recovery

Failover moves a workload from a system that has failed to another that is ready to take over. NIST's glossary defines it as the capability to switch over automatically, typically without human intervention or warning, to a redundant or standby system upon the failure or abnormal termination of the previously active system. In practice the word also covers a planned or manual switch, where a person decides to declare the failure and start the standby.

Small businesses meet failover at several levels. A firewall with two internet circuits fails over to the second line when the first drops. A pair of firewalls or switches fails over when one device dies. A server protected by a backup appliance can be started as a virtual machine on that appliance or in the cloud. A replicated system keeps a current copy in a second location, ready to take the load. Each level trades cost against speed: the faster and more automatic the switch, the more equipment or subscription it takes to keep a standby current.

Failover is not backup, and one does not replace the other. Replication copies everything to the standby, including a deleted file, a corrupted database or ransomware encryption, so a business still needs point-in-time backups to go back to a clean state. Failover also has a second half that plans tend to skip. Failback moves the work back to the repaired primary, along with whatever data changed while the standby was in charge, and it needs its own procedure and test. A failover that has never been exercised tends to stumble on small things: a DNS record, a license tied to the old hardware, a firewall rule nobody wrote down.

Reviewed by Joel Baum, Founder. Our editorial standards.

Why it matters for a small business

Failover is how a recovery time of minutes is bought, and it costs more than restoring from backup, so it belongs on the systems where an hour of downtime really hurts. The useful exercise is to sort your systems into those that must fail over, those that can be restored within a day and those that can wait, then spend accordingly. Whatever you choose, ask to see it work. A standby that has never taken the load is a hope with a monthly fee.

Failover NetSys has measured

NetSys decides with each client which systems fail over and which restore from backup, in what order, and who approves each step. For the systems that need it, disaster recovery as a service keeps current replicas in the cloud, with a written runbook covering every dependency and scheduled failover exercises that record the measured recovery time.

One published example: in our work for a large international food importer, the failover of the ERP and SQL core was tested at 15 minutes. A time measured in one test is evidence for that system, not a promise for every outage. Our disaster recovery service prices replica storage and test frequency per business.

Sources

Checked on November 22, 2026.

Common Questions

Failover: FAQs

What is the difference between failover and failback?

Failover moves work from a failed primary system to a standby. Failback moves it home again after the primary is repaired, carrying across any data that changed in the meantime. Both need a written procedure and a test, and failback is the one most easily left out.

What is the difference between failover and backup?

Failover keeps a service running by switching to a standby system. Backup keeps point-in-time copies of data so you can go back to an earlier state. Replication behind a failover copies mistakes and ransomware along with good data, so a business that needs failover still needs backups.

Is failover automatic?

It can be either. Automatic failover detects the failure and switches with no one involved, which suits network links and clustered systems. Manual failover waits for a person to declare the outage and start the standby, which is slower but avoids switching on a false alarm. The recovery plan should say which applies to each system.

Does a small business need failover?

For some systems, yes. A second internet circuit with automatic failover is worth considering for any office that cannot work offline. Failover for servers and applications is justified where the cost of an hour of downtime is high. Other systems are usually better served by a tested restore from backup.

Disaster Recovery

Discuss disaster recovery for your business.

Tell us about your current systems, the result you need and your timeline. We will discuss the work, responsibilities and pricing before you decide on an engagement.