We use it mostly for VMs that are hosting client-facing applications and mostly client databases. We replicate 100 servers; we have 100 protected VMs.
VMware Systems Engineer at a computer software company with 501-1,000 employees
Is stable, easy to use, and has good technical support
Pros and Cons
- "We've never had any major headaches with the virtual-protection groups. They seem to work exactly as they should. If there's ever an issue with replication, we know right away, so it's all been very reliable."
- "The time between releases is too long. Zerto doesn't seem to really keep up with the products with which they need to be compatible. For instance, the 9.5 updates 3 took about 90 days to come out after the latest version of vCenter 7.0 update 3 was released."
What is our primary use case?
What is most valuable?
We've never had any major headaches with the virtual-protection groups. They seem to work exactly as they should. If there's ever an issue with replication, we know right away, so it's all been very reliable.
Zerto is much easier to use than Veeam when you compare the two in terms of ease of use. Everything is very straightforward and simple in the Web Client. It's very clear if something is wrong, and everything in the Web Client works great. In Veeam, it's a little more complex; I find myself having to look through long error messages when a job fails. Whereas with Zerto, if I see a red VPG I can click on it. I would then know exactly which VM is having an issue, and I can try to troubleshoot the issue.
What needs improvement?
The time between releases is too long. Zerto doesn't seem to really keep up with the products with which they need to be compatible. For instance, the 9.5 updates 3 took about 90 days to come out after the latest version of vCenter 7.0 update 3 was released.
We were facing a vulnerability, so we had to choose between patching our vCenter to address that vulnerability, which would break the Zerto operability, or leaving it as is with a potential vulnerability. That was really the main issue we ever faced with Zerto.
For how long have I used the solution?
I've been working with Zerto for the past three or so years, but my company used it before I started working there.
Buyer's Guide
Zerto
March 2025

Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
842,690 professionals have used our research since 2012.
What do I think about the stability of the solution?
Zerto is very stable. I've never had an issue related to stability with Zerto, and anytime we have had any potential issues, we get alerts from Zerto. It has always been a simple fix. Also, the issue has never had to do with the platform; it's always been a VM that was powered off or deleted.
How are customer service and support?
Technical support has been pretty sufficient. I've only had one or two cases ever that weren't related to looking for a release date, but I've had pretty good success with them so far.
I would give technical support a rating of eight out of ten. They've never particularly impressed me, but they've always done their job.
How would you rate customer service and support?
Positive
How was the initial setup?
I was not present for the initial setup, but I deployed Zerto Virtual Manager. It was pretty straightforward. You walk through the wizard, and if you have all your networks on the server and everything is done correctly, you can start to build VPGs right away.
If you have all of the network and firewall rules already in place, you could probably stand up a new one in 45 minutes.
What other advice do I have?
It's a pretty set-it-and-forget-it type of tool, and it's very reliable. So, I would rate it an eight on a scale from one to ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.

