We performed a comparison between BDRSuite and Druva Phoenix 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."The initial setup is easy and very nice."
"The most useful feature is that you can back up the virtual machines in different ways. You can back up from a vhost, and you can also back up from a Windows server. It doesn't matter what type of infrastructure or hypervisor is there. It's very flexible, which is its most useful feature for us."
"Their technical support is very good to work with, as they are able to propose alternate solutions to problems that work well for us."
"The most important features are the backup and the availability of the Universal Explorer. The in-transit compression is great."
"There is an option to back up a specific folder from a specific source, not the whole virtual machine."
"We have seen ROI. The real return is when something bad happens. All the proof of concept work that we did, all the testing we did, it all panned out for us. We're already seeing a return on that."
"Vembu provides us with a way to instantly recover data. It offers instant data recovery through a local backup server deployed at the customer's site. We can quickly recover data either by copying it back to the main server or if the backup server is powerful enough, we can also directly start a virtual machine from the backup."
"I am able to run Vembu on Windows NAS, which is beneficial. It does install on a Windows-based NAS. You can have the server running from the location where you are storing backups. You don't need a separate server for it in this case."
"Druva Phoenix is easy to use and easy to start with."
"Once you set it up and you tell it exactly what needs to be backed up, you literally forget about it. It sends you emails and notifications of the current status of the jobs."
"I found the cost-effectiveness of Druva Phoenix to be its most valuable feature, especially when compared to on-premises backup solutions."
"I would definitively say that we have been able to make our people more productive by at least 30%."
"The most valuable features of Druva Phoenix are the simple portal to log in and flexibility."
"It is very easy, unless you know exactly what you're doing, to corrupt the virtual machines and they get locked up. Just brief detail: When you are creating a system, if you don't have absolutely every other little background processes in place, it creates Snapshots of the virtual machines. Once it does that, it then won't be able to have a backup. From that point on you have to destroy the virtual machine, which is completely counterproductive on a large system. There is a fundamental flaw in the setup that can be very dangerous, potentially."
"The reports are at a basic level and there is room for improvement there. It only has historical reports and VM backup job-level reports."
"Vembu will tell you the next scheduled backup, but it doesn't show you the last successful backup. I would have them include a column under "List of Backup Jobs" and have two other columns which say, "Last Successful Backup" and "Next Scheduled Backup", because you don't know now if it's backed up successfully. It just says, "The next scheduled time is this." You don't know from looking at that pane of glass when the last time it actually happened without digging further into reports."
"Vembu software runs on a Windows Server. The Windows Server has to be connected to the internet so it can connect with Vembu’s servers. It has to connect with Vembu. For some reason, if it doesn't connect, it stops working, and I don't know why on earth they do that. They require it to connect to the internet and connect with Vembu for it to continue to function. If the internet is down or if the server can't reach the internet, it stops working after a few days. That's not great because there are some people who want to do backups but they don't want to have their server accessible on the internet."
"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."
"The initial setup process can be more simplistic and quicker."
"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."
"There were issues with the implementation because of incompatibilities between the tool implementation and our current VMware installation. So, it was an implementation issue that doesn't allow me to use it for VMware backup in the manner in which we would want to use it. That wasn't clear from the evaluation stage nor was it clear from the first utilization of it because it worked in the environment that it was being evaluated in. Based on that, we went ahead and made the purchase of the full implementation. At that point, it became clear that there would be limitations in that implementation that could not be overcome without doing upgrades to the production environment."
"Druva Phoenix should include a few reporting features that it doesn't provide currently."
"Druva Phoenix is optimized to work with x86 platforms, making it unsuitable for backing up non-x86 architectures like AIX. The solution is primarily designed for physical Linux and Windows systems based on the x86 architecture, as well as virtualized Windows and Linux environments. However, if you have an AIX system, it cannot be deployed in the cloud, and therefore, backing it up in the cloud is not a concern."
"There is room for improvement in the reporting aspect of Druva Phoenix."
"They were able to give us a very reasonable price considering we were non-for-profit organizations, however, there is always room for improvement on that cost."
BDRSuite is ranked 7th in Disaster Recovery (DR) Software with 62 reviews while Druva Phoenix is ranked 13th in Disaster Recovery (DR) Software with 5 reviews. BDRSuite is rated 8.2, while Druva Phoenix is rated 8.8. The top reviewer of BDRSuite writes "Can automatically pull the virtual machines that we have in an environment". On the other hand, the top reviewer of Druva Phoenix writes "Cost-effective and has excellent technical support". BDRSuite is most compared with Veeam Backup & Replication, NAKIVO Backup & Replication, Vinchin Backup & Recovery, Acronis Cyber Protect and Hornetsecurity Altaro VM Backup, whereas Druva Phoenix is most compared with Druva inSync, Azure Backup, Veeam Backup & Replication, AWS Backup and Rubrik. See our BDRSuite vs. Druva Phoenix report.
See our list of best Disaster Recovery (DR) Software vendors and best Disaster Recovery (DR) Software 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.