Listing Thumbnail

    CloudEndure Disaster Recovery to AWS

     Info
    CloudEndure Disaster Recovery enables organizations to quickly and easily shift their disaster recovery strategy to AWS from existing physical or virtual data centers, private clouds, or other public clouds, in addition to supporting cross-region / cross-AZ disaster recovery in AWS.
    Listing Thumbnail

    CloudEndure Disaster Recovery to AWS

     Info

    Overview

    Play video

    Product update: AWS Elastic Disaster Recovery, the next generation of CloudEndure Disaster Recovery, is now the recommended service for disaster recovery to AWS. Learn more here: https://thinkwithwp.com/disaster-recovery .

    As of March 31, 2024, CloudEndure Disaster Recovery (CEDR) will be discontinued in all AWS Regions except for the following regions and use cases:

    AWS China regions - cn-north-1 and cn-northwest-1 AWS GovCloud regions - us-gov-west-1 and us-gov-east-1 Usage in conjunction with AWS Managed Services (AMS) Usage with AWS Outposts

    If there is still a need to get started with CloudEndure Disaster Recovery, subscribe on this page and then follow the instructions to register new servers.

    CloudEndure Disaster Recovery is an automated IT resilience solution that lets you recover your environment from unexpected infrastructure or application outages, data corruption, ransomware, or other malicious attacks. Block-level, continuous data replication enables recovery point objectives (RPOs) of seconds. Continuous data replication to a low-cost staging area in AWS reduces your compute and storage footprint to a minimum. Automated machine conversion and orchestration enable recovery time objectives (RTOs) of minutes.

    Highlights

    • Replicate any physical, virtual, or cloud-based workload with RPOs of seconds and RTOs of minutes. Fail over to previous points in time to recover from data corruption, ransomware, or other malicious attacks. Fail back when disaster is over.
    • DR TCO reduction: Uses minimal compute and low-cost storage, and eliminates OS and application software licensing during normal operations (real-time replication). Only pay for relevant compute and OS/application licenses when recovery is needed.
    • Enterprises use CloudEndure to replicate their most critical databases, including Microsoft SQL Server, Oracle, and MySQL, as well as enterprise applications such as SAP.

    Details

    Delivery method

    Features and programs

    Financing for AWS Marketplace purchases

    AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
    Financing for AWS Marketplace purchases

    Pricing

    CloudEndure Disaster Recovery to AWS

     Info
    Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time.

    Usage costs (2)

     Info
    Dimension
    Cost/host/hour
    Hourly rate for protected machine
    $0.028
    Hourly rate for AWS protected machine
    $0.028

    Vendor refund policy

    If you need to request a refund for software sold by Amazon Web Services, LLC, please contact AWS Customer Service. Web Support: bit.ly/1Q6bE3; Phone Support: bit.ly/MFEcTIAnnual SubscriptionsAnnual subscription cancellations or downgrades are not supported. If you need help with or want to upgrade your subscriptions, please click here: https://thinkwithwp.com/marketplace/help/buyer-annual-subscription 

    Legal

    Vendor terms and conditions

    Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .

    Content disclaimer

    Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.

    Usage information

     Info

    Delivery details

    Software as a Service (SaaS)

    SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.

    Support

    Vendor support

    Support for CloudEndure Disaster Recovery is determined by your support level agreement with AWS. We strongly encourage customers using CloudEndure Disaster Recovery for production workloads to purchase either Business or Enterprise Support from Amazon. Learn more:

    AWS infrastructure support

    AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

    Similar products

    Customer reviews

    Ratings and reviews

     Info
    4
    11 ratings
    5 star
    4 star
    3 star
    2 star
    1 star
    45%
    36%
    0%
    9%
    9%
    11 AWS reviews
    sharmauiuc

    Issue with Customer Service

    Reviewed on Feb 26, 2019
    Purchase verified by AWS

    Very poor customer service.

    Unable to help with the issue even after repeated reminders. I have had a machine being backup and when I tried to restore, the restoration failed.
    I waited for two days for anyone to respond.

    The backup of the machine continued for 60 days. When I tried to restore I could not restore. On a different note, I was able to restore using Acronis Cloud without any issues.

    Dave van Nierop

    CloudEndure Disaster Recovery

    Reviewed on Aug 16, 2018
    Purchase verified by AWS

    Commercial license required

    AWS cloud-to-AWS cloud has full functionality
    Generic cloud/onsite-to-cloud has limited functionality and multiple licenses are needed - 1 for cut-over and 1 for fail-back (2 separate project licenses)

    Caveat - if you replicate a source server that has multiple NIC's, your target instance only contains the primary NIC which means when you failback, your original instance is not a match to the final instance; instead, you have to snapshot your failback instance and build a new instance while adding devices [and checking ip forwarding] etc

    Director6974

    It has saved us money from having to buy hardware for disaster recovery

    Reviewed on Jul 23, 2018
    Purchase verified by AWS
    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.
    GlobalIn47b7

    Ease of use and reliability, meets our DR requirements

    Reviewed on Apr 11, 2018
    Purchase verified by AWS
    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?
    SharePoi2b31

    Technical support has been very good

    Reviewed on Mar 08, 2018
    Purchase verified by AWS
    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?
    View all reviews