A Fortify 24x7 brand. Security operated for the plant, the depot, and the offices behind both.Sign inRaise a job
Industry LockNetworks
Bay 06 / Backup and continuity

Until it has been restored, a copy is only a belief.

Backup is where confidence and evidence part company. Almost every business believes it has copies. Rather fewer can say when one was last restored, who watched, and how long the whole of it took. This bay covers the machines, the servers, the cloud accounts nobody remembers, and the verification that turns a belief into a record.

N-able CoveDropsuiteScheduled verification
Every tag in this bay carries its own counting unit
Tags in this bay9
Plant on the lineN-able Cove, Dropsuite
One unit equalsMachine, user, file, or whole tenant
Copies keptWell clear of what they protect

The machines, and the one server in the plant office

N-able Cove covers workstations at file level and at whole-disk level, servers on bare metal, and hypervisor guests. In an industrial business the awkward one is nearly always the same: a physical server running a license dongle and an application older than most of the people using it, which nobody has patched because nobody dares.

That machine gets a whole-server copy, and the copy can come back onto different hardware or onto a virtual machine. Which is the point, because the original hardware is exactly what is going to fail.

The cloud accounts almost nobody copies

The service itself is kept running by Microsoft and by Google. Keeping a copy of the contents is your responsibility, and the distinction usually gets discovered on the morning somebody empties a mailbox that mattered or closes a leaver's account before anybody checked it.

The Microsoft tenant is N-able Cove work. Google Workspace goes to Dropsuite, and so does the Entra ID configuration everything else trusts, and so does the QuickBooks Online company file. The verification line then runs the recovery to a rota and hands over a dated record, the artifact an auditor or an insurer asks to see.

The day you need the copy is never the day to find out how long it takes.
Tags in this bay

Specifications and rates

Every rate on this page comes live off the billing service. Anything locked on stays on the worklist while you read on.

Hasp open, tags below
Fortify-CDP-FFDanger tag

Working File History

Plant · N-able Cove, versioning the documents somebody has open

Continuous versions of whatever is in active use on a Windows workstation, aimed at the far commoner disaster: somebody overwrote the good copy on Thursday and it went unnoticed until Monday.

  • Frequent versions of working documents rather than one nightly snapshot.
  • Restores handled per file, without pulling an entire machine back.
  • Copies held away from the workstation they were taken from.
Mounted onN-able Cove, on the Windows workstation you enroll
IsolatesThe overwrite itself. A prior version stays reachable
Retained forVersions to whatever retention was fixed at scoping
Released byAnyone with portal access, or a Fortify 24x7 engineer on request
Signed off byThe engineer who ran the restore, in the job record
Readingper Windows workstation
settled one month aheadQTY
Fortify-CDP-WKSTNDanger tag

Workstation Image Backup

Plant · N-able Cove, taking the whole workstation

The entire machine and not a folder off it. When a drive fails or a laptop goes missing between two sites, the replacement gets built back to whatever the last good copy holds.

  • Whole-disk copies of Windows and macOS workstations.
  • Recovery onto the original hardware, onto different hardware, or onto a virtual machine.
  • Copies sit off the machine, so a machine going missing takes nothing with it.
Mounted onN-able Cove, on the Windows or macOS workstation you enroll
IsolatesThe dead drive. The machine is rebuildable without it
Retained forCopies to whatever retention was fixed at scoping
Released byAnyone with portal access, or a Fortify 24x7 engineer on request
Signed off byThe engineer who ran the restore, in the job record
Readingper workstation
settled one month aheadQTY
Fortify-CDP-SRVRDanger tag

Physical Server Backup

Plant · N-able Cove, on bare metal

Bare metal copies for the servers still standing in a rack on your own site, which in an industrial business is usually the file server, the licence server, and the box the line-of-business application refuses to leave.

  • Whole-server copies including the operating system and application state.
  • Recovery back to the original hardware or forward onto a virtual machine.
  • Sized against the volumes you genuinely hold, not a figure guessed at scoping.
Mounted onN-able Cove, on the physical server you enroll
IsolatesThe failed server. Its state survives the hardware it ran on
Retained forCopies to whatever retention was fixed at scoping
Released byA Fortify 24x7 engineer, working alongside your own team
Signed off byThe engineer who ran the recovery, in the job record
Readingper physical server
settled one month aheadQTY
Fortify-CDP-VMDanger tag

Virtual Server Image Backup

Plant · N-able Cove, on hypervisor guests

Guest-level copies of virtual servers. Counting happens per guest, so the invoice agrees with the inventory your own team keeps instead of a host count somebody has to translate.

  • Copies taken at guest level across the common hypervisors.
  • Restore a whole guest, or reach into one and pull a single file out.
  • Priced by the virtual server, the count your own team already keeps.
Mounted onN-able Cove, on each virtual server guest you enroll
IsolatesThe lost guest, and the single file lost inside a healthy one
Retained forCopies to whatever retention was fixed at scoping
Released byA Fortify 24x7 engineer, working alongside your own team
Signed off byThe engineer who ran the recovery, in the job record
Readingper virtual server
settled one month aheadQTY
Fortify-CDP-ContinuityDanger tag

Restore Verification

Plant · N-able Cove, proving the copy rather than assuming it

