Nine lines, because the material worth duplicating refuses to sit in one place. Some of it is on desks, some on a machine in a back room, and an increasing share lives in accounts run by a platform that keeps them available without keeping a second copy on your behalf.
Availability is what a platform undertakes to provide. Preservation of what you put inside it is a separate undertaking that nobody made. Deleted items folders empty themselves, retention windows shut, and taking an account away carries off the post with it. The ledger has the same problem in a sharper form, since an import that goes in wrong has no button sized to undo it.
So the duplicates here run across the entire picture: desks and back rooms, the Microsoft side, the Google side, the books, and the directory arrangement that decides who is able to open any of it.
An untested duplicate is a conviction. It may well be a reasonable conviction, but it is not evidence, and evidence is what a serious customer is asking for when they ask whether recovery has ever been rehearsed.
The rehearsal line stands copies up on a rota and records the outcome and stamps a date against it. Problems then surface on a dull afternoon when nothing else is happening, which is the only sensible occasion to discover them.
Nine lines. Take whichever match what you genuinely run and leave the others. Storage is held in a shared pool instead of rationed out one machine at a time.
Earlier versions of whichever documents are open today. The ordinary save is not the problem. The problem is the quotation that was right on Tuesday, is wrong by Thursday, and has been saved over four times in between by three different people.
| Claimed for | Windows workstations where documents change every day |
|---|---|
| Reduces | Saved over work with no earlier state to fall back on |
| Term | Renews monthly. Earlier states held twenty eight days. |
| Filed by | N-able Cove |
| Examined by | Fortify 24x7 people, on runs that fail or get skipped |
The entire machine rather than a chosen selection of folders. Once a drive fails, the question worth answering is how soon that person is productive again, and the answer improves enormously when the applications, the licences and the awkward undocumented settings all came back with the files.
| Claimed for | Workstations that would be slow and irritating to rebuild by hand |
|---|---|
| Reduces | Days spent reassembling a machine after a drive fails |
| Term | Renews monthly. Five hundred gigabytes in the shared pool. |
| Filed by | N-able Cove |
| Examined by | Fortify 24x7 people, on runs that fail or get skipped |
That machine in the back room which every other machine leans on. Copies are taken with the database engine aware they are happening, which is the whole difference between something that restores and a directory of files that restores into an error.
| Claimed for | Physical servers carrying accounting or trade specific systems |
|---|---|
| Reduces | The one failure that stops the whole business trading |
| Term | Renews monthly. Two thousand gigabytes in the shared pool. |
| Filed by | N-able Cove |
| Examined by | Fortify 24x7 people, on runs that fail or get skipped |
Identical protection for virtual servers, charged one guest at a time. Charging by guest keeps the invoice tracking what is genuinely running, so a densely packed host is not priced as though it were nearly idle.
| Claimed for | Virtual servers on your hypervisor or on a hosted one |
|---|---|
| Reduces | Losing a guest along with everything it was serving |
| Term | Renews monthly. Two thousand gigabytes in the shared pool. |
| Filed by | N-able Cove |
| Examined by | Fortify 24x7 people, on runs that fail or get skipped |
Keeping a tenant reachable and keeping what is inside it are separate undertakings, and only the first belongs to the platform. The deleted items folder duplicates nothing: it empties, windows close, and removing a leaver carries their post off as well.
| Claimed for | Microsoft 365 tenants carrying mail and documents that matter |
|---|---|
| Reduces | Irreversible loss through deletion, closed windows and departures |
| Term | Renews monthly. One terabyte in the pool for each user. |
| Filed by | N-able Cove |
| Examined by | Fortify 24x7 people, on runs that fail or get skipped |
Precisely the same argument, one platform to the left. Messages, stored documents, address books, diaries and task lists are duplicated and can be returned one at a time, which is the only sort of recovery anybody is ever glad to run.
| Claimed for | Google Workspace tenants of any size |
|---|---|
| Reduces | Mail and documents vanishing along with a removed account |
| Term | Renews monthly, taken up front, closes when you say so |
| Filed by | Dropsuite |
| Examined by | Fortify 24x7 people, on runs that fail or get skipped |
Everything else about a business can be reassembled from the ledger, and the ledger cannot be reassembled from anything else. A mistaken import or an enthusiastic bulk edit is genuinely painful to unpick by hand. This holds an uninterrupted duplicate and returns it in a single move.
| Claimed for | Every QuickBooks Online company file where books are kept |
|---|---|
| Reduces | Unpicking a mistaken import or bulk edit by hand |
| Term | Renews monthly, taken up front, closes when you say so |
| Filed by | Dropsuite |
| Examined by | Fortify 24x7 people, on runs that fail or get skipped |
The mail is not the subject here. The arrangement behind the mail is. Membership, roles, policies and application consent decide who is able to reach what, and one careless adjustment there is far harder to spot than a missing document. This keeps the arrangement and reports when it shifts.
| Claimed for | The Entra ID directory sitting behind a Microsoft tenant |
|---|---|
| Reduces | Permission changes that go unremarked for weeks |
| Term | Renews monthly. No ceiling on retention. |
| Filed by | Dropsuite |
| Examined by | Fortify 24x7 people, on directory changes |
A duplicate never tested is a conviction, not a control. This line stands copies up on a rota and records the outcome with a date stamped against it, so when an insurer or a large customer asks whether recovery has been rehearsed, the answer is a record instead of a shrug.
| Claimed for | Systems you would rather not rehearse recovery on for the first time live |
|---|---|
| Reduces | Learning on the worst possible day that a duplicate never returned |
| Term | Renews monthly, taken up front, closes when you say so |
| Filed by | N-able Cove |
| Examined by | Fortify 24x7 people, who read each rehearsal outcome |
Worth reading twice. A claim with no stated boundary is one nobody bothered to examine.