Flamingo Raises $4.5M Seed Round

Skip to content

Backup solutions for IT teams: enterprise, appliance or cloud

Best Practices
Technology
IT Operations
Conrad LunderstedtConrad Lunderstedt
September 30, 2026
285 views
Backup solutions for IT teams: enterprise, appliance or cloud

Enterprise backup compared by architecture: appliance, software on your own storage, direct-to-cloud and hybrid, with endpoint and laptop backup, backup storage tiers, 3-2-1-1-0, RPO and RTO sizing, restore testing and a buyer checklist for IT teams.


Updated: November 2026

Enterprise backup is the set of tools and processes that copy an organization's servers, virtual machines, endpoints, SaaS data, databases and configuration, and restore them after a failure, deletion or attack. Whether a restore works on the day you need it comes down to architecture: where the copies live, who can delete them and how fast they come back. This guide compares enterprise backup solutions by architecture, from on-premises appliances to direct-to-cloud and hybrid, covers endpoint and laptop backup, and ends with a checklist IT teams can use to pick one.

TL;DR

  • Pick the architecture before the brand. Appliance, software on your own storage, direct-to-cloud and hybrid fail in different ways, and the product is a detail inside that choice.
  • Protect more than servers. VMs, endpoints and remote laptops, Microsoft 365 or Google Workspace, databases and configuration each need their own coverage and restore path.
  • Follow 3-2-1-1-0. Three copies, two media, one offsite, one immutable or offline, zero errors on verified restores.
  • Size from RPO and RTO. Backup frequency, retention and bandwidth come from how much data you can lose and how long you can be down.
  • Harden and patch the backup system. It holds a copy of everything, so give it its own admin accounts, MFA and the same patch cycle as your other critical servers.
  • Measure restores. A successful job only proves data was copied. A tested restore proves it comes back.

What enterprise backup has to cover

A backup plan that stops at the file server covers one workload out of six. The table lists all six, what breaks without a backup and what each one needs.

WorkloadWhat breaks without a backupWhat the backup needs
Physical serversHardware failure takes the OS, apps and data togetherImage-level backup with bare-metal restore
Virtual machinesA host or datastore loss takes every VM on it at onceHypervisor-level backup with changed block tracking
EndpointsLaptops hold files that never reach a serverAgent-based file backup, policy-driven
Microsoft 365 / Google WorkspaceDeleted mail, OneDrive and SharePoint data past retentionThird-party SaaS backup with its own retention
DatabasesA consistent file copy of a running database may not restoreApplication-aware or native dump backups
ConfigurationFirewall, switch, hypervisor and cloud settingsExported configs and infrastructure-as-code in version control

SaaS is the first gap to close. Microsoft keeps the service running, but recovering what your users deleted or overwrote is on you. Our guide to Microsoft 365 backup covers where Microsoft's retention ends and a backup has to take over.

Configuration is the other quiet gap. CISA's #StopRansomware Guide (September 2023) advises keeping infrastructure-as-code templates backed up offline and under version control, so resources can be redeployed quickly. A restored server is not much use if the network it plugs into has to be rebuilt from memory.

Endpoint and laptop backup

Laptops are the workload a server-first plan skips. Files saved to a local drive never reach the file server, and a lost, stolen or encrypted laptop takes them with it. Enterprise endpoint backup closes that gap with an agent on each device that backs up chosen folders, or the whole disk, on a schedule set by central policy.

For a hybrid or remote workforce, cloud-based laptop backup is the practical design. The agent sends changes straight to the provider's cloud over any internet connection, so a laptop that has not been on the office network for a month is still protected. Look for policy-based folder selection, bandwidth throttling, encryption with keys you control, legal hold for departing staff, and self-service restore so users can get a file back without a ticket.

File sync and backup solve different problems. OneDrive Known Folder Move keeps folders such as Desktop, Documents and Pictures in OneDrive, but a deletion or a ransomware encryption syncs to the cloud copy too, and OneDrive's own Files Restore reaches back 30 days. Back up the endpoint, or the Microsoft 365 tenant behind it, with a tool that keeps its own retention. Our guide to backup software for Windows endpoints and servers compares agent options.

The four backup architectures

Enterprise backup solutions come in four shapes: two on-premises (an appliance, or software on your own storage), one cloud-only and one hybrid. Each one decides where copies live, how fast a local restore runs and what an attacker can reach.

Backup appliances

An appliance is a box that arrives with the backup software and storage already installed. You plug it in, point it at your servers and it keeps local copies while replicating to the vendor's cloud.

The appeal is speed and simplicity. Local restores run at LAN speed, and an appliance with instant virtualization can boot a protected server as a VM on the appliance itself while you fix the original. The trade-offs are a fixed storage ceiling, a hardware refresh every few years and a subscription that bundles the cloud tier whether you need it or not.

The bundled subscription is where buyers push back. This r/sysadmin thread from January 2025 starts with a small company paying $775 a month for Datto to back up under 2 TB on one physical server, and the replies split between building your own and renegotiating the service.

Software on your own storage

