Fewer handovers
Our engineers can work on every layer of the service. You don’t have to piece a recovery together from three suppliers.
We build the software, run the data centre and do the recovery work ourselves.
That means the engineer who picks up the phone during an incident knows the whole chain, from the backup agent on your server to the storage in Amsterdam.
What it changes when one company runs the whole chain.
Software, infrastructure and operations are built for the same job: getting your data back.
Features our engineers needed themselves
Recovery across hypervisors, network continuity and forensic analysis of old backups exist because our engineers needed them.
Talk to the people who do the work
You discuss your environment directly with the engineers who will run it.
Technical capabilities
What the platform does, shown step by step.
Pick an area. The animations use an example environment. Which platforms and objectives apply to yours, we confirm before onboarding.
Protection & integrity
- Immutable copy of every backup
- Recovery points stay locked for the retention period you choose. Nobody can change or delete them early.
- Own data centre, optional local copy
- Backups live in our own data centre in Amsterdam. Add a local copy if you want fast restores on site.
- Microsoft 365 and basic Entra ID
- Mail, OneDrive, SharePoint and Teams data plus basic identity information, within a defined scope.
- Restore check
- After a restore we compare checksums with the recovery point, file by file.
Recovery & failback
- On site or in our data centre
- Start recovery VMs on the local backup server or in Amsterdam, depending on what failed.
- Cross-hypervisor recovery
- A VMware VM can run on Hyper-V. We confirm which source and target combinations apply to you.
- IP and VLAN continuity
- Recovered systems keep their IP address and VLAN, so applications and users find them again.
- Capacity when you need it
- We reserve the compute your critical workloads need during an outage.
- Failback
- When your environment is ready, we sync the changes made in DR and switch production back.
Threat analysis
- Retrospective threat matching
- When a new malware indicator is published, we check your older recovery points for it too.
- Flagged content
- Infected files are marked and left out of the restore.
- Ransomware change analysis
- We look for patterns across your backup history, such as a sudden spike in changed or encrypted files.
- Isolated investigation
- We boot an older version of a server without network access to see when the problem started.
Managed delivery
- Daily operations
- Our engineers watch the jobs, fix failures and run restores for you.
- Recovery tests
- We test restores against the applications and network dependencies that matter to you.
- RPO and RTO
- We set recovery point and recovery time objectives per service, together with you.
- Coordinated recovery
- Who decides, who executes and who gets informed is written down before an incident.
Your data stays in the Netherlands, on hardware we run.
The backup service runs on Immutec’s own private cloud in a data centre in Amsterdam. Indexing and scanning of backups also happen on our own systems.
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 to 2 December 2027.Request a copy of the certificateHow your backups are protected.
The rules behind every recovery point, in one place.
3-2-1-1-0
Three copies, on two kinds of storage, one off site, one immutable, and zero errors in the checks.
Ceph storage, run by us
The protected copies live on our own Ceph storage cluster in Amsterdam. Recovery points are locked for the retention period you choose.
No login for anyone
You have no login to the protected storage, and neither does an attacker with your admin passwords. Our data centre opens an encrypted connection to collect the data and closes it again. You request a restore through our engineers.
Deleting early takes two people on site
Removing protected data before its retention date needs a signed written request and two of our engineers physically present in the data centre.
Optional local backup server with honeypots
A local backup server keeps a copy on site for fast restores and can start recovery VMs. It also contains honeypots that alert our engineers when someone in your network touches them.
Questions for your technical review.
Scope
Which workloads and recovery actions are covered? Who manages production, backup, incident response and sign-off?
Objectives and dependencies
What are the RPO and RTO? Which applications, identities and network services have to come back together?
Data and access
Where are the copies? What retention applies? Who may approve a recovery, access data or approve a switchover?
Testing and exit
How is recovery tested? How is failback planned? How do you get your data back if you leave?
Bring your hardest recovery questions.
Our engineers will go through your environment and requirements with you in a technical session.