What is our primary use case?
We implemented Zerto because we wanted a flexible and quick tool that allowed us to recover in different situations. This purpose was successfully fulfilled by Zerto during the proof of concept phase, so we implemented it.
How has it helped my organization?
Zerto helps with quick recovery and integration with other processes. Providing as a service approach allows end-users to operate and perform recovery operations on their own assets based on their requirements and schedule preferences. It helps not only with recovery but also with DR tests that need to be executed at specific time frames, such as out-of-business hours. We had a few different requirements during its implementation, and Zerto helped us very well with all these needs.
Zerto has some specific options for replication, but it is mainly for virtual machines. We mainly use it for virtual machines. Zerto is not suitable for physical servers, but it can be used for virtual solutions such as OpenShift, Kubernetes, etc. In terms of its effect on our RPO, as I have not used a similar solution previously, the RPO value that we are getting is very good. It fits the requirements that we have from our customers because what we provide to our customers needs to be proven by the tests that we perform. Usually, their expectations are much lower than what we receive from Zerto. For example, we have application owners for whom 24 hours duration is enough to recover the business as compared to the 10 minutes that I have using Zerto. We use Zerto in real DR exercises and ask our customers to verify the results and the status of the recovered system and answer if the recovery was successful. We provide them the time needed to recover their system, and often, it is much quicker than what they require, so from our perspective, Zerto is very good. However, we cannot verify everything because we have some limitations in our DR test scenario. I can be 100% sure of the results of recovery only in the case of a real disaster on my infrastructure. At this time, based on the DR tests, it meets my customer needs.
We conduct DR exercises at least twice a year to measure the downtime we would have in the case of a real disaster. We simulate the disaster in a controlled environment and perform all related exercises. Once all activities are performed, we measure the time needed to recover systems from the data center that is down due to a natural disaster or technical issue. We get an idea of the downtime but the actual downtime varies depending on the issue type. It might not always be predictable or reduced through tooling as network or server issues can arise. In some specific scenarios, the downtime could be lower by using Zerto, whereas in some cases, Zerto would not help much. Based on the results of disaster recovery exercises and the RTO measured not only for one application but for recovering all of the applications in affected data centers, we can say that the time we need to recover the full data center is much lower than using traditional backup recovery solutions. Recovery with Zerto is much faster because we can recover in parallel many systems.
What is most valuable?
I am quite familiar with the user interface. It is easy for me to operate and perform different operations because I am an experienced user. In my opinion, the user interface is easy to understand and operate. The user interface is user-friendly.
Another important feature is the tool's automation capabilities, as it provides an external API to integrate with other tools and processes. This allows for a comprehensive IT ecosystem within a single dashboard, tailored to specific needs. Some operations can be limited for end-users. All of this can be provided not only through the GUI but also using the API. You can create your own application, integrate it with Zerto API, and develop features in your own application. You can use the API to integrate with your application and provide only the features that you want to end-users, facilitating custom application development. You can split the responsibilities based on the roles provided as well as based on your requirements. It is very flexible. From my point of view, the end-user experience is very good as an administrator of the tool and as the person responsible for the disaster recovery process.
What needs improvement?
As a user who used Zerto for eight years, there are specific issues that it cannot address. For instance, recovering physical servers is directly connected to the virtualized solution in use, meaning your infrastructure needs a VMware or Hyper-V solution. It cannot be used for bare metal physical server solutions. One improvement could be addressing the market segment related to physical servers. I understand this is a limitation of Zerto's technology. Still, from a customer's perspective, I would ask the vendor to find a solution to use Zerto for virtualized physical systems, such as physical servers.
A second area for improvement relates to the speed of implementation. There should be a more streamlined process for enterprise applications.
For how long have I used the solution?
I have used Zerto for about eight years.
What do I think about the stability of the solution?
I did not encounter any issues during the operations, so I would rate it a nine out of ten for stability, so there is room for improvement on the vendor's side.
What do I think about the scalability of the solution?
From my perspective, given the size of my infrastructure and the limitations based on the vendor's requirements and documentation, it fulfills my needs. Therefore, I would rate it a ten out of ten because I have not faced a situation where I needed more than what it provides.
It is being used at multiple locations.
How are customer service and support?
I have the opportunity to use Zerto support, and I have used it many times for various questions and solving different issues or problems I encountered in my infrastructure. I would give them a rating of ten because it represents the highest level of support based on the technical knowledge of the support team, response time, and effectiveness of the provided resolutions.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Zerto was the first tool I started using once I took on the disaster recovery manager role in my company. I did not have experience with other tools.
How was the initial setup?
The speed of implementation is an area for improvement. While deployment on straightforward infrastructure is easy, an enterprise company with strict access and vulnerability limitations requires manual configurations. This is neither easy nor quick.
Implementation depends on the environment and customers. From an enterprise perspective, I expect a more streamlined implementation process, as many steps require manual action. This challenge is specific to my company due to limited access and port blockages. Implementing such tools is a one-time task. My intention is to provide feedback related to the installation process, not the operation.
What's my experience with pricing, setup cost, and licensing?
I do not have much experience with different tools, so I cannot directly compare Zerto with other solutions. While conducting our proof of concept, I compared prices with just one other vendor. At the time, the price for Zerto was more favorable. Since I only use this tool and I do not have the need for others, it is difficult to compare the price now.
What other advice do I have?
Zerto is an asynchronous replication solution. It provides what they call near-zero RPO value. There is a delay of a few seconds depending on the parameters of your infrastructure, such as the bandwidth, the workload in your infrastructure, the distance between data center latencies, and the speed of the network connections. There is no one solution that meets all the needs. You need to decide whether you need a synchronous or asynchronous solution. You should be aware of the pros and cons of both and the requirements of your organization. Synchronous replication might be risky in some specific situations. What looks good on paper might not always be good in reality. Zerto meets our needs for flexibility. It mitigates different problems related to infrastructure, even though there is always the possibility of losing some data.
I would rate Zerto a ten out of ten considering the features, support, feature development roadmap, and the frequency of new features provided to customers.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.