CloudEndure Disaster Recovery Review

The ability to replicate our database and our data from one cloud to another is the most valuable feature.


What is most valuable?

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.

How has it helped my organization?

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

What needs improvement?

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.

For how long have I used the solution?

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

What was my experience with deployment of the solution?

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.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

Customer Service:

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.

Technical Support:

I've never heard of any complaints.

Which solution did I use previously and why did I switch?

We tried a native solution from Rackspace but it failed.

How was the initial setup?

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

What about the implementation team?

We implemented it ourselves in-house.

What was our ROI?

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.

What other advice do I have?

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.

**Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Add a Comment
Guest