Recovery point objective (RPO)
RPO is the target point in time to which data must be recovered after an outage. It helps define the amount of recent work your institution could accept losing, and informs backup frequency and recovery design.
Powering Higher Education
Backup & disaster recovery
Backup and disaster recovery planning helps schools, colleges and universities restore websites, applications and teaching services after disruption. Education Host scopes backup layers, recovery options and restore testing around the systems you run and the teaching deadlines they support.
We start with a conversation about your requirements. This is not a self-service backup product.

RPO describes the recovery point your data needs to reach; RTO describes how long service recovery is intended to take. Agree both around the impact on teaching, assessment and administration, then test whether the planned recovery can meet them.
RPO is the target point in time to which data must be recovered after an outage. It helps define the amount of recent work your institution could accept losing, and informs backup frequency and recovery design.
RTO is the target duration for recovering a service after disruption. Restoring a database, making the application available and checking it works may all be part of that recovery.
Recovery objectives are requirements to assess and agree, not recovery guarantees. A successful backup job alone does not demonstrate that either objective can be met.
Definitions and planning guidance: NIST: recovery point objective; NIST: recovery time objective; NCSC: data security and backups
Most organisations only find out how good their backups are on the day they need them. Universities, colleges and schools need confidence about what would happen, and how quickly, before the question becomes urgent.
A backup job that runs is not the same as a backup that restores. Without restore testing, failures surface at the worst possible moment.
Course content, student work and departmental sites are edited by many hands. A deleted database or overwritten site needs a known route back.
A plugin, theme or system update that breaks a live site is routine. Recovering from one shouldn't require improvisation.
If an attacker can reach your backups from the compromised system, they are not a recovery plan. Separation matters.
Hosting suppliers, platforms and local infrastructure can fail. Important workloads need copies that don't share the same fate.
Knowing data exists somewhere is not a plan. Institutions need realistic expectations of how long recovery takes and how much could be lost.
Across Education Host managed services, backup protection is designed in layers to reduce dependence on a single system or copy. The layers and their coverage are agreed for each service and workload.
Backups and recovery planning built around the hosting platform, managed infrastructure and service architecture itself. This is the foundation every managed service sits on.
Scheduled backups for servers, websites, databases, application data and managed services where appropriate, aligned to agreed retention and recovery requirements.
Additional separation for important workloads. Copies are held independently of the production system, helping reduce risk from accidental deletion, system failure, ransomware, supplier issues or local infrastructure incidents.
Exact arrangements depend on the service and the workload. Retention, frequency and recovery expectations are agreed rather than assumed.
Whether or not Education Host runs your infrastructure, the fundamentals of dependable backup are the same. These are the points we work through with institutions:
Backup and recovery support is delivered as part of our managed services, or as focused work alongside what you already run, depending on the service and what your institution needs.
Scheduled backups for managed websites, applications and databases, with agreed retention and recovery requirements.
Backup planning for cPanel and managed hosting environments, including student and departmental hosting where appropriate.
Independent recovery copies held separately from production systems, for workloads that justify the additional layer.
A structured look at what is currently backed up, where the gaps are and what would happen in a restore.
Restore testing can be included, alongside documented recovery steps and realistic recovery time expectations.
Recovery options for education platforms we manage, including backup arrangements for Cloud Pulse, Student Web Host Manager and wider managed infrastructure, agreed during scoping.
Education runs to a calendar. Losing a system in week three of teaching, or during an assessment window, is a different problem from losing one in August. Recovery planning should reflect that.
Labs, module sites and teaching environments that lectures depend on the same week they fail.
Coursework, projects and portfolios that often cannot be recreated if they are lost.
Sites run by departments and staff, edited by many people, usually without their own recovery plans.
Submission deadlines and marking windows, when downtime and data loss carry the highest cost.
Evidence that critical services have a tested route back, for continuity planning and risk registers.
Clear answers about retention, separation and recovery when auditors, insurers or governors ask.
Bring a list of your important systems, current backup arrangements and the disruption your institution needs to plan for. We can review the gaps and scope support, including the responsibilities that remain with your team or another supplier.
Identify the websites, databases and applications in scope, their owners and anything they need to run. Confirm which systems are managed by Education Host and which need a separate arrangement.
Explain which services must return first, especially around assessment or admissions. Agree who authorises a restore, who performs it and who checks the recovered service before normal use resumes.
Review what is copied, how often, where copies are held and how access is separated from production. Agree retention and recovery points for each workload, including any gaps in the current coverage.
Agree a safe test scope and record the backup used, what was restored, the checks performed and any remaining issues. Include applications and dependencies in the checks, rather than treating a completed file copy as a complete recovery test.
You can start with system names and a summary of the current arrangements. Access details and sensitive information are handled separately after scope is agreed.
Contact usAnswers to common questions from IT teams, digital teams and leadership about backup, restore testing and recovery planning.
Backup is keeping copies of data and systems so they can be restored after loss or damage. Disaster recovery is the wider plan for when something serious goes wrong: how services are brought back, in what order, how quickly and by whom. Good practice needs both.
Recovery time and recovery point objectives are assessed and agreed for each service and workload. Education Host does not publish a universal recovery-time or data-loss guarantee; the scope, dependencies and restore testing determine what can be agreed.
No. Backup coverage is defined for the managed service and agreed workloads. Other institutional systems, external services and dependencies need their own confirmed backup and recovery arrangements.
A restore test should demonstrate that the selected backup can recover the agreed data or service and that the recovered result works. Record the recovery point, time taken, checks performed and unresolved dependencies against the agreed test scope.
No. Backups are one ingredient of disaster recovery. A recovery plan also covers where restores run, who is responsible, how long recovery takes, what data loss is acceptable and how the process is tested. That is why restore testing and documentation matter as much as the backup jobs themselves.
Copies that live with the production system share its risks: accidental deletion, compromise, supplier failure or a local infrastructure incident can affect both at once. An independent off-site copy gives important workloads a route back that does not depend on the system that failed.
Yes. Restore testing can be included as part of a managed backup arrangement, along with documented recovery steps your team can follow, so recovery is demonstrated rather than assumed.
Yes. We can review what is currently backed up across your websites, hosting and platforms, identify gaps and single points of failure, and recommend improvements, whether or not Education Host runs the underlying infrastructure.
Yes. Retention periods, backup frequency and recovery expectations are agreed per service rather than fixed. Different workloads justify different arrangements, and academic calendars often shape what sensible retention looks like.
Yes, where appropriate. Backup planning for cPanel environments and managed servers is part of our managed hosting services, and off-site recovery copies can be configured for workloads that need the additional layer.
Backup and recovery arrangements for Education Host platforms, including Cloud Pulse teaching labs and Student Web Host Manager, are agreed during scoping, depending on the service and the workloads involved, alongside the platform-level resilience our managed infrastructure provides.
This is for universities, colleges, schools and education organisations that want sensible, managed advice: a conversation about what you run, what it needs and how recovery would work. There is no checkout and no one-size-fits-all package.