Skip to main content
Nexa TechNexa Tech

Backup and recovery

Designed backwards from the restore.

A backup that has never been restored is an assumption. We design backup and disaster recovery from agreed recovery objectives, and test them by restoring.

Where it fits
  • On-premises and virtualised server estates
  • Hybrid estates spanning on-premises infrastructure and cloud services
  • Cloud-hosted and SaaS workloads
  • Healthcare and other availability-critical settings
  • Organisations with regulatory retention requirements
Aisle between two rows of closed, mesh-fronted server cabinets under recessed ceiling lighting
Backup and recovery

Our scope

What we do on these systems.

  1. 01Agree recovery time and recovery point objectives per system with the organisation, before any platform is chosen
  2. 02Design the backup architecture (schedules, retention, copy counts and an immutable or offline tier) against those objectives
  3. 03Specify where backup data lives: on-site, second site or cloud, with restore bandwidth checked against the recovery time
  4. 04Write the DR runbook: the order systems come back, who does what, and the decision points (not a contact list)
  5. 05Commission by performing restores (file, application and full system) and recording the measured times
  6. 06Schedule recurring restore tests so the capability is maintained rather than assumed

Platform

What the system does.

  • Recovery point and recovery time objectives defined per system, not one policy for everything
  • Multiple backup copies across separate media and locations, including one isolated from the production network
  • Immutable or offline copies that a compromised administrator account cannot delete
  • Application-consistent backups of databases and virtualised workloads
  • Restore options from a single file to a full site, so a full restore is never the only path
  • Replication to a second site or cloud for the systems whose recovery time demands it
  • Backup job monitoring and failure alerting, so a silent failure is not discovered at restore time
  • Restore times measured in tests rather than quoted from a datasheet

Next step

Bring the complete environment into one conversation.

Tell us what you are planning, replacing, integrating or trying to stabilise. We will help define the right next step.