Fewer operational handovers
Our specialists can work across the agreed service rather than leaving you to assemble a recovery from disconnected components.
Technology & trust
Deep capability.
Clear accountability.
We develop our own technology and operate our own private cloud. Our specialists work across the protection and recovery stack, with the control to support complex recovery requirements.
Why owning the stack matters
Control from the recovery point
to the running system.
Our software, infrastructure and operations are developed around the same purpose: protecting data and making recovery practical.
Capability shaped by recovery needs
Recovery across supported environments, network continuity and historical investigation are part of our technical focus.
A direct technical conversation
Talk through the environment, dependencies and supported recovery approach with the people responsible for delivery.
Technical capabilities
Explore the functions.
Bring us your requirements.
We confirm supported platforms, coverage, capacity and recovery objectives for each environment.
01 / CAPABILITY AREAProtection & integrity+
Immutable protection in every backup
Preserve recovery points under the agreed retention policy. Immutability is built into all our backup services.
Private cloud & optional local copy
Store backups on our own infrastructure, with local backup where requested and designed into the service.
Microsoft 365 & basic Entra ID
Include supported cloud data and basic identity information in a defined backup scope.
Restore integrity verification
Check restored content against the selected backup.
02 / CAPABILITY AREARecovery, failover & failback+
Local or data centre recovery
Run supported recovery VMs on the local backup server or in our data centre.
Cross-hypervisor recovery
Restore virtual machines across supported source and target environments.
IP & VLAN continuity
Reconnect recovered systems with the required network identity and segmentation.
Scalable recovery capacity
Allocate compute resources around the agreed workloads and scenario.
Managed return to production
Synchronise changes from DR and coordinate the source environment restart.
03 / CAPABILITY AREAThreat analysis & investigation+
Retrospective threat matching
Reassess historical backup information as new malware indicators become available.
Flagged content & restore selection
Identify suspicious content and keep identified malware outside the selected restore scope.
Ransomware change analysis
Inspect changes across backup history for signs of ransomware activity.
Isolated investigation
Boot and examine historical systems in isolation to narrow the incident timeline.
04 / CAPABILITY AREAManaged delivery+
Specialist operations
Manage the agreed backup work, monitoring, checks and restores.
Recovery validation
Test agreed scenarios against the relevant application and network dependencies.
Defined recovery objectives
Agree RPO and RTO for the selected service and environment.
Coordinated recovery
Work to defined priorities, authorisations, escalation and communication paths.
Sovereign private cloud
Know where your data is.
Know who operates it.
Your agreed cloud backup service runs on Immutec’s own private infrastructure in the Netherlands. We also carry out backup indexing and assessment on our own systems.
Data location is one part of the conversation. We also agree access, retention, responsibilities and the recovery arrangements you need.
ISO270012022
Information security management
ISO 27001:2022 certified
Certificate K-0222603/1, issued by Kiwa Nederland B.V. The published scope covers the development, implementation and delivery of managed data protection solutions.
Published validity: 3 December 2024 – 2 December 2027.View the published certification details ↗For your technical review
A useful due-diligence conversation starts here.
Service boundaries
Which workloads and recovery actions are in scope? Who manages production, backup, incident response and acceptance?
Objectives & dependencies
What are the agreed RPO and RTO? Which applications, identities and network services must return together?
Data & access
Where are copies held? What retention applies? Who can authorise recovery, access data and approve a cutover?
Validation & exit
How will recovery be tested? How is failback planned? What are the data retrieval arrangements at the end of the service?
Let’s make it concrete
Bring the difficult
recovery questions.
Our specialists can work through your environment and requirements in a technical discussion.