Try our new research platform with insights from 80,000+ expert users
Joseph Lamb - PeerSpot reviewer
IT Manager at Nevada Bank and Trust
Real User
Top 20
Easy to use with near-synchronous replication and simpler disaster recovery testing
Pros and Cons
  • "Our RPOs and RTOs are now more in line with our other critical systems."
  • "The pricing could be a little bit lower."

What is our primary use case?

We are using it to back up and replicate our critical infrastructure to allow us to replicate back when we are in a disaster recovery situation or a test.

How has it helped my organization?

When we were in a disaster recovery (DR) test, we could not pull back the data in a timely manner. Zerto allows us to pull the data back in a timely manner. We also can create better RTOs and RPOs. We wanted an RTO of fifteen minutes and we've managed that.

What is most valuable?

To be able to replicate back to production is the most useful aspect of the product. It allows us to do a disaster recovery test and recover within eight hours. I couldn't do that before.

I'm also working with near-synchronous replication. It's very important to be able to keep my production and replication in sync.

I like the idea of Zertos being able to block unknown threats and attacks. In fact, one of my machines had a little encryption on it, and it detected that encryption, and I had to go look at it. It was nothing, in that instance, however, it was a neat feature. We could see that it was definitely looking for encryption and malware on our side.

Our disaster recovery testing is a lot easier and is much better with this product. Our RPOs and RTOs are now more in line with our other critical systems. We're now down to five minutes, well below our original 15-minute RTO goal.

Instead of being up all night, trying to get data back, I would no longer need to stay up all night. I've saved about four hours.

The product is easy to use.

What needs improvement?

I haven't noted any areas of improvement just yet.

I'd like to see a way to do a one-stop shutdown of replication so I know I'm not missing data and can do my DR test. 

I'd like to get better recovery point objectives and get more data back from our DR site faster. 

The pricing could be a little bit lower.

Buyer's Guide
Zerto
March 2025
Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
842,767 professionals have used our research since 2012.

For how long have I used the solution?

I've been using the solution for about two months now.

What do I think about the stability of the solution?

The solution is stable. I have never had any issues. 

What do I think about the scalability of the solution?

I have not tried to scale the solution. 

I have the solution for multiple locations in one department. 

How are customer service and support?

I've had two cases resolved via technical support. They helped me resolve issues I had with the installation. It did take me a few tries to resolve the issues.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We have used Veeam in the past. It's pretty good for certain things. However, it was hard to get continuous replication. Zerto is much easier to get that constant replication that we need. In terms of speed, for Veeam, it's about an hour right now across our secondary data center. It's not as fast. We moved to Zerto to get more data back from our DR site faster.

How was the initial setup?

I was involved in the initial setup. The initial setup is easy. Veeam had an easier setup, however, once we got Zerto going, it was easier to scale up and test. It's easier to manage in the long run.

The deployment had a bit of complexity. The problem we had was that the VRAs would not install and we had to turn off some security features. The ESXi server was not well documented. 

We set it up in multiple locations in one department.

It took us about three weeks to deploy the solution. 

The maintenance is simple. I handle the maintenance myself. 

What about the implementation team?

We handled the initial setup in-house internally. I managed the process completely by myself.  

What was our ROI?

It's just been a few months. We have yet to see a return on investment. 

What's my experience with pricing, setup cost, and licensing?

Zerto is a bit more expensive compared to Acronis or Veeam. That said, for us, the pricing was still reasonable. That said, we couldn't do all of our machines. 

Which other solutions did I evaluate?

We also evaluated Nutanix and Acronis.

We chose Zerto since it has very good integration with HPE servers. It's also an industry standard. Many people are using it. 

What other advice do I have?

I've never used its immutable copies features. I've just discovered the feature and need to look more into it.

I didn't use the cloud while using this solution. I have used the solution to help me protect VMs in my environment. 

I haven't had to migrate data just yet. The solution has yet to help us reduce downtime. It also has yet to help us save time in data recovery situations due to ransomware. We haven't had an incident as of yet. While it's saved time, we haven't been able to test all of our machines and all of our servers yet.

At this point, the solution has not reduced the staff involved in data recovery.

This product augmented what we have in terms of legacy backup solutions. It did not replace anything. 

My advice to others is to use Zerto for critical servers and things that need to be watched carefully for malware and encryption. 

I'd rate the solution eight out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer1564125 - PeerSpot reviewer
Senior Systems Engineer at a recruiting/HR firm with 1,001-5,000 employees
Real User
Knowledgeable support, good disaster recovery options, and the one-to-many replication capability is helpful
Pros and Cons
  • "The one-to-many replication functionality is helpful. While we were protecting our VMs in Azure, we were able to use the one-to-many feature to also replicate the same VMs to our new data center, in preparation for data center migration."
  • "If the log was more detailed and more user-friendly, we wouldn't have to make the calls to the support to try and figure out where the problem lies."

What is our primary use case?

We are using Zerto as our disaster recovery solution for on-premises to Azure, and also from Azure to Azure between different regions.

At this time, we are only using it for DR. However, we will also be using it for data center migration.

How has it helped my organization?

I would rate Zerto's ability to provide continuous data protection a ten out of ten. The tool is very easy to use. It's also a very simple and very quick setup. The outcome from our setup showed that we had very low RPO and RTO. The interface is intuitive and as such, anyone can log in and figure out how to use the management utility.

