Our biggest use case is real-time replication to a secondary site in case of the need for a disaster failover. We also use it for file-level protection and restore, but the main purpose is to help add another layer of protection in the event of a disaster.
IT Analyst at a wholesaler/distributor with 5,001-10,000 employees
We have seen significant reduction in RPOs and are now able to position our DR in the cloud
Pros and Cons
- "The near-synchronous replication is one of the primary reasons we're using Zerto because we have recovery intervals of sub-five seconds. On a scale of 10, where 10 is "very important", this feature is a 10."
- "Zerto's connectivity with automation platforms could be improved. For example, vCenter can use a VMware-developed tool called Site Recovery Manager. That can be integrated with automation platforms such as Terraform, Ansible, Chef, or Puppet, to perform automated, self-sufficient recoveries to essentially avoid any downtime. To my knowledge, Zerto does not have integration with those platforms."
What is our primary use case?
How has it helped my organization?
The biggest improvement we have seen is that Zerto has taken our anticipated recovery time from between hours and days down to seconds or a minute. Zerto has also helped us to protect VMs, and the effect on our RPOs has been incredible. Pre-Zerto, it was days if not weeks. Now it's six seconds. I don't even know if you could compare it to the RPO of our old solution. It's 100x. If we were to recover using our old system, we would lose between a day and a week's worth of data. With this, we lose virtually none.
And in terms of our RTO, recovering and validating the system has gone from between hours and days, to now happening in a matter of 30 minutes to a few hours. It has helped reduce downtime by days. Similarly, our DR testing has gone from being a multi-day process to a multi-hour process, and we use almost all of that time we save for bolstering value in other projects.
As for the number of staff involved in our backup and DR management operations, Zerto has helped us decrease it.
It has also allowed us to locate our DR in the cloud. We currently use Azure, and this ability is incredibly important as it has enabled us to reposition our resources in an environment that is separate from our main environment.
What is most valuable?
The most valuable features for us are the analytics and reporting. Being able to see a snapshot of our environment, and knowing where we stand in our recovery atmosphere using Zerto, are really valuable aspects.
The near-synchronous replication is one of the primary reasons we're using Zerto because we have recovery intervals of sub-five seconds. On a scale of 10, where 10 is "very important", this feature is a 10.
We also use Zerto for immutable data copies. We have two recovery locations and both of them are immutable, both for short-term and long-term recovery. Using this component has essentially enabled implementation of the 3-2-1 rule for us. Zerto has been pivotal in that process. Before that, the process hadn't changed in about a decade and a half. This enabled us to take a leap into the 21st century in that facet.
What needs improvement?
Zerto's connectivity with automation platforms could be improved. For example, vCenter can use a VMware-developed tool called Site Recovery Manager. That can be integrated with automation platforms such as Terraform, Ansible, Chef, or Puppet, to perform automated, self-sufficient recoveries to essentially avoid any downtime. To my knowledge, Zerto does not have integration with those platforms. Zerto does have an API, but a lot of those automation platforms have prebuilt runbooks to enable that process, whereas Zerto does not.
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.
844,944 professionals have used our research since 2012.
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 incredibly stable, to the point that we don't have to second-guess whether it is functioning properly.
What do I think about the scalability of the solution?
Its scalability is infinite. We have yet to run into an issue of resource allocation or scalability.
How are customer service and support?
Their support is very good. Debatably, it's the best support we have seen out of all of our vendors.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
One of our previous solutions was VMware Site Recovery Manager. We switched because we have some servers that have a lot of transactions and we weren't able to afford to lose even an hour's worth of data. Zerto takes that potential data loss down to seconds.
And Zerto is much easier to use.
How was the initial setup?
Our deployment is both on-prem and, for replication, in Azure. The initial setup was straightforward. There was a learning curve in transitioning from our old environment, but it didn't take very long to learn.
It took us about a month to fully deploy.
Outside of updates, it doesn't require any maintenance.
What about the implementation team?
We did it in-house with support from Zerto when needed. On our side there were two or three people involved, but it was primarily done by me.
What's my experience with pricing, setup cost, and licensing?
It's expensive, for sure, but for us, it comes down to the fact that we do not replicate our entire environment using Zerto. We replicate the mission-critical servers and services, so the yearly cost of Zerto is heavily outweighed by the potential cost of an outage. It's expensive but worth it.
Which other solutions did I evaluate?
We very briefly looked at solutions such as Veeam and the option of continuing to use VMware SRM. The biggest difference was the de-snapshotting of the environment into journals with extremely low RPOs, versus scheduling a snap at a certain time.
What other advice do I have?
Overall, Zerto is pricey and it fulfills a very specific need, but it is incredibly worth the investment if uptime and recoverability are priorities.
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.