Here you license backup software and run it on hardware you choose: a backup server, a NAS, a SAN or an object store. You control capacity, retention and where the offsite copy goes.

This is the most flexible option and can be the cheapest per terabyte at scale. It also puts the design work on your team. Someone has to harden the backup server, separate its credentials from the domain, size the repository and set up the offsite copy.

Enterprise backup storage comes in four tiers, and larger designs mix them. A backup server with direct-attached disk is the simplest repository. A deduplicating storage appliance cuts the capacity long retention needs. On-premises S3-compatible object storage adds object lock for immutable copies, and tape or a cloud object tier holds the offsite copy. Our Veeam Backup & Replication review shows how one software-on-your-storage product uses hardened repositories and object storage.

Direct-to-cloud backup

Agents on each server or endpoint send data straight to the provider's cloud, with no local repository. There is no hardware to buy or maintain, and offsite is built in.

The catch is restore speed. Pulling a multi-terabyte server back over the internet takes days, so full-server recovery depends on your bandwidth or the provider's option to ship a drive. Direct-to-cloud fits endpoints, branch offices and SaaS well. It fits large file servers less well when the recovery time target is tight.

Hybrid backup

Hybrid keeps a fast local copy on-site and a second copy in the cloud. Day-to-day restores come from the local copy, and the cloud copy covers site loss and ransomware that reaches the local repository.

Appliances that replicate to a vendor cloud are hybrid by design. Software-on-your-storage setups become hybrid when you add a cloud or object-storage tier. For IT teams with servers on-site and a recovery target measured in hours, hybrid covers both the fast local restore and the copy that survives a site loss.

ArchitectureLocal restore speedOffsite copyCost modelMain risk
ApplianceFast, can boot VMs on the boxVendor cloud, bundledHardware plus subscriptionStorage ceiling, lock-in to the bundle
Software on your storageFast, depends on your hardwareYou design itLicences plus your hardwareDesign and hardening are on your team
Direct-to-cloudSlow for full serversBuilt inPer device or per TBBandwidth limits large restores
HybridFast from local copyCloud tierCombinationTwo tiers to monitor and test

The 3-2-1-1-0 rule in practice

The classic rule comes from US-CERT's 2012 guide to data backup options: keep three copies of important files, on two different media types, with one copy stored offsite. Ransomware changed what "offsite" has to mean, so vendors extended it. Veeam's version, 3-2-1-1-0, adds one immutable or air-gapped copy and zero errors after automated verification and restore testing.

In an enterprise backup design, each digit maps to something concrete:

  1. Three copies: production data, the local backup and the offsite backup.
  2. Two media: for example disk in the local repository and object storage or tape offsite.
  3. One offsite: a cloud tier, a second site or tape that leaves the building.
  4. One immutable or offline: object lock, a hardened repository with no shell access, or media that is physically disconnected.
  5. Zero errors: automated verification of every backup, plus scheduled restore tests.

The fourth digit exists because attackers go for backups first. CISA's guide says it plainly: "many ransomware variants attempt to find and subsequently delete or encrypt accessible backups." If the backup server uses domain admin credentials, whoever steals those credentials can delete your recovery along with everything else. Keep backup admin accounts separate from the domain, protect them with MFA and make at least one copy impossible to change before its retention ends. Our breakdown of a ransomware attack shows where in the attack chain backups get hit.

The cost of getting this wrong shows up in the numbers. In Sophos' State of Ransomware 2025 survey of 3,400 organizations (June 2025), only 54% of organizations used backups to restore encrypted data, the lowest rate in six years. The 2026 edition, a survey of 2,158 IT and security leaders in 17 countries published in July 2026, shows a rebound to 66%.

IBM Technology's walkthrough covers the 3-2-1 rule and why the extra immutable copy matters now:

Harden the backup system itself

The backup platform holds a copy of everything, so it deserves the same protection as a domain controller. Attackers who reach it can read your data, delete your recovery or both.

Start with identity. Give the backup console its own admin accounts that are not members of the domain, and put MFA on every one of them. A backup server joined to the domain inherits every domain compromise, so keep the repository server off the domain entirely.

Then shrink the attack surface. The repository should accept backup traffic and little else: no internet browsing, no email, no shared admin tools, and remote access only from a management network. Hardened Linux repositories go further by removing shell access for the backup service account, so even a stolen credential cannot delete immutable files.

Patch the backup stack on the same cycle as your other critical servers, because backup software is a target in its own right. CISA's Known Exploited Vulnerabilities catalog lists two Veeam Backup & Replication flaws, CVE-2023-27532 (added August 2023) and CVE-2024-40711 (added October 2024), both marked as known to be used in ransomware campaigns. Our comparison of patch management software covers tools for patching servers across a fleet, including enterprise and cloud setups.

Encrypt backups at rest and in transit, and store the encryption keys somewhere a disaster cannot reach. An encrypted backup with a lost key is as gone as a deleted one. Write down where the keys live, who can reach them and how you retrieve them when the primary site is dark.

Finally, watch the backup system itself. Alert on failed jobs, on retention or immutability settings being changed, on new admin accounts and on large deletions. A sudden drop in backup size is worth a look too, because it can mean data was encrypted or deleted upstream before the job ran.

