AWS Elastic Disaster Recovery Reviews

I've used the solution for migrations. I worked for a company that went Chapter 13, and we had to migrate into the cloud.

I've used it for disaster recovery as well. 

It is easy to use. I haven't had any issues with the client and console. 

When we tested it, it worked fine. 

The solution is free to use. 

The setup is pretty straightforward.

It's stable.

The solution is scalable.

Technical support is helpful and responsive. 

When I tested a failover, it didn't work. I set up a test, deleted the source, and went to fail it back, and it didn't work. 

The solution doesn't need any new features.

AWS is no longer using the solution anymore. 

I've been using this solution for about two years, before AWS bought it.

I'd rate the stability nine out of ten. There are no bugs or glitches and it doesn't crash or freeze. 

I'd rate the scalability nine out of ten.

We do not have plans to increase usage at this time. 

I'm not sure how many people are using it. 

Technical support was excellent. 

Positive

The initial setup was straightforward. It was not complex at all. 

I did witness an ROI while using it. 

The solution was free to use. It was just the price of the storage, and that was it. It gave us 2,000 licenses, which is enough for anybody.

We are using an older version from before AWS bought it. 

This is a good product. I'd rate it nine out of ten.

My purpose for utilizing CloudEndure Disaster Recovery is to streamline our disaster recovery procedure. In the event of any issue arising in our on-premise infrastructure, we aim to quickly switch over to AWS. Our setup is designed to facilitate this process, and we frequently conduct tests to ensure its reliability. While we have yet to experience an actual disaster, we conduct multiple tests annually. Furthermore, as a partner, I implement this solution for our clients. Currently, we have five customers using it, with the number steadily increasing.

We have the solution deployed on-premise located on the Amazon AWS infrastructure.

Although we have not yet utilized it for an actual disaster, one of our clients has been affected by ransomware or similar attacks. It is crucial to be able to quickly restore their infrastructure outside of their primary infrastructure, and that is exactly what we are accomplishing with this solution. Since the client we are working with is not a large enterprise, they do not have the financial resources or budget to create a secondary site for disaster recovery. Our solution enables them to be prepared without having to allocate funds for a complete data center to perform the restoration.

The most valuable aspect of CloudEndure Disaster Recovery is its instant block replication feature. This allows us to perform live block verification and eliminates the need to concern ourselves with recovery point objectives. This capability is particularly advantageous for critical workloads.

The failback could be improved. It should be more intuitive.

I have been using CloudEndure Disaster Recovery for approximately one and a half years.

The stability could be improved. There is sometimes a lag in the replication and we have to reinstall the agent. It does not happen all the time but when it does in a particular server we need to reset it. A lot of our customers are relying on this solution and this is not a good scenario.

I rate the scalability of CloudEndure Disaster Recovery a ten out of ten.

I have worked with the support once and I had a good experience. 

I rate the support of CloudEndure Disaster Recovery a nine out of ten.

Positive

The initial setup of CloudEndure Disaster Recovery was simple with the new interface.

Both the customer and I are responsible for implementing the solution.

We have seen a return on our investment. When compared to the cost of building a complete data center, the solution is much more affordable. However, it can still be expensive for small customers since the snapshots require significant storage space. While the solution itself may not seem costly on paper, keeping several days of snapshots can increase the price. This is due to AWS EDS storage costs since that is what we are using for the snapshots.

I rate the price of CloudEndure Disaster Recovery a six 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 use it for disaster recovery. It appears to be working fine for us.

We were in a different environment which had its own tool for performing disaster recovery. When we moved into AWS, we decided to move forward with this tool for disaster recovery. 

It provides our disaster recovery solution. It works fine in our tests.

Disaster recovery. It is what we have the product for.

Sometimes, one of the servers will get behind for one reason or another, and it does not notify us when that happens. This could be a helpful improvement.

Sometimes a server will get a bit behind. 

There has never been any issues with scalability. They license us on a per machine basis. We have a set number of machines, which we have licensed.

Technical support has been very good. They usually respond quickly to our requests.

Our group did not use a different solution, but our data center had a different solution. When we went to AWS, the data center people were not able to support us with a disaster recovery solution, so we looked and chose CloudEndure.

The initial setup is really straightforward.

We were happy with the pricing that they gave us.

We investigated several different options and chose this one.

Follow the write-up. It is very good. 

Disaster recovery.

I wouldn't necessarily say there has been a particular improvement. This is a DR solution, so we are able to meet the disaster recovery requirements of our applications.

• Ease of use
• Reliability
• Cost
• Stability

