Quick summary
- Most “multi-cloud” backup is one product per cloud. Veeam deploys a separate product (with a separate license) in each cloud and joins them under Veeam Backup & Replication. Druva, Rubrik and Commvault run as SaaS. The native tools (AWS Backup, Azure Backup, Google Cloud Backup and DR) each protect only their own cloud.
- Coverage is uneven across clouds for every vendor. Check each tool cloud by cloud. Google Cloud is where the gaps show: Druva has no native Google Cloud protection, and N2W covers Compute Engine VMs and persistent disks.
- Cross-cloud recovery varies more than anything else. Veeam documents restores in every direction between AWS, Azure and Google Cloud through Veeam Backup & Replication. Commvault restores AWS and Azure VMs into either of the other two clouds. NetBackup restores between AWS and Azure. N2W restores AWS workloads into Azure.
- N2W is one deployment for all three clouds. Adding a cloud means adding an account to the console you already run. Backups stay in your own accounts, and pricing counts protected instances whichever cloud they’re in, starting at $249 a month for up to 20.
If you run production on AWS and Azure, with some Google Cloud VMs, N2W gives you one console and one license with nothing to deploy per cloud. If you need deep Google Cloud database coverage or cross-cloud restores in every direction, look at Veeam or Commvault. If you live in one cloud, its native tool is the place to start.
Which multi-cloud backup solution is best?
| Tool | What it protects in AWS / Azure / Google Cloud | How it’s delivered | Where backups live | Cross-cloud recovery | Pricing |
|---|---|---|---|---|---|
| N2W | AWS: EC2, EBS, RDS and more. Azure: VMs, managed disks, Azure SQL. Google Cloud: Compute Engine VMs and persistent disks | Software in your own cloud account; one console for all three clouds | Your own AWS, Azure and Google Cloud accounts | AWS to Azure (bootable for Ubuntu 22 and 24; Windows as data disks) | $249/month for up to 20 instances (Standard); higher plans quote-based |
| Veeam | AWS: EC2, RDS, DynamoDB, EFS, FSx and more. Azure: VMs, Azure SQL, Cosmos DB, Azure Files. Google Cloud: VMs, Cloud SQL, Cloud Spanner | A backup appliance per cloud, in your account, managed from Veeam Backup & Replication | Your own object storage (an S3 bucket on AWS) | Every direction between AWS, Azure and Google Cloud, through Veeam Backup & Replication | Free for 10 instances on standalone appliances; then quote-based subscription |
| Commvault Cloud | AWS: EC2 (Clumio adds S3, RDS, DynamoDB and more). Azure: VMs. Google Cloud: Compute Engine with Persistent Disk and Hyperdisk | SaaS (also sold as software or an appliance) | Your storage, or Commvault’s Air Gap Protect | AWS or Azure VMs into any of the three; Google Cloud VMs stay in Google Cloud | VM Backup $102.49 per 10-VM pack per month (AWS and Azure); Clumio per GiB |
| Cohesity (NetBackup) | VMs, applications and volumes on AWS, Azure and Google Cloud; managed databases on all three | Software you run (NetBackup); DataProtect is the SaaS option | Your storage (NetBackup) | AWS to Azure and Azure to AWS, NetBackup 10.5 or later | NetBackup quote-based; DataProtect as a Service on AWS Marketplace from $29,100 a year per 10 TB |
| Rubrik Security Cloud | AWS: EC2, S3, RDS, DynamoDB, Aurora. Azure and Google Cloud workloads (plus BigQuery and Cloud Storage), and OCI | SaaS, one control plane for all clouds | Rubrik Cloud Vault, a separate identity domain Rubrik runs, for air-gapped copies | Not documented publicly | Quote-based |
| Druva | AWS: EC2, RDS, S3, DynamoDB, EFS. Azure: VMs, SQL, Blob, Files. Google Cloud: no native support | SaaS, one console | Your AWS account for EC2 snapshots; Druva Cloud once air-gap backup is on | Not documented for cloud workloads | Quote-based, billed in credits (1 TB stored for a month) |
| Native tools | Each protects its own cloud only | Built into each cloud | The provider’s own vaults (Google Cloud also supports your own storage) | None | Consumption-based, per GB stored plus per-resource fees |
The prices above cover different things. N2W and Veeam license software, and you pay your cloud provider separately for the storage backups use. SaaS and per-TB prices usually include the vendor’s storage. Compare like with like before you compare totals.
What is multi-cloud backup?
Multi-cloud backup is protecting workloads that run in more than one public cloud, typically AWS, Azure and Google Cloud, under one set of policies and one view of what’s covered. It’s a different question from cross-cloud recovery, which is restoring a workload from one cloud into another.
Most teams need the first and occasionally want the second. A tool can do multi-cloud backup well and offer no cross-cloud recovery at all. For background on why teams end up on more than one cloud, see what multi-cloud is and how it succeeds.
How we evaluated these tools
We compared each tool on five things, checked against each vendor’s own documentation and pricing pages in November 2026:
- Coverage per cloud. Which workloads it protects in AWS, Azure and Google Cloud, listed separately, because no vendor is equally deep in all three.
- Console and deployment. One product for every cloud, or a separate deployment per cloud.
- Custody. Whether backups stay in your accounts or move into storage the vendor runs.
- Cross-cloud recovery. Which directions are documented, and with what limits.
- Pricing. What’s published, and what the price covers.
The list is scoped to cloud workloads on AWS, Azure and Google Cloud. Endpoint, consumer and SaaS-app backup (Microsoft 365, Google Workspace) are out of scope.
The 7 best multi-cloud backup solutions
1. N2W
What it does: Backup and disaster recovery software that runs inside your own cloud account and protects AWS, Azure and Google Cloud from one console. N2W never holds or accesses your data.
Best for: Teams running production on AWS and Azure, with or without Google Cloud VMs, who want one console and one license and want backups to stay in accounts they control.
Key features:
- A single deployment for all clouds. The console runs in whichever cloud you install it in. Azure and Google Cloud join as accounts. An existing customer adding Google Cloud installs nothing; they add a project to the console they already run.
- Coverage per cloud. On AWS: EC2, EBS, RDS and more. On Azure: VMs, managed disks and Azure SQL. On Google Cloud: Compute Engine VMs and persistent disks, with cross-region backup and DR and cross-project data copying for supported VM scenarios.
- Backups as often as every 60 seconds, and recovery in under 60 seconds on AWS. The City of Oakland recovered a full environment in about 30 seconds.
- Recovery Scenarios and Dry Runs on AWS and Azure. A Recovery Scenario brings back many instances together, in parallel or in an order you set, with the network they need. A Dry Run checks a recovery without launching anything, so you can test DR every month without paying for test instances.
- Cross-cloud recovery from AWS into Azure. Ubuntu 22 and 24 workloads restore as bootable Azure VMs; Windows workloads restore as data disks. It runs one way, AWS to Azure, from a backup already in a storage repository. See how cross-cloud restore works.
- Immutability through each cloud’s own lock. S3 Object Lock and EBS Snapshot Lock in compliance mode on AWS. A lease on the storage repository and a Delete lock on snapshots on Azure.
- One coverage view. The unprotected resources view lists what isn’t backed up across all connected clouds, Google Cloud included, and you can add up to 200 unprotected resources to a policy in one click.
Pros:
- Nothing extra to deploy per cloud, and no per-cloud license
- Backups stay in your own AWS, Azure and Google Cloud accounts
- Whole environments recover in order, and you can test it without launching anything
- Up to 92% lower backup storage costs on AWS and 70% on Azure by archiving to cheaper storage tiers
Cons:
- Google Cloud coverage is Compute Engine VMs and persistent disks only. No Cloud SQL, GKE or Hyperdisk, and no N2W-applied immutability on Google Cloud
- Cross-cloud recovery currently runs AWS to Azure only, and Google Cloud is not part of it
- Not built for on-premises VMware estates
Pricing: The Standard plan is $249 a month for up to 20 protected instances. Advanced, Enterprise and Enterprise+ are quote-based. Price is set by how many instances you protect, whichever cloud they run in, and you pay your cloud provider directly for backup storage. See N2W pricing.
Bottom line: The pick for AWS and Azure estates that want one console and one bill across clouds, with Google Cloud VMs in the same place.
2. Veeam
What it does: Veeam Backup for AWS, Veeam Backup for Microsoft Azure and Veeam Backup for Google Cloud are Linux appliances that run in your account, one per cloud. Veeam Backup & Replication manages all of them from one console. Veeam Data Cloud is Veeam’s separate SaaS service for AWS and Azure.
Best for: Teams already running Veeam on-premises who want their cloud backups under the same console.
Key features:
- The widest Google Cloud workload list here: VMs, Cloud SQL and Cloud Spanner.
- Cross-cloud restore in every direction between AWS, Azure and Google Cloud, when the appliances are managed by Veeam Backup & Replication.
- Backups in your own object storage, such as a folder in an S3 bucket on AWS.
Pros:
- The broadest cross-cloud restore matrix on this list
- Free for small estates
Cons:
- One appliance to deploy, patch and size per cloud
- Several workloads (DynamoDB, Redshift, FSx, Cloud Spanner, Cosmos DB) and the cross-cloud restores need a Veeam Backup & Replication server
- Pricing comes in several separate paths (appliances, Veeam Data Cloud, Vault storage), which makes totals hard to compare
Pricing: Free for up to 10 instances on appliances that aren’t managed by Veeam Backup & Replication. Beyond that, a subscription under the Veeam Universal License, quote-based. Veeam Data Cloud for Azure is $42 per TB a month (regional and reseller pricing varies). Veeam doesn’t publish a price for the AWS edition.
Bottom line: Strong if you already run Veeam Backup & Replication and need Google Cloud databases or restores in every direction.
3. Commvault Cloud
What it does: Commvault’s data protection platform, sold as SaaS, software or an appliance. Clumio, which Commvault acquired, protects AWS data services as a separate product.
Best for: Large enterprises protecting cloud, SaaS and on-premises data from one vendor.
Key features:
- Google Cloud Compute Engine with Persistent Disk and Hyperdisk, with snapshots copied to your own storage or to Commvault Air Gap Protect.
- Cross-hypervisor restores: EC2 into Azure or Google Cloud, and Azure VMs into EC2 or Google Cloud. Google Cloud VMs restore into Google Cloud or VMware only.
- Clumio for AWS covers S3, EC2 and EBS, RDS, Aurora, DynamoDB and more, at per-GiB prices.
Pros:
- The broadest workload coverage across cloud, SaaS and on-premises
- Supports Hyperdisk on Google Cloud
Cons:
- Clumio backups sit in Clumio’s SecureVault, outside your accounts, and Clumio’s Azure support is on its roadmap
- The published VM pack covers AWS and Azure, not Google Cloud
- A lot of platform if your estate is all public cloud
Pricing: VM Backup is $102.49 per 10-VM pack per month for Azure and Amazon EC2, with volume discounts above 50 VMs. Clumio is priced per GiB: EC2 and EBS in SecureVault Standard is $0.045 per GiB-month. Google Cloud protection is quote-based.
Bottom line: The broad-coverage option for enterprises that want one vendor for cloud and everything else.
4. Cohesity (NetBackup)
What it does: Cohesity merged with Veritas, so NetBackup now sits in the Cohesity portfolio. NetBackup is software you run that protects VMs, applications and managed databases across AWS, Azure and Google Cloud. DataProtect as a Service is Cohesity’s SaaS option.
Best for: Enterprises already standardized on NetBackup that want cloud workloads in the same platform.
Key features:
- Managed database coverage on all three clouds: RDS, Aurora, DynamoDB and Redshift on AWS; Azure SQL, Cosmos DB, MySQL, PostgreSQL and MariaDB on Azure; Cloud SQL and BigQuery on Google Cloud.
- Cross-cloud VM restore between AWS and Azure, both directions, from NetBackup 10.5, for RHEL, SLES, Ubuntu and Windows.
Pros:
- Deep database coverage across clouds
- Restores between AWS and Azure run in both directions
Cons:
- Cross-cloud restore needs a 10.5 or later media server and drivers installed before backup, and doesn’t cover Google Cloud
- NetBackup is a large platform to run for a cloud-only estate
Pricing: NetBackup is quote-based. DataProtect as a Service is listed on AWS Marketplace at $29,100 for 12 months per 10 TB of back-end capacity, with a 10 TB minimum.
Bottom line: A natural fit for existing NetBackup shops extending into the cloud.
5. Rubrik Security Cloud
What it does: Rubrik’s SaaS platform for backup, recovery and data security across cloud, SaaS and on-premises.
Best for: Security-led teams that want backup and data security posture management from one vendor.
Key features:
- One control plane across AWS, Azure, Google Cloud and OCI, with one SLA policy model in place of per-service snapshot schedules. On AWS that covers EC2, S3, RDS, DynamoDB and Aurora, plus configuration such as VPC, IAM and KMS. On Google Cloud it includes BigQuery and Cloud Storage.
- Air-gapped copies in Rubrik Cloud Vault, a separate identity domain outside your accounts, with Retention Lock and Quorum Authorization so no single admin can shorten retention or delete a backup.
- Ordered recovery of an application’s stack: Rubrik maps an application’s dependencies (VMs, databases, object storage, networking, IAM) and recovers them in order from a clean point.
- Threat detection on backups, including anomaly detection and threat hunting to find the last clean recovery point.
Pros:
- AWS, Azure, Google Cloud and OCI under one control plane and one policy model
- Backup and data security in one platform
Cons:
- It’s SaaS, so Rubrik controls your data. Its control plane holds privileged access into your accounts, and your air-gapped copies sit in Rubrik’s storage, outside your accounts. A breach or outage at Rubrik becomes your risk, and Rubrik joins your audit scope as a third party holding your data
- Rubrik’s technical documentation is behind a login, so per-cloud workload lists and cross-cloud options are hard to check before you talk to sales
Pricing: Quote-based.
Bottom line: A strong fit when the security team owns backup and wants every cloud, including OCI, under one policy model.
6. Druva
What it does: A SaaS data protection platform built on AWS, covering cloud workloads, endpoints and SaaS apps.
Best for: AWS and Azure teams that want no backup infrastructure to run and also protect Microsoft 365 or endpoints.
Key features:
- AWS: EC2, RDS, S3, DynamoDB and EFS. Azure: VMs, SQL, Blob and Files.
- One console across both clouds.
- EC2 snapshots stay in your AWS account unless you turn on air-gap backup, which moves copies into Druva Cloud.
Pros:
- Nothing to deploy or patch
Cons:
- No native Google Cloud workload protection; Compute Engine appears only as a host for Druva’s agent-based file and database backup
- Air-gapped copies live in Druva Cloud, outside your accounts
- No documented cross-cloud recovery for cloud workloads
Pricing: Quote-based, measured in credits. One credit is 1 TB of deduplicated, compressed backup data stored for a month. Customers buying through AWS Marketplace or an MSP are billed differently.
Bottom line: Convenient for AWS and Azure teams that want backup as a service. Not a Google Cloud option.
7. The native tools: AWS Backup, Azure Backup and Google Cloud Backup and DR
What they do: Each cloud’s own backup service. AWS Backup protects AWS services (plus VMware through Backup gateway). Azure Backup protects Azure workloads and on-premises machines. Google Cloud Backup and DR protects Compute Engine, Persistent Disk, Filestore, Cloud SQL, AlloyDB and self-managed databases.
Best for: Teams running entirely in one cloud.
Key features:
- Nothing to deploy, and billing through the cloud you already pay.
- Deep coverage of each provider’s own services, including managed databases.
Pros:
- The lowest-effort start in a single cloud
Cons:
- None of the three protects another cloud’s workloads, so a multi-cloud estate runs three tools, three consoles and three sets of policies
- No cross-cloud recovery
Pricing: All consumption-based. AWS Backup charges per GB-month stored and per GB restored; AWS’s own examples use about $0.05 per GB-month for EBS backups in US East. Azure Backup charges a monthly fee per protected instance plus storage; an Azure VM of 50 to 500 GB costs $10 a month to protect in East US, before storage. Google Cloud Backup and DR lists prices per GiB-hour; in us-central1 that works out to about $0.045 per GiB-month for vault storage plus about $0.02 per GiB-month to manage a Compute Engine VM.
Bottom line: The baseline to beat in each cloud on its own. They don’t add up to a multi-cloud tool.
Which multi-cloud backup solution should you choose?
N2W is the better fit when production runs on AWS and Azure, you want one console and one license, backups have to stay in your own accounts, and you need ordered recovery you can test. Google Cloud VMs and disks come into the same console.
Veeam is the better fit when you already run Veeam Backup & Replication, or you need Google Cloud databases protected and cross-cloud restores in every direction.
Commvault is the better fit when you want one vendor for cloud, SaaS and on-premises data and have the team to run a large platform.
Cohesity NetBackup is the better fit when NetBackup already protects your data center and you want cloud databases in the same platform.
Druva is the better fit when you’re on AWS and Azure only and want SaaS with nothing to deploy.
The native tools are the better fit when one cloud holds nearly everything. Add a second tool once another cloud joins.
What multi-cloud backup costs you beyond the license
- Copies that cross clouds pay egress. Moving a backup from AWS to Azure is data transfer out of AWS, billed by AWS, on top of whatever the backup tool charges. Budget for it before you design a cross-cloud copy schedule.
- Parity gaps. Every tool on this list protects one cloud more deeply than the others. Map your workloads cloud by cloud before you choose, especially managed databases.
- One console per cloud adds up. Three consoles mean three sets of policies, credentials, alerts and reports to keep in step. That’s where coverage drifts and a new resource goes unprotected.
- Custody. A tool that stores copies in its own cloud adds a third party to your audit scope and may not let you choose the region.
What this looks like in practice
Aptean, an enterprise software company, started with N2W when it ran only on AWS. As it expanded into Azure, it kept N2W for both clouds and added Wasabi as an off-cloud storage layer independent of AWS and Azure. “N2W followed through on its roadmap, which gave me the confidence to stay with them as we expanded into Azure,” says Ravi Reddy, Sr Director, Cloud Ops and Technology Transformation. Read Aptean’s story.
Frequently asked questions
It depends on where your workloads run. For AWS and Azure with some Google Cloud VMs, N2W covers all three from one console, keeps backups in your accounts and starts at $249 a month for 20 instances. For deep Google Cloud database coverage or cross-cloud restores in every direction, Veeam and Commvault go further. For a single cloud, start with the native tool.
No. AWS Backup protects AWS services and VMware VMs through Backup gateway. Azure Backup protects Azure workloads and on-premises machines, and Google Cloud Backup and DR protects Google Cloud. Protecting more than one cloud with native tools means running each one separately.
Multi-cloud backup protects workloads in several clouds under one set of policies. Cross-cloud recovery restores a workload from one cloud into another, for example an EC2 instance into an Azure VM. Many tools do the first without the second, and the ones that do the second document specific directions and operating systems.
Yes, with tools that document it. N2W restores Ubuntu 22 and 24 EC2 instances into Azure as bootable VMs, and Windows instances as data disks, from a backup in a storage repository. Veeam and Commvault also document EC2-to-Azure restores, and NetBackup 10.5 restores between AWS and Azure in both directions.
Not necessarily. Some tools still need a separate deployment per cloud: Veeam runs one appliance per cloud and joins them in Veeam Backup & Replication. N2W runs only one deployment, and you add a cloud by adding an account. The native tools each cover only their own cloud.
It’s the strongest isolation a cloud backup can get. A copy in a separate account of the same cloud still sits under the same provider and control plane, so an attacker holding those credentials may reach it. A copy with a different provider, under different credentials, sits outside that blast radius. N2W does this by copying AWS backups to Azure Blob or Wasabi.
Three ways. Per protected instance (N2W, Veeam), where data volume doesn’t change the price and you pay your cloud for storage. Per TB stored (Druva credits, Cohesity DataProtect, Clumio, Veeam Data Cloud), where the vendor’s storage is usually included and the bill grows with data. Per GB plus per-resource fees (the native tools). Check what each price covers before you compare totals.