

HPE Zerto Software and AWS Elastic Disaster Recovery are leading products in the disaster recovery space. AWS Elastic Disaster Recovery holds a slight advantage due to its integration and advanced features. Users prefer AWS for its comprehensive capabilities, whereas HPE Zerto Software attracts with competitive pricing, making it appealing for cost-sensitive businesses.
Features: HPE Zerto Software offers continuous data protection, ransomware protection, and multi-cloud support. AWS Elastic Disaster Recovery excels with seamless AWS integration, automated orchestration, and real-time replication ensuring minimal data loss. Each product provides unique capabilities tailored to different user needs.
Room for Improvement: HPE Zerto Software could enhance Hyper-V support and improve its cloud-native integration. AWS Elastic Disaster Recovery may need to expand compatibility with non-AWS ecosystems and reduce setup complexity for new users. These improvements could broaden their customer base and improve user experience.
Ease of Deployment and Customer Service: AWS Elastic Disaster Recovery seamlessly deploys within AWS, making it ideal for users already in the AWS cloud. HPE Zerto Software provides flexibility across different environments, catering to non-cloud-native enterprises. AWS's integrated support enhances the user experience within its ecosystem, while HPE Zerto offers robust external analytics capabilities.
Pricing and ROI: HPE Zerto Software is known for its competitive pricing and flexibility in cost-efficient deployments. AWS Elastic Disaster Recovery may involve higher initial costs, yet it promises robust ROI through efficiencies and resilience via automation. The choice often hinges on immediate budget constraints versus long-term value and resilience offered by each product.
However, with AWS Elastic Disaster Recovery Service being a native service, integration is seamless, highlighting the return on investment.
The recovery process requires fewer people and much less time, which has saved my organization engineering effort and operational time.
We no longer have to schedule employees on weekends since the system automatically triggers alerts, allowing engineers to respond as needed.
Before, it was a huge cost. It was several thousand dollars to do a DR test, whereas now, I click a button.
It saves us a lot of time and gives us the ability to perform other DR plans for other systems.
It's not only in the cloud; it's DR as a service, which means that the recovery operations are performed by a dedicated team specializing in this area.
In case of any issue, they are ready to provide support within the defined SLA timeline.
Helping us in troubleshooting each and every step if we face any issues.
Higher tiers offer faster response time and more direct technical help.
I have never had an issue that was not resolved, and I have never been in a situation where they did not respond.
I would give them a rating of ten because it represents the highest level of support based on the technical knowledge of the support team, response time, and effectiveness of the provided resolutions.
When I open a ticket, I usually get a call within an hour or two.
We can expand it to multiple data centers or different areas such as EMEA and APAC.
AWS Elastic Disaster Recovery is scalable because it can protect and replicate multiple servers and workloads, and it runs on AWS infrastructure.
The scalability is quite good and we were able to scale this service to many of the services that our company uses.
I would rate it a ten out of ten for scalability.
Customers need to follow good engineering practices for optimal product use.
By adding more hosts and installing VRAs on each, tasks can be efficiently managed.
It is very good and very reliable.
AWS is not difficult, but the cost associated with replicating data to another region can be significant.
AWS Elastic Disaster Recovery is stable.
I promptly delete the malfunctioning elements and set them up again to resume replication, ensuring stability.
The ease of use was so good with Zerto that they were able to migrate things much quicker.
It is very reliable.
Our RPO improved from approximately three to four hours to less than one minute.
This would detail user activity directly in the ACL console for easier debugging and auditing.
It would be beneficial to get some insights when a disaster happens, including identification and probable solutions to ensure effective recovery.
If I have 350 objects that I am protecting, I would like Zerto to be able to fire them up in one order, rather than having to manually bring them up in a sequence.
If the host has a lot of VMs on it, there may not always be enough time to relocate all of the VMs from a protection group standpoint to other hosts before the replication appliance that Zerto uses to manage that powers itself down.
If HPE Zerto Software has it built-in where we're going to vCenter and you click on it, it will build the VPG and indicate configuration requirements, that would be amazing.
In my case, since the cloud is basically a pay-as-you-go model, we only pay for the replication storage, data transfer, and small staging instances.
Continuous replication minimizes data loss and the cost-efficient staging environment helps reduce infrastructure expenses compared to maintaining a full secondary disaster recovery site.
There is definitely a scope of improvement, and for year-end licensing, they should definitely improve the cost.
If you want a good-quality tool that is robust and does a good job for you, you have to pay a higher price to get that, and Zerto is no different.
However, it can become quite expensive when you start looking at the number of workloads you have in the environment and what you would like to do.
Zerto is easier to set up and use, and it's less expensive.
AWS Elastic Disaster Recovery supports a wide range of source environments, including VMware, Hyper-V, physical servers, and other cloud providers, making it versatile for different IT infrastructures.
The low RPO at a seconds-level replication and a fast recovery with a low RTO provide the most cost-effective way, paying mostly for storage until failover.
Overall, the best combination of AWS Elastic Disaster Recovery is its near real-time replication and quick recovery testing, and this makes the service very useful in real-world scenarios.
Zerto offers excellent technical support with responsive and helpful experts.
If we were attacked, I could revert to a backup from five seconds before the attack, and no one would know we were attacked.
The replication time and the minor amount of time it takes to sync a new server outside of any of my huge 40-terabyte boxes is ridiculously quick.
| Product | Mindshare (%) |
|---|---|
| HPE Zerto Software | 7.3% |
| AWS Elastic Disaster Recovery | 2.3% |
| Other | 90.4% |
| Company Size | Count |
|---|---|
| Small Business | 7 |
| Midsize Enterprise | 5 |
| Large Enterprise | 11 |
| Company Size | Count |
|---|---|
| Small Business | 90 |
| Midsize Enterprise | 92 |
| Large Enterprise | 195 |
CloudEndure Disaster Recovery enables real-time replication and rapid recovery to enhance organizational resilience. Key features include block-level data replication, ease of use, cost-effectiveness, and automated recovery orchestration. Users benefit from increased efficiency, improved workflows, and enhanced data management, significantly improving organizational performance and business continuity.
Zerto is used for disaster recovery, business continuity, data migration, and ransomware recovery, providing continuous data protection and near real-time replication. Valued for ease of use, efficient failover processes, and versatile integration, it enhances organizational efficiency, reduces errors, and boosts productivity.
We monitor all Disaster Recovery (DR) Software 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.