NetApp Disaster Recovery
7.0#4 in disaster recovery softwareFrom $0.03 a monthWebSelf-hosted
VisitNetApp Disaster Recovery vs Veeam Recovery Orchestrator
Veeam Recovery Orchestrator
7.2#1 in disaster recovery orchestration softwareFree planFree planWebAPISelf-hostedWindows
VisitWhat both publish
| Fact | NetApp Disaster Recovery | Veeam Recovery Orchestrator |
|---|---|---|
| Company size | NetApp’s LinkedIn profile lists the company size as 10,001+ employees. | Veeam's company page describes its workforce as more than 7,000 employees. |
| Founded | 1992 | 2006 |
| Headquarters | San Jose, California, United States | G2's Veeam seller profile lists Kirkland, Washington as the headquarters location. |
| Rating on G2 | 0 out of 5 from 0 reviews, as shown on G2’s disaster recovery category listing for the product. | 4.6 out of 5 from 752 reviews for Veeam Data Platform; this listing covers the broader platform, not Orchestrator alone. |
| Support | The product page offers chat with a NetApp expert, documentation, a test drive, and a free trial. | Veeam offers email and phone technical support to customers on maintenance and during the official evaluation period. |
NetApp Disaster Recovery plans
- 30-day free trialFree
- Free TrialFree
- 36 Month Subscription$0.03 a month
- 12 Month Subscription$0.04 a month
- Pay-As-You-Go$0.04 a month
Veeam Recovery Orchestrator plans
- Evaluation licenseFree
- NFR licenseFree
- Perpetual license—
- Rental licensePriced on request
- Subscription license—
- Veeam Recovery Orchestrator (licensed through Veeam Data Platform)Priced on request
Pick NetApp Disaster Recovery if…
It suits teams protecting VMware or Kubernetes workloads across the listed on-premises and cloud recovery scenarios. Capacity-based licensing may be relevant to teams evaluating protection by source volume usage rather than VM or application count.
Pick Veeam Recovery Orchestrator if…
It suits organizations coordinating and testing recovery for supported virtual and physical Windows workloads. Teams should account for its license requirements and Windows Server deployment.