ISD Engineer at a financial services firm with 10,001+ employees
Powerful and reliable
Pros and Cons
- "The most valuable feature is Zerto's ability to precopy data to a remote destination prior to the actual live migration period. That saves us a lot of time and has been very helpful. For example, if we had migrations occurring in waves over a period of several weeks with a VPG or VPG setup of approximately 50 VMs, that is multiple gigabytes of data, even terabytes in many cases. Having that data already copied on the evening of the migration saves considerable hours of time. It easily saves us four to six hours a night."
- "The VPG model causes us a bit of concern. We are considering using Zerto to replace Site Recovery Manager. Site Recovery Manager is very easy when we have entire data scores being replicated. We don't have to make any decisions when it comes to groupings. It is all covered. If we move to Zerto, which we are considering, we will have to work much closer with the applications teams to develop the VPG configuration and determine how the VMs will be grouped. It will be a lot more overhead for us to go that route."
What is our primary use case?
We have previously used Zerto for data center migration projects. We have another data center migration coming up within the next year where we will be using Zerto as well.
How has it helped my organization?
We had pretty strict requirements when it came to cross data center migration capabilities. We wanted to ensure that no plugins or drivers were needed. We also wanted a simple deployment. Zerto very easily fit that bill.
What is most valuable?
The most valuable feature is Zerto's ability to synchronize data to the remote destination prior to the actual live migration date. This saves a massive amount of time during the actual migrations, and has been extremely beneficial. Having the data already synchronized on the evening of the migrations makes the final moves fast, easy, and seamless.
The interface is very easy to use. The product is easy to understand. We have had great success in using it for migrations. The benefit for us has primarily been the ease of use and stability of the product.
What needs improvement?
The VPG model has caused a bit of a concern. We are considering using Zerto to replace Site Recovery Manager. SRM is very easy when we have entire data stores being replicated. We don't have to make any decisions when it comes to groupings of VMs. If we move to Zerto, which we are considering, we will have to work closely with our applications teams to create VPGs and determine how the VMs will be grouped. This will probably be beneficial in the long term, but short term it will create more work for our team.
I spoke to a Zerto engineer who mentioned that we could do a VPG at the cluster level and a VPG at the datastore level. However, the one issue we've seen with VPGs is if the synchronization fails the entire VPG has to be recreated. Even though we can cover our environment at the cluster level or datastore level, that wouldn't be ideal. We really need a simpler solution for DR that will cover all of our VMs at once, instead of spending a considerable amount of time on VPG creation.
For how long have I used the solution?
We have been using Zerto for about three years.
What do I think about the stability of the solution?
The stability is very good. All of the components that we set up for Zerto have been very stable.
What do I think about the scalability of the solution?
Scalability has met our needs.
How are customer service and support?
Support has been excellent. We had a couple of issues initially with a VPG that wasn't functioning properly. Support was very quick to respond. They were able to assist us and resolve the issue very quickly. We have only had to call support one time.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We also use Site Recovery Manager. SRM does not have the same feature set for migrations that Zerto has.
How was the initial setup?
The product was easy to deploy. At the time, the only thing that we wanted to improve was to have an appliance for the ZVM, instead of a Windows server. I understand an appliance is available now. This will be very beneficial in the future.
The deployment was straightforward. We basically went through the documentation and then had a planning meeting with Zerto. Once we understood all of the requirements we were able to deploy very quickly with really no issues at all. We deployed Zerto in less than a week.
What about the implementation team?
We implemented the product ourselves. Zerto's expertise has always been very good.
What was our ROI?
Our migrations were all successful. We had no issues at any point during the project. That is what really sold us on Zerto.
What's my experience with pricing, setup cost, and licensing?
The licensing costs are not cheap. It is an expensive product. However, you do get what you pay for.
Which other solutions did I evaluate?
There was really no other product that compared to Zerto. Zerto had exactly what we were looking for in a data center migration product. It had the ease of use and interface that we were looking for, that is, very simple and straightforward.
Zerto's ability to copy the data first, then synchronize just prior to the migrations made it much faster and easier for us to use than other solutions.
What other advice do I have?
Understand the VPG configuration. Understand that you will need to make some decisions as to how to cover your VMs. We eventually went with one VPG per VM for our migrations. This is because we discovered if the VPG has a problem, then you need start over and recreate the VPG. If you choose to cover 50 VMs on a VPG, and if that VPG fails for some reason, then you need to restart the whole process. So you need to consider your VPG design and how you are grouping your VMs.
We haven't used it yet for disaster recovery, but that is something that we will be looking at over the next year.
We have had great success with the product. It is one of the very few products that we have recently used that literally had no issues and worked exactly as designed. At every single point in our migration, it was successful. We had multiple migration waves that occurred over a period of a year and a half. We literally had no failures during that entire time, which is of rare in the industry and made us very happy. Now that we have another data center migration project coming up, we decided we were just going to go straight back to Zerto.
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.
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.
844,944 professionals have used our research since 2012.
Sr Manager IT Infrastructure at a transportation company with 10,001+ employees
The replication increases our DR capabilities
Pros and Cons
- "From a management perspective, one of the biggest benefits is to see the excitement of your engineers having a tool that truly enables them, really making their lives easier. That is something that I love. When we came out of the PoC, their eyes were just wide with excitement of what was possible now."
- "They could iron out the licensing aspect of it, so we might be a bit quicker when implementing and starting to use it."
What is our primary use case?
We are using it to decommission a data center, then moving the data over to other data centers that will still persist within our environment. Also, we now have a more robust disaster recovery for a lot of our non-vital, non-critical applications.
How has it helped my organization?
From a management perspective, one of the biggest benefits is to see the excitement of your engineers having a tool that truly enables them, really making their lives easier. That is something that I love. When we came out of the PoC, their eyes were just wide with excitement of what was possible now.
What is most valuable?
The replication would be the best feature. It increases our DR capabilities. We put a lot of time and effort into DR overall. For the amount of time that it takes to test and go through those activities on a regular, recurring basis, well, this cuts down on the time commitment, not just by the infrastructure team, but by the application teams and all their peripherals. Even just from a man-hours perspective, it is a huge cost savings. You cut down three hours per application, and an application has anywhere from three to 12 developers plus others who support that application. So, you are probably looking at 20 people times three hours, then times however many applications we have, which is in the thousands. That compounds pretty quickly.
For how long have I used the solution?
We have been officially using it for three weeks.
What do I think about the scalability of the solution?
It seems as though everything on the scalability factor checks out. However, we will see that very soon in our use case.
We have thousands of applications and servers. There is an exorbitant amount of data.
How are customer service and support?
The support that came in and engaged with us, setting us up through the PoC, were fantastic. Coming out of it, I already have five engineers who have gone through multiple levels of certifications. So, it appears as though that technical expertise, to be able to improve themselves, is right there at their fingertips. It seems highly available. I would rate them as nine out of 10.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We have used Site Reliability Manager (SRM), which is capable, but to a lesser degree. Zerto is 10 times to 100 times easier to use. It is amazingly fast.
How was the initial setup?
I was not involved in the initial setup or deployment.
From the team, the deployment was very straightforward. The proof of concept that we ran took a little over a week. They were able to stand it up from scratch, deploy, and run several tests of varying complexities. Everything went smoothly. We put a contract and agreement together in record timing for our company.
What about the implementation team?
We had a terrific hands-on proof of concept with the Zerto team, where they came in and worked with our infrastructure engineers. Our engineers were completely amazed by the solution's capabilities. As quickly as we could get our licensing in place, we did. Now, we have had our licenses assigned for the last two or three weeks.
What was our ROI?
From our perspective, we are already thin-staffed as it is. So, Zerto has allowed us to focus on other things that are equally important.
We have not been able to apply ROI yet, just because of our circumstances. We are waiting on teams to move out of the data center. However, we are now poised and ready. Once that onslaught of requests come in, that is when we will really see the return on it.
If you are a numbers person, the benefit far outweighs the cost from any other competing software or service provider. When you are talking about trying to keep a reduced amount of engineers in the happiest state possible in their work environment to do the workload that they had traditionally done with double the amount of people on their teams, this tool relieves all the stress that they are carrying with them on a daily basis, even though they don't have to implement it on a daily basis. I have seen that firsthand. That return on investment is almost invaluable.
What's my experience with pricing, setup cost, and licensing?
They could iron out the licensing aspect of it, so we might be a bit quicker when implementing and starting to use it. At the same time, our sales rep and all the supporting team members from HPE and Zerto were great and very flexible. It is hard to be critical of that.
Which other solutions did I evaluate?
We have not done another valuation recently. Zerto was the first in quite some time.
What other advice do I have?
I would rate this solution as nine out of 10.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Cloud Hosting Operations Manager at a energy/utilities company with 10,001+ employees
Reduced the backup recovery time of our main backup solution by several hours
Pros and Cons
- "It reduced the backup recovery time of our main backup solution by several hours. It's reduced our time because before we have to build a system and restore the data, we install the application and restore the data that took us at least a good 24 hours to do that. And now it's really minutes for us to recover our backup solution."
- "I'm not sure if it has throttling, meaning, what's going over the wire and how we can throttle that to reduce the amount of data that's going across the bandwidth. I can't remember if that's something that's in this product. It might be in the more recent version."
What is our primary use case?
We're replicating mainly some of our critical applications. One is our backup solution and then also some critical applications that we don't want to have to recover from tapes. That's been working very well for us. We actually just recently went through a DR rehearsal, where we ran a quick test and that ran for about a week and then completed that test. Then we were able to report that we were able to successfully recover our critical ERP system inside of the remote location successfully.
How has it helped my organization?
I don't have to worry about Zerto so much. It definitely continues working. We definitely have monitoring and everything like this to make sure things are working just fine, but I can't complain about it in any kind of way. I know we are a little behind on the version that we're using and we need to be on the latest and greatest. Right now we're on version 7.0.
It reduced the backup recovery time of our main backup solution by several hours. It's reduced our time because before we have to build a system and restore the data, we install the application and restore the data that took us at least a good 24 hours to do that. And now it's really minutes for us to recover our backup solution.
Zerto reduced the number of staff involved in data recovery or in a data recovery situation. It's now only one person while it was four previously.
What is most valuable?
Comparing it to VMware SRM, Zerto is by far the best that I've used before for providing continuous data protection.
Different parts of the company use VMware, we use Zerto, and then we saw where they were taking us. Ours really takes less than an hour just to do a quick failover. So it didn't make any sense to go with VMware one, so we ended up going with Zerto.
An employee had actually introduced us to it and we looked at it and wanted to try it. He was working for a bank that does quite a bit as far as doing disaster recovery. So if a bank used it then I would definitely use it.
It is fairly easy. It's not as technical to get around it or anything like that.
It's a fairly easy tool to use.
What needs improvement?
I know that Zerto can definitely improve some functionalities. I know some of the cloud pieces probably enable that. At the moment, it's doing what we want for us, and what it's doing for us right now is plenty. I can't say there's any improvement that I can see that needs to be done at the moment.
I'm not sure if it has throttling, meaning, what's going over the wire and how we can throttle that to reduce the amount of data that's going across the bandwidth. I can't remember if that's something that's in this product. It might be in the more recent version.
For how long have I used the solution?
I have been using Zerto for three to four years.
How are customer service and support?
Their support has been very good. I can't complain about them.
How was the initial setup?
The initial deployment was straightforward for the admin that deployed it. It was not complicated. That person left and then another person came in who didn't know anything about this product and he picked it up fairly easily and he's able to manage it with ease.
He's a VMware administrator and he also maintains Zerto.
The deployment was done within a day.
We don't have plans to increase usage because we are at the point where we're closing out. We're migrating some of our data centers and right now I know it's going to continue utilizing what we have. We haven't even hit the capacity of what we've got right now. Because I think the license we have is around 75 servers. We haven't even hit that. The only thing that's stopping us from right now is just that we need to increase the storage at the remote location to handle additional workloads. We have around 14 servers.
What was our ROI?
We have seen ROI from Zerto.
It has reduced downtime. It went from 24 hours to four minutes. It could even be seconds. It's fairly quick.
The dollar amount would equate to something in the millions. For an environment to be restored it means restoring our ERP systems. Then in that ERP in that system, it also has some manufacturing as well.
What's my experience with pricing, setup cost, and licensing?
Pricing is fair. I don't see a big issue with the pricing for what we are trying to do. The things that we're replicating, if it were to go down it pays for it in itself there.
What other advice do I have?
We don't have any plans for long-term retention. They talked to us about it. But at the moment it's not in our forecast to look at that.
We don't have to failback because we just fail to a bubble, in other words. We don't want to bring down production because we're going through migration of our ERP. So we fail it over into this bubble. And that's what we're using. It is the test failover that we're using in that environment. Then in that environment, everything is isolated. That's how we use it today. We have never had to failback back to our main site.
I would rate it a nine out of ten.
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.
Manager of Information Services at a energy/utilities company with 51-200 employees
Good rollback capabilities, easy to use with an intuitive interface, and it has good integration with VMware
Pros and Cons
- "Zerto is easy to use and the interface is very intuitive."
- "It would be nice if we were able to purchase single licenses for Zerto. As it is now, scaling requires that we purchase a multi-pack."
What is our primary use case?
We are an electric utility and we have some pretty critical workloads. We have identified the most critical workloads in our environment and have implemented Zerto as a protective measure for them.
We try to keep our critical workloads protected, which are a subset of our systems. For example, we're not going to protect a print server with Zerto.
How has it helped my organization?
The fact that Zerto provides continuous data protection is key for us. We have tested on a regular basis, and in one case, we tested our entire ERP system. It is a pretty big workload that includes Linux servers, databases, and other components. It's about a 45-minute window to get it back up and running. For our test, we moved the entire system to our DR facility on a weekend, ran it for an entire week from the DR site, and then brought it back the following Sunday. It worked flawlessly.
What is most valuable?
I really like the 24-hour DVR-like rollback. For example, we had an issue a few years ago, when we still had an Exchange server on-premises. One of my staff came in for the morning to do vulnerability management, saw that some updates needed to be applied, applied the updates to the Exchange server, and it totally broke it. Everybody's email was down. To resolve things, we went to Zerto, rolled back to before the updates, and it was all done in less than five or 10 minutes. It was really quick. All of the email functionality was restored and it popped up and said, "Hey, you need an update." I said, "Please do not do that update." It was pretty good.
Zerto is easy to use and the interface is very intuitive. We have never had an issue with using it. We just have a one-man team to perform failbacks or workloads. It is very simple to do and during our test with the Exchange server, it was only a matter of a few clicks. It's always been an excellent product and they've only improved it over time. We're really pleased with it.
The integration with VMware is really good.
What needs improvement?
It would be nice if we were able to purchase single licenses for Zerto. As it is now, scaling requires that we purchase a multi-pack. It hasn't been a big deal for us but it would still be helpful to have a little bit more granularity on the license count.
The only timeline or limiting factor, in my opinion, is how long it takes to replicate. That all depends on your infrastructure, and we happen to be pretty fortunate that we have a nice pipe in between the two locations, between here and our DR site. If you don't have that limiting factor, it's just a matter of time. You just wait long enough for it to replicate over and then you're covered.
For how long have I used the solution?
I have been using Zerto for approximately seven years.
What do I think about the stability of the solution?
We do the updates regularly and Zerto has never given us problems. We work with a lot of different technologies and we have a lot of problems, but Zerto has not been one of them.
What do I think about the scalability of the solution?
We haven't had much opportunity to explore scalability at this point. We're responsible for another organization's IT, as well. They're a sister company of ours and they're smaller than us, so we do all of their IT and we have them on Zerto. They're using us as a DR point.
From an expansion perspective, we scaled up from our initial install to include theirs as well, which I think we got pretty close to doubling our license count.
We are 100% deployed at this point. If we were ever to add another sister company, which is possible because we have other sister companies where opportunities may arise. A lot of the time, they're so small that they can't afford IT, so it's easier to have us manage it. In cases like this, we may have an opportunity to deploy Zerto.
We have a very small team of three people, so Zerto does not affect our headcount. There is me, who is the manager of IT or manager of information services. Then, we have our desktop technician, and then we have our network administrator.
How are customer service and technical support?
We have never had to use Zerto's technical support for anything major. Any time that we have had to contact them, it has been for minor stuff and it's worked out fine.
Which solution did I use previously and why did I switch?
A long time ago, when we had an EMC SAN, there was a VMware plugin that served as a replication solution. However, it was terrible and it never worked.
Zerto is a major upgrade that is easier to use and switching was excellent.
Replacing our legacy solution with Zerto has definitely saved us time and improved the quality of our process. I never felt like I could trust our previous solution, which was a big deal because when you're talking about backups, trust is a major factor. You have to be able to trust your solution and feel like it's going to work in a bad situation.
Zerto is one of those things that you love to have but you hate to have to use because it means that something bad is going on. That said, if there are serious problems then you want to have something that's rock solid. For us, that's Zerto, and we feel strongly about that.
How was the initial setup?
The initial setup was very straightforward. We had some training with some Zerto engineers on how to set up the recovery groups and other things, but once that was set up, we made several changes later on as we played with it. Overall, it was very straightforward to configure and I think that we only had an hour of training.
The deployment took us a couple of weeks to get everything figured out, although it wasn't necessarily Zerto that was the hold-up. We only had a certain number of licenses, perhaps 15 in total. We spent time trying to determine which were our critical workloads, and there was some internal debate about it. From the Zerto perspective, there weren't a lot of issues.
It didn't take a lot of time, just a couple of weeks to get us up and going. We were actually up and technically running within that same day, but to truly boot it and get it where it needed to be, it took a couple of weeks. It was a new technology to us at the time, so it took a while to get up to speed with it.
In terms of our implementation strategy, we just tried to identify the critical workloads, find the ones that really needed to be protected and start to make those recovery groups. Then, we organized them in such a way that things worked properly. For example, the components of our ERP system do have to come up in a certain order. Finding all of that stuff out and fine-tuning the process was part of our strategy. Then, we slowly started moving those workloads across. We broke it down into groups and we did those groups one at a time until the implementation was complete.
What about the implementation team?
Our in-house team was responsible for implementation.
Maintenance-wise, we just keep it updated. Our network administrator applies the updates and checks the health from time to time. We have a dashboard on our big screen if we feel the need to monitor it. If we walk by and it looks like a protection group is in the red or yellow, then we look at what needs to be done to get the problem straightened out.
What's my experience with pricing, setup cost, and licensing?
Price-wise, it's right in line with what we would figure. For what you get for it, it's really a good value, and we've never had any problem renewing it or anything like that.
License-wise, we budgeted $1,000 per VM. The minimum spend on it, in the beginning, can sometimes be a little bit of a headache for people, and they might have to budget creatively to get there, but once you're there, the renewals are worth it.
Licensing requires purchasing packages that consist of several licenses, and they cannot be purchased one at a time.
We paid for an hour of training that we took but otherwise, there have been no costs in addition to the standard licensing fees.
Which other solutions did I evaluate?
We began looking at Zerto for several reasons including the cost, ease of use, and really, the flexibility of it. When you want to switch it over and do a different workload, it's not that big of a deal.
When we first began to consider using Zerto, we had a discussion with a grocery chain that is close to us. It's a specialty grocery chain and they have exotic foods sold out of two different locations. Christmas is their busiest time of year and they have several cash registers at each location doing transactions constantly.
They had to use Zerto during the middle of that Christmastime rush and failover, from one site to the other, all of their point of sale systems. They never lost a penny in transactions. For us, that was a big testimonial. They have a similar size of environment to ours as far as server infrastructure goes, so we didn't even look at anything else.
What other advice do I have?
At this time, we don't use Zerto for long-term data retention. Instead, we have some other technologies in place for that. We have Veem and we have some SAN replication and we have some network-attached storage, as well. We use Zerto as our first line of defense. For example, in response to a ransomware attack, we would use Zerto for sure to roll back before that event happened.
We have not had a ransomware attack, at least not yet. We fully expect that, if it ever does happen, we'll definitely utilize Zerto. It is essentially our insurance policy. If we ever have a ransomware incident, that would be our first line of defense to recover from it. In fact, we really haven't had many opportunities to use Zerto, thankfully. Zerto is one of those things that are great, and we're glad we have it, but you hope we never have to use it.
At this time, everything we do is on-premises but having DR in the cloud with Zerto is definitely something that we want to do in the future.
It is not important to us that Zerto offers both backup and DR functionality. For backup, we have it covered in other ways. Being in the utility business, we're very big on redundancy. In fact, we have backups to cover the backups and we have about five different levels of them that we utilize. Zerto covers the front line, and when something bad happens, we can roll back within a 24-hour period using it. Then, we have deeper levels handled by other products like Veeam. Funnily enough, Veeam kept telling us that they would add Zerto-like features, and at the same time, Zerto kept telling us that they would add Veeam-like features. We continue to use both of them.
I've recommended Zerto to several IT professionals that I've talked to because it's such a good product. I give them examples of what we have done.
Overall, it's a fantastic product.
I would rate this solution a ten out of ten.
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.
Solutions Architect / Building Supervisor at a university with 5,001-10,000 employees
Continuous and reliable data protection, saves us time, and the support is helpful
Pros and Cons
- "It is convenient to use because the API allows for seamless integration when performing our day-to-day operations."
- "Some of the integrations with our internal tools, in particular, company-specific ones, do not work. In cases like this, we have to ask for additional support."
What is our primary use case?
We primarily use Zerto for backing up our databases.
We are heavily invested in database technology. We use SQL databases such as PostgreSQL and MS SQL, and we are also functional with NoSQL databases. Our use cases are majorly relying on databases for financial vendors and most of the time, we have to perform day-to-day operations with respect to finance and accounting.
We have been using the data retention functionality for a long time and whenever there is a failure and the system goes down, we recover the data from that particular snapshot in time.
We also require security, as it is one of the major concerns. Ultimately, we align these two things together.
We are deployed in AWS, although we are also deploying in GCP and plan to do so with Azure as well.
How has it helped my organization?
Zerto provides us with continuous data protection that is reliable. It is convenient to use because the API allows for seamless integration when performing our day-to-day operations.
Currently, we do not have any long-term data retention activities, and it is not one of our core operations. However, in the past, we did have several such use cases.
Using this solution saves us time because we have been capturing the volumes and snapshots, are we able to perform operations on the Delta. This is an important benefit to us because we are able to deploy everything into production, then continue to get the backups and snapshots from there.
Another time-effective benefit is that once we are fully backed up, we are able to perform Lambda functions on our use cases. This saves us a lot of time.
In some instances, Zerto has saved us time and on the number of people involved during failback. The number of people that are involved depends upon how critical the failure is. Any time there is a failure, we have to work from the most recent backups. For example, if the incident happens at 9:00 PM and there is a snapshot that was taken at 8:00 PM, there is one hour of work to make up for. This is much easier and quicker than having to look back at the logs for the entire day.
On a day-to-day basis, using Zerto saves us approximately 20% to 30% in terms of time. Overall, considering both our test and production environments, using Zerto benefits us with an approximate time savings of 60%.
We are using Zerto for DR in the cloud, and it has saved us money over using a physical data center. In a cloud-based deployment, the cost is quite a bit less compared to a physical environment. Also, because the cloud is a pay-as-you-go model, and you don't need the service all of the time, the paid resources are not wasted. I estimate that we save thousands of dollars per year in operations costs.
With our backups fully in place, in the cloud, Zerto has helped us reduce downtime.
What is most valuable?
The most valuable features for me are the fast performance and seamless integration. The performance is one of the main features and the integration has helped me a lot.
When we have a system that is being fully replicated, we also get snapshots. Then, we perform our activities on the snapshots only, which reside on the cloud-based volumes. This means that our production environment is not affected.
We have low latency in production because most of the things we do are on the cloud. When we have the backup, we just start to perform the data operations and with the help of Zerto, we can do this quite efficiently.
Zerto is quite easy to use. With the click of a button, I have been able to use it to do what I need. Furthermore, any end-user that I have worked with has easily been able to make use of its functionality.
What needs improvement?
Some of the integrations with our internal tools, in particular, company-specific ones, do not work. In cases like this, we have to ask for additional support. This is an area that has room for improvement.
If the API integration worked more efficiently then that would be an improvement.
For how long have I used the solution?
We have been using Zerto for between two and three years.
What do I think about the stability of the solution?
Zerto is a stable and reliable product. We have not experienced any anomalies in the tool. For all our use cases and workloads, we rely on it and have found that everything can be done easily.
What do I think about the scalability of the solution?
We have not had problems when we want to redeploy a number of things, so scalability has not been an issue.
We have between 30 and 40 users, including engineers, architects, and management. We are a growing and expanding company, and our workload increased from day to day. I expect that our usage of Zerto and other solutions will increase.
How are customer service and technical support?
We often reach out to contact technical support and it is good. We have a lot of use cases that we need support for because we don't always have a sufficient solution.
How was the initial setup?
The initial setup was straightforward, although we did have some problems. For example, there were instances where we could not integrate with our internal tools and we were not able to solve the problem. We looked at the FAQ and reached out to customer support to ask what the ideal solution would be.
Overall, it took between six and nine months to deploy.
What about the implementation team?
We deployed Zerto using our in-house team.
What was our ROI?
We have seen ROI in terms of time savings, as well as other points.
What's my experience with pricing, setup cost, and licensing?
We subscribe to their annual license package and we have tier one support with them. There are no costs in addition to this.
Which other solutions did I evaluate?
We have evaluated other tools including Veeam and Veritas. There were several factors, including cost, that led us to proceed with Zerto.
What other advice do I have?
My advice for anybody who is implementing this product is to have things properly architected in advance. Otherwise, the implementation will be a hassle. Once the design is complete, if they need to change it then it will be time-consuming.
I would rate this solution a 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?
Amazon Web Services (AWS)
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.
Technology Infrastructure Manager at County of Grey
If we do have an event or disaster, we know that we can recover from that much quicker than we were able to before
Pros and Cons
- "There wasn't anything in place that compares to what we're getting from Zerto. Before Zerto, we didn't have a proper disaster recovery program or application in place. We had a simple backup solution where we could back up our data every 24 hours. So we went from that to being able to recover full systems within a matter of minutes. With Zerto, if we do have an event or disaster, we know that we can recover from that much quicker than we were able to before."
- "Long-term retention of files is a function that isn't available yet that I'm looking forward to them providing. The long-term retention is the only other thing that I think needs improvement."
What is our primary use case?
We needed Zerto in order to provide a disaster recovery solution for the entire organization. We use it to replicate some resources on-prem and for quick recovery. We also use Azure to replicate for disaster. If we ever have a catastrophic failure or attack at our main headquarters, we could failover and run our resources in Azure.
We don't use Zerto for backup, we use Veeam. Once the new long-term retention features are added to Zerto, then we will investigate using it for that and possibly dropping Veeam.
How has it helped my organization?
There wasn't anything in place that compares to what we're getting from Zerto. Before Zerto, we didn't have a proper disaster recovery program or application in place. We had a simple backup solution where we could back up our data every 24 hours. So we went from that to being able to recover full systems within a matter of minutes. With Zerto, if we do have an event or disaster, we know that we can recover from that much quicker than we were able to before.
We use Veeam Backup for data and not for replication so this is purely just for disaster recovery and replication. We don't use it for data backup, we're still using Veeam for that.
Zerto definitely decreases the time and people it takes when we need to failback or move workloads. The benefit of using it with the Cloud is that we don't have to maintain extra hard work or an extra infrastructure for disaster recovery. With Zerto and Azure, it can all be done essentially by one person. If we're restoring data and systems from the cloud, it can all be controlled from the Zerto interface, whether it's on-premise or in the Cloud. To move the data back, depending on the size of the disaster, if we were to have to rebuild our hardware on-premise, that would obviously require more people. But if it's just a matter of restoring data from the Cloud, it would only need one person. Whereas before, you could probably still do it with one person, but the amount of time that would take would be a lot longer. We would have had to rebuild servers to restore the data. With Zerto, we can restore entire servers from our Cloud repository and have them up and running, it would just be dependent on the speed of the internet. Zerto could easily save us days of time.
It saves us time in data recovery situations due to ransomware. If we had a ransomware attack, we could have our systems available for investigation and run our environment entirely in Azure, separate from our on-prem network. With Zerto as well, we could also recover our systems to the point in time before the ransomware attack happened, ensuring that it doesn't happen again. With our resources in the Cloud, we can scan it for infections and pull it out if it's been lying dormant. The big benefit against ransomware is that we can easily just go back in time to the point before the attack.
The ability to do DR in the Cloud rather than in a physical data center has enabled us to save money. It has saved us quite a bit of money by utilizing Cloud resources, instead of buying a whole new recovery site on-premise. We did an analysis of the buy and one of the reasons why we went with Zerto on Azure is because of the amount of money that we would save over a five-year period. Based on our analysis, it saved us roughly $25,000 a year.
What is most valuable?
The one-click failover feature is very valuable because of the ease of use as well as the little to no data loss with the constant replication in journaling technologies that it has.
The one-click failover feature is really valuable to us because we need a solution that's easy to use. There's the potential that myself or other staff may not be available at the point of the disaster and it would be possible to have somebody who may not know the technology be able to initiate a failover on our behalf by simply just asking them to click a button.
The important features of having little to no loss of data are extra valuable because if we do have a failover event or an event where we need to initiate a failover for disaster, having no data loss is really important because if we were to have a disaster where we needed to initiate the failover for recovery, and if there was data loss, that's lost time from staff. It's also really hard to tell what data is lost and what has to be made up. We have certain resources here that can't afford any sort of downtime or loss of data.
Its journaling technologies are always sending replicated data up so that we can view what the recovery point objectives would be in real-time. We can see it could be a matter of six seconds to a couple of minutes, and that gives us peace of mind that things are moving constantly so that when we do have a failure, we can go back to pretty much any point in time that we want and have our systems available again.
Zerto is very easy to use, the interface makes it really easy. The wizards that are available, the how-to guides, and the support from Zerto has made it really easy to use. With little to no training, we were able to get it up and running in the test environment in under a day. The interface makes it really easy to use from using it from day to day, setting up new jobs for replications, or even restoring data.
What needs improvement?
Long-term retention of files is a function that isn't available yet that I'm looking forward to them providing. The long-term retention is the only other thing that I think needs improvement.
For how long have I used the solution?
We have been using Zerto for around nine months.
What do I think about the stability of the solution?
Zerto is very stable, we have not had any issues with it so far.
What do I think about the scalability of the solution?
Scalability is fantastic. It can go from a very small number of machines up to a very large number of machines without any issue. We started small and they included more and more to it and I haven't had any issues. We have not had any problems scaling across sites to other sites within the organization and integrating it all together. It's as advertised that it can be in any environment of any size. It scales very well.
Only one or two people are required for the maintenance of this solution. As the manager of technology and infrastructure, I and the system administrators do the maintenance. I mostly work with it. One of my other staff works with it from time to time, but for the most part, it just does its thing and we don't really need to do a whole lot with it.
Zerto is used extensively in my company in the sense that it is our primary disaster recovery solution. It is used for servers throughout the County for all departments. Every system that we have in place relies on Zerto for DR. As servers increase, we will add those servers to Zerto, for disaster recovery purposes. It's completely integrated into our system.
Zerto hasn't reduced the number of staff involved in overall backup and DR management only because we have a small team to begin with. Our infrastructure team that I'm in charge of is only six staff. So DR and backup is one job amongst many, for all the staff here. The amount of time dedicated hasn't changed a whole lot for us.
How are customer service and technical support?
Their support is fantastic. Anytime we've had an issue, which has been not too many, they've been very good to resolve any issues.
Which solution did I use previously and why did I switch?
We also use Veeam and it is really easy to use too. They're both easy programs to use. If anyone can use Veeam, they can use Zerto. I wouldn't say Zerto's any easier or Veeam's any harder. They do different things; Veeam does back up really well. If you need a backup solution, Veeam is far cheaper. Whereas Zerto is fantastic at disaster recovery and replication, but when it comes to backup, that's not really what it's made for. Moving forward that may change. But Zerto is definitely a much costlier program compared to Veeam but it does a lot more.
How was the initial setup?
Zerto itself was straightforward to set up. There was good documentation available and we utilized some of their engineering services to help set up as well. For the size of the products and the complexity that it can do, the actual setup and operations over this are quite easy. It took a couple of days, which included getting everything in Azure set up properly.
The implementation strategy that we did was to create the on-premise environment for a dedicated network, virtual machines, and the installation. Then Azure would become our disaster recovery site in the event that we needed it if we had a disaster on-premise, we could failover all of our services and servers that we needed to in Azure. Then our client computers would connect to them while in the Cloud while be prepared for recovery on-premise.
What about the implementation team?
We utilized a third-party consultant to assist with setting up our Azure environments and Zerto technicians helped us set up Zerto on Azure. Our experience was really good. There were some challenges and there was lots of learning to do, but overall, the experience was good. The staff from Zerto were exceptionally good. They really know the product well, helped quite a bit, and provided instructions and training on how to use it outside of that.
What was our ROI?
I think that return on investment will come in the event that we do have a disaster that we need to recover from. We have seen some ROI from Zerto by moving virtual machines between data centers, where that has saved us a lot of time. The technology not only is useful for disaster recovery, but also for server maintenance and moving resources between posts and impairments. Before, it could take hours to copy virtual machines, even days. We use Zerto to move resources around with little to no downtime in a lot quicker time. So we were able to save staff time and resources by using Zerto.
It wouldn't have cost us too much with the government. It's hard to equate a lot of downtime to dollars and cents for us because it's more so around staff time and convenience. We have long-term care homes that we need that are up all the time. And any of those maintenance windows we usually schedule after hours. So it's more of an inconvenience for IT staff to work overnight instead of during regular business hours.
What's my experience with pricing, setup cost, and licensing?
Zerto is not cheap; however, it is worth the cost. The licensing model is easy. You buy based on the amount of virtual machines you want to protect and go from there. Even though it is not a cheap program, you do get what you pay for, but overall it became cheaper than maintaining a separate data center.
Which other solutions did I evaluate?
We looked at Cohesity, Rubrik, and Commvault. Veeam does replication as well, but it doesn't do it nearly as well. We looked at a few other solutions from Dell. We went with Zerto because it had all the disaster recovery functions that we needed, the ability to recover within minutes with minimal to no data loss, and is integrated well with Azure.
What other advice do I have?
I would recommend doing the free proof of concept exercise with Zerto pre-sales engineers and work with them to discuss your environment and then review their recommendations on implementation. From time to time do the free training. I highly recommend doing that. Get your hands on this software and try it out first before doing the production implementation.
The biggest lesson I have learned is that disaster recovery doesn't have to be hard.
I would rate Zerto a ten out of ten. I don't rate many things ten, but Zerto offered me exactly what they're upfront with, what it will do, and it's doing exactly what they said it would do.
Which deployment model are you using for this solution?
Hybrid 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.
Infrastructure Architect at a comms service provider with 1,001-5,000 employees
User-friendly, easy to set up, and offers good speed to recovery times
Pros and Cons
- "The disaster recovery features are the best I've found."
- "We'd like to be able to migrate data without its operating system or any other functionality and without having to go through a virtual machine or server."
What is our primary use case?
The solution was primarily used for disaster recovery for clients. If there was a major issue in the data center, it allowed the client to move to the second data center. It was also used for migration to virtual machines.
How has it helped my organization?
My customer recently (a few years ago), had a major issue in one of the data centers. It was a virus attack that destroyed the servers and virtual machines. We could not recover those servers or virtual machines. After that, we decided to remove the corrupted data center and get everything recovered using Zerto. We were able to do that with the agreed-upon RTO and RPO for the customer.
What is most valuable?
The replication between data centers is great. It allowed us to ensure all data was replicated from one side to another.
The near-synchronous replication is great to have. It works better than other solutions.
It's very user-friendly and straightforward. There are no bugs in the software.
The disaster recovery features are the best I've found.
This product allows us to do disaster recovery in the cloud rather than the physical data centers. We have multiple customers who are on a hybrid cloud. Some are on a private cloud and some are on a public cloud and Zerto allows us to provide the functionality whereby we can cover both as well as across physical data centers. We use Zerto for AWS, Azure, and GCP.
It was nice to use with AWS. Everything was in place on AWS and the functionality is well documented. We've done a POC on it. We have not yet had a chance to do a real disaster recovery just yet.
Zerto has helped us protect VMs in the customer environment. The overall effect on the RPOs is good. We can do it at a maximum within 15 minutes, however, often we can do it within five minutes, or even one minute.
The speed of recovery is very quick compared to other tools.
It's easy to migrate data with Zerto. It's simple. Even non-technical users can see what information is needed in order to enable the replication from one site to another.
Users can still collaborate during the migration process in Azure. It depends on how much data you are including from your data center. The bandwidth connectivity between two data centers is very high.
The RTO is pretty good. We typically give our customers a heads up it will be eight hours, however, it's often less.
It's helped us reduce downtime. For example, when I was using another solution, we wanted to restore a VM. It took more than eight hours to restore ten virtual machines. In contrast, Zerto only takes 45 minutes.
We had a corruption at one point on 20 to 25 VMs, that were critical from the customer's point of view. They had already spent so much time trying to troubleshoot. We decided to use Zerto to restore the machines and give them the latest backup. We were able to give them everything in less than one minute.
For the customer to recover using a different solution, it would take much longer. Zerto takes far less time. For example, compared to VMware SRM, it takes almost double the time compared to Zerto.
We've been able to reduce DR testing. When we used to give RPO and RTO time to our customers, two hours for RPO and eight hours for RTO, once we started using Zerto, we reduced RPO to 15 minutes.
It's reduced the staff time involved in a data recovery situation. When we initially set up Zerto, it immediately starts replicating and does incremental replication as well. Therefore, at any given point in time, the latest data is already available on the recovery side. We just have to trigger it and everything will be restored as per our configuration. We likely save three to four hours of work during the disaster recovery period. And, in the disaster recovery phase, every minute is crucial.
It's also reduced staff involvement. It's not complex and very straightforward. Since tasks are reduced, we do not need so much staff.
What needs improvement?
Previously, it was not compatible with the public clouds. However, now that it is, it's helped a lot. One of the most challenging aspects in migrating items from private to public.
We'd like to be able to migrate data without its operating system or any other functionality and without having to go through a virtual machine or server.
For how long have I used the solution?
I've used the solution since 2015. I stopped using it around 2022.
What do I think about the stability of the solution?
The solution is absolutely stable. We have customers that have used it since 2016 without any concerns.
What do I think about the scalability of the solution?
The product can scale.
How are customer service and support?
We haven't had to engage with technical support.
Which solution did I use previously and why did I switch?
I'm familiar with VMware SRM.
Not a lot of people in the market are aware of Zerto. They need to market it better.
However, Zerto is pretty simple and straightforward, compared to other options on the market.
Replacing the legacy solution has helped customers remove compatibility issues and reduce costs.
How was the initial setup?
The deployment of the product is straightforward. We have, for example, more than 100 VMware ESX-site servers and there are two agents in terms of virtual machines that get deployed on all of them.
To deploy the solution, it only takes 30 minutes. You only need one or two resources to manage the implementation. The maintenance is minimal. Once it's set up, it's fine.
What was our ROI?
Our customers have witnessed an ROI.
What's my experience with pricing, setup cost, and licensing?
The product is cost-competitive and less than other options. I do not have too much data on the exact costs, however. However, we are definitely saving costs when we compare Zerto to VMware.
What other advice do I have?
My understanding is we have a partnership with Zerto. It provided free training to our employees and we have done multiple certifications.
We did not use it for immutable data copies.
We don't use it for blocking unknown threats and attacks. We don't use it for security purposes. We have other security protection services for our customers, including firewalls and antivirus. We use Zerto only for disaster recovery.
I'd advise potential users to pay attention during the initial setup and watch what you are replicating from one side to another. After the setup, you will not have to put a lot of time in - as long as you pay attention during the initial phase.
I'd rate the solution nine out of ten.
Which deployment model are you using for this solution?
Hybrid 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. The reviewer's company has a business relationship with this vendor other than being a customer: Partner

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
AWS Elastic Disaster Recovery
Datto Cloud Continuity
Druva Phoenix
Precisely Assure MIMIX
Infrascale Backup & Disaster Recovery
Vision Solutions Double-Take
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?