Being able to achieve such a low RPO and RTO has significantly reduced our lengthy recovery times. For example, a recovery that previously took four hours is now completed in 40 minutes. Furthermore, it allowed us to complete the data center migration very quickly, with very little downtime.

Using Zerto has allowed us to reduce the number of people involved from a failover standpoint. There are only a few of us who can perform the failover and it is done with the click of a button. From an overall verification standpoint, the application owners are still required to verify.

We have saved money by performing DR in the cloud rather than in a physical data center for a couple of reasons. First, we saved money by not having to upgrade our hardware and pay for additional facility costs. Second, in Azure, we saved between 10% and 20% compared to Azure site recovery.

What is most valuable?

The most valuable feature is the disaster recovery capability.

The one-to-many replication functionality is helpful. While we were protecting our VMs in Azure, we were able to use the one-to-many feature to also replicate the same VMs to our new data center, in preparation for data center migration. Importantly, we were able to do this without affecting the DR setup.

What needs improvement?

When you're configuring the VPGs, they can improve the process by looking at the hardware configuration of the existing VMs and then recommending what they should be, rather than us having to go back and forth. For example, on the VM configuration portion of creating the VPGs, it should already figure out what sort of CPU, memory, and capacity you need, rather than us trying to write that down and then going in afterward to change it.

The logging could be a lot better from a troubleshooting standpoint. If the log was more detailed and more user-friendly, we wouldn't have to make the calls to the support to try and figure out where the problem lies.

They could improve on how many machines the management server can handle for replication.

For how long have I used the solution?

We have been using Zerto for approximately two years.

What do I think about the stability of the solution?

Stability-wise, it's pretty good and we've been happy so far. We've had a couple of issues here and there, but nothing that wasn't easily resolved.

What do I think about the scalability of the solution?

The scalability is pretty good. If you need to scale then you can always add more appliances on the Azure side, which is very easy to set up. For the on-premises side, you only need one management server.

We are not a very large environment; we have approximately 400 servers, and then we are protecting about 125 VMs. In terms of users, we have close to 3,000 full-time employees and then about 25,000 contractors. Being a recruiting company, we have a large base of contractors.

The site reliability engineers are the ones that use Zerto more often, and there are three or four of them.

How are customer service and technical support?

The technical support is pretty good. The level-one has a lot of knowledge and because we've been using the product for a while now, if we get to the point of calling support, usually we have everything ready to go. We explain the situation to level-one support and we can always escalate easily to the next engineer.

Which solution did I use previously and why did I switch?

Prior to using Zerto, for our on-premises environment, we did a typical database replication from our production site to a secondary site in another city across the country on the West Coast. We also replicated the storage and application code, and it was a very lengthy process. One of the environments took as long as four hours.

We switched primarily for the time savings, although there was also the cost factor. In order to meet the growing demand of our business in IT, we would have had to upgrade all of our hardware, as well as pay extra for facility costs. As such, it did help out on both sides of things.

Also, just the process itself was a lot simpler. It would have required coming up with five or six different teams to do the individual parts, whereas this automates everything for you from a server level.

We use a different product as our backup solutions. Zerto is strictly for DR and data center migration.

How was the initial setup?

To set up the initial environment, it took about an hour. This included setting up the appliance, making sure it's added to the domain, and things like that. But then, creating all of the VPGs will probably be another couple of hours.

The strategy was that we already had everything ready to go, which included our server list and all of the VPG names. If you have that, you could probably have everything completed in half a day, or a day, from a setup standpoint. Of course, this is depending on how large of an environment it is, but for us, we set up five or six environments and it took us approximately half a day.

What about the implementation team?

We had assistance from the sales engineer. 

When we did the PoC, they showed us everything. Once we purchased the product, we used Zerto analytics to determine how many appliances we would need on the Azure side. Then, using that, we were able to break up the VPGs between the different sites.

What's my experience with pricing, setup cost, and licensing?

We have an enterprise agreement that combines all of the features, and we have approximately 250 licenses. There are two different licensing models. The one we purchased allows us to support Azure, as well as the on-premises jobs. This was a key thing for us and, I think, that is the enterprise license. They have a license for just their backup utility, and there's the migration option as well, but we went with the enterprise because we wanted to be able to do everything going forward.

Zerto needs to improve significantly on the cost factor. I know friends of mine in other businesses would not look at this when it's a smaller shop. At close to $1,000 a license, it makes it very hard to protect all of your environment, especially for a smaller shop.

We're very lucky here that finances weren't an issue, but it definitely plays a factor. If you look at other companies who are considering this product, it would be very expensive for somebody who has more than 500 servers to protect.

The bottom line is that they definitely have to do better in terms of cost and I understand the capabilities, but it's still quite pricey for what it does. It would make a huge difference if they reduced it because as it is now, it deters a lot of people. If you've got somebody who's already using VMware or another product, the cost would have to be dropped significantly to get them on board.

Which other solutions did I evaluate?

We did evaluate other vendors, but this was the only tool that was able to fully automate the conversion from on-premises VMware to Azure. This was important because our goal, or our DR objective, was to set up DR in Azure. Every other tool required having some sort of intervention from us to convert them to Azure format.

