How much recent work could be lost?
The recovery point objective describes the acceptable gap in recoverable data. Backup frequency and available recovery points matter.
How it works
Define the plan.
Give the work an owner.
A managed service starts with clear expectations and continues through daily operations, recovery testing and the incident itself. Here is how we build the working relationship.
- 01
Understand the business
Identify critical services, the people who use them and what an outage would stop. Review the existing environment and suppliers.
Business priorities · dependencies · current arrangements - 02
Agree the recovery service
Define coverage, retention, recovery objectives, capacity, roles and escalation. Make the handover of operational responsibility explicit.
Service scope · RPO / RTO · ownership - 03
Onboard and validate
Set up the agreed protection and recovery arrangements. Carry out the selected restore or recovery test and review the result together.
Configured protection · test scope · acceptance - 04
Manage and maintain
Our specialists manage the agreed daily operations and checks. Changes to the environment or business need are reviewed against the service scope.
Operations · monitoring · follow-up - 05
Recover when needed
Follow agreed authorisations and priorities. Assess the recovery point, execute the selected recovery and validate the services required by the business.
Restore or DR · application checks · communication - 06
Return and improve
Where included, coordinate failback from DR to the prepared source environment. Review what happened and what the recovery plan should change.
Final synchronisation · cutover · review
Who does what
A practical handover.
Written down before the pressure.
The exact division is agreed for your service. This is the starting point for the responsibility discussion.
| Activity | Immutec | Your organisation / IT partner |
|---|---|---|
| Recovery priorities | Advise on technical options and dependencies | Define business priorities and acceptable impact |
| Daily backup operations | Manage and check the agreed service | Communicate relevant environment changes |
| Recovery validation | Execute the agreed recovery test | Validate business application functionality |
| Restore or DR | Lead and execute the agreed recovery work | Authorise, coordinate production and accept service |
| Cyber incident | Support recovery-point assessment and agreed recovery | Coordinate containment, remediation and incident response |
| Failback, where included | Coordinate synchronisation and recovery cutover | Prepare production and validate business operation |
Operational responsibilities, service levels and contractual liability are defined in the agreement. This overview does not replace the agreed scope.
How soon must the service return?
The recovery time objective describes the target time to restore service. It includes the environment and dependencies needed for useful operation.
Let’s make it concrete
Make recovery a plan.
Give it an owner.
Start with the systems your business needs most. We’ll work through the recovery priorities, responsibilities and a practical first step.