TBMR vs. Zerto

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.

Zerto is well suited for disaster recovery and virtual machine replication between multiple data centers. DR testing for audit or regulations is much easier with Zerto, great reporting, dashboard etc. It is not well suited for physical server replication for disaster recovery or as a primary backup solution.

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

• Anyone with a large disk (VMDK) knows the issues of VMware snapshots. Most backup software is a "point in time backup" that uses snapshots. While the backup can be run multiple times per day the stress of the snapshot on the host and storage is eliminated by the continuous protection of Zerto log replication.
• A client had a the disks on a VM go missing for some reason. We had them "flip the switch" for a real fail over and press the fail over button. The VM on our DR site started to come alive as the VM at the customer site was brought down. When the DR VM was fully up, automatic reverse replication started. The DR machine was available in a few minutes (to take into account different host hardware) for access. One the vm at both sites were in sync, we had the customer again repeat the fail over process and the DR site VM was turned off and the Production site VM was brought back on line. This was a 200 GB VM and the whole process was finished in about 3 hours.
• Zerto also allows for "Test" fail overs that can be configured on many different functions, such as host, datastore, network and IP usage. Configuring the IPs is crucial to avoid inadvertent site cross contamination of the same VM.
• Zerto can also retrieve files from any VM disk on the DR site without starting a VM. Very handy for retrieving files or directories.
• Since Zerto is running continuous log replication, changes on the production VM are nearly instantaneously copied to the DR site. As with any data process, having sufficient bandwidth for "churn" peaks minimizes the delay in updating the DR site.

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.

• Moving a VM from one protection group to another could be simplified.
• I would like to see an executive-style report of recovery and testing for upper management.
• The ability to deploy Zerto as a virtual appliance, without the need for a windows server.

Incentivized

We really like the easy setup of this replication solution, as well as the ease of management. Not to mention, our internal IT Economist determined that the Zerto solution would provide the best ROI out of the competing solutions we analyzed. So far, his calculations have been spot on, and we have saved substantially

Incentivized

Usability was the primary reason we purchased the software in the first place. We had compared it to several other software products in the same area, and it was by far the easiest to set up and use. Long-term maintenance proved to be similar, with updates driven by updates to VMware and vSphere, rather than the product itself.

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.

Overall support is very good. We sometimes get pushback when asking Level 1 support to escalate to Level 2. This causes undue frustrations when you need a more knowledgeable support person to get involved. We've had to escalate to account reps a few times for this scenario. Zerto is very responsive and normally handles our requests very quickly.

Incentivized

Make sure the end goal is in mind before implementing. That way results meet expectations.

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

We started out using Backup Exec which was in service until we virtualized our environment where it didn't perform as well at the time. Then we switched to Veeam which worked well, but then as we started needing to do migrations and off-site DR, we found ourselves relying on Zerto more often.

Incentivized

For my organization, the pricing model was an upfront investment for the Zerto licenses. My organization prefers to pay upfront and not deal with month-to-month or year-to-year pricing models that most companies are moving to. But for some, the investment may be more than they can afford, and would prefer the year-to-year pricing model.

Incentivized

I mean, it was 6 years ago, but we were up and going with all applications synchronizing in short order. The longest tasks was getting the 30 TB of application data synchronized between the datacenters.

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.

• Zerto is like having the best possible insurance ... it just works, and often provides the backups taken overnight that are key in recovering data/work between overnight backups.
• Zerto easily enabled the move of primary datacenters by allowing easy failover to a secondary site, and failback to the primary site.

Incentivized