Copies of machines, servers, virtual guests and the accounts nobody remembers to protect: mail tenants, Workspace, the bookkeeping ledger, the directory itself. Then one further line whose only occupation is proving a restore comes back, which is the gap between faith and knowledge.
Everyone grasps that a laptop wants a backup. Rather fewer notice that a mail tenant arrives without one. Availability of the service is what Microsoft and Google undertake; keeping a copy of whatever an account holder deliberately removed last spring is not, and every recycle bin has a floor.
The identical hole sits beneath the bookkeeping ledger and beneath the directory. A ledger platform with no copy of its own is one point of failure under every figure you publish. A directory with no snapshot turns a bad role change into an argument instead of an undo.
Until a copy has actually been brought back, holding one is an article of faith. Reasonable faith, admittedly, since jobs report success nightly. The way it fails in practice is an image that refuses to start on the one evening that counts.
This last line runs recovery by itself and produces dated evidence that a copy returned and came up. Insurers want that. Auditors want that. More to the point, it means the night you need something back is not the first night anybody has tried. Aim it at whatever would halt the business, and skip it everywhere else.
Billing supplies every figure below while the page loads. An entry holds its place while you go on reading.
Continuous version history for documents being worked on at a Windows desk. It carries the smallest price on this page and gets called on more than anything else, because the everyday catastrophe is not ransomware but somebody saving the wrong thing over the right one.
| Deposited on | Windows workstations, one unit for each machine |
|---|---|
| Seals | Nothing; this is a copying line and its work is the journey home |
| Held at | Versioned copies in N-able Cove cloud storage, kept away from the device |
| Sealed by | N-able Cove |
| Witnessed by | Engineers here, going through each day of job outcomes |
The whole machine imaged, rather than a chosen handful of folders. When a workstation is lost, stolen or encrypted, what you want back is the whole of it as it stood, not an afternoon spent trying to recall what had been installed.
| Deposited on | Workstations on any supported platform, one unit for each machine |
|---|---|
| Seals | Nothing; it assures you a copy exists, never that nothing will go wrong |
| Held at | Images in N-able Cove cloud storage, drawn against a pooled allowance |
| Sealed by | N-able Cove |
| Witnessed by | Fortify 24x7 engineers confirming jobs finish and restores behave |
Server imaging that understands the databases running above it, so what gets taken is a copy in a condition capable of coming back, rather than a snapshot of files caught halfway through a write.
| Deposited on | Physical servers, one unit for each machine |
|---|---|
| Seals | Nothing; the worth of it lies in a coherent copy and a proven way home |
| Held at | Server images in N-able Cove cloud storage, against the pooled allowance |
| Sealed by | N-able Cove |
| Witnessed by | Fortify 24x7 engineers going over job outcomes and retention settings |
The identical treatment for virtual machines, counted one to a guest. Snapshots taken on the hypervisor are convenient and they are not backups, because they sit on the very storage they are meant to be protecting.
| Deposited on | Virtual servers, one unit for each guest |
|---|---|
| Seals | Nothing; the object is a copy that outlives the platform holding it |
| Held at | Guest images in N-able Cove cloud storage, against the pooled allowance |
| Sealed by | N-able Cove |
| Witnessed by | Fortify 24x7 engineers verifying nightly that the run completed |
Microsoft keeps your tenant running. Retaining a copy of whatever somebody deliberately removed four months back is not part of that undertaking. Mail, documents, sites and chat history are copied out to storage that is not the tenant.
| Deposited on | Every licensed user in the tenant, one unit per person |
|---|---|
| Seals | Nothing; it is the copy that outlasts the tenant recycle bin |
| Held at | Copies in N-able Cove cloud storage, beyond your Microsoft tenant |
| Sealed by | N-able Cove |
| Witnessed by | Fortify 24x7 engineers keeping an eye on the copy schedule |
The identical argument aimed at Google Workspace. Copies of mail, of drive material, of contacts, of calendars and of tasks go to storage held apart from the tenant, and a single item comes back without an entire account being replayed.
| Deposited on | Every licensed Workspace user, one unit per person |
|---|---|
| Seals | Nothing; its purpose is that a deletion stops being final |
| Held at | Copies in Dropsuite storage, kept apart from your Google tenant |
| Sealed by | Dropsuite |
| Witnessed by | Fortify 24x7 engineers checking that accounts remain in scope |
Copies of a QuickBooks Online company taken continuously, priced per company and not per user. A bookkeeping platform with no independent copy of its ledger is one point of failure sitting beneath every figure you report.
| Deposited on | Each QuickBooks Online company, one unit per company file |
|---|---|
| Seals | Nothing; it is the ledger copy the platform never keeps on your behalf |
| Held at | Copies in Dropsuite storage, well away from the bookkeeping platform |
| Sealed by | Dropsuite |
| Witnessed by | Fortify 24x7 engineers confirming the copy is up to date |
A directory is the skeleton key for everything federated behind it, and hardly anybody copies one. Snapshots of people, groups, roles and policy turn a bad change into something you can see, understand and undo rather than something you argue about.
| Deposited on | The directory tenant itself, counted as one unit |
|---|---|
| Seals | Nothing; it makes a directory change visible and makes undoing it possible |
| Held at | Configuration snapshots in Dropsuite storage, outside the directory |
| Sealed by | Dropsuite |
| Witnessed by | Fortify 24x7 engineers reading what the change monitoring reports |
Recovery tested automatically, producing proof with a date on it that a copy returned and came up. Holding a copy nobody ever retrieved amounts to an article of faith, and this line is what separates faith from knowledge.
| Deposited on | Each protected system you want evidence for, one unit apiece |
|---|---|
| Seals | Nothing; it proves the copies you already pay for can actually be used |
| Held at | Test outcomes and dated evidence recorded within N-able Cove |
| Sealed by | N-able Cove |
| Witnessed by | Fortify 24x7 engineers going over every verification that failed |
Backup undertakes something about copies and about the journey home. Nowhere does it undertake that nothing gets lost, and for this audience a single boundary counts above every other.
Heads up: card statements show FORTIFY 24X7 - Cryptinest is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.