If you are using AWS for your disaster recovery, it's important to use AWS Elastic Disaster Recovery to ensure continuity in case of any failures. Having a strategic approach means considering the cost of disaster recovery as part of your overall planning. Overall, I rate the solution an eight out of ten.
AWS Elastic Disaster Recovery is a robust and reliable solution for disaster recovery needs. However, thorough planning and regular monitoring are crucial to maximizing its benefits and ensuring seamless operation. I rate it a nine.
Systems Administrator at a educational organization with 5,001-10,000 employees
Real User
Top 20
2024-02-23T19:51:37Z
Feb 23, 2024
The solution's replication was fine. We faced issues when we actually tried to utilize it. Every time we made a big change to any of the on-premise servers that were being replicated, we'd always have to change our replication engines, sizing, and the disc it's written on. Otherwise, it would end up taking around 30 days for a small monthly Windows update to replicate. I would not recommend CloudEndure Disaster Recovery to other users because of all the issues we had with the wrong sizing and the fact that there are better solutions in the market. Overall, I rate the solution a two out of ten.
Before implementing CloudEndure Disaster Recovery, my advice to others is to thoroughly read the documentation. We made some mistakes during our initial implementation, which caused problems and incurred additional costs. We attempted to failover a few servers just to test the solution but later realized that we couldn't simply delete them and resync from on-premises. We had to perform a full rollback, which we were not prepared to do at the time. As a result, we were unable to stop the server running on AWS and had to delete it entirely, causing us to start the synchronization process from scratch. This was a significant issue, especially since the server was a large five-terabyte space server. By carefully reading the documentation, you can avoid making such mistakes. I rate CloudEndure Disaster Recovery an eight out of ten.
Director, IT Operations & Information Systems at a media company with 501-1,000 employees
Real User
2018-07-23T07:36:00Z
Jul 23, 2018
I was able to build this up real quick and testing has always been successful as well. I have had issues bringing data back to the facility, but the restore has always worked with CloudEndure. Before you jump into it, test it and be aware of the bandwidth. We did have to put in a dedicated AWS direct line for our building. Make sure if you are going to put something in place like this that you have the proper bandwidth. The bandwidth is a constant upload communication to the AWS DR environment, so if you do not have the proper bandwidth, it will definitely eat up your internet line.
Data backup involves copying and moving data from its primary location to a secondary location from which it can later be retrieved in case the primary data storage location experiences some kind of failure or disaster.
If you are using AWS for your disaster recovery, it's important to use AWS Elastic Disaster Recovery to ensure continuity in case of any failures. Having a strategic approach means considering the cost of disaster recovery as part of your overall planning. Overall, I rate the solution an eight out of ten.
AWS Elastic Disaster Recovery is a robust and reliable solution for disaster recovery needs. However, thorough planning and regular monitoring are crucial to maximizing its benefits and ensuring seamless operation. I rate it a nine.
I would recommend AWS Elastic Disaster Recovery to other users.
The solution's replication was fine. We faced issues when we actually tried to utilize it. Every time we made a big change to any of the on-premise servers that were being replicated, we'd always have to change our replication engines, sizing, and the disc it's written on. Otherwise, it would end up taking around 30 days for a small monthly Windows update to replicate. I would not recommend CloudEndure Disaster Recovery to other users because of all the issues we had with the wrong sizing and the fact that there are better solutions in the market. Overall, I rate the solution a two out of ten.
We are using an older version from before AWS bought it. This is a good product. I'd rate it nine out of ten.
Before implementing CloudEndure Disaster Recovery, my advice to others is to thoroughly read the documentation. We made some mistakes during our initial implementation, which caused problems and incurred additional costs. We attempted to failover a few servers just to test the solution but later realized that we couldn't simply delete them and resync from on-premises. We had to perform a full rollback, which we were not prepared to do at the time. As a result, we were unable to stop the server running on AWS and had to delete it entirely, causing us to start the synchronization process from scratch. This was a significant issue, especially since the server was a large five-terabyte space server. By carefully reading the documentation, you can avoid making such mistakes. I rate CloudEndure Disaster Recovery an eight out of ten.
We are partners with Amazon. I'd rate the solution eight out of ten.
I rate CloudEndure Disaster Recovery an eight out of ten.
I would rate this solution a five out of ten.
I would recommend this product for cloud-based solutions. I can't recommend it for Azure. I would rate it an eight out of ten.
I was able to build this up real quick and testing has always been successful as well. I have had issues bringing data back to the facility, but the restore has always worked with CloudEndure. Before you jump into it, test it and be aware of the bandwidth. We did have to put in a dedicated AWS direct line for our building. Make sure if you are going to put something in place like this that you have the proper bandwidth. The bandwidth is a constant upload communication to the AWS DR environment, so if you do not have the proper bandwidth, it will definitely eat up your internet line.