Cloud backup vs local backup
Also known as: onsite vs offsite backup, cloud vs local backup, hybrid backup
Local backups store copies on-site (an external drive or backup appliance) for fast restores, while cloud backups keep copies at a remote data centre for protection against fire, theft, and ransomware.
They solve different problems, so the strongest approach usually combines them: local for speed, cloud for resilience.
Cloud backup vs local backup, explained at three levels
At home
Keeping a spare house key in your kitchen drawer is fast, but useless if the house burns down. A key left with a relative across town survives the fire, but takes a drive to fetch. Local and cloud backups work the same way. A local backup sits on a drive in your home or office. A cloud backup is copied over the internet to a distant data centre.
At work
Local backup stores copies on hardware at your site, such as an external drive, NAS, or backup appliance. Cloud backup sends copies over the internet to a provider's data centre. Each covers a different risk: local restores are fast but share the building's fate, while cloud copies survive fire, theft, and on-site ransomware but restore more slowly. Most businesses need both.
At home
Speed is the key difference. A local USB or network drive can restore at hundreds of megabytes per second. Over a typical home connection of a few hundred megabits per second, pulling one terabyte from the cloud takes many hours, sometimes days. Cloud backup, though, runs automatically in the background, keeps copies away from home disasters, and usually stores many past versions. A common home setup pairs Time Machine or File History locally with a cloud service.
At work
In a business, local backup is usually a backup appliance or NAS that takes image-based snapshots of servers every hour or so. Those snapshots are then replicated to the vendor's cloud or to object storage such as Wasabi or Backblaze B2. Ransomware is the main reason both are needed: a reachable local backup can be encrypted or deleted, while an immutable cloud copy sits beyond the attacker's reach.
At home
The trade-off is bandwidth against risk. A cloud backup's first full copy, called seeding, can take days over a normal connection, and a full disaster restore can take just as long, so some providers ship data on physical drives. Local backups avoid that wait but share every risk of the building. While it's tempting to pick one, in my view anything you can't afford to lose deserves both.
At work
A robust hybrid design maps each tier to recovery objectives: frequent local snapshots for low RPO and fast restores, replication to immutable cloud storage for offsite and ransomware protection, and optionally cloud failover so servers can run in the provider's data centre during an outage. Key controls include encryption in transit and at rest, separate credentials for the backup console, data residency in Canada where required, and scheduled restore tests from both tiers.
Real-world examples
At home
Sophie accidentally deleted a critical project folder. Because her MSP kept a local backup appliance, she had the folder restored in minutes, no waiting on a slow internet download. The cloud copy stayed as her disaster safety net.
At work
A burst pipe flooded Carlos's office overnight, destroying the server and its local backup drive. The cloud backup, untouched at a remote data centre, let his MSP restore operations on temporary hardware within a day, something local backups alone could never have done.
How it compares
| feature | Local backup | Cloud backup |
|---|---|---|
| Restore speed | Fast (data on-site) | Slower (over internet) |
| Survives site disaster | No | Yes |
| Ransomware resilience | At risk if connected | Strong if immutable |
| Ongoing cost | Mostly upfront hardware | Monthly subscription |
| Best role | Fast everyday restores | Offsite disaster recovery |
These aren't rivals: local backup handles speed, cloud backup handles catastrophe. Combining them satisfies the 3-2-1 rule and covers both routine and worst-case recovery.
For analysts
Don't frame this as an either/or decision. The resilient answer is local plus cloud: fast local restores for the daily 'oops,' and an immutable offsite cloud copy for the disaster that takes out the whole office.
History & origin
Businesses long relied on local backups (tapes, then external drives and appliances) because bandwidth made offsite copies impractical. As internet speeds rose and cloud storage became cheap in the 2010s, cloud backup went mainstream. The rise of ransomware, which targets locally connected backups, cemented the case for keeping an offsite cloud copy that attackers on the local network can't reach.