Druva Phoenix (UNPUBLISHED) vs. Iperius Backup

Durva Phoenix is well suited for the VMware platform and has great restore functionality during disaster recovery. We use a different VM platform so our disaster recovery has a longer timeline if there is a critical failure as we need to get a base OS loaded before we can restore the VM data to it. This is the tradeoff between an expensive VM platform and a near free VM platform. Druva Phoenix is well suited to file version recovery if a previous data state is required by your employees or customers. Very quick to restore.

Incentivized

Iperius Backup is a very simple and cheap but absolutely effective solution for small infrastructures. You can use it both on Windows clients and servers, it can integrate with ESXi, MySQL, MSSQL, etc. I think the best way to use it is with their cloud space (Iperius Cloud Storage) that allows you to take care effortlessly of your small customers' data. When it comes to more complex infrastructures, I prefer relying on something different (Nakivo Backup and Replication, Promox Backup Server).

Incentivized

• The best part about Druva is that you deploy, which is fairly easy especially with your technical rep being available for the whole process, and then you let the system do your work. If a backup fails I get a report, there is no need to check it every day or even weekly.
• The file server backup is great. Searching is easy and the capability to pull back a full folder or individual file makes life a lot easier to support my end users.

Incentivized

• Less than 15' to set up
• It has its own cloud storage solution
• It has a monitoring console
• It's very cost effective

Incentivized

• The UI is good, but a bit inconsistent. Some types of backups are shown differently to others. It never gets in the way, but a bit more consistency would be good.
• The system is usage based, which is understandable, but a shock after using inSync, their other backup product, which is not. Careful planning and thought is needed if you are on a tight budget

Incentivized

• Lack of clear documentation
• Rsync not supported
• Apparently NFS shares are supported but it's not clear how to use them
• Iperius Console should be improved (it's almost a read-only dashboard and you need too many clicks to get where you want to go)

Incentivized

Certain backup solutions can be cumbersome on how they actually work. Where that's properly deploying hardware or software that will house the backups. Druva is different where the software and infrastructure is completely managed. All we needed to do is deploy agents and proxies and point the backups to Druva Phoenix

Incentivized

It's been pretty easy to get a hold of the Support team and they work well to resolve our issues. I wish I could email support directly (which we used to be able to do) versus having to login to the console and report an issue from there, that's a feature I'd like to see brought back but otherwise, their Support team is pleasant to work with.

Incentivized

Druva stacks up well against its competitors. I do not remember it being at a disadvantage in any category. Phoenix couldn't provide message-level restore on an on-premise Exchange server but after we moved to the cloud that requirement went away.

Incentivized

The company used several free solutions (e.g. Cobian Backup et al.) but they were outdated and there was no standardization, nor a simple way to monitor all the backup jobs. Iperius had all the key features needed for the task and the project is very much alive (regular new releases).

Incentivized

• This is a necessary service to keep your information safe. I would not say that there is a tangible ROI unless you reach a point where your server gets attacked and wiped-out. Then, you can recover your information in an easy manner, which could represent a potential several-thousand-dollar savings.

Incentivized

• One standard solution for small customers
• One console to monitor backup jobs

Incentivized