We performed a comparison between Azure Site Recovery and Druva Phoenix based on real PeerSpot user reviews.
Find out in this report how the two Disaster Recovery as a Service solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The documentation is good, and it can be integrated with other products."
"The solution is secure, reliable, and scalable."
"Azure Site Recovery allows my company to save around 30 percent of the time on every VM that we need to back up and restore."
"It is a very stable product and very scalable."
"They're moving a lot of their workload to cloud and aiming for a seamlessly integrated product."
"Our primary use case is for disaster recovery and business continuity and disaster recovery (BCDR)."
"Site Recovery's most valuable features include its user-friendly console and the ease of migration."
"Azure Site Recovery helps to save costs."
"The most valuable features of Druva Phoenix are the simple portal to log in and flexibility."
"I would definitively say that we have been able to make our people more productive by at least 30%."
"Druva Phoenix is easy to use and easy to start with."
"Once you set it up and you tell it exactly what needs to be backed up, you literally forget about it. It sends you emails and notifications of the current status of the jobs."
"I found the cost-effectiveness of Druva Phoenix to be its most valuable feature, especially when compared to on-premises backup solutions."
"In the newest version of Azure Site Recovery, the configuration was a little more complex, so this is an area for improvement."
"I would like to see more security features."
"The primary area for improvement in Azure Site Recovery is its pricing."
"The tool should improve synchronization."
"I conveyed the feedback to the agent, suggesting an increase in the agent count in our VNS in the USA. I also addressed notification concerns, as some issues didn't trigger alerts during a recent call."
"Could have more integration with other platforms."
"Azure Site Recovery's deployment is complex. There are a lot of bugs, and it needs to improve stability."
"Site Recovery's scalability could be improved."
"They were able to give us a very reasonable price considering we were non-for-profit organizations, however, there is always room for improvement on that cost."
"There is room for improvement in the reporting aspect of Druva Phoenix."
"Druva Phoenix should include a few reporting features that it doesn't provide currently."
"Druva Phoenix is optimized to work with x86 platforms, making it unsuitable for backing up non-x86 architectures like AIX. The solution is primarily designed for physical Linux and Windows systems based on the x86 architecture, as well as virtualized Windows and Linux environments. However, if you have an AIX system, it cannot be deployed in the cloud, and therefore, backing it up in the cloud is not a concern."
Azure Site Recovery is ranked 1st in Disaster Recovery as a Service with 18 reviews while Druva Phoenix is ranked 7th in Disaster Recovery as a Service with 5 reviews. Azure Site Recovery is rated 8.2, while Druva Phoenix is rated 8.8. The top reviewer of Azure Site Recovery writes "Useful for restoration purposes that ensures that the users get to save a lot of time". On the other hand, the top reviewer of Druva Phoenix writes "Cost-effective and has excellent technical support". Azure Site Recovery is most compared with Veeam Backup & Replication, VMware SRM, Zerto, AWS Elastic Disaster Recovery and VMware Cloud Disaster Recovery, whereas Druva Phoenix is most compared with Druva inSync, Azure Backup, Veeam Backup & Replication, AWS Backup and Rubrik. See our Azure Site Recovery vs. Druva Phoenix report.
See our list of best Disaster Recovery as a Service vendors and best Disaster Recovery (DR) Software vendors.
We monitor all Disaster Recovery as a Service reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
