Sealed, dated, and set well back from the bench where the spilling goes on, a keeping jar holds what must survive. Nine labels are in this drawer. Desktops. Servers. Anything running inside a hypervisor. Plus the cloud accounts a practice quietly assumes are being copied by somebody. One of the nine has no purpose beyond proving the other eight.
Keeping your tenant available is Microsoft's job, and Microsoft does it well. Holding a copy of the mailbox a leaver emptied on their final afternoon is not, and neither is rebuilding the SharePoint library somebody reorganised on a Friday. Google draws the line in exactly the same place. Availability of the service is theirs. What sits inside it is yours to look after.
No gap turns up more often at scoping than this one, and almost nobody arrived at it deliberately. It is an untested assumption, usually because the question sounds like something that must already have been settled.
Copies get lifted by that final preparation, restored to a calendar, and returned with dated proof of the run. All the difference in the world sits between assuring an auditor that backups happen and showing one halfway through coming back.
It also turns up the quiet failures. A job reporting success every night while stepping around one database. A retention figure somebody edited last year. A machine that fell out of the set during a rebuild and was never put back. All of those are ordinary and none is rare, and the only way to meet one early is to open the jar and look inside.
Billing supplies these figures directly. Add something and it stays on your script, untouched, for the rest of the page.
The cheapest jar on the shelf and the one that gets opened most. Twenty eight days of versions for the documents and folders somebody works in daily, so a file mangled at lunchtime is recoverable by the afternoon without anybody restoring a whole machine.
| Made up for | Windows machines where somebody edits documents that matter every day |
|---|---|
| Acts on | Nominated files and folders, versioned as they change |
| Shelf life | Twenty eight days of versions |
| Dispensed by | N-able Cove, held centrally by Fortify 24x7 |
| Counter-checked | Completion is reported machine by machine, failures named |
When the machine itself has gone, a whole disk copy is what you want. Drives fail, laptops get stolen, and reception computers get encrypted overnight. What comes back is the machine, and not merely the documents it carried.
| Made up for | Workstations whose rebuild would cost a clinical day to reconstruct |
|---|---|
| Acts on | The whole disk, taken as an image on a schedule |
| Shelf life | Retention set with you and drawn from pooled account storage |
| Dispensed by | N-able Cove, operated by Fortify 24x7 |
| Counter-checked | Outcomes come back machine by machine, every month |
For the physical server most practices still keep on site, usually running the practice management system or the imaging archive. It understands databases, so what gets taken is coherent rather than a mid-write snapshot that comes back as rubble.
| Made up for | On-site servers carrying practice management or imaging archives |
|---|---|
| Acts on | The whole server, with database aware quiescing where it applies |
| Shelf life | Retention agreed per guest, drawn from pooled account storage |
| Dispensed by | N-able Cove, operated by Fortify 24x7 |
| Counter-checked | Every outcome is reported, and a failed run gets chased not filed |
The same treatment for virtual machines, counted per guest rather than per host. Practices that consolidated onto a single hypervisor tend to have four or five guests doing quite different jobs, and each of them needs its own copy and its own schedule.
| Made up for | Consolidated practices running several guests on one hypervisor |
|---|---|
| Acts on | The guest, imaged and held away from the host it runs on |
| Shelf life | Retention agreed per guest, drawn from pooled account storage |
| Dispensed by | N-able Cove, operated by Fortify 24x7 |
| Counter-checked | Reporting per guest, so a quiet failure cannot hide behind a busy host |
Reachability of the tenant is Microsoft work, and Microsoft does it well. Holding a copy of the mailbox a departing biller emptied, or of the library somebody reorganised on a Friday, is not. That gap is what this preparation covers, per licensed user, over mail, files, sites and chat.
| Made up for | Any practice whose mail and documents live in Microsoft 365 |
|---|---|
| Acts on | Tenant contents copied out on a schedule: mail, files, sites, chat |
| Shelf life | Retention drawn from a terabyte of pooled storage for each user |
| Dispensed by | N-able Cove, operated by Fortify 24x7 |
| Counter-checked | Completion comes back per user, and a skipped account is named |
Identical reasoning, applied on the Google side. For every licensed user out come mail, drive, contacts, calendars and tasks. Narrow a restore to one message and no working mailbox gets buried under an old one.
| Made up for | Practices running Google Workspace, whole or alongside Microsoft |
|---|---|
| Acts on | Mail, drive, contacts, calendars and tasks per licensed user |
| Shelf life | Retention agreed at scoping, held apart from the originating tenant |
| Dispensed by | Dropsuite, operated by Fortify 24x7 |
| Counter-checked | Completion reporting arrives per user each month |
The practice ledger is a record that regulators, accountants and your own partners will eventually ask about. A bad import or a deletion inside QuickBooks Online is not something the platform will undo for you. Continuous copies, restored back with one action.
| Made up for | Practices and billing companies keeping books in QuickBooks Online |
|---|---|
| Acts on | The ledger inside the company file, copied continuously |
| Shelf life | History accumulates continuously while the line is paid |
| Dispensed by | Dropsuite, operated by Fortify 24x7 |
| Counter-checked | Copy state is visible per company file rather than assumed |
The directory is the part nobody copies until the day a policy is deleted and forty people cannot sign in. This line keeps the configuration: groups, roles, conditional access, application assignments, with change monitoring that tells you what moved.
| Made up for | Any tenant where a deleted policy would stop the practice working |
|---|---|
| Acts on | Directory configuration: groups, roles, policy, assignments |
| Shelf life | Configuration history is kept without a retention ceiling |
| Dispensed by | Dropsuite, operated by Fortify 24x7 |
| Counter-checked | Change monitoring names what moved and the hour it moved |
Until somebody restores it, a backup is only a theory about a backup. What this preparation does is take your copies, restore them on a calendar, and return dated proof of each run. That is the whole gap between assuring an auditor backups happen and putting one in front of them mid-recovery.
| Made up for | The copies you would be most embarrassed to find broken |
|---|---|
| Acts on | The backup itself, restored on a schedule and then verified |
| Shelf life | Verification records file with each system they prove |
| Dispensed by | N-able Cove, with the schedule set and read by Fortify 24x7 |
| Counter-checked | This line is itself the counter-check: dated proof, per system |
Copies are only worth what a restore proves. Everything here is bounded by the scope you agree with us and the retention you pay for.
Heads up: card statements show FORTIFY 24X7 - MediSafe Networks is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.