Skip to main content
Druva Documentation

How Phoenix Cloud DRaaS is different than traditional DR

Phoenix Editions: File:/cross.pngBusiness         File:/tick.png Enterprise     File:/tick.pngElite
(Purchase Separately)

Phoenix Cloud-based Disaster Recovery feature offers a compelling alternative to the traditional disaster recovery. Unlike the traditional disaster recovery, Phoenix DRaaS eliminates the infrastructure overhead and significantly reduces downtime by enabling IT to harness the power of the public cloud and providing an on-demand solution for immediate spin up and failover to any AWS region.

Traditional disaster recovery

  • Expensive: The traditional disaster recovery setup comprises a secondary physical disaster recovery site that involves huge upfront CAPEX. It also requires an identical hardware system and software patches as that on the primary site that make the entire proposition of maintaining a secondary site cost-prohibitive.
  • Limits geographical reach for disaster recovery: Disaster recovery site cannot span more than 30-60 miles away from the primary site, which is insufficient for coherent disaster recovery planning where customers want more protection than just a few miles and for a few critical applications.
  • Heavy on IT resource requirements: The traditional disaster recovery requires IT expertise to perform complex processes for disaster recovery testing.
  • Operates in the event of a disaster: The disaster recovery site operates only in the event of a disaster. It requires an overhead of complex processes to bring the site live, which may compromise data and business continuity.
  • Disaster recovery site failure: Additional cost may incur to start operations at disaster recovery site in case of disaster recovery site failure. It may jeopardize data and business continuity.

Phoenix disaster recovery

  • Cost-effective: Disaster recovery site based on public cloud infrastructure such as AWS, drastically reduces the overall CAPEX of implementing a DR solution, thereby making it accessible to organizations, which previously had no disaster recovery strategy in place due to costs involved in the traditional setup.
  • Enables extensive geographical reach: Owing to the public cloud infrastructure, the location of the disaster recovery site can now be as far as across continents from the primary site.
  • Provides secure failover: Failover occurs in the customer-managed AWS account with already established security and network settings. Unlike most DRaaS vendors, Druva does not have any access to the failover environment.
  • Simplified workflows: Phoenix DRaaS workflow allows administrators to preconfigure failover settings such as VPC, subnet, security groups, and IP assignment, making actual failover a simple one-click operation.
  • Development and test use: Phoenix DRaaS facilitates easy setup of the Development/Test lab environments that are identical to the production systems. It also eliminates the overhead of setting up labs in traditional data centers.
  • Migration: Phoenix development allows to seamlessly migrate workloads into the cloud with minimal manual customization.
  • Automated disaster recovery sites: Phoenix DRaaS provides automated disaster recovery sites that are brought online in a few minutes, which avoids data loss and ensures business continuity.
  • Robust failback: Phoenix DRaaS enables administrators to recover virtual machines with a single click in the data center and thus reduces the need of a managed DR site, onsite hardware, and heavy administration and maintenance.