Nine lines. Workstations, servers both physical and virtual, and those cloud accounts everyone presumes are being handled somewhere else. One line here matters more than the rest and sells least of all: it exercises recovery to a schedule and writes down what came out.
Keep a copy on the machine and it dies alongside the machine. Keep one inside the same cloud tenant and it inherits both that tenant's misfortunes and its retention rules, which is the identical error wearing quieter clothes. N-able Cove carries hardware and the Microsoft half. Dropsuite carries Google Workspace, Entra ID configuration, plus whatever ledger QuickBooks Online happens to hold.
Storage is pooled by line rather than fixed per machine, which is what prevents one unusually large server from crowding everything else off the same subscription.
Verification exercises recovery by itself and records what came out. Leave it off and every other line on this bench amounts to a schedule that appeared to complete. Put it on and recovery becomes something you can place before an insurer, before an auditor, or before a board that has lately started asking questions.
It also decides when you find out. A verification failure surfaces on an unremarkable weekday with room to fix it, rather than during the one hour of the year when nobody has room for anything.
Every figure below is taken from billing as this page loads. Whatever goes onto the tray remains there while you read on.
Twenty eight days of version history for whichever documents are in play on a Windows workstation. Cheap, frequent rescue from ordinary human error, as distinct from the whole machine answer further down this bench.
| Runs on | Windows workstations |
|---|---|
| Reacts to | Overwrites, deletions, yesterday's perfectly good version |
| Shelved for | Machines whose output is documents |
| Cleared by | Engineers drive the restore if you would rather not |
| Assayed by | Counted per Windows workstation, each month |
The machine entire, not a folder from it. Workstations under Linux, macOS or Windows, sitting against 500GB of pooled storage, which keeps one heavy laptop from crowding everything else out.
| Runs on | Workstations under Linux, macOS or Windows |
|---|---|
| Reacts to | A failed drive, a stolen laptop, an unplanned rebuild |
| Shelved for | Machines that would take a day to reassemble by hand |
| Cleared by | Engineers drive the restore if you would rather not |
| Assayed by | Counted per workstation, each month |
Whole copies of physical servers under Linux or Windows, databases handled properly, resting against 2000GB of pooled storage.
| Runs on | Physical servers under Linux or Windows |
|---|---|
| Reacts to | Failed hardware, corruption, a volume encrypted overnight |
| Shelved for | The machine in the cupboard nobody dares reboot |
| Cleared by | Engineers drive the restore if you would rather not |
| Assayed by | Counted per physical server, each month |
The same handling for guests on a hypervisor, databases included, resting against 2000GB of pooled storage. Counting guests rather than hosts is what keeps the invoice matching the register.
| Runs on | Windows and Linux guests on a hypervisor |
|---|---|
| Reacts to | Corruption, deletion, a host that stopped hosting |
| Shelved for | Guests that people lean on every working day |
| Cleared by | Engineers drive the restore if you would rather not |
| Assayed by | Counted per virtual server, each month |
Copies of Exchange, of SharePoint, of OneDrive, of Teams, all taken out beyond Microsoft, with 1TB pooled against each licensed user. Keeping a tenant running is Microsoft's undertaking. Keeping its history belongs to somebody else entirely, which is the gap this line fills.
| Runs on | A Microsoft 365 tenant joined with your consent |
|---|---|
| Reacts to | Deletion, lapsed retention, a mailbox emptied deliberately |
| Shelved for | Every tenant, given that a recycle bin copies nothing |
| Cleared by | Engineers drive the restore if you would rather not |
| Assayed by | Counted per licensed user, each month |
Everything a Workspace tenant holds gets lifted out: messages, drives, contacts, calendars, tasks. The restore is fine enough to hand back one item rather than an entire account.
| Runs on | A Google Workspace tenant joined with your consent |
|---|---|
| Reacts to | Deletion, departure, a shared drive tidied too keenly |
| Shelved for | Businesses whose working record lives in Workspace |
| Cleared by | Engineers drive the restore if you would rather not |
| Assayed by | Counted per licensed user, each month |
The ledger copied continuously, restored in one click, charged by company. Books are the one record where a rough recollection of last quarter will not do.
| Runs on | QuickBooks Online joined with your consent |
|---|---|
| Reacts to | A bad edit, a bad import, a deletion nobody intended |
| Shelved for | Anyone who has to sign the numbers afterwards |
| Cleared by | Engineers drive the restore if you would rather not |
| Assayed by | Counted per company file, each month |
The directory itself: groups, policy and configuration, retained without limit and watched for changes as they happen. Reassembling a directory from memory is not a recovery plan, it is an anecdote.
| Runs on | An Entra ID tenant joined with your consent |
|---|---|
| Reacts to | Configuration and policy moving, whoever moved them |
| Shelved for | Tenants where access is itself the control |
| Cleared by | Engineers drive the restore if you would rather not |
| Assayed by | Counted per tenant, each month |
The line that converts this whole bench from a belief into a measurement. Recovery is exercised automatically and each success is written down as evidence rather than assumed from a green tick.
| Runs on | Anything a backup line already covers |
|---|---|
| Reacts to | A restore that quietly stopped producing anything usable |
| Shelved for | Anyone required to evidence recovery rather than assert it |
| Cleared by | Results recorded and handed over exactly as they came out |
| Assayed by | Counted per protected system, each month |
Recovery is the easiest promise to oversell, so these limits are printed before you buy instead of afterwards.
Heads up: card statements show FORTIFY 24X7 - H2 Tech Systems is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.