Until somebody has restored it, a copy is only a belief. This line runs the recovery to a rota and hands over the evidence, which is what a customer audit or an insurer asks to see.

  • Scheduled recovery of the protected system, run and checked.
  • A dated record that goes straight to an auditor with no preparation needed.
  • A failed verification raises a job with us before you find it the hard way.
Mounted onN-able Cove, run against a system some copy line already holds
IsolatesThe assumption. Recovery becomes something you can point at
Retained forVerification records, kept while the subscription is live
Released byNot applicable. Verification runs and reports, it holds nothing
Signed off byThe Fortify 24x7 engineer who reviewed the run, on the record
Readingper protected system
settled one month aheadQTY
Fortify-CDP-M365Danger tag

Microsoft 365 Protection

Plant · N-able Cove, taking the Microsoft tenant

Microsoft runs the tenant and keeps it up. A copy of the contents is down to you, and most companies find that out on the morning somebody empties a mailbox that mattered.

  • Mail, calendar, contacts, OneDrive, and SharePoint content.
  • Restore in place, or export out, per item or per site.
  • Independent of the tenant, so a bad day in the tenant does not take it.
Mounted onN-able Cove, connected to the Microsoft 365 tenant
IsolatesThe deletion, whether it was a mistake or entirely deliberate
Retained forCopies to whatever retention was fixed at scoping
Released byAnyone with portal access, or a Fortify 24x7 engineer on request
Signed off byThe engineer who ran the restore, in the job record
Readingper licensed user
settled one month aheadQTY
Fortify-CDP-GWSDanger tag

Google Workspace Protection

Plant · Dropsuite, copying the Workspace tenant

On the Google side the argument does not change. Contacts, Calendar, Drive, and Gmail lifted clear of the tenant, so an account shut in a hurry does not take the contents down with it.

  • Contacts, Calendar, Drive, and Gmail, all four kept clear of the tenant itself.
  • Search across the copy, then restore or export what you found.
  • Covers the leaver whose account was closed before anyone checked it.
Mounted onDropsuite, connected to the Google Workspace tenant
IsolatesThe closed account, and everything that was inside it
Retained forCopies to whatever retention was fixed at scoping
Released byAnyone with portal access, or a Fortify 24x7 engineer on request
Signed off byThe engineer who ran the restore, in the job record
Readingper licensed user
settled one month aheadQTY
Fortify-CDP-QBODanger tag

QuickBooks Online Protection

Plant · Dropsuite, copying the books

A copy of the accounting record itself. A miskeyed batch, a bad import, or a well-meaning cleanup can put the ledger somewhere you cannot argue it back from without one.

  • A scheduled copy of the company file inside QuickBooks Online.
  • Restore the whole file, or pull specific records back into it.
  • Priced by the company file, the way an accounting team already counts.
Mounted onDropsuite, connected to the QuickBooks Online company file
IsolatesThe bad import, and the cleanup that went further than intended
Retained forCopies to whatever retention was fixed at scoping
Released byYour finance team, or a Fortify 24x7 engineer on request
Signed off byThe engineer who ran the restore, in the job record
Readingper company file
settled one month aheadQTY
Fortify-CDP-EntraDanger tag

Entra ID Configuration Backup

Plant · Dropsuite, copying the directory configuration

Directory configuration is the thing everything else trusts, and it is almost never backed up. Groups, roles, policies, and app registrations, copied so that a bad change can be read back and undone rather than rebuilt from memory.

  • Users, groups, role assignments, policies, and the app registrations.
  • A record you can read of how the directory stood before a change.
  • Priced by the tenant, since a directory does not come in any smaller unit.
Mounted onDropsuite, connected to the Entra ID tenant
IsolatesThe change nobody documented, and the rollback nobody could plan
Retained forConfiguration copies to whatever retention was fixed at scoping
Released byA Fortify 24x7 engineer, working with your own directory owner
Signed off byThe directory owner, on the change record
Readingper tenant
settled one month aheadQTY
Honest scope

Where this bay stops

Nine lines, and a clear edge around all of them. What follows is what backup does not cover.

  • It does not back up plant control systems. PLC programs, HMI projects, robot configurations, and historian databases fall outside every line in this bay. Those need a plan of their own, usually from whoever commissioned the equipment.
  • Recovery time depends on what you hold. A first copy reads the whole scope once and is heavy. A restore finishes when the volume of data and the link between here and there let it. Sizing gets done with you honestly, and no number gets quoted that flatters us.
  • Retention is a decision you make. How far back a copy reaches is set when the line is scoped, and it drives cost. There is no infinite history hiding behind a monthly rate.
  • A copy is not an archive. Backup exists to get you back to working. Keeping records for a statutory period, under legal hold, or in a shape an auditor will accept as immutable is a separate design conversation.
  • Verification proves the run, not the outcome. The verification line proves the copy restores. Whether the restored system then does everything your business needs is a question your own people have to answer, and we will happily sit in on that test.
Money side

Heads up: card statements show FORTIFY 24X7 - Industry Lock Networks is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.

Bay 01Detection and responseBay 02Execution controlBay 03Mailbox defenseBay 04Device fleetBay 05Data protectionBay 06Backup and continuity
All 24 lines The six baysClient portal Open the board