I don't recall all of the tools that we looked at, but I think we looked at VMware SRM and also a product from EMC, from a replication standpoint. Ultimately, from a strategy standpoint, this was the only thing that was really capable of doing what we wanted.

What other advice do I have?

My advice for anybody who is interested in Zerto is definitely to do a PoC. Run it against your environment to do a thorough comparison. This is the best scenario; instead of just picking the product, let it go through the different options. For example, whether you are doing on-premises to on-premises, or on-premises to the cloud, this product can do it, but you'll only see the results that you want to see if you grind it against your own environment.

Overall, we are very happy with this product.

I would rate this solution a ten out of ten.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Buyer's Guide
Zerto
March 2025
Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
842,767 professionals have used our research since 2012.
Enterprise Architect at a transportation company with 10,001+ employees
Real User
Our effort for DR is a fraction of what it was; we just click the VMs that we want to protect and they are protected
Pros and Cons
  • "Zerto's support for different hypervisors is a valuable feature because we have a mixed bag. We have VMware and we have Hyper-V. For us, that was extremely critical when we made the decision. We wanted a single tool that is able to replicate all our virtual servers. At this point, I think the only tool on the market that can do that on-premise is Zerto."
  • "We own another solution called VMware Site Recovery Manager, SRM. We have licenses for our entire environment and we still decided not to use it. That's how big the difference was in the experience that Zerto provides."
  • "They definitely have room for improvement in a couple of areas. One is role-based access control. Right now, they don't have an identity source so they use the identity of the vCenter or the VMM. If they connected to an identity source like Active Directory and allowed for granular roles and permissions, that would be an improvement."

What is our primary use case?

It's on-prem only, and we're replicating part of production data centers to the DR location. We use it 100 percent for DR. Zerto, as a product, has a lot of capabilities, but we're only using it to replicate servers for disaster recovery, on-prem.

How has it helped my organization?

Providing DR for the entire organization is a big improvement, compared to the previous way we did DR. With the old DR tool we identified the systems that we wanted to protect and we installed agents and installed a server in the remote location and pretty much treated every physical and virtual server the same way. That tool was agent-based and required installation and maintenance of a server on the remote site. Now, the effort involved is a fraction of what it was before. We just click the VMs that we want to protect and they are protected.

Zerto has reduced the number of staff involved in DR.

It has also helped to reduce downtime. With our old solution, something that took 10 to 15 minutes of outage, required one reboot, which took less than a minute, with Zerto. That amount of downtime would have cost our company a couple of thousand dollars.

What is most valuable?

Zerto's support for different hypervisors is a valuable feature because we have a mixed bag. We have VMware and we have Hyper-V. For us, that was extremely critical when we made the decision. We wanted a single tool that is able to replicate all our virtual servers. At this point, I think the only tool on the market that can do that on-premise is Zerto.

It does a great job of continuous data protection. That's why we're using it for DR. It has the journal, the recovery points. It's doing its job. It's a good tool.

It's extremely easy to use with a very intuitive interface. You can set up a VPG (virtual protected group) and add VMs to it in a couple of clicks. Everything is in a single dashboard and you can do everything from there. If you need some granular information, you click the Analytics and get your RPO or RTO and how much data you would lose if you do a DR at this point in time. 

What needs improvement?

They definitely have room for improvement in a couple of areas. One is role-based access control. Right now, they don't have an identity source so they use the identity of the vCenter or the VMM. If they connected to an identity source like Active Directory and allowed for granular roles and permissions, that would be an improvement.

Another area of improvement is support for clusters. They have very limited support for Microsoft clustering.

Also, integration with VMware could be improved. For example, when a VM is created in vCenter, it would be helpful to be able to identify the VM, by tags or any other means, as needing DR protection. And then Zerto should be able to automatically add the VM to a VPG. 

There is definitely room for improvement. But what they have implemented so far, works pretty well.

For how long have I used the solution?

I have been using Zerto for about five years.

What do I think about the stability of the solution?

It's pretty stable. 

We're always one version behind. The current version is 8.5 and we're running 8. We always wait until at least Update 1 before we upgrade. So when v9 is out, we'll probably upgrade to 8.5, Update 1, or whatever the current update is. Because we are a little bit behind and we're running on a very stable, mature version, we rarely experience issues.

What do I think about the scalability of the solution?

We're running thousands of hosts. Scalability is not a problem.

We plan to keep the product. It's doing a good job.

How are customer service and technical support?

Our experience with their technical support has been good. But keep in mind that we have a pretty high-level, Premium Support agreement with Zerto. We have a dedicated technical account manager from Zerto, and he has direct access to the developers.

Which solution did I use previously and why did I switch?

We used Double-Take DR which treated all the physical and virtual servers exactly the same way with agents. Zerto replaced it.

We switched because it is a little bit inefficient to treat all the virtual machines as separate physical servers, because on the DR site you need to install them, you need to configure them. You need to put the agents on both sites and configure the replication relationship. It's very complex. And whenever you need to patch or do some maintenance on the target site, it's double the work because you patch the source and you patch the target—you have a live server at the remote site. With Zerto, as soon as I patch the VM at the source, the updates are replicated to the target immediately.

Zerto's ease of use is very good compared with other similar solutions for replication.