Principle Systems Engineer at a government with 10,001+ employees
Flexible and easy to use, saves us time in database replication tasks, and a knowledgeable support team
Pros and Cons
- "The most valuable feature is the point in time recovery. This allows us to recover at any point in time, up to a minute or so."
- "I am a little bit worried about how Zerto will work with large volumes of data, such as replication for big data and very large files."
What is our primary use case?
We primarily use Zerto for replication and disaster recovery.
How has it helped my organization?
Zerto is good in terms of providing continuous data protection. We have databases that require point in time recovery capability and Zerto is very flexible in this regard, compared with some other solutions we use, such as Sybase Replication and Oracle Replication.
We do not yet use Zerto's long-term retention feature but we are planning to do so. Currently, we are exploring AWS Glacier for long-term retention, and we will see how Zerto can help with the process.
Using Zerto has helped to simplify our process. The DBS steps are very deeply involved in the case of Sybase replication. This means that it takes a lot of technical skill, time, and effort to manage Sybase replication. Compared with that, Zerto is very user-friendly.
When we need to failback or move workloads, Zerto decreases both the number of highly skilled people involved and the time it takes to complete. For example, to do a command-line restore and recovery of Sybase involves pages of steps and it requires a talented DBA. However, with Zerto, we can take care of that with an intern. Only one person is involved in the process for either case, but with Zerto, fewer skills and experience in recovery are needed.
Fortunately, we have not yet been the victim of a ransomware attack. However, I am confident that Zerto can help, should that situation occur. Similarly, since implementing Zerto, we have not had any downtime. That said, we have simulated different scenarios and our results were good.
What is most valuable?
The most valuable feature is the point in time recovery. This allows us to recover at any point in time, up to a minute or so.
Zerto is pretty user-friendly. Normally, data recovery involves a lot of DBS skills but with Zerto, it is point-and-click.
It is very important to us that Zerto provides both backup and disaster recovery in a single platform. Because of problems that people are facing, we needed to have recovery time objectives (RTO) and recovery point objectives (RPO) for the major cloud providers. This is the primary reason that we were looking for an up-to-date and current solution.
What needs improvement?
I am a little bit worried about how Zerto will work with large volumes of data, such as replication for big data and very large files. I have not tested it yet, so I can't say for sure whether it will choke or not.
The two large clouds that we use are AWS and Azure, and compatibility with these is always important for us.
For how long have I used the solution?
We have been using Zerto for approximately five years. We are using one version back from the current one.
What do I think about the stability of the solution?
In terms of stability, so far it looks okay but I am not sure how Zerto will react to volume loads. We haven't had a chance to test that because we don't have such a large environment.
What do I think about the scalability of the solution?
Scalability has been good but I have yet to see how large a file it can handle.
We have two DBAs using the product, and then we have some interns to help out.
Currently, it is running in a small network where it is backing up a couple of replicated environments. We may increase our usage in the future, as we are now just beginning to back up everything to AWS.
How are customer service and technical support?
Zerto's technical support team is pretty knowledgeable.
Which solution did I use previously and why did I switch?
Prior to Zerto, we were using Sybase replication. When Sybase was acquired by SAP, we began having trouble when we needed technical support. The reason that we started looking for a replacement product is that we used to contact technical support in California when we needed help. However, we now have to call Germany first, only to have them redirect the call to California. SAP is a mess.
How was the initial setup?
I was involved in setting up the proof of concept, and I found that the initial setup was okay.
Once the PoC was complete, we went into small volume testing and then started using it after that. The deployment only took us a couple of hours.
What about the implementation team?
A couple of people from our organization handled the deployment, and we had some Zerto technical reps available to answer questions. The Zerto staff are pretty knowledgeable and they answered the questions well.
What was our ROI?
Compared to the licensing fees with Oracle and SAP, we see a return on investment.
What's my experience with pricing, setup cost, and licensing?
Price-wise, Zerto is fairly reasonable and I can't complain about it when we compare it against Oracle and SAP licensing.
We have not tried using any features that are outside of the standard licensing fees.
Which other solutions did I evaluate?
We looked into Oracle GoldenGate but it is pretty expensive and cumbersome. Sybase is better than Oracle in terms of pricing, but Zerto is cheaper.
What other advice do I have?
We have not yet enabled data recovery in the cloud, but we are planning to use it. As of now, we haven't tested it. We always back things up but in terms of restoring and testing, we are behind.
My advice for anybody who is considering this product is that it is pretty user-friendly compared to Oracle and SAP. This is a good solution to start with. Once it has been implemented, I suggest moving to volume testing to see how well it handles large volumes of data.
We have never had a real situation where we were under the gun for the purpose of RTO and RPO recovery times. As such, I can't say for sure how it will behave in a real situation but we are satisfied with our tests.
I would rate this solution an eight 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.
Buyer's Guide
Zerto
March 2025

Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
842,690 professionals have used our research since 2012.
Works at a wholesaler/distributor with 10,001+ employees
Simplifies our multi-target replication from remote locations that lack redundancy
Pros and Cons
- "We use to use VMware replication appliances to attempt to replicate our VMs to remote locations and servers, but Zerto's one-to-many replication options with deduplication have made the process much simpler without having to constantly worry about the versions of each driver."
- "The number one thing we have found we would like changed so far is the cost per VM. It would be great to get that pricing reduced."
What is our primary use case?
We use Zerto at our remote locations as a backup solution in environments where we don't have the infrastructure for redundancy. It allows us to use two HPE DL380 servers as stand-alone VMware hosts and replicate the VMs without needing shared storage.
How has it helped my organization?
Using Zerto, we are able to replicate / backup our VMs and between servers and locations, without the need for shared storage, which provides redundancy in case of hardware failure. We are able to fail the VMs over to the secondary host, which also allows us to patch or repair hardware without extended downtime.
What is most valuable?
We use to use VMware replication appliances to attempt to replicate our VMs to remote locations and servers, but Zerto's one-to-many replication options with deduplication have made the process much simpler without having to constantly worry about the versions of each driver.
What needs improvement?
The number one thing we have found we would like changed so far is the cost per VM. It would be great to get that pricing reduced.
The need for a VM to be spun up on every host is challenging. In our remote locations, it's not a big issue, but as we look to use that in our main data center where we have hundreds of hosts, it becomes more daunting.
For how long have I used the solution?
I have been using this solution for six months.
What do I think about the stability of the solution?
In the six months that we have used it, we have not had any issues.
What do I think about the scalability of the solution?
So far, it looks like it should scale to our entire environment of over three thousand VMs.
Which solution did I use previously and why did I switch?
Prior to this solution, we use to use SRM. We were looking to switch because SRM continues to be troublesome and requires a select combination of drivers and versions across the environment to work correctly.
How was the initial setup?
This initial setup was pretty straightforward with the exception of needing a VM on every single host.
What's my experience with pricing, setup cost, and licensing?
The cost per VM is a bit high.
Which other solutions did I evaluate?
We also looked at RapidDR from HPE but it only works on our HPE SimpliVity servers and not across all of our hardware.
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.
Director with 51-200 employees
The two key features for AssureStor are hypervisor based replication and the automation for failover, testing and failback.
What is most valuable?
The two key features for AssureStor are hypervisor based replication and the automation for failover, testing and failback.
As a cloud service provider we are always looking at how we can reduce risk for our customers, the ability to provide a DR service that delivers RPO’s typically as low as 15 seconds, over relatively slow connections is fantastic. And as the replication is performed at the hypervisor level we can protect any virtual (VMware or Hyper-V) environment without worry about the storage layer. The automation element is also a crucial element as it ensures we do not have to spend lots of man hours in the event of a DR failover request, as well as streamlining the ability to test the DR environment without needing any down-time of the production environment. And finally add in the ability to automatically reverse replication once you have failed over allowing you to re-seed the production site and failback with minimal downtime and you have a great all-round DR solution.
How has it helped my organization?
Before we took on Zerto our DRaaS offering was based on snapshot based backup’s with an automated restore process to our cloud hypervisors. This was a good service but we could only offer RPO’s as low as 1 hour and even then this was subject to caveats specifically around the size of the VM and how quickly we could ship the new data to our cloud platform. In addition, testing was much more cumbersome and meant a much higher number of hours had to be invested in every DR test, ultimately raising our costs. With Zerto in place we are now offering commercially sound services to small and large businesses without the worry of needing to invest in large numbers of staff to manage and perform testing, etc.
What needs improvement?
Backup capability as it is limited and not as streamlined as it could be. At present Zerto delivers backup protection by making duplicate copies of VM disks to a defined storage location (but this is limited on the schedule and retention). In the latest version 4.5 this has now been extended with the capability to do object level recovery from the replicated VMs, the caveat here is that the retention period is limited to the journal retention (which is a maximum of 14 days). I would like to see a more integrated backup/retention capability in the solution allowing more flexible scheduling and unlimited retention with the capability to easily restore objects using the one Zerto web interface. The backup images should be able to be stored off-site, away from the main replication site, and easily be reintegrated in the main DR platform if needed for VM recovery of an old image.
For how long have I used the solution?
I've been using it for 18 months. v4.5 for the last four weeks, and prior to that we ran v4.0 since our initial deployment.
What was my experience with deployment of the solution?
When we first deployed Zerto we didn’t understand some of the limitations around the built-in database (it uses SQLite). Whilst this would normally be fine for most small to medium deployments (the database is supported for up to 100 protected VMs and 4 sites), as a cloud provider we needed to have greater scalability. This is provided by using a full deployment of Microsoft SQL, thankfully Zerto have a tool that will migrate the SQLite DB into your Microsoft SQL server so the transfer is pain free, but I would make sure that anyone who is deploying in an environment that may have more than 100 VMs to deploy initially on Microsoft SQL. Another area to be aware of in scalability is not with Zerto itself but the demands it can put on the DR storage environment, you will be replicating all your VM disk writes as well as journaling and potentially adding more demand when testing (as the Zerto continues to replicate even when testing, which is great, but does hammer the storage).
What do I think about the stability of the solution?
We've had no issues with the performance.
What do I think about the scalability of the solution?
It's been able to scale for our needs.
How are customer service and technical support?
In one word, fantastic. When we evaluate a product one of the key areas we look at is the level of technical support we will get from the vendor. Bottom line IT systems have a habit of going wrong (one of the reasons I have had a job for the past 20 years), so once you accept that no system will be error-free, you need to know that if you do need help its available. We have had issues, bugs and questions and in every case we have been supported by the Zerto tech support team.
Which solution did I use previously and why did I switch?
Our DRaaS platform, prior to Zerto, was an extension of our Asigra Cloud Backup platform. Whilst this worked it could not deliver the low RPOs we now see with Zerto nor the efficiencies we see from Zerto in managing day-to-day tasks on the platform such as validation, failover tests (and on the odd occasions actual live failovers). Our choice with Zerto was based on our own piece of mind, we protect a variety of end-users so never failing them (i.e. never failing to replicate their VMs and know we can spin them up when needed) was crucial, Zerto has delivered this for us.
How was the initial setup?
Our deployment was fairly complex, but then we had to deploy a platform capable of multi-tenant support with complex networking and integration with vCloud Director so that customers could access their DR systems via a secure web interface. If you are deploying a site-to-site solution then deployment is very straightforward. Each site requires a Zerto Virtual Manager (ZVM) which is deployed upon Windows, this will then integrate with your vCenter servers at each site. From here it’s a few button clicks to deploy the Virtual Replication Appliance/s (VRAs) which are small Linux systems bound to each host that handle the ‘smart’ features of Zerto Replication, linking the site and your off.
What about the implementation team?
Deployment was performed using in-house resources. The most important bit of advice I can offer to anyone considering implementing Zerto is understand your storage requirements at the production site and then decide on what levels of performance are acceptable. If you want to have low RPOs (seconds) then remember that you will be replicating all of your production writes into the DR storage device. And as initially these writes are put into the journal datastore and then read out after the defined retention period and written to the actual storage datastore be careful not to overload your DR SAN. As an example we deploy using separate SANs for journals and customer storage, with larger customers getting dedicated storage designed to accommodate their traffic patterns.
What's my experience with pricing, setup cost, and licensing?
As a Zerto Cloud Service Provider (CSP) our licence model is different to end-users who can purchase the licence on a perpetual basis. For us the ROI was under 6 months, but we already had a large portion of the hypervisor and storage environment needed so were able to keep our costs to a minimum.
What other advice do I have?
Zerto, in my opinion, is one of the best DR products on the market currently, its only flaw (if it can be called that) is that it is limited to virtual environments, specifically VMware & Hyper-V (it does also support replication to AWS if needed). If you are looking to streamline your DR capability and remove risk then speak to Zerto and get them to run you through a demo, what they say the product can do is not sales talk, it really can do it.
Zerto Dashboard
Failover Wizard
Recovery Checkpoints (Journal)
Disclosure: My company has a business relationship with this vendor other than being a customer: We're partners.
Architect at a comms service provider with 10,001+ employees
Stable and scalable solution with a valuable live migration feature
Pros and Cons
- "The most valuable feature of this solution is the live migration."
- "This solution could be improved by being more cloud agnostic."
What is our primary use case?
Our main use case for this solution is disaster recovery, migration and app testing.
How has it helped my organization?
Zerto helped to reduce downtime. I worked a lot in a consulting capacity and experienced DR situations where XYZ was down or a data center was down. Using Zerto to get them back up and online was a lifesaver.
Zerto reduced the staff involved in data recovery. It's a tool that allows you to do a lot just with one person at the console.
What is most valuable?
The most valuable feature of this solution is the live migration.
What needs improvement?
This solution could be improved by being more cloud agnostic.
For how long have I used the solution?
I have been using this solution for eight years.
What do I think about the stability of the solution?
This is a very stable product. I've never heard anybody complain about its stability. I would say it's probably one of the best out there.
What do I think about the scalability of the solution?
This is a scalable solution.
How are customer service and support?
The technical support for this solution is good and their staff are knowledgeable and able to assist quickly with resolutions.
I would rate them a nine out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I've used several other products including Site Recovery Manager. Zerto is the easiest to learn. There is much less of a learning curve. Other tools specific to VMware are now trying to emulate what Zerto has done to make processes easier. Zerto was a huge step in making things more simple to manage. The app works really well and integrates with VMware really well.
How was the initial setup?
The initial setup is straightforward, especially if those setting it up understand the company's infrastructure. The problems are not directly related to Zerto itself. They're always related to how the infrastructure is set up or how the network itself is segmented and having certain people that have control or access and others that don't.
What was our ROI?
The return on investment is in the ease and functionality of the tool as opposed to actually a gain from using the tool.
What's my experience with pricing, setup cost, and licensing?
There may be less expensive solutions on the market but with Zerto, you get what you pay for. A lot of people don't like to think about the price until it's already happened and then the price is too high because they would be losing either way. It's better to think about it and pay for it upfront than pay for it after the problem.
Which other solutions did I evaluate?
We previously used and considered Site Recovery Manager.
What other advice do I have?
I would rate this solution a nine out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Lead Network Security Engineer at a energy/utilities company
File recovery tool offering reliable recovery of data in the case of ransomware attacks
Pros and Cons
- "Zerto gives us peace of mind knowing that if we were attacked by ransomware, we would be able to recover data from the time before the ransomware to get us back to being fully functional."
- "The backup end of this solution could be improved. We tried using it as a full backup solution and it took way too long to complete at least one backup."
What is our primary use case?
We started off using this solution for disaster recovery and DR testing but then it morphed into more of a file recovery tool. We can usually get closer to a point in time recovery using Zerto versus the nightly backups that we do.
How has it helped my organization?
Zerto gives us peace of mind knowing that if we were attacked by ransomware, we would be able to recover data from the time before the ransomware to get us back to being fully functional. Zerto helped to reduce our company's disaster recovery testing model to where we can do it all within a day. We normally pick a time around lunchtime on a set day for the different groups to test with and it is completed by the time lunch is over.
It definitely does make life easier when you're in a situation where you have to have all hands on deck as it doesn't require you to have as many people to bring everything back up.
What is most valuable?
The file recovery functionality is definitely the most valuable as well as the amount of time it takes to recover a VM. The different snapshots it makes are great, especially when we try to schedule DR testing with our business unit. The less time that we have to spin up the environment, the better the whole testing process will go.
One common use case I'll get is when someone says, "I deleted," or, "I've changed a file." I can ask them, "What time did you do it?" If they tell me a specific time, for example, 1:15 PM, I can pull that file at 1:14 PM and recover the data.
What needs improvement?
The backup end of this solution could be improved. We tried using it as a full backup solution and it took way too long to complete at least one backup. We tried it once and didn't try again. I'm not sure if they've improved that since then but we actually went in a different direction for backups.
For how long have I used the solution?
I have been using this solution for six years.
What do I think about the stability of the solution?
This is a stable solution.
What do I think about the scalability of the solution?
We haven't had to scale much as we're a small business. If we were to grow, it would be a couple of servers at a time so I can't really speak to the scalability of it. We have 400 servers total and only use Zerto with what we consider mission critical.
How are customer service and support?
The customer support is excellent. When you call with an issue, they answer almost immediately. The guys are really knowledgeable.
I would rate their support a ten out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We started off with Site Recovery Manager. We did not like the process and once we tried Zerto, we saw how easy it was. That's been the solution until recently as we've added a second data center in which we use now Pure Storage with VMware. They do active clustering and we can use a simple vMotion to move from one site to another versus the way we used to do it before completing a migration with Zerto.
We still keep using Zerto because we know Zerto works. Zerto is a lot faster especially compared to what we used to do with Site Recovery Manager.
How was the initial setup?
The initial setup is straightforward. I just followed the documentation online and it was set up in a day.
What about the implementation team?
I completed the setup myself. There may have been a help check afterwards once we got the first test recovery group setup.
What was our ROI?
Based on the fact that we can rely on Zerto for recovery if anything were to happen and the confidence that our management has in this product, it's definitely worth the money.
What's my experience with pricing, setup cost, and licensing?
We paid a big investment upfront with renewal fees each year. This is another reason why it's easier for us to keep this product as well as have another solution, because we've already paid the money upfront.
What other advice do I have?
When evaluating Zerto, I would advise others to try to think of any potential scenario to test with and use it to prove whether it does or doesn't work.
I would rate this solution a ten 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.
Systems Analyst at a energy/utilities company with 1,001-5,000 employees
Gives us more granularity, but not at the expense of complexity
Pros and Cons
- "The most important features are the simplicity of recovery and the wider capabilities and feature sets than VMware SRM has."
- "I haven't been a super big fan of the support area. The support could really be better in terms of responsiveness. I've had some issues that took two or three days to get resolved. Once I got to the right person, they were resolved quickly, but it took a while to get to that person."
What is our primary use case?
We use it for disaster recovery, by replicating to our DR data center.
How has it helped my organization?
It has simplified our disaster recovery plan. With VMware SRM it was a little bit more complex. Zerto adds more granularity, but not at the expense of complexity.
What is most valuable?
The most important features are the
- simplicity of recovery
- wider capabilities and feature sets than SRM has.
For how long have I used the solution?
I have been using Zerto for about three years.
What do I think about the stability of the solution?
We've been using it since version 7. Since then, it's gotten better and better. We've had some bad experiences with DR tests where everything went sideways and we had to restore a bunch of VPGs or recreate them. It seems like those situations are happening less and less as the product develops.
What do I think about the scalability of the solution?
We have 1,200 seats and we have about 1,000 VMs that are replicated. So far, scalability hasn't really been an issue. We haven't run into a problem scaling it out.
How are customer service and support?
I haven't been a super big fan of the support area. The support could really be better in terms of responsiveness. I've had some issues that took two or three days to get resolved. Once I got to the right person, they were resolved quickly, but it took a while to get to that person.
On a scale of one to 10, today I would rate their support at about a seven. If you had asked me two years ago, I would have rated it at three.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
We were an SRM customer and moved to Zerto. We had issues with SRM and I think we had some issues with Zerto initially. We've had it for three years and we've gone through several revisions. With every revision, it seems to get better. They keep adding feature sets.
SRM and Zerto are really the primary competitors. We like the fact that Zerto does VM-based replication instead of having to involve storage-based replication. You can just point to an instance of it and say, "Replicate to this DR data center," whereas SRM is a little bit more complex in that context.
The speed of recovery between Zerto and SRM is similar. With the later versions of Zerto, the recovery speed has become a little bit faster.
How was the initial setup?
It's very straightforward to set up. You just install the software and point it at your vCenter. There are not really a lot of overly complex parts to the installation. It installs relatively easily and quickly.
What about the implementation team?
We did it ourselves.
What was our ROI?
We haven't seen ROI because we've not ever had to recover anything. But in an instance where we would have to recover from a disaster, we would definitely see ROI. It's like paying for insurance. You don't really see any value in it until you need it.
What's my experience with pricing, setup cost, and licensing?
The licensing is a little bit steep, but there is some value that you do get for it as well.
What other advice do I have?
In our usage, Zerto has not helped to reduce downtime or the number of staff involved in a data recovery situation. It also hasn't reduced our DR testing. We do a DR test regularly and that is about the same as it was.
I don't have any advice, but I would absolutely recommend it. The simplicity of how they have laid out the VPG structure, and being able to separate those out into groups, as opposed to SRM where you're replicating everything, seems like it's really well designed.
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.
Continuous streaming keeps us up to date a lot faster
Pros and Cons
- "The most valuable features are the continuous streaming, that it takes very little CPU usage — it doesn't affect production — and the recovery time is very short."
- "With the VPG (virtual protected group) it would be nice if you could pick individuals in the grouping instead of having to failover the whole group."
What is our primary use case?
It is controlling our mission-critical production system as a backup and a failover.
How has it helped my organization?
Zerto has taken us from being able to do a failover in four to six hours down to one to two hours.
What is most valuable?
The most valuable features are
- the continuous streaming
- that it takes very little CPU usage — it doesn't affect production
- the recovery time is very short.
What needs improvement?
With the VPG (virtual protected group) it would be nice if you could pick individuals in the grouping instead of having to failover the whole group.
Other than that, it's a pretty good product.
For how long have I used the solution?
I have been using Zerto for about a year.
What do I think about the stability of the solution?
It's very stable.
What do I think about the scalability of the solution?
I don't see a problem with scaling it at all. They could improve setting up for SQL clustering or for SQL Always On. It really is set up for a one-to-one and not for a multiple solution. They could work on that.
We will probably increase our usage in the future. Right now we have a license for 15 VMs through Zerto and we are only using 10.
How are customer service and support?
We haven't worked with Zerto's technical support other than during deployment. Everything seems to be running really well now. During deployment, their support was very responsive. It's just that they did not have a good solution that worked with VMware and Nimble.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We were using Veeam. We switched to Zerto because it has continuous streaming that would keep us up to date a lot faster. Veeam kept promising they were going to have that, but they never came through on their promise, after waiting for a year. We were able to convince management to switch to Zerto.
How was the initial setup?
The initial setup of the product was very complex. We were using a SQL Server cluster with a Nimble array, so it was very complicated to get everything set up correctly so it would failover correctly.
Our deployment took about six months. We had an implementation strategy for the solution but it failed three times before they could get it to work. Our deployment plan was set up to failover for our SQL cluster and several web servers to a backup location. In setting up with the Nimble, Zerto recommended that we use an RDM. The RDM did not work. We were using VMware with Nimble and the Zerto team had not used that particular solution before. We jumped through hoops three times before we were able to get the right combination to get the cluster to failover correctly.
There are only three of us working with Zerto. I am the DBA, we have a system administrator, and we have our IT director. We learned very quickly how to use the product very thoroughly since we had to rebuild our solution three times.
What about the implementation team?
We were working with Zerto directly. They didn't have a good solution and we had to test out a lot of things with the hardware and software that we were using. They could have improved that. They kept giving us solutions that would not work, so we had to keep trying different solutions.
What was our ROI?
It's hard to say if we have seen ROI since it's only been running for about four months. I think that we will see cost savings over the next year.
What's my experience with pricing, setup cost, and licensing?
As far as licensing goes, start out with what you need to get started and you can always scale up. Zerto worked very well with us. They have a tool called zPlanner which was able to document how much we needed to get started. That was a very handy tool.
Which other solutions did I evaluate?
We looked at some other options, but nothing really compared to what Zerto offered.
The main differences were the ease of use, not having to have a dedicated person assigned to watching it, and the automation. A lot of this stuff is taken care of through Zerto without us having to script or put a lot of effort in on the back-end. Everything is automated.
What other advice do I have?
Make sure that they can demo what you want done before you move forward. We had a problem with the SQL clustering. Make sure that the equipment that you're using is certified by all the vendors that are involved, like VMware.
Now that we have the solution working, we're very happy. We've had it working for the last four to five months. We were able to test it with a test platform and it worked amazingly.
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?