Backup is the one control here whose worth is decided entirely on the worst day. Everything else can be partly right and still help. A copy either comes back complete or it does not. Nine posts across machines, servers, and whichever cloud accounts most offices assume somebody else already copies.
Microsoft keeps the service up. Google keeps the service up. Read either agreement and that is exactly what it undertakes, which is a wholly different thing from keeping your records. Deletions replicate. So does a mailbox emptied by somebody holding a stolen password, and so does the account of a leaver that got closed on the last day.
The retention window inside a tenant is a courtesy measured in days or weeks, and it is not what you want to be reading about for the first time in the middle of the emergency. The tenant posts here exist for that reason, and it is the gap we turn up more often than any other on a first call.
What we design against is not an absent copy. It is a copy that has reported green for three years and cannot be restored, because nobody ever tried, and the one time it matters is the one time everybody finds out together.
So a restore runs on a schedule, and what came back gets written down. That is what the verification post buys: not a louder promise, but evidence that the copy came back, on a date you can point at.
Each rate below comes from billing the moment the page opens. Anything under this district drops into your roster while you read on.
Frequent copies of the documents somebody is actually editing, so an overwrite late in the day does not cost the whole day.
| Runs on | N-able Cove |
|---|---|
| Hardware | Windows workstations |
| Reaches | Working documents and their version history |
| How often | Continuous through the working day |
| Caveat | This is file history and not a whole machine image |
| Billed per | Windows workstation, each month |
A copy of the entire machine, so a dead drive turns into a replacement machine instead of a week spent rebuilding.
| Runs on | N-able Cove |
|---|---|
| Hardware | Windows and macOS workstations |
| Reaches | The whole machine, restorable in full or by file |
| Kept where | Away from the machine the copy came from |
| Getting it back | The full image, or individual files taken from it |
| Billed per | Workstation, each month |
The same protection aimed at the hardware your whole office stops working without.
| Runs on | N-able Cove |
|---|---|
| Hardware | Physical servers running Windows or Linux |
| Reaches | The whole server, restorable in full or by file |
| Workloads | Aware handling for the common server workloads |
| Getting it back | Onto the same box, or onto a replacement |
| Billed per | Physical server, each month |
Guests copied as guests and billed by the guest, so the figure matches whatever the hypervisor console already shows.
| Runs on | N-able Cove |
|---|---|
| Hardware | Guests on Hyper-V or on VMware |
| Reaches | The whole guest, restorable in full or by file |
| Tally | Per guest, matching the hypervisor console |
| Getting it back | Back onto its own host, or onto another |
| Billed per | Virtual server, each month |
Mail, files, sites, and chat copied out of Microsoft 365 and held somewhere a deletion inside the tenant cannot reach.
| Runs on | N-able Cove |
|---|---|
| Reaches | Exchange, OneDrive, SharePoint and Teams |
| Kept where | Outside the tenant the copy was taken from |
| Getting it back | A single item, a whole mailbox, or an account |
| Reason | Tenant retention is short and deletions replicate |
| Billed per | Licensed person, each month |
The same gap, on the Google side. Mail, Drive, calendars and contacts copied out and held apart.
| Runs on | Dropsuite |
|---|---|
| Reaches | Gmail, Drive, Calendar and Contacts |
| Kept where | Outside Workspace, on retention you choose |
| Getting it back | By item or by account, closed accounts included |
| Reason | Workspace retention is short and deletions replicate |
| Billed per | Licensed person, each month |
The ledger copied on its own schedule, because an import gone wrong, or a range somebody deleted, should not be discovered by an accountant in April.
| Runs on | Dropsuite |
|---|---|
| Reaches | The QuickBooks Online ledger and its records |
| Kept where | Outside QuickBooks Online, on its own schedule |
| Getting it back | Records removed or overwritten, put back into the books |
| Fits | Anyone whose year end depends on the ledger being right |
| Billed per | Company file, each month |
Users, groups, role assignments, and the policy that settles who may sign in and from where. Rebuilding all of that by hand after one bad change is days of work.
| Runs on | Dropsuite |
|---|---|
| Reaches | Users, groups, roles, and directory policy |
| Kept where | Outside the directory it describes |
| Getting it back | Configuration state, not mail and not documents |
| Fits | Any tenant where one bad change stops everybody signing in |
| Billed per | Tenant, each month |
Somebody restores the copy on a schedule and records what came back. This is the post that turns a green report into something you have watched work.
| Runs on | N-able Cove |
|---|---|
| The job | Runs restores and records exactly what came back |
| How often | On a schedule agreed while scoping |
| You receive | A dated record for each system verified |
| Reason | An untested copy is only a rumor |
| Billed per | Protected system, each month |
Copies are the last control standing on the worst day, and even they have an edge. Here it is.
Heads up: card statements show FORTIFY 24X7 - Red White and Blue Networks is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.