How was the initial setup?

The initial setup of Zerto is quite simple. You build a SQL instance. You build a Windows VM and install the ZVM on it. You integrate it with vCenter and then, from the ZVM, you make sure your firewall ports are open and you push the VRAs down.

Deployment takes a couple of hours, for a relatively big environment. It would typically require 30 minutes of DBA time, an hour or two of Windows engineering time, and another person from VMware for another hour.

It doesn't require any staff for day-to-day maintenance. It's used by our operations team, which is close to 100 people; those are people who have access to it.

What about the implementation team?

It's quite easy and straightforward. We do it with internal labor.

What was our ROI?

The way we use it there is no return on investment. You can think of Zerto as an insurance policy. We use it to protect our business, but we actually hope that we'll never put it into action.

What's my experience with pricing, setup cost, and licensing?

It's not the cheapest tool, it's expensive. But it's doing a good job.

We pay the standard license, maintenance every year, and we pay for our technical account manager, which is pretty much Professional Services, with our Premium Support.

Which other solutions did I evaluate?

We looked at other solutions. We own another solution called VMware Site Recovery Manager, SRM. We have licenses for our entire environment and we still decided not to use it. That's how big the difference was in the experience that Zerto provides. 

We also compared Zerto with our previous disaster recovery solution, which was called Double-Take DR.

Zerto is much better. It is not a cheap solution. The fact that we decided to buy it when we already had all the licenses for VMware, bundled in our ELA with VMware, should tell you how big of a difference there was.

What other advice do I have?

My advice would be that when you need a tool to bet your business on, as a last resort, make sure you evaluate all the options, test them, and don't be cheap.

The biggest lesson I've learned from using Zerto is that a third-party company can do a better job of protecting the workloads than the vendor. It does a better job than VMware and Microsoft together.

In terms of using the solution for long-term retention, we're evaluating Zerto's offering. It's a new feature. We already have an established backup system, using Symantec. In a couple of years, when we need to refresh Symantec, we might consider it. But at this point we don't use it and we aren't considering it.

We use the Veritas NetBackup solution. They split from Symantec so Veritas is separate, but it was a Symantec solution for backup. We don't use Veeam, we don't use Cohesity, we don't use Rubrik. The only potential is to replace our Veritas/Symantec backup product, in the future, with Zerto Long Term Retention.

If we have a DR situation, we are not planning to fail back. It's not part of our DR strategy. If we need to fail-over a production data center, it means that this data center has been destroyed, it's a smoking hole in the grass. We will be running continuously from the DR data center, which is a full-scale data center.

I would rate Zerto at nine out of 10. There are new features that they're working on, which will be nice to have. That's why I won't rate it a 10, but overall it's a really good, stable, easy-to-use product.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
reviewer1456953 - PeerSpot reviewer
Systems Architect - Cloud at a computer software company with 5,001-10,000 employees
Real User
We are able to show, at a customer-level of granularity, what a customer's RPO was at any point, in real time
Pros and Cons
  • "Four years ago when we did a PoC between two other vendors and Zerto, there were two features of Zerto that sold it, hands-down. One was the ease of creating protection groups, the ease with which our engineers could create protection, add virtual machines into the Zerto product, and get them under DR protection."
  • "The second feature that sold us was the sub-second RPO. One of the things that made Zerto's product stand out from some of the more traditional solutions four years ago was its ability to maintain sub-second RPO over a group of machines, and that group of machines could be spread over multiple storage hardware."
  • "The number-one area in which they need to improve their product is what I would call "automatic self-healing." This is related to running them at scale... We have 1,000 VRAs and if any one of their VRAs has a problem, goes offline, all of the customer protection groups and all of the customers that are tied to that VRA are not replicating at all. That means the RPO is slipping until somebody makes a manual effort to fix the issue. It has become a full-time job at my company for somebody to keep Zerto running all the time, everywhere, and to keep all the customers up and going."

What is our primary use case?

Our use case is 100 percent disaster recovery between two different geographies. We have a very large private cloud offering. We've got about 1,200 customers and almost 10,000 VMs that are under Zerto protection. Every one of those virtual machines needs to be replicated from Waltham to Chicago, from the East Coast of the U.S. to the central U.S. Likewise, we have a European business with the exact same flow, although it's much smaller as far as number of VMs; it might be a couple of hundred. That implementation is going from Berlin to Amsterdam. We've got one-way protection in two different geographies and all of those machines are under Zerto protection.

How has it helped my organization?

The number-one benefit is that for the first time we could show, at a customer-level of granularity, how a customer was protected, and what their RPO was in, real time. Each one of our 1,200 or so customers has a portion of those 10,000 VMs. For the first time we were able to tell a product leader or product manager what the RPO was on Thursday at 2:00 PM for that customer. We could say, "Hey, it was 67 seconds." Our company is very customer-centric and customer-focused. There's less interest in what the overall health is, and a lot of times there's specific interest in, "Hey, how is that customer doing?" either for performance or for RPO time.

Zerto also allowed us to easily pick groups of virtual machines, group them as a whole, and have that be segregated from the storage layer. That is the storage-agnostic benefit from their product. That agnostic feature with respect to the storage layer allowed us to group VMs by customer and not only report on RPO by customer, but also to more easily sell different RPO plans. We were able to prioritize and say, "Okay, these 10 customers have platinum and these 500 have silver."

