Skip to content
RADIUSTECHNOLOGY

What We Manage

Backup &
Recovery

Copies that ran overnight are a start. Recovery readiness means knowing what is protected, how long you keep it, who is alerted when a job fails, and whether you could restore the thing the business actually needs — including after ransomware.

Scope

What may be in scope

Not every customer needs the same design. Microsoft 365 in particular is not one architecture for every tenant.

Microsoft 365 data

Mailbox, files and related data — where the business needs a copy beyond what Microsoft retains for its own operations.

Endpoints

Where a laptop holds work that does not live safely elsewhere.

Servers and cloud workloads

The systems the business cannot work without, wherever they run.

NAS and other storage

Shared files that are still the system of record for someone.

How Radius manages it

  1. Understand

    What exists, who uses it, and what the business actually depends on.

  2. Standardise

    A known configuration, documented, rather than every machine being a special case.

  3. Protect

    Identity, devices, backup and proportionate controls built into the way it is run.

  4. Monitor

    Watch health and change, so problems are noticed before they become a queue of people.

  5. Support

    When something fails, stay with it. Coordinate suppliers. Tell the business plainly.

  6. Improve

    Remove repeated faults, plan the next refresh, and stop work that no longer earns its place.

Responsibility

How it is run

We do not guarantee that every restore will succeed. Media fails, encryption keys get lost, and scope that was never backed up cannot be invented after the fact. The work is to make recovery a designed operation, not a hope.

  1. Retention

    How long copies are kept, chosen by the business, not by a default nobody reviewed.

  2. Monitoring and alerting

    A failed job is an incident, not a curiosity in a report.

  3. Recovery objectives

    Plain language for how much data you can afford to lose, and how long you can be down — as a design input, not a contractual slogan.

  4. Testing and documentation

    Restores practised where the design allows, and written so the next person could follow them.

  5. Continuity

    Backup sits next to the rest of operations: identity, devices, cloud and the network the restore will use.

Our standard

Backup is part of the Radius Standard: copies that can be restored, including after ransomware.

The Radius Standard →

Get started

See whether recovery is actually designed.

Backup coverage, monitoring and restore thinking are part of the Technology Review.