Definitely there should be better logging. From a customer perspective I would like to see more logs on what is happening. If there is an issue, I would like to know what the problem is. Right now, we have to depend on the support of the vendor to check and let us know, because we don't have access to a lot of logging information.

Also the UI could be a little sleeker.

There have been no issues. 

Scalability is pretty good. It's seamless; it can do it automatically. 

Their phone support is pretty good. The only thing I would like to see is, they don't have a formal ticketing system. There is no way I can go back and see what questions we had six months back, what issues we had, and how they were resolved. But otherwise, the support is fine.

This is the first solution we are using in the cloud. In the datacenters there are other solutions used, but this is the first time we are using a DR solution in the AWS cloud.

It was straightforward. It was pretty easy.

I feel the product's pricing is a good value. Licensing is pretty straightforward.

We went looking at other options but the market is not really mature yet. I don't think there are numerous options, at least for me, on the public cloud side. We did look at a couple of other options, but we didn't go into detail, to evaluate them. We evaluated CloudEndure and we were pretty much happy with it so we just went with it.

We did look at Dell EMC, NetBackup, things like that, but we didn't really pursue them.

Planning ahead is important, just making sure you really understand what you need before finalizing the solution.

The ability to replicate our database and our data from one cloud to another is the most valuable feature. We are using it for disaster recovery so we replicated all our databases from Rackspace Cloud to Amazon Cloud. We moved from Rackspace to AWS because we didn't want to end up in a situation where we would be locked, so we chose to replicate our databases to another public cloud.

We are currently only using it for disaster recovery but are planning to migrate.

It could be a bit more automated. When we wanted to start using replicated data, the process was complex. For example, with Amazon we needed to stop replication of CloudEndure, and needed to create another instance of our server. Only after that are we able to start using the data, and by then the data is outdated. Therefore, the data becomes outdated quickly. To actually start replicating the data, I need to start a manual process which takes time.

We've used it for four months so far primarily for disaster recovery.

We had issues, but it was because we needed to use a specific instance of a server in order to make CloudEndure work perfectly. I suggest that you use experts when you start using it.

It’s very stable. We haven’t experienced any problems since the system became operational.

We're only replicating database servers – 20 servers. However, in total data, our website is ranked #475 in the world. All our operational databases are replicated using CloudEndure.

It's very high. We have good relations with all levels of management in the company, including the CTO and their architects, so their customer support has been great.

I've never heard of any complaints.

We tried a native solution from Rackspace but it failed.

We set it up as part of a POC and it was easy.

We implemented it ourselves in-house.

It's disaster recovery so you’d need to look at the business data. I'd say that the ROI is extremely high and valuable.

We tried native solutions before, and once we migrate to AWS, we'll try their native solution as well, but we'll still need CloudEndure to replicate between our data centers.

We use CloudEndure Disaster Recovery for backing up our data and for recovery. My customers have some databases. They were looking for the DR solution.  CloudEndure is easy, and block-level replication will happen. Whenever my primary site goes down, the DR site will be up, and the data will be there. The DR data is there, and it will be a replication back will be my primary site. 

I have been using CloudEndure Disaster Recovery for approximately five years.

The solution is dependent on the network bandwidth. For example, if they have a bandwidth of 10Mbps the solution will run a little heavier. If the bandwidth is good the solution runs well.

CloudEndure Disaster Recovery is charging clients $20 to do the DR backups. It is an expensive solution.

I rate CloudEndure Disaster Recovery an eight out of ten.

I am a solution architect and I analyze customer's information in order to suggest products for them. CloudEndure Disaster Recovery is one of the solutions that I am familiar with.

It is used for backup and restore operations.

For regular backup and restore solutions, this product is fine.

I would like to see better support for creating and working with archives. Right now, it is difficult and painful to do. When you are working with multiple terabytes, there are no good solutions.

I have been using CloudEndure Disaster Recovery for the past five or six years.

I have worked with many different vendors and the choice of solution depends on the customer's requirements.

I would rate this solution a five out of ten.

The entire company uses it for reports we are sent to research. We also have reports that we write for various clients and it helps us look for our research requirements. All of the data and information is stored on the cloud. There were a few instances in which the entire system got hacked. There was an issue with the system, the hard drive, so we used the cloud backup to retrieve all the information from three to four years down the line.

The three things that could improvement are:

• The user interface
• Customer support
• Recovery time for the current customer query

We have been using CloudEndure Disaster Recovery for the last two years. 

It is stable. 

It is scalable for large nodes. 

The initial setup is pretty straightforward, it's not complex.

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.