What is most valuable?

Four years ago when we did a PoC between two other vendors and Zerto, there were two features of Zerto that sold it, hands-down. One was the ease of creating protection groups, the ease with which our engineers could create protection, add virtual machines into the Zerto product, and get them under DR protection. The other products we were looking at required work from two different teams. The storage team had to get involved. With this product, the whole thing could be done by just our virtualization team, and that was a big sell for us.

The second feature that sold us was the sub-second RPO. One of the things that made Zerto's product stand out from some of the more traditional solutions four years ago was its ability to maintain sub-second RPO over a group of machines, and that group of machines could be spread over multiple storage hardware. It was the storage-agnostic features of the product.

What needs improvement?

The number-one area in which they need to improve their product is what I would call "automatic self-healing." This is related to running them at scale. If you're a small company with 50 VMs, this doesn't really become a problem for you. You don't have 1,000 blades and 1,000 of their VRAs running that you need to keep healthy. But once you get over a certain scale, it becomes a full-time job for someone to keep their products humming. We have 1,000 VRAs and if any one of their VRAs has a problem, goes offline, all of the customer protection groups and all of the customers that are tied to that VRA are not replicating at all. That means the RPO is slipping until somebody makes a manual effort to fix the issue. It has become a full-time job at my company for somebody to keep Zerto running all the time, everywhere, and to keep all the customers up and going. 

They desperately need to work self-healing into the core product. If a VRA has a problem, the product needs to be able to take some sort of measure to self-heal from that; to reassign protection. Right now it doesn't do anything in that self-healing area.

For how long have I used the solution?

My company implemented Zerto in 2016, so we've been live with their product for a little over four years.

What do I think about the stability of the solution?

The stability comes back to size and scale. It depends. If you are not replicating heavy workloads—meaning you don't have a SQL server that's doing thousands and thousands of IOPS, and you don't have multiple SQL Servers on the same very large hardware blade—Zerto is incredibly stable, based on my experience with the product. 

However, we are doing that. There's a one-to-one relationship between the Zerto VRA, which is essentially their chunk of code that does the replication, and a physical server. The physical server is running anywhere from one to as many virtual servers as someone can fit onto it. And that one VRA has to manage and push all the change blocks for all the workloads running on it. So if you've got five or six really heavy workloads running, that one VRA that has to handle all of that and push it to your destination can, and does, crash. VRAs in that situation crash or become unstable. We've worked a lot with Zerto over the last two years on tweaking the VRAs with advanced settings. We've directly been involved with identifying a couple of bugs with the VRAs. When the VRAs are pushed, they can only be pushed so far and then they crash.

It does perform. However, we have VRAs that crash all the time. When we go back and we look at why they crashed it's because we're pushing them too hard. We're doing things that they would say we shouldn't be doing. They would say, "Don't set six SQL Servers on the same blade. That's too much. Don't do that."

Zerto has worked with us very effectively on identifying advanced settings that we can make to the VRAs to make them perform better, and to be more stable in the "abusive" environment that we throw at their code base.

It could be more stable for really heavy use cases like that. But Zerto would come back and say, "Well, our best practices would have you put some sort of anti-affinity rule in place so that you don't end up with that many heavy I/O machines on a single blade." They would say that doing so is not best practice; don't do it. You could say that we abused their product, in that sense. 

But it works. If you align with best practices, it's pretty stable.

What do I think about the scalability of the solution?

We have no concerns about the scalability, although I should qualify that statement. Zerto can scale horizontally extremely well. They've got one VRA per blade and that one VRA is their data plane. You can scale out your environment horizontally with as many blades or servers as you want, which is how people do virtualization and Zerto will scale with you. We've never hit a limit as far as its ability to scale as horizontally.

The caveat would be, as I mentioned elsewhere, the size of the pipe in your infrastructure to handle all of that replication. But that doesn't tie to the Zerto product itself. 

In terms of the issue of VRAs crashing, you want to scale horizontally rather than scale vertically, because if you scale vertically you're packing more and more virtual machines into the same number of physical servers. You're stacking them up high rather than across. If you stack them up high you have concerns about the scalability of the single VRA. The VRAs do get overloaded. Don't pack them too high. Scale out, not up.

Zerto has spread out as a company. They've mushroomed out into other areas. They've started to develop a presence in backup and they've started to develop a larger presence in reporting. Their core product, however, is known as ZVR—Zerto Virtual Replication. We've implemented that core product 100 percent. There's no other way we could be consuming it differently or more effectively.

The newer stuff they've come out with—certainly the backup—we don't touch that at all. The backup product is not ready for prime time. It might be good for a small customer that may have 50 machines they want to back up. But for our use case, with SOC compliance, and having to report on the success of backups for recovery, and although we looked very closely at their backup and where they were going with it, it's not ready for us.

They're starting to go into Docker containers. None of our product right now is containerized.

A third area is analytics and reporting. The analytics and reporting would be the one new area that they've put focus on that we could be using more and getting more value out of. They've got a SaaS solution now for reporting called Zerto Analytics. We do use it. You turn on their core product and you tell it to send your reports to their SaaS offering. We've done that and we can consume the analytics product, but we just haven't really operationalized it yet. That, for us, has been a tool looking for a problem.

