Zerto is used as our go-to disaster recovery failover software for the replication of key systems from our main office to our main data center. We primarily use it to protect VMs.
Senior Network Administrator at a financial services firm with 1,001-5,000 employees
The level of disaster recovery RPO that we can now offer has been a game-changer
Pros and Cons
- "The near-synchronous replication is key. That has allowed us to provide the low RPOs that we promise. For key systems, that has been the deciding factor."
- "I would like to see improvement on the Zerto Virtual Replication appliances, so that they are a little bit more streamlined as opposed to now where they just span multiple ZVR appliances like there were gremlins... as this thing grows it just spawns unlimited numbers of additional ZVR appliances and you end up with a bunch so that you can't really tell which is which."
What is our primary use case?
How has it helped my organization?
Being able to offer the level of disaster recovery RPO that we do has been a game-changer. Offering that level of RPO would have taken other methods to accomplish, but this has been straightforward.
It has been compatible with our VMware environments as time has progressed. We started using this in 2013. To make it easy and even more seamless, they spanned a Layer 2 subnet from one site to another using networking strategies. That way, when we fail over a VM or an asset, it does not change IPs at all. It has definitely given us a level of recovery that we would not have been able to accomplish as easily otherwise.
Recovery with Zerto is faster because, in the past, I believe our organization implemented asynchronous replication and used replication methods that were specific for storage. Having synchronous replication and an RPO that is essentially nothing, between sites, has definitely increased our response time. It allows us to immediately fail over seamlessly. It has also reduced RTOs throughout, since the recovery point objective in general is just a second. The smaller our RPO gap, the faster the RTOs we get.
In terms of downtime, there was a particular situation where we had an unexpected double outage of our WAN link. Unbeknownst to us, both of the fiber runs, although they were from the same company, ran through the same place, along the same train tracks where there was maintenance going. We were able immediately to fail over to our secondary site and keep downtime to zero.
That was an outage that I now know, in hindsight, lasted a couple of hours and it was during the peak closing of the US market for trading. It would have cost us millions. It would've been bad if something had gone wrong, since we needed to trade "now, now, now," but would not have been available. Thankfully we were able to trade.
Another benefit is that it allows for automated testing and non-impactful testing with the ability to spawn VMs in a test. We can perform any type of DR and integrity testing at will without impacting our production. I can't really quantify it but I know that DR tests definitely move a lot quicker now. Normally, DR testing would happen over a weekend. And it used to be the case that we would fail over everything immediately. We still have tests where we do live failovers with Zerto, because they really want to say we have done them. But we have averted investing time in monthly and quarterly tests over a weekend because we can present the automated testing that happens by Zerto with that test network. Without that, we would have to do monthly live testing, so it saves us time.
What is most valuable?
The most valuable feature is its ability to do failovers from one site to another.
It's also very intuitive, simple, and very straightforward. Its layout doesn't seem very complicated. It shows its features upfront. When I first started using it in 2016, I had not heard about the product, but coming to this company and having to take over managing it was not challenging at all. I was able to intuitively start using it. I have not had any issues with the interface. It's a clean interface and that has allowed me to intuitively use and configure it.
The near-synchronous replication is key. That has allowed us to provide the low RPOs that we promise. For key systems, that has been the deciding factor. The other option would have been establishing VMware's native HA approach, where you have to spawn new VMs. It's not as transparent as Zerto, it's more under the woodwork. Zerto's ability to offer that level of synchronicity and immediateness has enabled us to offer that level of SLA for our processes in case of a disaster.
What needs improvement?
Recently, I started to try to deploy vVols instead of VMFS volumes in my VMware environment and I did encounter an incompatibility. It seems that for Zerto volumes to be protected, there's some sort of limitation with drives having to be either thick-provisioned or thin-provisioned, I forget which. But there's some sort of inherent limitation that causes an incompatibility with vVols and VMware. That has to be overcome somehow. It has to be flexible enough to be able to do its thing.
And for an additional feature, and I'm not sure if this is already in the works, I would like to see improvement on the Zerto Virtual Replication appliances, so that they are a little bit more streamlined as opposed to now where they just span multiple ZVR appliances like there were gremlins. We have our three main ZVR appliances, each one of them associated with one of the hosts, but as this thing grows it just spawns unlimited numbers of additional ZVR appliances and you end up with a bunch so that you can't really tell which is which. Better management of those ZVR appliances would help, if you have to vMotion them off of something.
If you want to migrate a ZVR appliance from one storage to another, you can't really tell what's what and there are multiple pieces related to this ZVR appliance. I would like to see that cleaned up a little bit with better management features for ZVR appliance maintenance overall.
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.
849,190 professionals have used our research since 2012.
For how long have I used the solution?
I've been with the company since May of 2016, so I've been using Zerto for that long—going on seven years. Through the years, I have become a Zerto-Certified administrator because Zerto offers a free course on it.
What do I think about the stability of the solution?
It's very stable and very hands-off. I have so many other things to do and the last thing I need to be doing is babysitting Zerto, and that's not the case. Thankfully, it's one of those solutions that you set and forget. You pop in every once in a while and make sure the VPGs are still green and thinking.
The only thing that has happened over the years is that the data store that this thing was on might have run out of space, but that was for other reasons. As long as you keep an eye on it, it will probably always be green and you'll never have to do anything.
How are customer service and support?
I've been able to engage with their support many times over the years and I have not had bad experiences with them. They've always been very efficient and prompt in taking me out of very sticky situations.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We already have solutions in place for backup, such as Rubric. We used to be a Veeam shop.
How was the initial setup?
I wasn't involved in the initial setup.
We have two environments, one in our main office and the other in a data center. We have virtual protection groups that protect VMs in the main office and we are able to move them from failover to the data center as a DR strategy. That will change in the future when we move all assets that currently exist in our practice office into the data center as its native location. For now, it's office and data center, but in the future it will be data center and data center.
Our Zerto environment is VMware vSphere 7, and ESXi 7. It's mostly Windows VMs but there are some Linux VMs in there. It's a mixture of thick and thin-provisioned drives, all on VMFS data stores. Those are VMs that it protects and that it is able to move from one place to another.
As for maintenance, Zerto is really hands-off. It's just the usual software updates and that's about it.
I believe the next step is that the recovery ZVMs (Zerto Virtual Managers) will turn into appliances, so they will be full Linux appliances. That will be great because we won't have to patch the Windows box underneath. Once that migration happens, it'll be even easier to manage. The only other thing that I have to do every once in a while is when we have another VM to protect. I edit the VPG and keep moving.
What was our ROI?
We have seen ROI due to the lack of losses from downtime that has been avoided.
What's my experience with pricing, setup cost, and licensing?
The pricing seems reasonable. It's still within what we consider to be value-add. Currently, we're running 50 licenses. We're probably going to downsize because there have been organizational changes in our environment and we don't protect as many VMs as we used to.
Which other solutions did I evaluate?
We have not looked to change over since I got here because Zerto has been that good.
What other advice do I have?
We don't really leverage the restore point backup capabilities of Zerto, although we do, in our virtual protection groups, configure it to have at least two hours' worth of restore points since the last RPO. We also haven't ventured toward DR in the cloud, although there will be initiatives in the future, but it's just something we have not done yet. At least for the assets we're covering with Zerto right now, we've limited ourselves to being able to pivot between data centers.
Currently, we are using it to provide DR coverage for key assets, but I am also going to use it to move all these assets from the practice office in downtown Chicago to the data center, which will be its permanent location. I am going to leverage Zerto's move capabilities to relocate those VMs, Windows Servers, and Linux boxes to the data center permanently. And then I'll establish a recovery relationship between data centers.
For the cost of the product, its value-add, and the return on investment, which is twofold, you should definitely consider Zerto. The hands-off approach and stability of the product alone will give additional dividends. Invest in the solution. It's pretty great.
Zerto is a 10 out of 10 for me. It's one of the easiest pieces of software that I have to manage and one of the most reliable over the years.
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.

