We performed a comparison between AWS Elastic Disaster Recovery and Code42 Incydr based on real PeerSpot user reviews.
Find out in this report how the two Backup and Recovery solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The initial setup is pretty straightforward, it's not complex."
"Technical support has been very good. They usually respond quickly to our requests."
"The setup is pretty straightforward."
"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 have never had any issues with scalability."
"It's on the cheaper side and not too expensive for users."
"CloudEndure Disaster Recovery is a fairly stable solution."
"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."
"Risk factors can be adjusted for all intricate details."
"Low system overhead, setting retention policies, ease of use"
"Backup and recovery have been great, but I love having the ability to keep the hybrid type build which they offer."
"Security tools: Being able to monitor data going in and coming off our endpoints. Seeing what it is and where it's going is awesome."
"The solution is very stable. Very rarely do we have any issues with it. We don't have to deal with bugs or glitches. It doesn't crash or freeze. We find it to be reliable."
"It required very little ongoing maintenance once setup."
"There are a couple of things. One of them is that they have what they call Incydr. Their detection and response solution to the insider threat area is called Incydr. That gives visibility to the clients that have widely dispersed employee bases due to work from home, or that had a dispersed workforce predating any of the work from home requirements. Even though they might not be inside the organization physically, they're inside the organization. It allows us to get some visibility into what people are doing, what the context is, and how to control what might be the potential for intellectual property theft or file exposure."
"It has quite a bit of flexibility in configuring backup sets."
"The user interface, customer support, and the recovery time for the current customer query could use improvement."
"I have not seen any areas that need improvement at this time."
"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."
"Sometimes a server will get a bit behind. "
"The UI could be a little sleeker."
"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."
"I set up a test, deleted the source, and went to fail it back, and it didn't work."
"The failback could be improved. It should be more intuitive."
"More security would be nice, I would love to be able to remotely brick a stolen laptop and it's hard disk drive (HDD)."
"Java, please get rid of Java."
"In a couple of instances, we had a little bit of trouble in getting it distributed throughout the organization. We ultimately managed to do it, but they talk about it being a pretty simple process, and it became a little laborious. It would just turn away. The agents were not being distributed. It was just churning and churning and churning. When we were looking for specific categories of data, it was getting bogged down, but that was not even so much Code42, although some of it was their issue."
"There doesn't seem to be any feature that is lacking."
"You can't always filter out data that you'd like to."
"What I think could be improved is how I get support."
"I think one we can improve is the compression."
"The application, written in Java, required far more system resources on a Client than other solutions."
More AWS Elastic Disaster Recovery Pricing and Cost Advice →
AWS Elastic Disaster Recovery is ranked 33rd in Backup and Recovery with 11 reviews while Code42 Incydr is ranked 31st in Backup and Recovery with 78 reviews. AWS Elastic Disaster Recovery is rated 7.4, while Code42 Incydr is rated 9.0. The top reviewer of AWS Elastic Disaster Recovery writes "Free, easy to use, and offers good support". On the other hand, the top reviewer of Code42 Incydr writes "Provides comprehensive visibility and protection, helps in identifying the gaps in security, and comes with excellent onboarding support". AWS Elastic Disaster Recovery is most compared with Azure Site Recovery, AWS Backup, Oracle Data Guard, VMware Cloud Disaster Recovery and Zerto, whereas Code42 Incydr is most compared with Threat Detection, Investigation & Response (TDIR) Platform, Microsoft Purview Data Loss Prevention, Morphisec, Forcepoint Data Loss Prevention and Backup and Restore for SharePoint & Microsoft Office 365. See our AWS Elastic Disaster Recovery vs. Code42 Incydr report.
See our list of best Backup and Recovery vendors.
We monitor all Backup and Recovery reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.