How was the initial setup?

It took us about two months to deploy the solution, but that was because we're a very conservative company. We purposely went extremely slowly. If we had wanted to go faster, it could have been done probably in a week or two, to get all 6,000 VMs under protection.

What about the implementation team?

When we deployed it, there were two dedicated people at our company who were involved, paired up with three people from a Professional Services team from Zerto. As a tertiary, we had a full-time person from our VAR, the reseller that sold us the licensing for Zerto. With that help from Zerto and the value added reseller, it only took two of us to install it to about 600 blades and probably 5,000 virtual machines.

Our experience was excellent. Both teams were great. It was a very painless rollout.

What's my experience with pricing, setup cost, and licensing?

I'm less involved with the pricing and licensing area now. The last time I was involved was a couple of years ago. In my opinion, their model is somewhat inflexible, especially for their backup product.

One of the reasons why we didn't pursue looking further at their backup product was, simply, licensing. Today we have to buy a Zerto license for every virtual machine that we want protected by their product. We have a lot of virtual machines that aren't production and that don't need to be protected by their product. They don't need sub-second RPOs. They do, however, need to be backed up. But Zerto's licensing model two years ago was, "Well, we don't care that you just need to back up those VMs, and you don't really need to replicate them. It's the same price."

We would have had to double our licensing costs for Zerto to adopt it as a backup solution. It was just not even within the realm of possibility financially. It made no financial sense for us to move off our current backup vendor. Their inability to diverge in any way from that was rigid.

Their licensing could be less rigid and more open to specific companies' use cases.

Which other solutions did I evaluate?

The other two vendors we evaluated back were Site Recovery Manager by VMware, and whatever Veeam's product was at the time. We also looked at CommVault lightly, but they were never considered seriously.

What other advice do I have?

Zerto can do what it says it can do. It can absolutely provide sub-second recovery point objectives, but with a couple of caveats. The caveats tend to apply to large companies like mine, and by "large" I mean if you have over 2,000 to 3,000 virtual machines, versus a small to medium-sized company that maybe has 50 to 500. Once you cross that barrier, you're getting into a larger environment that you're trying to replicate with Zerto.

A couple things can break down. Zerto's product doesn't control the path between your source production data and the destination you're trying to send it to. There can be tons of bottlenecks on that path; you can be going around the world. If the bottleneck doesn't exist there, their product can absolutely do what it says it does. It's up to the customer. The people using Zerto have to understand that they own the bottlenecks in their environment. If there is a bottleneck between production and the targeted DR, the RPOs are going to slip. You're going to go from sub-seconds to minutes or hours. That's not necessarily a fault of Zerto's product. It's the fault of the design of the customer's environment and what they brought it into.

That doesn't just exist for the pipe between the two sites. On the destination side, the side that's receiving this data, the storage layer underneath needs to be more performant than the production side. That's somewhat of a strange concept for a lot of customers and people coming into the Zerto solution. They see the marketing side of, "10 seconds to RPO" and say, "Yeah, I want that." But what it means is that you've really got to look at your hardware and you've got to have class-A hardware the whole way through that Zerto pipeline, for their product to do what it says it does. Zerto makes that very clear. They don't recommend hardware; they're not in the business of supporting other vendors. But they have a published list of best practices. The best practices clearly say everything that I just said. They also have best practices around managing your workload I/O on the source side, so that you don't overwhelm their product.

But not everyone follows best practices. Certainly, when we implemented it we said, "Yeah, we get that. We understand what you're telling us. We understand that's a best practice, but we're not going to do it anyway, because it's too expensive," or we didn't have it in budget for that year. So we knew it  and we went in without following them. A couple of years later, when we got to a tipping point, we realized, "Okay, we need to go back and align with some of those best practices," things we didn't think that we had the time to align with back in 2016. We've made that journey painfully with their product, but they were very upfront with us on what the requirements for their product would be.

Overall, I would rate Zerto as a solid eight out of 10 for the core disaster recovery offering.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Audrey Laurel - PeerSpot reviewer
IT Auditor at a agriculture with 201-500 employees
Real User
Top 20
The benefits are immediate, it is easy to use, and it reduces downtime
Pros and Cons
  • "The most valuable feature of Zerto is the quick recovery time."
  • "The technical support response time has room for improvement."

What is our primary use case?

We use Zerto to back up and recover our data servers.

How has it helped my organization?

Zerto is easy to use.

The near-synchronous replication is beneficial and simplifies my work.

I saw the benefits of Zerto immediately after we started using it.

Zerto does a good job of helping protect our virtual environment.

We have seen a 30 percent improvement in our RPO using Zerto.

We have seen a 40 percent improvement in our RTO using Zerto.

Zerto has helped us reduce downtime in several situations and has helped reduce the amount of our disaster recovery testing.

It helped save 20 percent of our time during data recovery situations due to ransomware.

Zerto has had a positive impact on our IT resiliency strategy.

What is most valuable?

The most valuable feature of Zerto is the quick recovery time.

What needs improvement?

The technical support response time has room for improvement.

For how long have I used the solution?

I am currently using Zerto.

What do I think about the stability of the solution?

I would rate the stability of Zerto eight out of ten.

What do I think about the scalability of the solution?

