The written response plan a financial practice has to keep is required to deal with recovery, and recovery is the clause most often drafted out of optimism. These nine entries cover the workstations, the servers, the cloud tenants, and the accounting ledger, and one of them exists solely to prove on a calendar that the copies open.
Microsoft 365 and Google Workspace are extremely good at keeping their own service available. Neither one is a copy of your material. Retention windows close, a deleted mailbox disappears permanently on a published timetable, and an account emptying itself on the way out is not a hardware fault anybody has undertaken to reverse for you.
None of that is a criticism of either company. It is a split of responsibility both of them publish openly and hardly anybody reads. Keeping copies away from the platform itself is how the second half of that split ends up covered.
Everything on this register can be bought without the proving entry, and every backup product ever sold has been bought that way at least once. The outcome is the practice that discovers, in the middle of a real event, that the job had been failing since February and reporting success anyway.
The proving entry opens the copies against a calendar, confirms they mount and read, and writes the outcome down. That written outcome is the whole difference between telling an examiner your practice takes copies and demonstrating that the copies work.
Not every machine needs a whole image. A workstation whose documents all live in the tenant generally needs the tenant covered and the file history entry, not an image of the disk. A server carrying an application nobody could rebuild from memory does need the image.
Describe what your office would genuinely have to reconstruct and we will tell you which entries to leave out. Talking a practice down two lines is a better trade for us than selling a restore that was never going to run.
Rates below are read live from the billing service. Anything you record sits on your order sheet while you carry on reading the rest of the register.
Frequent versions of the documents somebody has open right now, for the occasion when a file gets overwritten, mangled, or encrypted somewhere between two full runs.
| Supplied by | N-able Cove, licensed through us |
|---|---|
| Machines it reaches | Windows workstations |
| How often | Repeatedly across the working day |
| What comes back | Single documents and their earlier versions |
| Charged against | Each Windows workstation, every month |
A complete copy of the workstation, so that a dead disk or an encrypted machine turns into a rebuild measured in hours rather than a week spent reinstalling everything from scratch.
| Supplied by | N-able Cove, licensed through us |
|---|---|
| Machines it reaches | Windows and macOS workstations |
| What it takes | The whole disk, build and programs included |
| What comes back | Same hardware, different hardware, or one file |
| Kept unreadable | While moving and while stored |
| Charged against | Each workstation, every month |
Image copies of physical servers, the file server included, the directory controller included, and whichever application has refused to move anywhere for six years.
| Supplied by | N-able Cove, licensed through us |
|---|---|
| Machines it reaches | Physical Windows and Linux servers |
| What it takes | The whole server, application aware where supported |
| What comes back | Bare metal, a volume, or one file |
| Kept unreadable | While moving and while stored |
| Charged against | Each physical server, every month |
The identical coverage for virtual machines, billed per guest so the invoice reflects what your practice runs rather than how large the host underneath happens to be.
| Supplied by | N-able Cove, licensed through us |
|---|---|
| Machines it reaches | Virtual machines on supported hypervisors |
| What it takes | The guest image, application aware where supported |
| What comes back | A whole guest, a volume, or one file |
| Kept unreadable | While moving and while stored |
| Charged against | Each virtual server, every month |
Copies of Exchange Online material, of OneDrive, of SharePoint, and of Teams, held away from the tenant so that a deletion or a taken over account remains something you can come back from.
| Supplied by | N-able Cove, licensed through us |
|---|---|
| What it covers | Teams, SharePoint, OneDrive, and Exchange Online |
| Where copies live | Away from the Microsoft tenant itself |
| What comes back | The original location, or an export |
| Charged against | Each licensed person, every month |
The identical coverage for a practice on Google. Gmail, whatever sits in Drive, plus Calendar and Contacts, copied and held away from the tenant producing them.
| Supplied by | Dropsuite, licensed through us |
|---|---|
| What it covers | Gmail, Drive, plus Calendar and Contacts |
| Where copies live | Away from the Google tenant itself |
| What comes back | The original account, or an export |
| Charged against | Each licensed person, every month |
Copies of the accounting ledger, which for a small financial practice is the one record that would be hardest of all to reconstruct once somebody has made a mess of it.
| Supplied by | Dropsuite, licensed through us |
|---|---|
| What it covers | QuickBooks Online company material |
| How often | On a calendar, not by manual export |
| What comes back | Earlier states of the ledger |
| Charged against | Each company file, every month |
A copy of directory configuration: accounts, groups, roles, and the policy deciding who reaches what. Rebuilding that from memory after a bad change is considerably worse than it sounds on paper.
| Supplied by | Dropsuite, licensed through us |
|---|---|
| What it covers | Entra ID accounts, groups, roles, and policy |
| Why hold it | Coming back from lost configuration or a bad change |
| What comes back | Point in time captures, with a history of changes |
| Charged against | Each tenant, every month |
The entry converting a copy into evidence. Copies get restored against a calendar, checked that they mount and read, and written up so the outcome is something your practice can hand across.
| Supplied by | N-able Cove, exercised by our own engineers |
|---|---|
| How it works | A restore is performed and its contents are checked |
| What comes out | One written outcome for each system checked |
| If it fails | Raised as a case and worked by an engineer |
| Charged against | Each protected system, every month |
Two columns, both of them written to be relied on. The right hand column is the one worth reading twice, because a firm that misreads it will believe an obligation is covered when it is still open.
Heads up: card statements show FORTIFY 24X7 - Equity IT Solutions is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.
Equity IT Solutions raises no separate charge of its own, so a second line will never turn up beside that one.