We performed a comparison between AWS Elastic Disaster Recovery and BDRSuite based on real PeerSpot user reviews.
Find out in this report how the two Disaster Recovery (DR) Software solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."For regular backup and restore solutions, this product is fine."
"The initial setup is pretty straightforward, it's not complex."
"It's on the cheaper side and not too expensive for users."
"The setup is pretty straightforward."
"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."
"CloudEndure Disaster Recovery is a fairly stable solution."
"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."
"Technical support has been very good. They usually respond quickly to our requests."
"If we do a backup of a machine at some point and the server crashes, then we can restore this machine to a different server with the same settings and setup. We will just have to tweak one or two things, like the IP. Then, it is ready to go."
"Moving to cloud backups eliminated the need for clients to change USB drives or worry about drives being stored offsite."
"I am very pleased with the compression, especially with some of the larger SQL databases that need backup. The amount of compression is impressive."
"The most valuable feature is the ability, from a console, to manage the different computers to be backed up."
"It suits our needs, is versatile, and the functionality is there."
"We use it to maintain critical data and save it."
"There is an option to back up a specific folder from a specific source, not the whole virtual machine."
"Quick backup and restore; very simple and understandable interface."
"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."
"I have not seen any areas that need improvement at this time."
"The solution's network setup and a lot of the control tower setup could be improved."
"The UI could be a little sleeker."
"I would like to see better support for creating and working with archives."
"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."
"The user interface, customer support, and the recovery time for the current customer query could use improvement."
"The dashboard should more interactive."
"BDRSuite could improve support for XenApp Citrix Backup."
"The interface could be better because I have to fumble around to find things. I can't just sit down at the terminal and know exactly what to do. It could be just me, but I have used a number of different backup products, and I found them simpler. However, its features are very good, so I don't mind sacrificing a bit of extra time to do what I need."
"There are bugs. For one month, I encountered a big issue where my storage pool could not be identified. My backups were stopped because they were not able to locate the storage pool. So, I removed the settings and started the backups again. The application is not stable. It needs some debugging and testing on the build side of production."
"There are some limitation in Vembu that can be improved. When you take the backup from any server, the full incremental backup is limited. For example, if you run a weekly full backup and monthly backup, they cannot be run at the same time. I should not have to create a new job, but in this scenario, I am creating two jobs. The limitation is created because if I select monthly backup, then I cannot select weekly backup."
"The phone [support] system is a negative five on a scale from one to ten, where one is the worst. They wanted me to leave a message. When there is a problem with the product and you call in, you want to talk to somebody or wait to talk to somebody, not leave a message."
"What I would love to see on the dashboard are graphs, per backup job. I want to see the month and the days in it... If a job has failed, when did it actually fail and what percentage of it failed? Did it fail completely, 75 percent or 100 percent or did it only fail partially?"
"The product is co-branded, not white-labeled."
More AWS Elastic Disaster Recovery Pricing and Cost Advice →
AWS Elastic Disaster Recovery is ranked 17th in Disaster Recovery (DR) Software with 11 reviews while BDRSuite is ranked 7th in Disaster Recovery (DR) Software with 62 reviews. AWS Elastic Disaster Recovery is rated 7.4, while BDRSuite is rated 8.2. 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 BDRSuite writes "Can automatically pull the virtual machines that we have in an environment". AWS Elastic Disaster Recovery is most compared with Azure Site Recovery, AWS Backup, Oracle Data Guard, VMware Cloud Disaster Recovery and Zerto, whereas BDRSuite is most compared with Veeam Backup & Replication, NAKIVO Backup & Replication, Vinchin Backup & Recovery, Acronis Cyber Protect and Hornetsecurity Altaro VM Backup. See our AWS Elastic Disaster Recovery vs. BDRSuite report.
See our list of best Disaster Recovery (DR) Software vendors and best Backup and Recovery vendors.
We monitor all Disaster Recovery (DR) Software 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.
