Druva Phoenix (UNPUBLISHED) vs. TBMR

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

During the Sandy storm, I was told to get over 200 servers ready in case we declare a disaster. I was able to spin over 190 servers in five days. I recovered servers using TBMR recovery. I restored each server using TBMR. After the server was restored at Sungard, I powered on the server without NIC to prevent a production issue with duplicate a name or IP. I validated each server after restore to make sure OS is working correctly and all data had been restored. I did not restore images due to the size of storage. Overall, it worked out and we were ready before Sandy struck. We did not go into disaster mode, but my management was impressed that this product worked as described.

• 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

• It works 99.9% all the time if you setup correctly. In some instance there was issue was disk was not able to read partition. I called support and upload the log file. They told me during recovery point to new modify file instead of reading from backup configuration. It work and able to recover quickly
• The support is really great. They are always ready to help in any situation.
• During Sandy storm, we mentioned our challenges. They told us there will two support engineer will be stand by for support any time. Just let them know when you need support.
• Support is staff is very knowledgeable. They willing to go extra mile all the time

• 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

• There have been so bugs in the software. They provided me the next day with a temporary fix. In the next release, they will fix the bug permanenly.
• As far as we use it, I do not see too much on functionality.
• Setup is unique in every organization. It has been working well so far.

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

Support is great. They go beyond the normal service. I called a few times in the middle of the night for support. I was not able to recover some machines. They called back with half an hour and worked through it with me. They wanted to make sure I was able to recover the server. They are always willing to help.

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

When I started TSM/Spectrum Protect over 13 years ago, disaster recovery was not funded to much. Once all regulatory requirements and auditing became more visible, management decided to start disaster recovery. I looked into one other BMR product. It required lots of manual processes to build WinPE iso images. I needed to build ISO images for each version of the TSM Client. At that time, we had over 350 Windows and Linux servers. There were over 10 different TSM Clients running. It was difficult to maintain all the different ISOs. I am only one admin doing the backup job and other duties. It was not possible to keep. I started to shop around for a different BMR solution for TSM. I came across Cristie. We did POC testing for 1 month. We covered HP physical servers to IBM hardware and vice versa. It worked without any issue. We also tried to recover HP physical servers from DL360 to DL380 and others. It works every time. At that time my management got assurance that this is a good product for investment. We started with 300 licenses. Now we have over 200 Physical and 600 virtual license

• 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

• As of today, we are recovering servers without any issue. There is no 100% success. Some servers backup corrupted data and are restored the same way. It is called Garbage in Garbage out. So far management wants to continue the use of this product.
• My management wants to use TBMR or any other backup.
• Every year we are buying more licenses.