Our human resources solution is used by higher management competency. This is critical to the organization since it is used by higher management. ITM is really essential for the organization.
External reviews
12 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Managed services with seamless integration and good reliability
What is our primary use case?
What is most valuable?
For the past year, I have been using AWS, as there was previously no native replication service available. Initially, they offered services like CloudEndure, which was a third-party service. This caused problems with integrations with existing servers. However, with AWS Elastic Disaster Recovery Service being a native service, integration is seamless. Moreover, since it is a managed service, I reduce my time to manage infrastructure and applications, which adds another benefit.
What needs improvement?
Since I have to view everything on the console, the previous application solutions like IBM and Sanavi showed the RPO and RTO status directly. In AWS Disaster Recovery Service, these details are not available, making it difficult to check my replication status. I have to calculate whether my data is replicated to the Adarabad region or not. These features, if available in AWS, would be beneficial.
For how long have I used the solution?
I have been using it since 2019.
What do I think about the stability of the solution?
AWS is not difficult, but the cost associated with replicating data to another region can be significant. This is due to services like the duplication server, which continuously runs in AWS. I have more than 200 hosts, including email solutions and others, which contribute to the high cost. Cost is a concern. Otherwise, the service is reliable.
How are customer service and support?
Customer service is quite helpful. I have AWS enterprise-level support, which is very beneficial. In case of any issue, they are ready to provide support within the defined SLA timeline.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Earlier, I worked with IBM Sonavi. I stopped using it since we moved from on-premise to cloud. It's not in use right now.
How was the initial setup?
There were no issues during the initial setup.
What about the implementation team?
The implementation is actually managed by our partner. I have taken a rate per user storage. The licensing part is completely managed by the partner.
What was our ROI?
For the past year, I have been using AWS, as there was previously no native replication service available. Initially, they offered services like CloudEndure, which was a third-party service. This caused problems with integrations with existing servers. However, with AWS Elastic Disaster Recovery Service being a native service, integration is seamless, highlighting the return on investment.
What's my experience with pricing, setup cost, and licensing?
The setup is actually managed by our partner. I have taken a rate of per user. Licensing is completely managed by the partner. I am paying per user and per GB storage cost, while the infrastructure cost is separate.
What other advice do I have?
Although no financial benefit from using it has been observed, I recommend the solution. The overall product rating is eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Prevents security breaches and covers data leak and recovery
What is our primary use case?
If there is a data leak, incident, or compliance issue, auditors may want to verify whether there is a policy and plan in place for utilizing AWS Elastic Disaster Recovery.
As part of a strategic approach, I have been part of a team ensuring compliance with various regulations, including HIPAA compliance. I have contributed to developing strategies to satisfy audits and inspections from various government bodies. These strategies outline the plans and features to be utilized if needed.
What is most valuable?
AWS, as a cloud platform, helps build trust in its services. There have been incidents where clients using Amazon services faced security breaches, but these stories seem more frequent with Microsoft. This might be a personal bias, and others may have different experiences. AWS proactively protects its reputation by addressing issues and investing heavily in its tools, app tech, and engineers.
What needs improvement?
Pricing could be improved.
What do I think about the stability of the solution?
The solution is stable because we haven't had any incidents.
What do I think about the scalability of the solution?
It's scalable because of the value and investment it has made in terms of capacity.
What was our ROI?
Every business survives because of its reputation. In case of any disaster, AWS cannot guarantee 100% security, but it helps protect the company's reputation. It also assists in providing remedies to solve any particular problems that may arise. AWS is a platform that supports businesses.
What's my experience with pricing, setup cost, and licensing?
It has pay-as-you-go pricing. The cost will be different if you are not utilizing it as often as possible because there are costs beforehand and after an incident.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
Cloud-based solution enhances company backup but comes with high costs
What is our primary use case?
We are using AWS Elastic Disaster Recovery for backup purposes in our company.
How has it helped my organization?
AWS Elastic Disaster Recovery is convenient because it is cloud-based technology.
What is most valuable?
The strong points are the stability and scalability of the solution, as well as the convenience of it being cloud-based.
What needs improvement?
The cost of AWS Elastic Disaster Recovery is seen as expensive.
For how long have I used the solution?
We have been using AWS Elastic Disaster Recovery for five or six years.
What do I think about the stability of the solution?
I rate the stability of AWS Elastic Disaster Recovery as nine out of ten.
What do I think about the scalability of the solution?
I rate the scalability of AWS Elastic Disaster Recovery as nine out of ten.
How are customer service and support?
The customer service and technical support for AWS are very good and helpful. I rate it ten out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We did not work with any other products before AWS.
What about the implementation team?
We use a third-party consultant company to help with integration.
What's my experience with pricing, setup cost, and licensing?
The pricing of AWS is considered expensive compared to other options.
Which other solutions did I evaluate?
We have also used Microsoft Azure as an alternate solution.
What other advice do I have?
I would recommend AWS Elastic Disaster Recovery to other users.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Exceptional Solution in Disaster Recovery
What do you like best about the product?
CloudEndure Disaster Recovery is an exceptional solution that offers businesses the peace of mind they need in the face of unforeseen disasters. As a customer who has relied on this platform, I can confidently say that CloudEndure's capabilities go above and beyond in safeguarding critical data and ensuring business continuity.
One of the most impressive aspects of CloudEndure Disaster Recovery is its ease of implementation. The platform seamlessly integrates with existing infrastructure, regardless of the cloud provider or on-premises environment being used. Setting up the solution is straightforward, thanks to its user-friendly interface and comprehensive documentation. From initial setup to ongoing maintenance, CloudEndure simplifies the complex task of implementing and managing disaster recovery.
One of the most impressive aspects of CloudEndure Disaster Recovery is its ease of implementation. The platform seamlessly integrates with existing infrastructure, regardless of the cloud provider or on-premises environment being used. Setting up the solution is straightforward, thanks to its user-friendly interface and comprehensive documentation. From initial setup to ongoing maintenance, CloudEndure simplifies the complex task of implementing and managing disaster recovery.
What do you dislike about the product?
Complexity for Non-Technical Users
Cost
Lack of Integration
Cost
Lack of Integration
What problems is the product solving and how is that benefiting you?
Data Loss Prevention
Business Continuity
Business Continuity
CloudEndiure - A World Class Disaster Recovery Solution
What do you like best about the product?
The best thing about CloudEndure is how easy it is to setup and enable Disaster Recovery for any workload inside our outside AWS.
What do you dislike about the product?
I haven't yet faced any issue with CloudEndure till now and hence there is nothing to dislike.
What problems is the product solving and how is that benefiting you?
CloudEndure is helping me to provide Disaster Recovery Solution to my customers for their mission critical applications.
It has saved us money from having to buy hardware for disaster recovery
Enterprise disaster recovery.
How has it helped my organization?
We went from an organization with minimal to no disaster recovery. I was able to spin up the disaster recovery environment with AWS rather quickly and meet business requirements. We continue to build off of it as well. It is in place, and it is simple enough where we can continue to add licenses and systems, and swap systems out too. As we remove some servers, we can always add new ones in with the same license.
What is most valuable?
The speedy, quick configuration and installation was the initial reason for the product and what I enjoyed about it. Now, it just continues to be simple and works well.
What needs improvement?
One item that they did fix was, and this was when we first started, they had only one type of license. Then they did come out with a Tier 2 type of license, which costs a little less money. It updated a little less frequently, which seems to fit our needs. That was definitely helpful.
There are some servers where we do get failures with the CloudEndure client. I don't know necessarily if it's the CloudEndure issue, but it's something that my engineers fixed on our end. It's always something that's easily repairable, though. There is a constant update of the servers.
It's a fairly simple product once the infrastructure's in place. We did hire a third-party to help us build the AWS infrastructure to work with CloudEndure, but once it was up and running, it pretty much runs on its own now.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
There were no stability issues, once it was up. We built the environment once, but that was because we migrated to the additional licenses. However, once it was up, the only instability was just some random servers. There was pretty much always fixed on the client side, and usually it was Linux machine.
I don't recall any CloudEndure crashes with server usage.
What do I think about the scalability of the solution?
We just did an upgrade, and it went fairly smoothly. Once it is on the machines, if we are not changing anything around, it seems to work fine. Even the reporting features on the dashboard are pretty cool. You can see what state all the servers are in. You can get reporting if something is not updating, so the visual stations are good as well.
How is customer service and technical support?
Technical support has always been responsive. We engage with a third-party to work with us on CloudEndure and the infrastructure, so we work with them most of the time. For any of our dealings with CloudEndure, they have been pretty responsive.
Which solutions did we use previously?
We had an old school type of DR with replication.
Since we put CloudEndure in place, which is our DR for our Tier 1 and 2 servers, replicating out from our facility to AWS, and it has been bare-metal to bare-metal type of disaster recovery. This is our first cloud-based DR solution.
How was the initial setup?
The setup was fairly simple, and we spun it up pretty quickly. We did have a third-party help us, so most of the effort was putting into building the AWS environment, but that wasn't too difficult. We designed the AWS environment, then on a smaller subset, we installed the client and the client started replicating, and that was our initial test. Then from there, we kept adding servers.
What was our ROI?
It helped us build our disaster recovery. Our organization was moving towards the cloud in a lot of areas, so it saves us ample dollars from having to buy hardware for disaster recovery. We even used it for other cloud systems for disaster recovery as well. The other piece to it was not relying on any specific type of server. It worked on our Window servers and our Linux servers, because it is versatile.
What's my experience with pricing, setup cost, and licensing?
The pricing is better now that they had come out with the Tier 2 which replicates a little less often. In comparison to what I would have been spending with any other type of solution, the pricing is fair.
Where the price adds up, there are CloudEndure licenses, then there is the AWS environment, and finally, there is the AWS storage, so cumulatively, it adds up. The license would be better if it cheaper. I do not think it is great pricing, but I would say it's fair.
Through my third-party, I locked-in for the long-term. I received some price discounts from a three-year deal versus a one-year, which I probably question a bit now. It forced us into a certain amount of licenses. From year-to-year, I can't really play with it that often or drop it if needed. I am sort of locked into a certain amount of serviceable licenses because of the long-term deal. This has nothing to do with CloudEndure. This is between the third-party and me.
Which other solutions did I evaluate?
When we first went with this, it was we did lay out three options. We had somebody help us with making this decision. It was CloudEndure, it was moving towards a metal to metal type of DR solution, and the other one that we had up and running was VMware. I don't even know if they sell the product anymore, but VMware had a DR type of solution. We used the three of those, and we were testing them. VMware didn't seem to cut it. From a cost savings, it seemed like it made sense to go with CloudEndure and AWS versus a metal to metal type of DR solution. We did have a VMware solution in place, but we canceled it.
I haven't really compared other cloud-based DR solutions, so I can't compare it to anything else.
What other advice do I have?
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.
Ease of use and reliability, meets our DR requirements
Disaster recovery.
How has it helped my organization?
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.
What is most valuable?
* Ease of use
* Reliability
* Cost
* Stability
What needs improvement?
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.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
There have been no issues.
What do I think about the scalability of the solution?
Scalability is pretty good. It's seamless; it can do it automatically.
How is customer service and technical support?
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.
Which solutions did we use previously?
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.
How was the initial setup?
It was straightforward. It was pretty easy.
What's my experience with pricing, setup cost, and licensing?
I feel the product's pricing is a good value. Licensing is pretty straightforward.
Which other solutions did I evaluate?
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.
What other advice do I have?
Technical support has been very good
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.
How has it helped my organization?
It provides our disaster recovery solution. It works fine in our tests.
What is most valuable?
Disaster recovery. It is what we have the product for.
What needs improvement?
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.
For how long have I used the solution?
One to three years.
What do I think about the stability of the solution?
Sometimes a server will get a bit behind.
What do I think about the scalability of the solution?
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.
How is customer service and technical support?
Technical support has been very good. They usually respond quickly to our requests.
Which solutions did we use previously?
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.
How was the initial setup?
The initial setup is really straightforward.
What's my experience with pricing, setup cost, and licensing?
We were happy with the pricing that they gave us.
Which other solutions did I evaluate?
We investigated several different options and chose this one.
What other advice do I have?
Great product, very easy to install
Very easy to install product to setup DR data across regions. I know the people behind the product (but am not affiliated myself) and can say that they are a great team, they are very active and are releasing new features continuously.
showing 1 - 9