Sizing by RPO, RTO and retention

Two numbers drive every sizing decision. Recovery point objective (RPO) is how much data you can afford to lose, measured in time. Recovery time objective (RTO) is how long a system can be down. Our guide to RTO vs RPO walks through setting both per system.

RPO sets backup frequency. A database with a 15-minute RPO needs log backups or snapshots every 15 minutes. A file share with a 24-hour RPO is fine with a nightly job. RTO sets architecture. A four-hour RTO for a large server rules out pulling it back from the cloud over a normal internet line.

Bandwidth is where plans meet reality. Take an illustrative 10 TB environment with a 2% daily change rate and a 100 Mbps uplink:

StepDataTime at 100 Mbps
Initial cloud seed10 TBAbout 9 days
Nightly changes200 GBAbout 4.4 hours
Full restore from cloud10 TBAbout 9 days

The seed and the restore are why hybrid exists. The nightly change fits in the window, but nobody wants a nine-day RTO. Seeding by shipped drive, a local copy for fast restores, or a bigger pipe are the three ways out.

Backup method changes the math too. Incremental-forever designs move only changed blocks after the first full, and synthetic fulls rebuild a full backup on the repository without re-reading production. Our guide to incremental vs differential backup covers the restore-chain trade-offs.

Retention is the last dial. One standard pattern is grandfather-father-son: daily copies for two weeks, weekly for two months, monthly for a year and yearly for as long as regulation requires. Match retention to your compliance obligations and to how long an attacker might sit in the network before you notice.

Restores are the product

A completed backup job proves the data was copied. It does not prove the data comes back, boots or opens.

Restore testing has levels, and each catches a different failure. Automated boot verification catches a corrupt image. Starting services catches broken dependencies. Opening real data catches silent application-level corruption. A full recovery drill catches everything else, including missing passwords and undocumented steps.

This r/sysadmin thread asks the question every IT team should answer: how do you test restores, not just backups? The answers range from automated boot screenshots to quarterly restores into an isolated test domain.

A workable cadence: automated verification on every backup, a file-level restore test every month, an application restore into an isolated network every quarter, and a full disaster recovery exercise once or twice a year. Record the time each one takes, because that measured time is your real RTO. Our guide to disaster recovery testing covers the five test types and when to run each.

Evaluation checklist for enterprise backup solutions

Use these questions in vendor walkthroughs and trials, and record the answers in your data backup plan. Ask vendors to show each one live.

  1. Coverage: does it protect every workload in your table, including SaaS and databases, or do you need a second product?
  2. Immutability: can you lock backups so no one, including an admin, can delete them before retention ends?
  3. Credential separation: can the backup system run with its own accounts and MFA, outside your domain?
  4. Local restore speed: how fast can it restore a full server, and can it boot one instantly from the backup?
  5. Cloud restore path: what happens when you need 10 TB back from the cloud, and is drive shipping available?
  6. Verification: does it test backups automatically, and does it report failures clearly?
  7. Granular recovery: can you restore a single file, mailbox item or database table without a full restore?
  8. Reporting: can you show auditors job history, retention and restore test results?
  9. Scale and cost model: is pricing per device, per socket, per terabyte or bundled, and what happens at twice your data?
  10. Exit: can you read or export your backups if you leave the product?

Where this fits in your stack

This guide is for IT teams choosing backup for their own environment. If you run backup as a service for clients, our guide to MSP backup solutions covers the reseller side: margins, multi-tenancy and client reporting.

Managed enterprise backup, where a provider runs the jobs, monitoring and restore tests for you, uses the same four architectures with someone else at the console. Put the checklist above to the provider, and add two questions: who holds the backup admin credentials, and who holds the encryption keys.

For smaller companies, our small business backup guide keeps the choice simpler.

For copies that ransomware cannot delete, our guide to immutable backups goes deeper on how they work.

If your servers run on vSphere, our VMware backup guide covers image-level options and what to test.

Backup stays with the vendor you run. Flamingo, which publishes this guide, builds OpenFrame, open, AI-native infrastructure for IT and security, and it is not a backup product. What it can do is check that the backup agent is running on every device: run the check as a script across your fleet, collect the output in one place and flag the devices that fail it. OpenFrame costs $1 per device per month with 10M AI tokens included, or $0.80 billed annually with 25M tokens, after a 14-day free trial.

Start with the architecture, cover every workload, follow 3-2-1-1-0 and measure your RTO with real restores. The product that passes your checklist is the right one for your team.

Conrad Lunderstedt

Conrad Lunderstedt

Solution Architect

I'm Conrad, Solution Architect at Flamingo. I've spent about 26 years in IT, roughly half of it inside MSPs and the rest in enterprise environments, so I've watched vendor decisions get made on both sides of that line. Now I spend my days talking with MSPs about the stack they already run, and helping them work through the requests and issues that come with it.

Related Content

Frequently Asked Questions

/blog/enterprise-backup

Still deciding?

Ask Mingo answers from our docs and customer stories.

Loading related content and questions