The layer built on the assumption that the rest failed.
Backup is the only control in this catalog whose design premise is defeat. Every other family is trying to stop something happening. This one exists because one day something was not stopped, and the only question still open is how much work has to be done a second time.
It is also the first thing an attacker goes looking for. A competent ransomware crew hunts for reachable backups before encrypting a single file, for a plainly commercial reason: a victim who can restore has nothing left to negotiate about. Which makes custody, rather than capacity, the thing you are really buying.
Cove for machines, Dropsuite for the SaaS tenants.
Cove protects workstations, physical servers, and virtual servers. Passes are incremental after the first one, can be held in a local cache as well as the cloud, and are encrypted with 256-bit AES in flight and at rest. Bare-metal restore is available on Windows, so a dead machine can be rebuilt onto replacement hardware instead of reinstalled by hand over a weekend. The server line is application aware, carrying support for SQL, Oracle, MySQL, Exchange, and SharePoint rather than selling it separately.
The point that matters most is where the copy lives. The cloud vault sits outside the environment it protects, on separate infrastructure behind separate credentials. A compromised domain administrator can wreck anything reachable from inside your network. They cannot reach a vault that does not live there. That is the entire argument for this family, and it is also why replication has never been a backup: mirroring reproduces a catastrophe just as faithfully, and just as promptly, as it reproduces good work.
Dropsuite handles the platforms that are not machines. Microsoft 365 across Exchange, SharePoint, OneDrive, and Teams; Google Workspace across mail, drives, contacts, calendars, and tasks; QuickBooks Online by company file; and Entra ID configuration. Restores are granular, so one message or one document returns without disturbing anything around it.
Storage is pooled across the account rather than capped device by device, so one oversized server does not fail because a laptop somewhere was sitting on headroom it never touched.
The platform stays up. The contents are yours.
Read your Microsoft or Google agreement far enough and the division of labor is already written down: the vendor is accountable for keeping the service running, and you are accountable for what lives inside it. Very few people have read that far.
What the platforms hand you natively is a set of short-dated conveniences. Deleted mail waits in a bin for a fixed window you do not control. A leaver's mailbox disappears alongside the license somebody reclaimed to save money. Retention rules cover precisely what the person writing them thought of, on the afternoon they wrote them. An administrator whose account has been taken can empty sites wholesale, because emptying sites is what the role is for. None of it was designed with an adversary in the room.
On the directory the shortfall is sharper again. Microsoft keeps roughly thirty days of Entra ID history. The Entra line holds configuration without a horizon, watches attribute changes as they occur, and puts a value back the way it was, which is a different kind of recovery from pulling a file out of a vault.
An untested restore is a belief, not a control.
The recovery testing line performs restores to a schedule you choose, weekly or monthly, and issues proof that each one succeeded. What it buys is the difference between a recovery time you estimated and a recovery time somebody has watched happen, with paperwork behind it. When an auditor, an insurer, or your own board asks whether you have backups, this is the question they are really asking.
The lines in this family
Nine lines / prices fetched liveWorkstation Backup
per workstation| Scope | Full system backup of the workstation |
|---|---|
| Platforms | Windows / Linux / macOS |
| Locations | Cloud vault, with an optional local copy |
| Rebuild | Bare-metal restore onto replacement hardware, Windows |
| Scheduling | Data selection and schedule fully customizable |
| Encryption | 256-bit AES, in flight and at rest |
| Storage | 500 GB, pooled account-wide |
| Counted by | One workstation / monthly |
File and Folder Backup
per Windows workstation| Scope | Files and folders only, not the whole system |
|---|---|
| Platforms | Windows |
| Cadence | Two passes a day across protected office files |
| Versions | Any version from the past 28 days, back in seconds |
| Management | Centrally managed alongside the rest of the estate |
| Counted by | One Windows workstation / monthly |
The light line, for machines where the documents matter and the operating system is disposable.
Server Backup
per physical server| Scope | Full system backup of a physical server |
|---|---|
| Platforms | Windows / Linux |
| Applications | SQL, Oracle, MySQL, Exchange, and SharePoint support included |
| Recovery | A single file, or the whole server, bare-metal capable |
| Locations | Cloud vault, with an optional local copy |
| Encryption | 256-bit AES, in flight and at rest |
| Storage | 2000 GB, pooled account-wide |
| Counted by | One physical server / monthly |
Virtual Server Backup
per virtual server| Scope | Full system backup of a virtual server |
|---|---|
| Platforms | Windows / Linux |
| Applications | SQL, Oracle, MySQL, Exchange, and SharePoint support included |
| Recovery | One file or the whole guest, bare-metal capable |
| Encryption | 256-bit AES, in flight and at rest |
| Storage | 2000 GB, pooled account-wide |
| Counted by | One virtual server / monthly |
Microsoft 365 Backup
per licensed user| Workloads | Exchange / SharePoint / OneDrive / Teams |
|---|---|
| Mail retention | 7 years |
| Files and Teams retention | 1 year |
| Shared mailboxes | Carry no charge |
| Storage | 1 TB a user, pooled tenant-wide |
| Custody | Kept apart from the tenant and the credentials that administer it |
| Counted by | One licensed user / monthly |
Count the shared mailboxes as well: they attract no charge, and they are usually the place purchase orders and supplier correspondence accumulate.
Google Workspace Backup
per licensed user| Workloads | Gmail / My Drive / shared drives / contacts / calendars / tasks |
|---|---|
| Mail cadence | 12 passes a day |
| Drive cadence | 3 passes a day, My Drive and shared drives alike |
| Everything else | Contacts, calendars, and tasks once a day |
| Restore | Granular, from a single email up to the entire environment |
| Encryption | AES 256-bit, with TLS on the wire |
| Counted by | One licensed user / monthly |
QuickBooks Online Backup
per company file| Scope | QuickBooks Online company data |
|---|---|
| Cadence | Automated and continuous |
| Recovery | Download, restore, and replication in a single click |
| Storage | Unlimited |
| Access | From any device, wherever you happen to be |
| Availability target | 99.99 percent or better on data availability and service updates |
| Encryption | 256-bit AES, in flight and at rest |
| Counted by | One company file / monthly |
Intuit gives you no guarantee that your data is recoverable. This is the line that closes the gap.
Entra ID Backup
per tenant| Scope | Entra ID configuration: directory objects, roles, applications, policy |
|---|---|
| Retention | Unlimited, against Microsoft's own 30-day window |
| Monitoring | Change monitoring in real time, down to named attributes |
| Recovery | Roll an unwanted change back to its last known good value |
| Export | Open-standard export of the data |
| Counted by | One tenant / monthly |
One tenant, one rate. The directory is the control plane sitting under everything else you have bought.
Recovery Testing
per protected system| Function | Automated recovery testing |
|---|---|
| Cadence | Weekly or monthly, whichever you choose |
| Output | Proof of a successful restore, fit to hand to an auditor |
| Purpose | Turns an estimated recovery time into an observed one |
| Counted by | One protected system / monthly |
Bought against the systems whose recovery you would one day have to defend to somebody.
What backup is not, however well it is run
It is not prevention, and buying it instead of the other five families is the most expensive mistake available in this catalog. A restore means the incident already happened, the work already stopped, and somebody already lost a week of their life to it. Backup makes a disaster survivable. It does not make one cheap.
The first pass is the big one, since nothing has been sent yet. Leave the machine powered on and give it room. Everything after that sends only what changed.
Storage allowances are pooled across the account rather than guaranteed per device, and if your estate outgrows the pool we would rather raise it with you early than bill you a surprise. A SaaS connector protects exactly what you authorize it to see, so a tenant nobody connected is not covered by a subscription you have already paid for.
And an untested restore is worth roughly what an untested fire alarm is worth. If recovery is something you would ever need to prove to a regulator, an insurer, or a board, buy the testing line and let us hand you the evidence.
Heads up: card statements show FORTIFY 24X7 - CyberDefense is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.