Compute, storage and continuity

Backup success is not recovery

A completed backup job proves a process ran. Only a restore proves the data comes back. We design the backup, monitor it, test the restore and keep the evidence.

Backup storage media and cabling

What gets protected, and how well

Backup scope is a business decision wearing technical clothing. Which systems must come back within an hour, and which can wait a day? How much data can the organization afford to lose? Those answers determine the design and the cost, and they should be made deliberately rather than inherited from whatever was configured years ago.

What a backup design typically covers

  • Servers and virtual machines
  • Business files and shared folders
  • Databases
  • Microsoft 365 data, where separately configured
  • Laboratory and scientific data
  • Application configurations
  • Firewall and network device configurations
Ransomware resilience

Making backups survive an attack

Immutability

Backup copies that cannot be altered or deleted for a defined period, where the platform and storage support it.

Isolated credentials

Backup administration separated from domain administration, so one compromised account does not reach both.

Restricted administration

Fewer people able to change retention or delete backup sets, with changes logged.

Offline or separate copies

A copy that is not continuously reachable from the production network.

Disaster recovery planning

  1. Business impact

    What an outage of each system actually costs.

  2. Classify

    System criticality agreed with you.

  3. Set RTO and RPO

    Recovery time and recovery point objectives defined together — and only committed to after assessing systems, dependencies, budget and the recovery environment.

  4. Build runbooks

    Recovery procedures someone can follow under pressure, plus infrastructure configuration backups.

  5. Exercise

    Restore and recovery tests, with post-test reports and improvement actions.

Common questions

Can you make us ransomware-proof?

No. We can make backups materially more resilient through immutability, isolated credentials, restricted administration and separate infrastructure. No backup arrangement should be described as completely ransomware-proof, and we will not describe ours that way.

How often should we test restores?

On an agreed schedule, and after any material change to the environment. The test is only half of it; the retained evidence of the test is what you will be asked for.

Is Microsoft 365 backed up already?

Not in the way most people assume. Microsoft operates the service and protects the platform; retention of your data against deletion or a long-undetected problem is a separate product and a separate decision.

Find out whether your backups restore

Tell us what you back up today and when a restore was last actually tested.

  • Reply within one working day
  • Restore evidence, not just green dashboards

We use your details only to reply to you. See our privacy policy.

Need a consultation?

Tell us what you are building.

Share the problem, the platform and the deadline. We will come back with an approach, a team and an estimate.