Zerto is highly scalable.

How are customer service and support?

The technical support offers high-quality responses, but the response time is lengthy.

How would you rate customer service and support?

Neutral

Which solution did I use previously and why did I switch?

I previously used Azure Backup. Zerto is faster and more dependable. 

How was the initial setup?

The initial deployment was straightforward and took two hours to complete. A team of three people was involved in it.

What about the implementation team?

The implementation was completed in-house.

What's my experience with pricing, setup cost, and licensing?

Zerto is expensive but offers many features that make it competitive.

What other advice do I have?

I would rate Zerto nine out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
PeerSpot user
Muhammad Shahbaz Butt - PeerSpot reviewer
Senior Infrastructure Consultant at Azeemi Technologies
Consultant
Top 20
It is flexible, stable, and user-friendly
Pros and Cons
  • "Continuous protection is Zerto's most valuable aspect."
  • "Zerto can improve by offering bare metal recovery for our physical infrastructure."

What is our primary use case?

We use Zerto for disaster recovery and cloud migration.

We are an MSP, so we have Zerto deployed on multiple public clouds, private clouds, and on-premises.

We implemented Zerto because its continuous data protection significantly reduces data loss and downtime costs. In the event of a production issue, we can quickly recover using the user-friendly Check Point feature. Zerto also offers flexible support for storage models, primary and disaster recovery, and hypervisors.

How has it helped my organization?

Zerto's user-friendly interface simplifies data protection tasks. It allows users to create virtual protection groups easily, configure failover and recovery processes, and manage licenses.

Zerto's near-synchronous replication can replicate our primary data center services related to PR, which is essential. But somehow, we are facing some pros and cons on this. If we face any challenge like a ransomware attack on our PR site, with the synchronous mode, it is also replicated on DR. That can affect us. So, if we use an asynchronous model, our data will not be replicated continuously from the PR site to the DR site. There is a specific time bracket where the data has been replicated after a particular time frame. So, there are different types of business cases and business requirements. However, we are comfortable with the near-synchronous model.

Zerto helps us set up any disaster recovery site on a cloud-based model and establish an on-premises-to-cloud migration plan. The continuous data protection feature protects our infrastructure services from ransomware and other bugs.

Our virtual protection groups safeguard virtual machines across various models, including hypervisors and virtualized environments. When configured to route to our disaster recovery site after synchronization between sites A and B, VPGs achieve our desired Recovery Time Objective and Recovery Point Objective, meeting our Service Level Agreement. Flexible protection models range from 250MB to 350MB, with varying time slots to facilitate data recovery between the PR and DR sites.

Zerto provides two functionalities: live migration and test failover. Live migration allows a seamless transition of our primary machine to the disaster recovery site within ten minutes.

Zerto has reduced our RTO from 30 seconds to three to nine seconds and has helped reduce downtime.

Zerto has helped save time in a data recovery situation and helped reduce our DR testing.

It has improved our IT resiliency strategy by 90 percent.

The ability to perform disaster recovery in the cloud is helpful because it can reduce our DR footprint and time.

What is most valuable?

Continuous protection is Zerto's most valuable aspect.

What needs improvement?

Zerto can improve by offering bare metal recovery for our physical infrastructure.

For how long have I used the solution?

I have been using Zerto for three years.

What do I think about the stability of the solution?

Zerto is stable.

What do I think about the scalability of the solution?

Zerto is scalable, and if we need to scale down the line, we know it can handle it.

How are customer service and support?

The technical support is good.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We previously used VMware's Site Recovery Manager. We switched to Zerto because it is easier to use and requires less set-up time.

How was the initial setup?

The initial deployment of Zerto is straightforward. We must set up a VM server and install the VR agents, followed by the PR site.

The deployment times vary depending on the business model, but for someone with full knowledge of Zerto, it can be completed within 30 to 90 minutes.

What about the implementation team?

The implementation was completed in-house.

What other advice do I have?

I would rate Zerto ten out of ten, but I would like it to offer bare metal recovery as well.

No maintenance is required for Zerto.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
reviewer1623552 - PeerSpot reviewer
IT Manager at a engineering company with 10,001+ employees
Real User
Top 20
Provides near-synchronous replication, and improves our RPO, but the backup functionality needs improvement
Pros and Cons
  • "The most valuable aspect of Zerto is the recovery speed."
  • "The recovery processes of large datasets in the Cloud have room for improvement."

What is our primary use case?

We use Zerto for disaster recovery and backup of our application server.

How has it helped my organization?

Zerto's ease of use is moderate.

The near-synchronous replication is good.

We use Zerto to help protect our VMs.

Zerto improved our recovery point objective, but to achieve long-term data retention we had to invest in additional local storage.

From an IT resilience perspective, our UK-wide implementation ensured a swift recovery, solidifying the strategy's effectiveness.

It has enabled disaster recovery in the cloud. This is important from a software recovery perspective to keep things running.

What is most valuable?

The most valuable aspect of Zerto is the recovery speed.

What needs improvement?

The recovery processes of large datasets in the Cloud have room for improvement.

The backup functionality can be improved.

For how long have I used the solution?

I have been using Zerto for five years.

What do I think about the stability of the solution?

Zerto is stable.

What do I think about the scalability of the solution?

