What is our primary use case?
We use Zerto for the disaster recovery capabilities that it provides us. It is for our Tier 1 applications.
How has it helped my organization?
Zerto allows us to protect individual VMs. With the other solutions, we are protecting the storage that the VMs live on, which is costly, so Zerto does save us money.
Zerto has near-synchronous replication. It works very well. Our RPO or recovery point objective time was 20 minutes, and we were doing thousands of VMs. We not only met the RPO; we exceeded it. There were many times when it was just seconds behind.
We have used Zerto to help protect thousands of VMs in our environment. Zerto has had a good effect on our RPO. It has helped to exceed our RPO. Our RPO on some of our critical systems is 20 minutes, and we exceed that. Most of the time, we are under 2 to 3 minutes.
It is very easy to migrate data. We ended up migrating from one data center to another data center, and we moved 20,000 virtual machines with Zerto. It was great.
Zerto lowered our RTOs as well. As a part of the solution analysis that we did for the RPO and RTO, Zerto's interface to do a DR test or a DR recovery was the fastest. We had a 24-hour window to recover 5,000 virtual machines, and we were doing them in three to four hours.
Zerto has helped us to reduce downtime multiple times. We had one incident where we used it to do a recovery. The downtime was roughly about 20 minutes. We do not have a value on that because it is customers' health information. I do not know how it affected the end users or customers outside of our company, but it does affect them.
Zerto has saved us time. When files were deleted, we were able to recover the files quickly. While doing OS patching on the servers, when the servers failed on the reboot, we were able to recover all good things when it came to quick recovery on it. As opposed to pulling it from our backup, it has cut our time probably in three quarters.
Zerto has helped to reduce our organization's DR testing. A DR test or a recovery used to take us days, whereas now, it takes us hours. The system that we were using before took multiple engineers to do the DR test, whereas today, a single engineer can do the DR test, and then we need just a couple of engineers to do checks on it, so it saves us a lot.
Zerto has reduced the number of staff involved in a data recovery situation. Instead of a group of people, we now just need one.
We used Zerto for immutable data copies. It was good, and they were on a course, but they shifted their focus. They were doing DR specifically, and then Zerto started shifting over towards doing backups. We were very excited about their long-term backups, but when HPE bought them, HPE stopped that part of it because they were directly competing against their solution. At the time they were doing it, we were very excited about it.
What is most valuable?
The DR testing capabilities that it has are valuable.
Its ability to roll back if the VM or the server that you are recovering does not come up right is also valuable. You have the ability to roll back a few seconds or a few minutes. The rollback feature is great.
What needs improvement?
While going in, we were looking at the backup tool so that we had a DR tool and a backup tool, but they stopped developing their backup solution built into it. That was a bummer for us, so now, we have a DR solution, and we have a backup solution.
For the actual application itself, we have put in our request for certain features, and so far, they seem to be adding those features. In their latest one going to version 10, they did an appliance, which we had asked about 6 years ago. It is great to see that they are doing an appliance. There would be even more savings for us now because we do not have to pay licensing for a Windows VM.
For how long have I used the solution?
I have been using Zerto for about 7 years. I have used Zerto a few times at different companies.
What do I think about the stability of the solution?
We have seen very few issues. It is one of the few solutions that actually runs. If you do your leg work and implement it right and go through all the design and other things, you do not have to babysit the solution. Care and feeding is what it amounts to. That is all you have to do, whereas with a lot of the other solutions, you have to babysit them.
What do I think about the scalability of the solution?
Its scalability is very good. It scales very easily.
How are customer service and support?
They could do better in regards to escalating an issue. I would rate them an 8 out of 10. In defense of support, I know it is hard because they are talking to somebody who has got 28 years of IT support. When I get on the call, I am probably dealing with someone who is just starting out. He has to go through his standard process. However, somebody like me is looking for faster support and would like to get to a real smart guy quicker.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
For disaster recovery, we were using VMware Site Recovery Manager, and it was not able to provide the recovery, the RTO, or the RPO that the company required. I went out and did a discovery for different DR solutions, and that is where I came across Zerto. Zerto replaced VMware Site Recovery Manager, and it saved us millions.
How was the initial setup?
Our deployment model is hybrid. I was involved in the initial deployment. It was straightforward. It was a lot easier than VMware Site Recovery Manager. It took us a week to deploy it.
In terms of maintenance, other than typical patching and upgrades, it does not require any maintenance. VMware Site Recovery Manager required a lot of ongoing maintenance.
What about the implementation team?
We implemented it in-house. There were just three of us involved in its implementation.
What's my experience with pricing, setup cost, and licensing?
The pricing is based on virtual machines. They need to do better in regards to their tiering pricing rather than one price per VM. A lot of times we have VMs that are lower tier, such as Tier 2 or Tier 3, but we pay the same price as for Tier 1. I know they are developing this out, but it would be nice if they could provide a little better pricing in regards to their tiering protection.
Which other solutions did I evaluate?
We tested four different solutions, and Zerto was the only one that was able to meet our requirements. We did PoC on Zerto and two other solutions. Zerto was by far the leader when it came to disaster recovery.
What other advice do I have?
To those evaluating this solution, I would recommend doing a PoC on it. Deploy it in your environment and test it. Most of the problems you are going to see are due to the replication, and that is the site-to-site connection. One of the problems that I have experienced with Zerto has been related to replication, not the solution itself.
We have not used Zerto for blocking unknown threats and attacks. Thankfully, we have not had that. We do not have experience of that, thankfully.
We have used Zerto to do DR to both AWS and Azure, but the ability to do disaster recovery (DR) in the cloud is not something critical for us because the health insurance requirements for certification do not allow us to put our Tier 1 data in the cloud. Also, because our applications are multi-tiered where they reach out to the mainframe, Solaris, and other equipment outside of the virtual environment, it did not make sense to go to the cloud with it, but we do have it. We have a development environment there. A lot of times, we will use it to refresh the development environment. So, it is important, but in our case, it is not critical for us.
We have not had any issues utilizing Zerto to support DR on AWS, but AWS is on the slower side. The reason is that for the connection to AWS, even though it is a direct connection, the speed does vary for us.
I would rate Zerto a 10 out of 10.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.