IT Director at Kingston Technology
Easy-to-use interface, good telemetry data, and the support is good
Pros and Cons
- "If we lost our data center and had to recover it, Zerto would save us a great deal of time. In our testing, we have found that recovering the entire data center would be completed within a day."
- "The onset of configuring an environment in the cloud is difficult and could be easier to do."
What is our primary use case?
Originally, I was looking for a solution that allowed us to replicate our critical workloads to a cloud target and then pay a monthly fee to have it stored there. Then, if some kind of disaster happened, we would have the ability to instantiate or spin up those workloads in a cloud environment and provide access to our applications. That was the ask of the platform.
We are a manufacturing company, so our environment wouldn't be drastically affected by a webpage outage. However, depending on the applications that are affected, being a $15 billion dollar company, there could be a significant impact.
How has it helped my organization?
Zerto is very good in terms of providing continuous data protection. Now bear in mind the ability to do this in the cloud is newer to them than what they've always done traditionally on-premises. Along the way, there are some challenges when working with a cloud provider and having the connectivity methodology to replicate the VMs from on-premises to Azure, through the Zerto interface, and make sure that there's a healthy copy of Zerto in the cloud. For that mechanism, we spent several months working with Zerto, getting it dialed in to support what we needed to do. Otherwise, all of the other stuff that they've been known to do has worked flawlessly.
The interface is easy to use, although configuring the environment, and the infrastructure around it, wasn't so clear. The interface and its dashboard are very good and very nice to use. The interface is very telling in that it provides a lot of the telemetry that you need to validate that your backup is healthy, that it's current, and that it's recoverable.
A good example of how Zerto has improved the way our organization functions is that it has allowed us to decommission repurposed hardware that we were using to do the same type of DR activity. In the past, we would take old hardware and repurpose it as DR hardware, but along with that you have to have the administration expertise, and you have to worry about third-party support on that old hardware. It inevitably ends up breaking down or having problems, and by taking that out of the equation, with all of the DR going to the cloud, all that responsibility is now that of the cloud provider. It frees up our staff who had to babysit the old hardware. I think that, in and of itself, is enough reason to use Zerto.
We've determined that the ability to spin up workloads in Azure is the fastest that we've ever seen because it sits as a pre-converted VM. The speed to convert it and the speed to bring it back on-premises is compelling. It's faster than the other ways that we've tried or used in the past. On top of that, they employ their own compression and deduplication in terms of replicating to a target. As such, the whole capability is much more efficient than doing it the way we were doing it with Rubrik.
If we lost our data center and had to recover it, Zerto would save us a great deal of time. In our testing, we have found that recovering the entire data center would be completed within a day. In the past, it was going to take us close to a month.
Using Zerto does not mean that we can reduce the number of people involved in a failover. You still need to have expertise with VMware, Zerto, and Azure. It may not need to be as in-depth, and it's not as complicated as some other platforms might be. The person may not have to be such an expert because the platform is intuitive enough that somebody of that level can administer it. Ultimately, you still need a human body to do it.
What is most valuable?
The most valuable feature is the speed at which it can instantiate VMs. When I was doing the same thing with Rubrik, if I had 30 VMs on Azure and I wanted to bring them up live, it would take perhaps 24 hours. Having 1,000 VMs to do, it would be very time-consuming. With Zerto, I can bring up almost 1,000 VMs in an hour. This is what I really liked about Zerto, although it can do a lot of other things, as well.
The deduplication capabilities are good.
What needs improvement?
The onset of configuring an environment in the cloud is difficult and could be easier to do. When it's on-premises, it's a little bit easier because it's more of a controlled environment. It's a Windows operating system on a server and no matter what server you have, it's the same.
However, when you are putting it on AWS, that's a different procedure than installing it on Azure, which is a different procedure than installing it on GCP, if they even support it. I'm not sure that they do. In any event, they could do a better job in how to build that out, in terms of getting the product configured in a cloud environment.
There are some other things they can employ, in terms of the setup of the environment, that would make things a little less challenging. For example, you may need to have an Azure expert on the phone because you require some middleware expertise. This is something that Zerto knew about but maybe could have done a better job of implementing it in their product.
Their long-term retention product has room for improvement, although that is something that they are currently working on.
For how long have I used the solution?
We have been with Zerto for approximately 10 years. We were probably one of the first adopters on the platform.
What do I think about the stability of the solution?
With respect to stability, on-premises, it's been so many years of having it there that it's baked in. It is stable, for sure. The cloud-based deployment is getting there. It's strong enough in terms of the uptime or resilience that we feel confident about getting behind a solution like this.
It is important to consider that any issues with instability could be related to other dependencies, like Azure or network connectivity or our on-premises environment. When you have a hybrid environment between on-premises and the cloud, it's never going to be as stable as a purely on-premises or purely cloud-based deployment. There are always going to be complications.
What do I think about the scalability of the solution?
This is a scalable product. We tested scalability starting with 10 VMs and went right up to 100, and there was no difference. We are an SMB, on the larger side, so I wouldn't know what would happen if you tried to run it with 50,000 VMs. However, in an SMB-sized environment, it can definitely handle or scale to what we do, without any problems.
This is a global solution for us and there's a potential that usage will increase. Right now, it is protecting all of our criticals but not everything. What I mean is that some VMs in a DR scenario would not need to be spun up right away. Some could be done a month later and those particular ones would just fall into our normal recovery process from our backup.
The backup side is what we're waiting on, or relying on, in terms of the next ask from Zerto. Barring that, we could literally use any other backup solution along with Zerto. I'm perfectly fine doing that but I think it would be nice to use Zerto's backup solution in conjunction with their DR, just because of the integration between the two.
How are customer service and technical support?
In general, the support is pretty good. They were just acquired by HP, and I'm not sure if that's going to make things better or worse. I've had experiences on both sides, but I think overall their support's been very good.
Which solution did I use previously and why did I switch?
Zerto has not yet replaced any of our legacy backup products but it has replaced our DR solution. Prior to Zerto, we were using Rubrik as our DR solution. We switched to Zerto and it was a much better solution to accommodate what we wanted to do. The reason we switched had to do with support for VMware.
When we were using Rubrik, one of the problems we had was that if I instantiated the VM on Azure, it's running as an Azure VM, not as a VMware VM. This meant that if I needed to bring it back on-premises from Azure, I needed to convert it back to a VMware VM. It was running as a Hyper-V VM in Azure, but I needed an ESX version or a VMware version. At the time, Rubrik did not have a method to convert it back, so this left us stuck.
There are not a lot of other DR solutions like this on the market. There is Site Recovery Manager from VMware, and there is Zerto. After so many years of using it, I find that it is a very mature platform and I consider it easy to use.
How was the initial setup?
The initial setup is complex. It may be partly due to our understanding of Azure, which I would not put at an expert level. I would rate our skill at Azure between a neophyte and the mid-range in terms of understanding the connectivity points with it. In addition to that, we had to deal with a cloud service provider.
Essentially, we had to change things around, and I would not say that it was easy. It was difficult and definitely needed a third party to help get the product stood up.
Our deployment was completed within a couple of months of ending the PoC. Our PoC lasted between 30 and 60 days, over which time we were able to validate it. It took another 60 days to get it up and running after we got the green light to purchase it.
We're a multisite location, so the implementation strategy started with getting it baked at our corporate location and validating it. Then, build out an Azure footprint globally and then extend the product into those environments.
What about the implementation team?
We used a company called Insight to assist us with implementation. We had a previous history with one of their engineers, from previous work that we had done. We felt that he would be a good person to walk us through the implementation of Zerto. That, coupled with the fact that Zerto engineers were working with us as well. We had a mix of people supporting the project.
We have an infrastructure architect who's heading the project. He validates the environment, builds it out with the business partners and the vendor, helps figure out how it should be operationalized, configure it, and then it gets passed to our data protection group who has admins that will basically administrate the platform and it maintains itself.
Once the deployment is complete, maintaining the solution is a half-person effort. There are admins who have a background in data protection, backup products, as well as virtualization and understanding of VMware. A typical infrastructure administrator is capable of administering the platform.
What was our ROI?
Zerto has very much saved us money by enabling us to do DR in the cloud, rather than in our physical data center. To do what we want to do and have that same type of hardware, to be able to stand up on it and have that hardware at the ready with support and maintenance, would be huge compared to what I'm doing.
By the way, we are doing what is considered a poor man's DR. I'm not saying that I'm poor, but that's the term I place on it because most people have a replica of their hardware in another environment. One needs to pay for those hardware costs, even though it's not doing anything other than sitting there, just in case. Using Zerto, I don't have to pay for that hardware in the cloud.
All I pay for is storage, and that's much less than what the hardware cost would be. To run that environment with everything on there, just sitting, would cost a factor of ten to one.
I would use this ratio with that because the storage that it replicates to is not the fastest. There's no VMs, there's no compute or memory associated with replicating this, so all I'm paying for is the storage.
So in one case, I'm paying only for storage, and in the other case, I have to pay for storage and for hardware, compute, and connectivity. If you add all that up into what storage would be, I think it would be that storage is inexpensive, but compute added up with maintenance and everything, and networking connectivity between there and the soft costs and man-hours to support that environment, just to have it ready, I would say ten to one is probably a fair assessment.
When it comes to DR, there is no real return on investment. The return comes in the form of risk mitigation. If the question is whether I think that I spent the least amount of money to provide a resilient environment then I would answer yes. Without question.
What's my experience with pricing, setup cost, and licensing?
If you are an IT person and you think that DR is too expensive then the cloud option from Zerto is good because anyone can afford to use it, as far as getting one or two of their criticals protected. The real value of the product is that if you didn't have any DR strategy, because you thought you couldn't afford it, you can at least have some form of DR, including your most critical apps up and running to support the business.
A lot of IT people roll the dice and they take chances that that day will never come. This way, they can save money. My advice is to look at the competition out there, such as VMware Site Recovery, and like anything else, try to leverage the best price you can.
There are no costs in addition to the standard licensing fees for the product itself. However, for the environment that it resides in, there certainly are. With Azure, for example, there are several additional costs including connectivity, storage, and the VPN. These ancillary costs are not trivial and you definitely have to spend some time understanding what they are and try to control them.
Which other solutions did I evaluate?
I looked at several solutions during the evaluation period. When Zerto came to the table, it was very good at doing backup. The other products could arguably instantiate and do the DR but they couldn't do everything that Zerto has been doing. Specifically, Zerto was handling that bubbling of the environment to be able to test it and ensure that there is no cross-contamination. That added feature, on top of the fact that it can do it so much faster than what Rubrik could, was the compelling reason why we looked there.
Along the way, I looked at Cohesity and Veeam and a few other vendors, but they didn't have an elegant solution or an elegant way of doing what I wanted to do, which is sending copies to an expensive cloud storage target, and then having the mechanism to instantiate them. The mechanism wasn't as elegant with some of those vendors.
What other advice do I have?
We initially started with the on-premises version, where we replicated our global DR from the US to Taiwan. Zerto recently came out with a cloud-based, enterprise variant that gives you the ability to use it on-premises or in the cloud. With this, we've migrated our licenses to a cloud-based strategy for disaster recovery.
We are in the middle of evaluating their long-term retention, or long-term backup solution. It's very new to us. In the same way that Veeam, and Rubrik, and others were trying to get into Zerto's business, Zerto's now trying to get into their business as far as the backup solution.
I think it's much easier to do backup than what Zerto does for DR, so I don't think it will be very difficult for them to do table stakes back up, which is file retention for multiple targets, and that kind of thing.
Right now, I would say they're probably at the 70% mark as far as what I consider to be a success, but each version they release gets closer and closer to being a certifiable, good backup solution.
We have not had to recover our data after a ransomware attack but if our whole environment was encrypted, we have several ways to recover it. Zerto is the last resort for us but if we ever have to do that, I know that we can recover our environment in hours instead of days.
If that day ever occurs, which would be a very bad day if we had to recover at that level, then Zerto will be very helpful. We've done recoveries in the past where the on-premises restore was not healthy, and we've been able to recover them very fast. It isn't the onesie twosies that are compelling in terms of recovery because most vendors can provide that. It's the sheer volume of being able to restore so many at once that's the compelling factor for Zerto.
My advice for anybody who is implementing Zerto is to get a good cloud architect. Spend the time to build out your design, including your IP scheme, to support the feature sets and capabilities of the product. That is where the work needs to be done, more so than the Zerto products themselves. Zerto is pretty simple to get up and running but it's all the work ahead in the deployment or delivery that needs to be done. A good architect or cloud person will help with this.
The biggest lesson that I have learned from using Zerto is that it requires good planning but at the end of it, you'll have a reasonable disaster recovery solution. If you don't currently have one then this is certainly something that you should consider.
I would rate Zerto a ten out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
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.
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.
849,190 professionals have used our research since 2012.
Senior system admin at JBS USA
Synchronizes our VMs and provides reliable backup to our hosts in different plants
Pros and Cons
- "Zerto's near-synchronous replication is extremely important to our organization."
- "It would be good if we could store a snapshot of the images coming through so that we can always go back and have a vision history."
What is our primary use case?
We have multiple plans across the US. We use Zerto to transfer VMs from one plant to another plant, from east to west.
How has it helped my organization?
Zerto is a really great fallback software that gives us the redundancy we need.
What is most valuable?
Overall, the solution is really efficient. Zerto really helped us prevent the delay in bringing up the VM once it transfers because we wanted to ensure everything works.
Zerto's near-synchronous replication works great. We've had some issues before trying to synchronize VMs across long territory ranges, but Zerto did everything we needed it to do. Zerto's near-synchronous replication is extremely important to our organization. Our production line to uptime is almost 99.99%, so the near-synchronous replication really helps out.
We use SAP HANA with Zerto.
We use Zerto to protect VMs in our environment. The solution helps with recovery and ensures that we can transfer our VMs when we have a host failure. We have plants all over the US, and Zerto has really helped us keep everything running at almost 100% capacity.
Because of its near-synchronous uptime and recovery, Zerto's speed of recovery is ten times better than that of other disaster recovery solutions like Veeam and Commvault.
Compared to other solutions, Zerto's ease of use is pretty straightforward. I'm really excited to see how GreenLake has integrated Zerto and made it even more seamless.
What needs improvement?
It would be good if we could store a snapshot of the images coming through so that we can always go back and have a vision history.
For how long have I used the solution?
I have been using Zerto for four years.
What do I think about the stability of the solution?
Zerto is pretty stable software, and it's always been up when we needed it.
What do I think about the scalability of the solution?
I don't see any issues with the solution's scalability. We have 100 plants across the US and hundreds of other plants worldwide and have never had an issue adding any hosts or notes to the tool.
What about the implementation team?
We deployed the solution through a consultant.
What was our ROI?
We have seen a return on investment with Zerto.
What other advice do I have?
Zerto is really good software. It has all the features that I need. I love Zerto's integration with GreenLake, and now that we know more about it, we'll start utilizing it more. Zerto synchronized our VMs and delivered reliability by ensuring our hosts in different plants had a reliable backup.
Overall, I rate the solution an eight or nine out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Chief Information Officer & IT Security Chief & Officer at a insurance company with 5,001-10,000 employees
Integrates well with our environment and is very adaptable to our changing requirements
Pros and Cons
- "It's easy to install."
What is our primary use case?
It's used for general replication services and recovery. We're actually looking at its more integral use in DR in a business continuity role.
How has it helped my organization?
It integrates well with our environment, is very adaptable to our changing requirements, and is fairly easy for our team to use.
Zerto's near-synchronous replication is very efficient, very powerful, and very productive for us. It has helped us organize our recovery process a lot more, so it's led to process improvements.
Zerto is preparing us to do disaster recovery in the cloud rather than in a physical data center. But we are not there yet.
We use it to support disaster recovery on Microsoft, but we are also considering AWS.
We use Zerto to protect our VMs. We're still redefining our RPOs due to Zerto's performance. We're going back and replacing our baseline.
When it comes to speed of recovery, we believe Zerto is above the rest that we know of.
What is most valuable?
I just learned about Zerto's vault capability, which we're going to learn more about. That will be very valuable to us. We get almost real-time replication services.
Those features are so valuable because we're always prepared to restore if we need to.
What needs improvement?
The vault feature will be very valuable to us, so that's one feature we'd like to see implemented.
We're always looking for additional features and value from Zerto. Immutable replication services is one. I heard the vault will be totally protected from any outside influences, so that's another thing we're looking forward to.
We're always looking to integrate better with our environment.
For how long have I used the solution?
I have been using Zerto for roughly six years.
What do I think about the stability of the solution?
So far, it has been stable. No issues.
What do I think about the scalability of the solution?
We haven't tested scalability yet, but we are sure that scalability shouldn't be an issue. We'll find out.
How are customer service and support?
Good. Excellent. Now that Zerto is part of HP, we get greater support from HP's executive team.
Which solution did I use previously and why did I switch?
We used a variety of solutions in the past. Zerto does the job of two or three of those previous solutions, so we were able to consolidate.
How was the initial setup?
Zerto's team helped a lot. It was fairly straightforward and painless.
What was our ROI?
We have not come up with the metrics to determine the ROI yet, but we're working on it.
What's my experience with pricing, setup cost, and licensing?
The pricing, licensing, and setup costs are fair at best. It's not the cheapest, but it works for us.
Which other solutions did I evaluate?
We did evaluate other solutions. Cohesity, Commvault Cloud and Rubrik were the two others we considered.
We liked the resiliency, usability, and use cases of Zerto more.
What other advice do I have?
Overall, I would rate it around a seven out of ten. Once we understand the scalability, it could reach eight.
It's easy to install. Make sure your business requirements align with Zerto's capabilities. Others should study some of the use cases first before making a decision.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
HR Consultant at a consultancy with 1-10 employees
It's fast and automated, with minimal data loss
Pros and Cons
- "The best feature of Zerto is the fast, automated backup and recovery. The data lift for applications is short, with minimal data loss."
- "Zerto's analytics could be more detailed. The analytics report seems to be more difficult to read."
What is our primary use case?
We implemented Zerto to improve our backup speeds and data recovery time. Zerto is deployed across multiple departments, and around 12 admins and analysts currently use it.
How has it helped my organization?
Zerto has improved my organization in multiple ways, particularly its ability to scale. We have a massive environment that is undergoing cloud development because we are not a very old company, and we needed something that could help us. It's doing its job. Zerto supports multifocal scenarios across the cloud and on-premise.
The solution has had a positive effect on our RPOs. The time is faster with Zerto. Another benefit is reduced downtime. Compared to what we used before, I'd estimate it reduces downtime by 25 percent. The solution has saved us time in a data recovery situation. I'm unsure how much, but it's a lot of time. Zerto has reduced our DR testing time by about 30 percent.
Zerto has simplified compliance with industry regulations by including audit logs and official reporting to support regulatory compliance. It has also simplified our workload because it can do so many jobs.
What is most valuable?
The best feature of Zerto is the fast, automated backup and recovery. The data lift for applications is short, with minimal data loss. Zerto has improved my RTO because we can replicate and easily manage our data, which has positively impacted my company.
Zerto is easy to use if the installation is done properly. Its near-synchronous replication is wonderful, but I'm still learning how to use it.
What needs improvement?
Zerto's analytics could be more detailed. The analytics report seems to be more difficult to read.
For how long have I used the solution?
I have used Zerto for 19 months.
What do I think about the stability of the solution?
I rate Zerton nine out of 10 for stability. It's highly stable.
What do I think about the scalability of the solution?
I rate Zerto seven out of 10 for scalability.
How are customer service and support?
I rate Zerto support eight out of 10.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We previously used Microsoft Azure's backup option. It was a little bit cheaper, but Zerto's recovery is faster. It's a little bit more expensive but much quicker.
How was the initial setup?
I wasn't part of deploying Zerto, but I believe it was straightforward for them. It required a four-person team and took around two hours. After deployment, we occasionally experience some software bugs that must be investigated.
What was our ROI?
We've seen a 10 percent ROI with Zerto compared to what we had before.
What's my experience with pricing, setup cost, and licensing?
I rate Zerto two out of 10 for affordability. The licensing model is somewhat complex. Adding more flexible and less costly options would help.
What other advice do I have?
I rate Zerto nine out of 10. I would recommend Zerto to others.
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.
IT Manager at Nevada Bank and Trust
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.
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.
Senior Systems Engineer at a recruiting/HR firm with 1,001-5,000 employees
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.
Enterprise Architect at a transportation company with 10,001+ employees
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.

Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros
sharing their opinions.
Updated: March 2025
Popular Comparisons
Veeam Data Platform
Commvault Cloud
Rubrik
VMware Live Recovery
BDRSuite Backup & Replication
Nasuni
NAKIVO Backup & Replication
Arcserve UDP
Dell RecoverPoint for Virtual Machines
Hornetsecurity Altaro VM Backup
AWS Elastic Disaster Recovery
Datto Cloud Continuity
Druva Phoenix
Precisely Assure MIMIX
Infrascale Backup & Disaster Recovery
Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Software replication to remote sites during disaster recovery?
- What are the differences between Zerto, VMware SRM and Veeam Backup & Replication?
- Why is disaster recovery important?
- Can Continuous Data Protection (CDP) replace traditional backup?
- Can you recommend a disaster recovery automation tool?
- How does Datto compare to ShadowProtect?
- When evaluating Disaster Recovery Software, what aspect do you think is the most important to look for?
- What is the difference between cyber resilience and business continuity?
- Internal vs External DR Site: Pros and cons
- Disaster Recovery Software: Which is the Best Solution in the Market?