A managed service starts with clear agreements and continues through daily operations, recovery tests and the incident itself. This is how we set it up.
Which services are critical, who uses them and what stops when they are down? We also look at your current environment and suppliers.
Priorities · dependencies · current setupCoverage, retention, recovery objectives, capacity, roles and escalation. And in writing, which work moves to us.
Scope · RPO / RTO · responsibilitiesWe set up the backups and recovery arrangements, run the first restore or recovery test and go through the result with you.
Configuration · test scope · sign-offOur engineers run the backups and checks. When your environment or business changes, we check whether the service still fits.
Operations · monitoring · follow-upWe follow the agreed permissions and priorities, pick the recovery point, run the recovery and check the services the business needs.
Restore or DR · application checks · communicationIf failback is part of the service, we move systems from DR back to your environment. Then we look at what the plan should change.
Final sync · switchover · reviewThe exact split is agreed per customer. This is where the conversation starts.
| Activity | Immutec | Your organisation / IT partner |
|---|---|---|
| Recovery priorities | Advises on technical options and dependencies | Sets business priorities and acceptable impact |
| Daily backup operations | Runs and checks the backups | Tells us about relevant changes to the environment |
| Recovery tests | Runs the recovery test | Checks that the business applications work |
| Restore or DR | Leads and does the recovery work | Gives the go-ahead, coordinates production and signs off |
| Cyber incident | Assesses recovery points and runs the recovery | Coordinates containment, clean-up and incident response |
| Failback, if included | Coordinates the sync and the switchover | Prepares production and confirms the business can work |
Responsibilities, service levels and liability are set out in the contract. This overview does not replace it.
RPO and RTO
How much work you lose depends on when the last backup ran. How long you are down depends on everything that has to happen before people can work again. An example:
The recovery point objective is the gap between the last usable backup and the moment things went wrong. Back up every four hours and you can lose up to four hours of work. Back up more often and the red band gets shorter.
The recovery time objective runs until users are back at work, not until a server boots. Choosing the recovery point, the network, application checks and a test with your own people all count. A prepared DR environment and a tested plan make that bar shorter.
One of our engineers goes through your environment with you and tells you what we would take over and what that takes.