Zerto is scalable.

How are customer service and support?

The technical support is good.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We used various solutions in the past including Veeam and Quest AppAssure.

We came to the end of what we could do with AppAssure so we moved on to Zerto.

How was the initial setup?

The initial deployment was difficult. The deployment took a couple of weeks and required around four people.

What's my experience with pricing, setup cost, and licensing?

While Zerto excels in disaster recovery, its backup capabilities fall short. To ensure proper data protection, we require a separate backup solution alongside Zerto for disaster recovery therefore the price for Zerto is high.

Which other solutions did I evaluate?

In our search for a cloud-based disaster recovery solution, we considered both Veeam Cloud Connect and Zerto, ultimately choosing the latter.

What other advice do I have?

I would rate Zerto seven out of ten. It only works for virtual machines, not physical ones. This means we need separate software for physical machine backup, which adds complexity and cost.

Zerto's recovery speed falls in line with what we've experienced from other disaster recovery solutions.

Disaster recovery testing was prevented due to security restrictions. Our policies don't permit creating a sandbox environment that interacts with Zerto.

Four people are required for the maintenance of Zerto.

I recommend Zerto for disaster recovery purposes.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Head of IT at Leadway Pensure PFA
Real User
Top 20
Provides near-synchronous replication, immutable data copies, and impressive recovery speed
Pros and Cons
  • "Real-time replication is a valuable feature, ensuring that changes made to the production site are immediately reflected at the recovery site."
  • "Zerto's solution could benefit from additional security features, such as malware scanning tools at the recovery site."

What is our primary use case?

We use Zerto for our application data recovery.

How has it helped my organization?

Zerto's near-synchronous replication delivers exceptional results. The data at our recovery site is kept nearly identical to production in real-time, minimizing data loss to near zero.

By utilizing Zerto's immutable data copies and adhering to the three-two-one rule, we have established a highly effective recovery strategy.

While Zerto doesn't inherently block unknown threats or attacks, its detailed history logs enable us to revert to a pre-attack state, essentially restoring a clean system.

Our production machine experienced changes that caused the application to crash. To resolve this quickly, we restored the machine to its previous state using a recovery copy located at the recovery site that was made by Zerto. After powering on the restored machine, we changed its IP address, making it accessible again.

Zerto has a positive effect on our RPOs.

It boasts impressive recovery speed. As a customer, all we need to do is power on the machines at the recovery site - that's how simple and fast it is. Even if the recovered state isn't ideal, we can easily rewind to a specific point in time and power up another instance of the machine at that moment.

Zerto makes it easy to migrate data. The total configuration is user-friendly.

While our current RTO is three hours, Zerto can significantly reduce it to just five minutes.

Zerto helps us significantly reduce downtime during hardware failures, software updates, and natural disasters.

While we haven't experienced a ransomware attack, we have a recovery plan in place. If one were to occur, we could quickly restore production to a previous point in time, minimizing downtime and data loss.

Zerto helps us reduce the amount of disaster recovery testing we need to perform, which also allows us to reduce the number of staff required for the testing down to two.

The Zerto application is licensed per VM. However, the amount of data stored on each VM does not affect the licensing cost. Whether we have terabytes or just a few bytes on each VM, the licensing fee remains the same. This means we only pay for the machines we are replicating, which can lead to significant cost savings.

What is most valuable?

Real-time replication is a valuable feature, ensuring that changes made to the production site are immediately reflected at the recovery site.

Another feature I appreciate in Zerto is its detailed logging. This functionality allows us to easily access past data and reconstruct the machine's state at any given point in time.

We can recover the replicated machine at the recovery site by simply clicking it back up from the replicated machine. This allows us to keep the original machine running while the recovered machine is active. It's also vendor-agnostic, meaning it works with different hardware vendors like HP or NetApp. In other words, Zerto adapts to the specific hardware we have regardless of the vendor.

What needs improvement?

Zerto's solution could benefit from additional security features, such as malware scanning tools at the recovery site.

For how long have I used the solution?

I have been using Zerto for five years.

What do I think about the stability of the solution?

Zerto is stable.

What do I think about the scalability of the solution?

Zerto is scalable. We just need to add a license and they provide a new key.

How are customer service and support?

The technical support team offers an excellent service. They empower customers by providing comprehensive documentation and guidance, helping them resolve future issues independently.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?


How was the initial setup?

The initial deployment was straightforward, and I handled it independently. My only reference was the provided documentation; I required no further assistance.

What's my experience with pricing, setup cost, and licensing?

Zerto's pricing doesn't depend on the number of virtual applications. Even if we have a server with 200 terabytes of data, we'll only pay for protecting that single server, not for the total size of the replicated data. This simplifies our cost structure.

The licensing cost is fair.

Which other solutions did I evaluate?

I evaluated Veeam and SIM before choosing Zerto. Zerto's interface is much easier to use than the other solutions I tested. Integrating into our environment is also seamless.

What other advice do I have?

I would rate Zerto a ten out of ten.

No maintenance is required.

You can save a lot of time researching solutions by choosing Zerto. It's efficient, easy to deploy, and easy to maintain. Additionally, Zerto offers excellent support, including comprehensive documentation, breach and RCM coverage information, and a knowledgeable customer support team.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2025
Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros sharing their opinions.