A Fortify 24x7 brand. Pilotage across the security stack, and your own people stay on the helm.Chart roomSpeak to a duty engineer
Independence IT Group
Chart 08 / Backup and anchorage

Every backup is flawless until somebody asks for a restore.

Nine lines here, with a single idea threaded through all of them. A copy nobody has read back is an assumption in the shape of a control. This station keeps copies riding well away from whatever they protect: on the machines, on the servers, and inside the cloud accounts that most companies quietly assume are somebody else's problem.

N-able CoveDropsuiteRestores rehearsed
9 lines drawn here / every rate live from billing
Lines on this chart9
PlatformsN-able Cove + Dropsuite
Billed onSystem, user, or tenant
RestoresRehearsed on a schedule

The accounts everybody assumes are covered

Both Microsoft and Google run genuinely resilient platforms, and resilience is not a backup. A retention window closes. A mailbox deleted long enough ago stops being recoverable. An account in hostile hands can destroy an enormous amount before anybody raises an eyebrow. None of that counts as the platform failing, and all of it is the reason a separate copy exists. It is also the gap we find open most often in companies of this size.

Directory configuration and the accounting ledger tell the same story. A badly reconfigured Entra tenant is not repaired by opening a support case, and a set of books does not matter less than a file server merely because it happens to live in somebody else's software.

A copy nobody has read back is an assumption in the shape of a control.

Rehearsing beats assuming

A green backup job describes a job. The continuity code takes scheduled restores, reads the data back, and evidences that it returned intact, which converts recovery from something everybody assumes into a dated document. An assessor asks for that document early, so none of the effort is wasted during years when nothing at all goes wrong.

Sizing is where expectations go astray. The first copy reads the entire scope once and every copy after it carries only differences, which makes week one considerably heavier than the weeks that follow. Schedules end up sized to the volume genuinely present, never to a number offered during a scoping call.

Codes drawn on this chart

Line sheets and rates

Figures underneath arrive directly out of billing. Whatever gets logged waits in the logbook while you keep reading.

Fortify-CDP-FFLine sheet

Working File History

N-able Cove, keeping file and folder history on Windows

Frequent copies of live working files on a Windows machine, reaching back far enough that a ruined afternoon can be undone without rebuilding anything.

  • Copies at file and folder level, holding recent versions ready to retrieve.
  • Managed centrally, so recovery never depends on whoever sits at that desk.
  • Light enough that nobody using the laptop notices it is happening.
Piloted onN-able Cove file and folder protection
SoundsChanges to live working files on the covered machine
Logged forRecent versions, retrievable with no whole machine rebuild
Handed toFortify 24x7 engineers, once your team asks
Charted byWindows workstation, monthly
Soundingper Windows workstation
taken each month, always up front
QTY
Fortify-CDP-WKSTNLine sheet

Workstation Image Backup

N-able Cove, taking the entire machine

An image of the whole workstation, turning a dead disk or a laptop left in a taxi into a rebuild from a known image instead of a reconstruction from memory.

  • Spans Windows, macOS, and Linux workstations alike.
  • Brings the whole machine back, not merely the documents somebody filed correctly.
  • Storage is pooled, so a single heavy machine needs no special arrangement.
Piloted onN-able Cove workstation protection
SoundsThe entire covered workstation, well beyond its documents
Logged forCopy history, with recovery points held to the agreed schedule
Handed toFortify 24x7 engineers, once your team asks
Charted byWorkstation, monthly
Soundingper workstation
taken each month, always up front
QTY
Fortify-CDP-SRVRLine sheet

Physical Server Backup

N-able Cove on bare metal, aware of the databases

Entire server copies that understand the databases running on them, sized for the machines whose absence stops a department working before lunch.

  • Windows and Linux servers, with awareness of applications and databases.
  • Pooled storage, sized against the volume genuinely in front of us.
  • Restores driven by our engineers, not handed to whoever happens to be free.
Piloted onN-able Cove server protection
SoundsThe entire server, databases running on it included
Logged forCopy history and recovery points on the agreed schedule
Handed toFortify 24x7 engineers, who drive the restore
Charted byPhysical server, monthly
Soundingper physical server
taken each month, always up front
QTY
Fortify-CDP-VMLine sheet

Virtual Server Image Backup

N-able Cove, protecting hypervisor guests

The identical protection for virtual servers, billed by guest so the quantity lines up with the inventory your platform team already maintains.

  • Copies taken at guest level for Windows and Linux virtual machines.
  • Aware of databases, so what returns is internally consistent.
  • Billed by guest, which is a figure you are already tracking anyway.
Piloted onN-able Cove virtual server protection
SoundsThe entire guest, databases inside it included
Logged forCopy history and recovery points on the agreed schedule
Handed toFortify 24x7 engineers, who drive the restore
Charted byVirtual server, monthly
Soundingper virtual server
taken each month, always up front
QTY
Fortify-CDP-M365Line sheet

