TBMR vs. Veeam Data Cloud for Azure

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.

For our purposes I can't particularly find any shortcomings of Veeam Backup for Azure. It has been working well for our needs for a few years now. Maybe for someone with a larger cloud footprint or more complex needs, or maybe someone who wants to be able to deploy and configure the appliance using infrastructure as code it may not be as practical.

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

• Reduce storage costs and minimizing the impact on network consuption.
• Veaam Backup for Azure provides application-aware backups for Microsoft SQL Server, ensuring that our data is backed up and available for recovery correctly.
• Replication: Veeam Backup for Azure helps us to replicate our workloads to another Azure region or on-premises environment for disaster recovery purposes and compliance needs.

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.

• Documentation around service account permissions was a little sparse when we implemented it
• It's sometimes hard to get the reason behind a (rare) job failure without going into logs
• The UI around snapshots and backups could do with some clarity around the restore points that will be available

Incentivized

Plainly, the product just works. I don't have to babysit it.

Incentivized

It was so easy that you thought it wasn't working. Once you saw data and was able to recover it or do a restore with the product those beliefs in the system went to the roof. Once you get a product that does everything you want it to do, you will give it it's props.

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.

Great support team!

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

Backup Exec was a very clunky application and took forever to backup to and restore from. We would backup to SSD external hard drives from a flash array, but the process still took forever to finish. Sending our data to the Azure blob storage via Veeam is a faster and more secure process than saving to the external hard drives with Backup Exec.

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.

• We have had fast recovery of documents when needed; sub 10 minutes from start of restore to complete and in the users hands
• Easily a value add for backing up files outside of the given Microsoft retention period; piece of mind
• Easy tool to use with minimal training required to use it and set up backups
• When you do change your cloud licensing it does require manual intervention to update backup data requirements. if the business makes changes then your backup person may not know to make these changes

Incentivized