# Is Veeam Data Platform worth it as an IT resilience orchestration platform for an enterprise team that needs combined backup, DR orchestration, and ransomware recovery, or does Zerto cover the same failover automation with less overhead?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">I've been considering whether Veeam's all-in-one solution for backup, disaster recovery (DR) orchestration, and ransomware recovery is suitable for an enterprise team, or if Zerto might be a better fit due to its lighter footprint and automation for failover. Both products are highly regarded in the <a class="a a--md" elv="true" href="https://www.g2.com/categories/it-resilience-orchestration-automation-itro">IT Resilience Orchestration Automation (ITRO)</a> space, and reviewer feedback generally aligns on the trade-offs involved.</p><ul>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/veeam-data-platform/reviews"><strong>Veeam Data Platform</strong></a> (4.6 stars, 724 reviews): G2 reviewers consistently value backup, replication, orchestrated recovery, immutable storage, and ransomware tooling (cleanroom recovery, anomaly detection) in one platform, which is exactly the combined-capability ask. The recurring counterpoint is cost and complex licensing plus operational overhead at scale, so the breadth comes with weight.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/zerto/reviews"><strong>Zerto</strong></a> (4.7 stars, 75 reviews): G2 reviewers praise near-zero RPO replication and simple, fast orchestrated failover and testing, and several note it needed fewer teams to run DR than their previous tooling. It's lighter on the failover job specifically, though it leans on separate backup tooling for full coverage, and its journals consume storage.</li>
</ul><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">If you want alternatives in the same bracket, <a class="a a--md" elv="true" href="https://www.g2.com/products/vmware-live-recovery-vlr/reviews"><strong>VMware Live Recovery (VLR)</strong></a> (4.5 stars, 136 reviews) is worth a look for VMware-heavy estates wanting unified DR and ransomware recovery, and <a class="a a--md" elv="true" href="https://www.g2.com/products/commvault-cloud-rewind/reviews"><strong>Commvault Cloud Rewind</strong></a> (4.7 stars, 18 reviews) targets automated, dependency-aware cloud rebuilds if your critical apps are cloud-native.</p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">The honest read: pick Veeam if consolidating backup, DR, and ransomware into one platform is the goal, and you'll use the breadth; pick Zerto if failover automation with less overhead is the priority, and you already have backup covered.</p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Which are you optimizing for, one platform that does everything, or the leanest possible failover layer? And do you already have a backup tool you're happy with?</p>

##### Post Metadata
- Posted at: 23 days ago
- Author title: Marketer
- Net upvotes: 1


## Comments
### Comment 1

&lt;p&gt;The deciding factor is whether reducing tool sprawl outweighs Veeam’s added licensing and management complexity.&lt;/p&gt;

##### Comment Metadata
- Posted at: 11 days ago
- Author title: Marketing Executive





## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: about 13 years ago
  - Comments: 4


