Nine lines, because there are nine genuinely different things to copy and a single price for all of them would be a lie in both directions. Desks, cupboard servers, hypervisor guests, the two large cloud tenants, the directory wiring, the books, and a ninth line that exists to prove the eight before it.
A desk, a cupboard server, a guest on a hypervisor, one Microsoft tenant, one Google tenant, the directory wiring and a set of books are seven different objects and none of them gets copied the same way. Bundle them at one price and you either overcharge the shop with four laptops or undercharge the practice with two servers and a hundred mailboxes.
Desks, servers, guests and the Microsoft tenant all go to N-able Cove. Google Workspace, the Entra directory wiring and the QuickBooks Online company file all go to Dropsuite. Buy whichever lines match what your firm genuinely runs and leave the others where they are.
This one costs small firms real money every year. Microsoft and Google will keep the tenant running; neither of them holds on to what your office manager deleted, and the grace period before it goes for good is markedly shorter than people picture. A leaver in a temper, a botched sync, or a mailbox somebody cleared out are all ordinary Tuesday events with no ordinary remedy.
The final line exists because a copy is worth nothing until somebody has put one back. Verification runs to a rota, checks that what came back is readable, and writes down that it was, with a date beside it. That dated line is what an insurer asks for, and it is the only truthful answer to the question of whether any of this works.
Billing supplies each figure below as the page draws. Add a line and it sits on the board while you read further down.
Earlier versions of whatever is open on somebody's screen right now, taken over and over across the working day. More requests arrive about this than about anything else here: it was fine before lunch and it is wrong now.
| Position | Recovery console, drafts row |
|---|---|
| Watches for | Runs that failed, runs that finished short, and runs that quietly stopped happening |
| Log kept | Run results and draft counts per desk, reviewed at the console |
| Escalation path | A second failure in a row raises a callout before you have noticed anything |
| Sign-off | Closed when a clean run finishes and the record carries the timestamp |
The entire machine copied, so a failed disk becomes a delay instead of a fortnight. For most small firms the cost of building a desk back from nothing has always been the lost hours rather than the replacement hardware.
| Position | Recovery console, workstation row |
|---|---|
| Watches for | Failed runs, data growing faster than the rota allows, desks that stopped copying |
| Log kept | Run history and copy size per desk, held at the console |
| Escalation path | Two failures in a row raise a callout with nobody having to ask for one |
| Sign-off | An engineer closes it after a clean run and notes it in the handover |
That box under the stairs running your bookings, your dispensary or the shared drive gets copied whole, and gets a route home that somebody has walked end to end rather than sketched on a whiteboard.
| Position | Recovery console, server row |
|---|---|
| Watches for | Failed or short runs, and any growth the rota can no longer carry |
| Log kept | Run history, copy size and the results of test restores, per server |
| Escalation path | A failed server run raises a callout at the console the same day |
| Sign-off | Closed once a clean run finishes and the size is back where it should be |
Guests on your hypervisor copied one at a time, so nobody need argue about hypervisor host licensing. Bring one back where it was, or somewhere else altogether.
| Position | Recovery console, guest row |
|---|---|
| Watches for | Guests missing from the rota, failed runs, and snapshots left lying about |
| Log kept | Run history per guest, naming the host it was sitting on at the time |
| Escalation path | A guest dropping out of the rota raises its own callout |
| Sign-off | Closed once the guest is back on the rota and running clean |
Microsoft will keep your tenant up. Microsoft will not hold on to the thing your office manager deleted in March, and the grace period is a good deal shorter than most people picture. This line holds on to it.
| Position | Recovery console, Microsoft row |
|---|---|
| Watches for | Failed collections, people added without cover, licences pulled part way through |
| Log kept | Collection history per person, listing what was taken on each pass |
| Escalation path | Anyone left uncovered for a whole cycle is raised for you to look at |
| Sign-off | Closed once that person is being collected and the record confirms it |
The identical argument, one tenant across. Once the bin empties it is gone, and somebody leaving on bad terms takes a startling amount with them unless a copy is already sitting somewhere else.
| Position | Recovery console, Google row |
|---|---|
| Watches for | Failed collections, people added without cover, accounts suspended part way through |
| Log kept | Collection history per person, listing which services were taken on each pass |
| Escalation path | Anyone left uncovered for a whole cycle is raised for you to look at |
| Sign-off | Closed once that person is being collected and the record confirms it |
Your accounts sit in somebody else's cloud. A bad import, or an account somebody deleted, can burn a week of a person's life to unpick by hand. Keeping your own copy of that company file shrinks the week to an afternoon and a cup of tea.
| Position | Recovery console, ledger row |
|---|---|
| Watches for | Failed collections, and any stretch where the company file went uncopied |
| Log kept | Collection history per company file, dated at each good copy |
| Escalation path | A missed collection raises a callout to whoever you named for the accounts |
| Sign-off | Closed once a clean copy of the file exists and is recorded |
Not the mail, the wiring. People, groups, roles, and the rules deciding who may open what. The afternoon somebody edits that badly, having yesterday's version written down is the entire difference between an hour and a week.
| Position | Recovery console, directory row |
|---|---|
| Watches for | What moved between one copy and the next, plus any collection that did not run |
| Log kept | Dated copies of directory objects and settings, held per tenant |
| Escalation path | A failed collection raises a callout; a large unexplained change is flagged for you |
| Sign-off | Closed once a clean copy exists and has been held against the previous one |
An untested copy is a rumour with a filename. The restore actually gets performed, to a rota. What came back gets checked for readability. The result gets written down with a date beside it, and that dated line is the only honest answer available.
| Position | Recovery console, verification rota |
|---|---|
| Watches for | Restores that fail, restores that come back unreadable, and tests that never ran |
| Log kept | A dated pass or fail per system, held for as long as you subscribe |
| Escalation path | A failed verification raises a callout on the day it happens |
| Sign-off | Closed only after a later restore has come back clean and been recorded |
Backup is the control everybody says they already have. What these nine lines will actually do is set out below.
Heads up: card statements show FORTIFY 24X7 - SecureOps Solutions is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.