The new reality
Having the backup is one thing. Getting back up and running when the server, the building or the data are gone is another.
Almost every company runs backups, and is right to. But a backup stores a copy of the data; on its own, it does not put the company back online. When a critical server fails, an attack encrypts the systems or the site becomes unreachable, restoring everything from scratch can take days, and the company stays down the whole time. Disaster Recovery as a Service, or DRaaS, is what closes that gap: a managed plan that keeps a ready-to-boot copy of your environment in a secure cloud and, on the day of the disaster, brings your systems back up and running, the most critical ones first.
Only 32% of companies believe they could recover around fifty servers within five business days. Source: Veeam, Data Protection Trends 2024.
In 94% of ransomware attacks, criminals tried to compromise the victim's backups. Source: Sophos, The State of Ransomware 2024.
Cyberattacks were the leading cause of outages for the fourth year in a row, and 76% of organizations were hit by ransomware in the past twelve months. Source: Veeam, Data Protection Trends 2024.
If your main server stopped right now, or an attack locked everything, how soon, and from where, would your company get back up and running?
How much does each hour of downtime cost your company? Calculate it in minutes.
The real problem
Servers go down for mundane reasons. The company stops for expensive ones.
Disaster is rarely the movie version: most of the time it is a dying disk, an infected attachment or a power outage. What separates a scare from a crisis is not whether the backup exists, it is whether the company can get back up and running fast. Here is how downtime turns into loss:
The hardware that won't power on
The main server fails: a disk dies, the power supply burns out, the board gives in. The backup exists, but restoring the entire system from scratch, onto new hardware, takes hours or days, and operations sit idle waiting.
The ransomware that locks everything
An infected attachment encrypts the servers and, in the same move, the attack tries to wipe the backups. Without an isolated copy and a plan to spin the environment up elsewhere, the company is held hostage, with data and operations frozen at once.
The building you can't reach
Fire, flooding, a drawn-out power outage or simply no access to the site. The servers may even be standing, but no one can reach them, and a company cannot operate from a building it cannot enter.
The restore that becomes a marathon
Restoring for the first time, under pressure, without ever having rehearsed: reinstalling the system, reconfiguring, bringing each service back one by one. Every hour of downtime charges its bill, and what looked fast on paper turns into days in practice.
In all these cases, having a backup was not enough. What protects the business is a recovery plan: a ready-to-boot copy of the environment, kept beyond the attack's reach, and the ability to spin the systems up elsewhere, in the right order, before the loss grows. That is exactly what disaster recovery as a service delivers.
The concept
What disaster recovery as a service is
It is a managed continuity service. Zamak keeps a copy of your environment, servers and critical systems, always ready to boot in a secure cloud, updated with each backup. When a disaster takes your environment down, that copy is brought online and your operation comes back up in that cloud, the most important systems first, while your site is recovered. You neither buy nor maintain a second data center: the recovery infrastructure is ours, and you only truly use it when you need it.
The environment comes back up, not just the files
Recovery does not just hand back loose data: it boots the whole system, working, in the order you define, so the company gets back to operating, not just so the files reappear.
No second data center of your own
The ready-to-boot copy lives in a secure, managed cloud. You neither buy nor maintain idle recovery hardware: the infrastructure is ours, and it can cost up to 60% less than maintaining a traditional appliance.
Beyond the attack's reach
The copies stay isolated and immutable, off your network. Neither a ransomware strain that tries to wipe the backups, nor an intruder, nor an insider can reach your chance to turn back.
Not sure what an outage would cost your company today? Start there: calculate the cost of each hour down in minutes.
What you get
What is included
A continuity plan built, maintained and tested by Zamak, with recovery already prepared for the day the disaster arrives.
What Zamak runs
The technical backline of your continuity, from day to day to the day of the disaster.
- Keeps a ready-to-boot copy of your environment, updated with each backup.
- Stores that copy in a secure cloud, isolated and immutable, always available.
- Defines the priority order with you: which system needs to come back first.
- Tests recovery automatically and proves, with saved evidence, that the environment boots.
- Leads the recovery when the disaster happens and oversees the return to operation.
What you receive
More than a backup: your business back up and running.
- Your environment recovered and running in a secure cloud, without maintaining a second data center.
- Priority-based recovery: what is critical to the business comes back first.
- Periodic proof that recovery works, with date and screenshot.
- Restore straight onto hardware, even onto equipment different from the original.
- All in the same Zamak continuity console, alongside your server and workstation backups.
- Support from the Zamak team in a real recovery, during business hours, leading the process at your side.
Tech specs
The engineering behind the comeback
For those who want to look under the hood: what underpins fast recovery of the entire environment, with no appliance and no improvising.
Ready-to-boot copy
With each backup, a virtual machine of your system, already prepared to start, is created and kept up to date in a secure destination. In a disaster, it is brought online, instead of you building everything from scratch at the worst possible moment.
Recovery in the cloud
The environment is recovered inside a secure cloud, on Microsoft Azure, with you paying for compute only when you trigger the recovery. No appliance, no second data center, no idle hardware waiting for the disaster.
Priority-based recovery
The comeback happens in the order of criticality you define: the essential system comes up first, then email, then the rest. The company gets back to operating by what matters, without waiting for the entire environment.
Recovery straight onto hardware
When it makes sense to return to a physical machine, recovery restores the full system onto new equipment, even unlike the original, with no need to install the operating system first. It works for physical and virtual servers.
Recovery tested, with proof
Automated tests boot the copy in an isolated environment and verify, through machine intelligence, that the system actually starts, with over 99% accuracy in the verification, saving date and screenshot as proof.
Immutable and isolated
The copies stay isolated, off your network, and cannot be altered or deleted, not even by a compromised administrator. That is what ensures your chance to come back survives the attack itself.
Recovery runs on infrastructure certified in SOC 2 Type II, ISO 27001, ISO 9001, HIPAA and PCI-DSS, with the region set to your data residency requirements. The recovery environment is available around the clock, with high availability.
It is the difference between hoping the company comes back and knowing, with proof, that it does, and in what order.
Take this documentation to present to decision-makers.
How it compares
Our disaster recovery, next to the alternatives
The recovery solution Zamak delivers, Cove Data Protection by N-able, is compared by the manufacturer itself against the best-known alternatives on the market. See where it stands apart in continuity.
Where recovery happens
Zamak's choice
Zamak (Cove Data Protection)
In a secure cloud, no appliance or second data center
Veeam
You provision and maintain your own infrastructure
Datto
An on-site appliance, that grows and fails
Ready-to-boot copy (standby)
Zamak's choice
Zamak (Cove Data Protection)
Created with each backup and included
Veeam
A separate feature or license
Datto
Tied to the on-site appliance
Recovery in the public cloud
Zamak's choice
Zamak (Cove Data Protection)
On Microsoft Azure, paying for use only when triggered
Veeam
You build and host it yourself
Datto
The vendor's cloud, billed by use and peak
Immutable, isolated copies (anti-ransomware)
Zamak's choice
Zamak (Cove Data Protection)
Automatic and included, no hardware
Veeam
Require dedicated hardware
Datto
Tied to the appliance architecture
Automatically tested recovery
Zamak's choice
Zamak (Cove Data Protection)
Hosted, with machine-intelligence verification
Veeam
Your own scripting or a separate license
Datto
Tied to the on-site appliance
Cost of continuity
Zamak's choice
Zamak (Cove Data Protection)
Up to 60% less than traditional appliances, no proprietary hardware
Veeam
Infrastructure cost on you
Datto
Appliance plus peak-usage billing
Comparison published by N-able, maker of Cove Data Protection, against Veeam and Datto.
Risk and impact
From real risk to business impact
The main server fails: a disk dies, the hardware burns out.
The company stops for hours or days while everything is restored from scratch.
How DRaaS responds
The ready-to-boot copy is brought up in the cloud and operations return, in priority order.
Ransomware encrypts the servers and tries to wipe the backups.
Data and operations held hostage at once, with the backup perhaps lost along with it.
How DRaaS responds
Isolated, immutable copies, beyond the attack's reach, ready to spin up in a clean environment.
The building becomes unreachable: fire, flooding, power or access.
The servers may be standing, but no one can reach them, and the company cannot operate.
How DRaaS responds
Recovery runs in a secure cloud, independent of the physical site, and the team operates from wherever it is.
No one knows how long each system takes to come back, or in what order.
In the crisis, deciding what to recover first becomes a gamble, and the loss window grows with every undecided hour.
How DRaaS responds
The priority order and the return target for each system are already defined and rehearsed, before the real day.
Backup protects the data. Disaster recovery protects business continuity: the difference between having the copy and getting back to operating.
For every role
What changes for each role in your company
The same continuity, read through the eyes of whoever decides, owns the budget, runs the environment and resells IT.
Owner and founder
Build it, protect it, grow its value.
What you built cannot stop because of a burned-out server or an attack. Knowing the company gets back to operating fast protects revenue and reputation, and becomes proof of governance that weighs in your favor in audits, insurance and when growing the company's value.
Manager and director
Predictable cost. No surprises.
Trade the unpredictable risk of days of downtime for a contracted continuity plan, with predictable cost and no buying or maintaining a second data center. You answer the board and the insurer with a tested plan, not with hope.
IT lead and team
A secure extension of your team.
Zamak is a backline, not a replacement: your team does not have to build and maintain the recovery infrastructure or rehearse the switch to the recovery copy alone, and gains a tested plan and support in a real recovery, without losing control of the environment.
IT partner and provider
Grow your book without growing your technical team.
Offer managed disaster recovery to your clients without building a DR site. You keep the relationship and the contract; Zamak runs the technical backline of continuity and stands with you when the disaster hits the client.
The care a license doesn't include
Why Zamak
Buying a recovery license is the easy part. What truly brings continuity is the service behind it: defining with you what needs to come back first, keeping the copy ready and tested, and, on the day of the disaster, leading the recovery at your side. That is the backline Zamak places next to your team, adding to the work of whoever already runs your environment, never taking their place.
In the end, it is the difference between owning a recovery license and having a continuity plan that someone built, tested and knows how to trigger at the right moment.
15 years serving companies that cannot stop · Microsoft Solutions Partner · Addee (N-able) Elite Group · Great Place to Work.
Recovery runs on infrastructure certified in SOC 2 Type II, ISO 27001, HIPAA and PCI-DSS.
Still wondering?
Frequently asked questions
See also Check your ransomware readiness · Calculate the cost of an outage
Next steps
Don't wait for the disaster to find out how soon the company comes back.
The time to build the continuity plan is before the outage, not during it. Building and testing the plan takes time, and the disaster gives no warning: whoever waits for the server to fail ends up signing up under pressure, on the worst day. Talk to Zamak and design the recovery of your environment, in the order your business needs.
Request a proposal
Leave your details and a specialist from your country gets back to design your continuity plan and present the proposal.
Talk to a specialist
A conversation about your critical systems and how to recover them fast, with no commitment.
Check your ransomware readiness
Find out in minutes how well your environment would withstand, and recover from, an attack.