Microsoft 365 Protection

N-able Cove, copying the Microsoft tenant

An independent copy of Exchange, SharePoint, OneDrive, and Teams, kept somewhere other than whichever tenant it is protecting.

  • Spans mail, sites, drives, and Teams material for each licensed person.
  • Recovery down to one mailbox or one site, without touching anything else.
  • Held somewhere other than the tenant, which is the entire reason to buy it.
Piloted onN-able Cove for Microsoft 365
SoundsExchange, SharePoint, OneDrive, and Teams, per licensed person
Logged forCopy history, with fine grained recovery points per service
Handed toFortify 24x7 engineers, once your team asks
Charted byLicensed user, monthly
Soundingper licensed user
taken each month, always up front
QTY
Fortify-CDP-GWSLine sheet

Google Workspace Protection

Dropsuite, copying the Workspace tenant

The identical independent copy on the Google side, spanning mail, drives, contacts, calendars, and the task lists.

  • Mail, drives, contacts, calendars, plus tasks belonging to the licensed person.
  • Recovery reaching down to one item where one item is the requirement.
  • Held somewhere other than the tenant it protects.
Piloted onDropsuite for Google Workspace
SoundsMail, drives, contacts, calendars, plus tasks held by the licensed person
Logged forCopy history, with recovery reaching down to one item
Handed toFortify 24x7 engineers, once your team asks
Charted byLicensed user, monthly
Soundingper licensed user
taken each month, always up front
QTY
Fortify-CDP-QBOLine sheet

QuickBooks Online Protection

Dropsuite, copying the ledger

Continuous copies of a QuickBooks Online company, on the principle that a set of books does not matter less for living inside somebody else's software.

  • Copies taken continuously rather than once overnight and hoped for.
  • The company can be put back into the platform in a single action.
  • Billed by company, which is exactly how your finance team counts them.
Piloted onDropsuite for QuickBooks Online
SoundsChanges to the company as your finance team enters them
Logged forContinuous history, replaceable straight back into the platform
Handed toFortify 24x7 engineers, once your finance team asks
Charted byCompany file, monthly
Soundingper company file
taken each month, always up front
QTY
Fortify-CDP-EntraLine sheet

Entra ID Configuration Backup

Dropsuite, copying directory configuration

Copies of Entra ID configuration with change monitoring attached, for the afternoon somebody reworks the directory and nobody present can describe how it looked beforehand.

  • Configuration copied, with retention that does not run out.
  • Changes are surfaced as they happen instead of found weeks afterward.
  • Puts configuration back, which is not something a support case achieves.
Piloted onDropsuite for Entra ID
SoundsDirectory configuration and every change made against it
Logged forRetention on configuration state that does not run out
Handed toFortify 24x7 engineers, working with your directory administrators
Charted byTenant, monthly
Soundingper tenant
taken each month, always up front
QTY
Fortify-CDP-ContinuityLine sheet

Restore Verification

Restores run on a schedule, proved, and written down

Automated recovery testing that reads a copy back and evidences that it returned intact, converting recovery from an assumption into a document with a date on the front.

  • Recovery runs to a schedule over whichever systems you nominate.
  • Evidence that recovery succeeded, dated and held for your assessor.
  • Anything broken surfaces here rather than in the middle of an incident.
Piloted onN-able Cove recovery testing
SoundsWhether a copy returns intact, tested on a schedule
Logged forDated evidence behind every successful recovery
Handed toFortify 24x7 engineers, who chase down what failed
Charted byProtected system, monthly
Soundingper protected system
taken each month, always up front
QTY
Honest scope

Where this chart runs out of water

Backup is the station people most want to consider finished the day it is purchased. These are the parts it does not carry for you.

  • Copies alone are no continuity plan. Taking copies and rehearsing restores is the mechanical half. Ranking which systems return first, and deciding what the business does while it waits, is a plan that has to belong to your team.
  • Recovery consumes real hours. Moving a large volume back takes as long as the link between the two ends allows. You will get the unflattering figure at scoping instead of an encouraging one.
  • Nothing after the last copy is in the copy. Work created between the final successful run and the failure is simply gone. How often copies run is a cost decision, and we will put the trade in front of you rather than settle it quietly.
  • Unlicensed systems are unprotected systems. Servers, tenants, and companies outside the quantity you bought are not covered, no matter how obviously important they look once something has gone wrong.
  • Clean copies do not cancel the incident. Having them shortens the outage a great deal. They do not undo the intrusion, they do not answer your notification obligations, and they do not give your people back the week they will spend on it.
NOTE 01

Heads up: card statements show FORTIFY 24X7 - Independence IT Group is a Fortify 24x7 brand, and your subscription is billed by Fortify 24x7.