Skip to content
The math on cloud backup has shifted twice. Analysts put the global cloud backup market at roughly $6.6B to $8.7B entering 2026, depending on methodology, with forecasts ranging from $14.85B by 2032 to $51.57B by 2034. At the same time, the threat model has changed: attackers are no longer just encrypting production. They are targeting the recovery path.
According to Veeam’s 2025 Ransomware Trends report, among ransomware-impacted respondents, 89% had backup repositories targeted and only 32% used repositories or services configured as immutable. Microsoft’s Storm-0501 reporting shows the same shift in cloud form: after pivoting into Azure, the actor attempted mass deletion of snapshots, restore point collections, storage accounts, and Recovery Services vault protection containers, then used cloud-based encryption where deletion failed.
Let’s look at 5 criteria to look for in a backup tool:
1. Security
Microsoft’s Storm-0501 reporting shows the shift from on-prem ransomware to cloud-native extortion: after pivoting into Azure, the actor attempted mass deletion of snapshots, restore point collections, storage accounts, and Recovery Services vault protection containers, then used cloud-based encryption against resources that remained protected.
The 2014 Code Spaces breach was an early public warning: an attacker with AWS control-panel access wiped EBS snapshots, S3 buckets, AMIs, instances, and backups to destroy the company’s recovery path.
What protects you: a backup vault with a separate identity boundary. On AWS, cross-account backup with limited IAM access. On Azure, immutable Recovery Services vaults with multi-user authorization. Pair that with MFA on console access, encryption at rest and in transit, and the basics most teams still skip. Current guidance lives in the AWS Backup security documentation.
2. Automation
You can’t trust a human to take an hourly snapshot of an EBS volume. Snapshots, copies to a secondary account or region, and lifecycle expiration all need to run on a schedule that survives a bad day.
AWS EBS snapshots are the building block. A raw snapshot becomes a backup once it’s scheduled, retained, and tested. Manual provisioning and copy-paste retention policies are how teams end up with snapshots that miss the resources that matter most.
3. Recovery drills
A second site that’s never been tested won’t help you when it counts. Drills tell you whether the network configuration works, whether the application starts cleanly, and whether your RTO and RPO numbers are real or aspirational.
This stopped being optional in 2025. For regulated sectors, drills are increasingly becoming a legal and audit requirement. DORA has applied since January 17, 2025 and requires EU financial entities to test ICT business continuity and response/recovery plans at least yearly.
NIS2 broadened cyber-risk management obligations across critical and important sectors, including business continuity, backup management, disaster recovery, and crisis management, though exact enforcement depends on national transposition.
Your backup tool should automate drills, generate reports an auditor will accept, and confirm the restored environment actually works.
4. Application-level backup
Application consistency is what turns a snapshot into a recoverable backup. That state holds only when open transactions are flushed to disk, the database sits quiescent, and the data on the snapshot reflects a recoverable point in time.
For SQL Server, Exchange, and other transactional workloads, that means VSS-aware backup or pre/post-snapshot scripts.
5. Consistent monitoring
Scheduling a backup and walking away is how you find out it’s been failing for six weeks. Active monitoring tells you when a job fails, when retention drift starts pruning the wrong restore points, and when an unauthorized identity touches the vault.
Amazon CloudWatch handles metrics, log aggregation, and alarms on the AWS side. Azure Monitor does the equivalent. Your backup vendor should also watch for the things attackers do first: disabled jobs, deleted snapshots, modified retention policies, suspicious API calls against your vaults.
Where N2W fits
N2W is a multi-cloud backup and DR platform built for AWS and Azure. It runs in your cloud account, is agentless for core cloud-native snapshot workflows, and supports optional N2W Thin Backup Agent or AWS SSM Agent workflows for application-consistent Windows backups. It also allows you:
- Backup intervals as low as 60 seconds for tighter RPOs
- Up to 92% storage cost reduction through tiered retention to S3, Glacier, and Azure Blob
- Cross-account and cross-region backup vaults to keep production and recovery isolated
- Automated, scheduled DR drills with audit-ready reports
- Application-consistent backup for Windows workloads via the N2W agent
- Centralized management of multiple AWS and Azure accounts under one policy engine
You can recover EBS volumes from snapshots, resize them, or swap them with an existing attached volume in a single step. The product runs in your environment, and customers keep recovery access even if they stop paying.
