Try our new research platform with insights from 80,000+ expert users
D. Ngunyen - PeerSpot reviewer
Cloud Architect at State of California
Real User
Helps reduce downtime and has a simple user interface
Pros and Cons
  • "When we use our VMware environment, sometimes the HP hardware is not compatible, and we start to lose data. I like that we can restore our whole application and public-facing system through Zerto."
  • "Zerto can improve the dashboard by making it even more simple. Right now, there's a lot on the dashboard, and it can be overwhelming. If you're an experienced user, then you'll find it easy to use, but if you're a beginner, it will take you some time."

What is our primary use case?

We primarily use Zerto for disaster recovery and backups.

What is most valuable?

When we use our VMware environment, sometimes the HP hardware is not compatible, and we start to lose data. I like that we can restore our whole application and public-facing system through Zerto.

It's the easiest way to do disaster recovery. It's less complicated than VMware.

Compared to the ease of use of other DR or backup solutions, Zerto's dashboard is the easiest. The user interface is much simpler, and maybe, that's what makes it easier.

Zerto helped reduce downtime when our data is corrupted. We're able to restore it relatively fast. There may be downtime of about half an hour for us, but the users don't see it; it's transparent.

The speed of recovery with Zerto versus the speed of recovery with other DR solutions is about the same.

Zerto reduced the number of staff involved in DR situations. We went from ten people to two for the whole organization.

It also reduced our organization's DR testing by about 30%. We've actually been able to move a lot of our resources (people) to AWS Innovation.

What needs improvement?

Zerto can improve the dashboard by making it even more simple. Right now, there's a lot on the dashboard, and it can be overwhelming. If you're an experienced user, then you'll find it easy to use, but if you're a beginner, it will take you some time.

For how long have I used the solution?

We've been using it for seven years now.

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

What do I think about the stability of the solution?

Zertos' stability is very good.

What do I think about the scalability of the solution?

It's very easy to scale, but the only problem is that there are additional costs associated with it. 

How are customer service and support?

Zerto's technical support is excellent. When you open a ticket, they get back to you right away. If you mark it as a priority, then you have instantaneous access to support. I would give technical support 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?

We have VMware products and tried to implement VMware Site Recovery Manager. However, it was just a little too difficult for our environment.

How was the initial setup?

At first, the initial deployment was complex, but now it's relatively easy. For someone experienced, it is not a problem.

We have five data centers, and we started with one and deployed it in phases. Because there are lots of firewalls and access, we picked one data center and then built the next one.

What about the implementation team?

We implemented it ourselves, and it took about a year to deploy it across the whole system.

What was our ROI?

For a long time, we needed disaster recovery that was more than IBM's, which is in Colorado. We needed something on-premises that was instantaneous. That's what Zerto offers, and that's the ROI we have with Zerto.

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

The last time I looked at pricing, it was very good. It's much cheaper than VMware by far.

Which other solutions did I evaluate?

We looked at VMware Site Recovery Manager and IBM, but they didn't work well.

What other advice do I have?

The best way to look at it is from an ease-of-use standpoint because when you look at VMware's version, it's a little bit more complex even though it is native to where we use it. That's why we went with Zerto.

Considering what we use Zerto for, I'd give it a ten out of ten because it is our primary solution.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer1952691 - PeerSpot reviewer
Virtualization Administrator at a financial services firm with 5,001-10,000 employees
Real User
We perform more DR testing now because it is so easy
Pros and Cons
  • "The test features have been really good for us. Our DR testing goes very quickly and easily now for all our stuff with Zerto. We have our priority recovery process, where we cover our databases for our app servers and web servers. All our teams pretty much get their VMs very quickly. The RPOs are very low."
  • "I don't like the evacuation process. The host evacuation process could be a little simpler too. It takes our maintenance a bit longer, when we are doing host maintenance, because we still need to evacuate the vRAs manually. I know they tried to make it more automatic, but it is not quite there yet."

What is our primary use case?

We mostly use it for disaster recovery purposes. We do a lot of migrations as well, e.g., VM from one site to another. We use Zerto for that, as we have hundreds of VMs that we protect as our main DR position using Zerto.

In general, our DR position is entirely based around Zerto. We use it for everything. We just have a couple things that we don't put on it. There are a couple of Oracle things that we replicate with different methods, but we pretty much do everything related to DR with Zerto.

We are not using it for backup. We are using it for continuous DR and replication between two on-prem sites. 

We have two data center sites with bidirectional replications. Each site protects the other site and we have our VPGs that go back and forth.

How has it helped my organization?

We perform more DR testing now because it is so easy. For example, what we are doing right now is baselines on our recovery time objectives, determining, "Okay, if we recover one VM, it takes this long. If we recover another VM this size, it is this long." Then, we recover 10, 100, and 800. That way, we get kind of a forecast, when we add VMs, about how that will affect our DR stance.

When we need to move a VM from one data center to another, it is replicated there. We don't need to do any snapshots of storage. We just make a VPG for it, do a move action, and it is just there. It works really well.

What is most valuable?

The test features have been really good for us. Our DR testing goes very quickly and easily now for all our stuff with Zerto. We have our priority recovery process, where we cover our databases for our app servers and web servers. All our teams pretty much get their VMs very quickly. The RPOs are very low. 

It is very easy to use. There are a lot of training materials online on the Zerto portal, which make it very simple to learn and use. You could go from not knowing how to use it to fully understanding all of it in a day. This can be done by using the Zerto University, getting your little certification and making your boss happy. It is pretty easy to set up VPG-wise.

You have a 24-hour journal. The amount of disasters and things that you can recover from using a 24-hour journal is huge, e.g., ransomware. We haven't had to do that yet, but the possibility is there. It is good to know that you can go back as far as you need.

What needs improvement?

I would like to see the app be more like the analytics site. Right now, when you go into the analytics, you need to zoom in real tight on your browser. You get a lot more from the analytics site than you do from the app. If they made those two more similar, it would be really useful for day-to-day monitoring of your stuff.

I don't like the evacuation process. The host evacuation process could be a little simpler too. It takes our maintenance a bit longer, when we are doing host maintenance, because we still need to evacuate the vRAs manually. I know they tried to make it more automatic, but it is not quite there yet.

For how long have I used the solution?

I have been using it for at least three years in my job function.

What do I think about the stability of the solution?

We have had no problems with it. Stability-wise, I can only say positive things because we haven't had any real negatives with it.

What do I think about the scalability of the solution?

It is very scalable. If you add a data center, then you just add a ZVM at that data center, link it up, and add your vRAs. After that, you are ready to start making VPGs. It is very simple to set up.

We don't have issues with scaling. If a vRA is getting a bit overloaded, it makes little vRAs. So, it kind of handles itself. We have our vRAs at the maximum size, as far as CPU and memory, that they can be. Our RPOs are really short, so we are doing pretty well for our size.

How are customer service and support?

Zerto's support is always responsive. I have never had any problems with it. Our lead Zerto engineer does a lot more stuff than I do as far as with support. Typically, I will escalate to her. If there is an issue, then I defer to her. However, as far as my experience with support, I have experienced nothing but good things. The learning portal, myZerto portal, and analytics are very good. I don't have to use support very often, which is a good thing.

If I were to rate it, I would probably rate it as 10 out of 10. Every time that I have needed them, they have been responsive and quick. I haven't used them that much, but when I have, they have been very responsive.

How would you rate customer service and support?

Positive

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

We have used SRM, who is Zerto's main competitor. 

SRM was pretty quick. However, the speed of recovery with Zerto is so simple. It can failover, e.g., do whatever kind of failover you want it to do. You choose your VPGs, then you are off. It is really fast and simple. A lot of people could handle using it pretty easily.

How was the initial setup?

I haven't found it to be hard. When you add a new host, you just go to set up and add a new host, then it builds a vRA. It is pretty easy to manage alerts. It will tell you exactly what is wrong, e.g., this doesn't have enough scratch disk, so you need to go update that. Or, this host is offline, e.g., you forgot to evacuate it, so then you need to take it out of Zerto. So, it will alert you to that stuff.

What about the implementation team?

I have done my share of deploying vRAs. Though, our lead Zerto engineer handled most of that stuff from the initial setup.

What was our ROI?

We have definitely seen a return on investment. We can move any of our VMs from either of our data centers back and forth very easily, bringing them back and doing tests as frequently as we want. We will be doing two tests next week. At previous companies, we did one test a year. Now, we are doing different stacks, e.g., if we do 20, 100, or 700 VMS, then it will be this long. So, we can forecast additional workload and how much that will affect our DR position.

Zerto is definitely a lot easier to manage. My whole team knows how to use it, since it is very simple to use and intuitive. There are a couple people who use it and I am the secondary person. We have someone who basically lives in Zerto. She adds stuff on a daily basis and we are always on top of our updates. We are always looking at whatever new features come out. We try to maximize our journals. We are up to 24 hours on a lot of them. Our average RPO is eight seconds, and that is pretty good since we have 1,500 VMs and 280-plus VPGs. We have a pretty big on-prem environment. So, the good thing about it is the frequency and ease of testing because Zerto is very simple to use. DR has enough problems to deal with and Zerto makes things a lot easier.

Which other solutions did I evaluate?

We have looked at Veeam and SRM. We examined the marketplace, Gartner, etc. This product that management chose, and we are pretty happy with it.

What other advice do I have?

Give it a try. Move some VMs back and forth to see how easy it is to use. The one-to-many is pretty good. We have two sites, so it is not a very big deal for us to do that, but it is very useful. 

I would rate Zerto as 10 out of 10. I love Zerto's CDP solution. It is really easy to use. It does everything that we need it to do and scales easily.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Zerto
March 2025
Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
849,190 professionals have used our research since 2012.
Daniel Modrušan - PeerSpot reviewer
Assistant Vice President & Principal Systems Engineer at Bangor Savings Bank
Real User
Top 20
Took our disaster recovery practice from sixteen hours down to thirty minutes
Pros and Cons
  • "I love Zerto's near-synchronous replication. I've been using Zerto for three years at my current employer and many years before that. It's been great. Anywhere I've used it, it's made the failover process a lot easier so that pretty much anybody can do it. This feature is our number one priority because we can keep our critical apps running if we have a failure, or even if we have a misconfiguration, it's very easy to recover something quickly."
  • "I would like for them to support additional hypervisor options. They support VMware but if they supported Hyper-V or Nutanix, it would be beneficial."

What is our primary use case?

Our primary use cases are for disaster recovery, data center movement, long-term recovery, and backup recovery.

How has it helped my organization?

Zerto took our disaster recovery practice from sixteen hours down to thirty minutes. 

What is most valuable?

The most valuable feature is the fully automated failover. The orchestration made the failover very easy for anyone who wasn't necessarily technically knowledgeable to be able to failover a machine.

I love Zerto's near-synchronous replication. I've been using Zerto for three years at my current employer and many years before that. It's been great. Anywhere I've used it, it's made the failover process a lot easier so that pretty much anybody can do it. This feature is our number one priority because we can keep our critical apps running if we have a failure, or even if we have a misconfiguration, it's very easy to recover something quickly.

We've moved some of our workloads to the cloud and back from the cloud using Zerto. The native tools provided by the cloud provider were not as seamless. Having DR in the cloud is very important to us because we trust that the cloud provider will provide a solution, but we also want to make sure that for our business purposes, we have a backup to disaster recoveries so that we're able to recover somewhere else if necessary.

We use Zerto to support DR on the AWS platform. We go between two different clouds. We go from VMware to Azure and also AWS.

Zerto made this quite seamless, especially going between two different clouds. It's just a matter of a couple of clicks. You don't need to understand what's happening on the back end.

We use Zerto to help protect VMs in our environment. It took our RPO from around four hours and now it could be seconds. We can recover the machine in under a minute as far as the boot time. We're between five and ten seconds RPO.

The magnitude of Zerto is much faster. We used to do a disaster recovery failover of our critical systems. It took about sixteen hours and once we had implemented Zerto, it took around thirty minutes to do for the same exact systems.

What needs improvement?

I would like for them to support additional hypervisor options. They support VMware but if they supported Hyper-V or Nutanix, it would be beneficial.

For how long have I used the solution?

We have been using Zerto for three years. 

What do I think about the stability of the solution?

It's been great. We've had it for three years. The only time we reboot the machines is for normal patches. We don't have to do anything else. It just works. We don't have to think about it. We've never had any issues over the three years we've been running.

What do I think about the scalability of the solution?

We started Zerto with a small footprint. We only did a few VMs as a POC with two nodes on each side. Then we've grown it to 34 nodes on each side, including the cloud. It's always the same amount of resources. We're running 150 protected VMs in there. It runs really well. 

How are customer service and support?

The few times we've had to use customer service, it's never been for anything that was really broken. It's more informational or because we didn't understand how the product works. They've been great with communication, they get back to us, and even if they don't get an answer right away in one day, they'll let us know with the ticket updates that they're still working on it. 

It's been really good as far as the little interaction we've had. The one nice thing is that we've never had to use it for anything that's been broken or that it's not working.

They have great communication. They don't just send you links to KB articles. 

How would you rate customer service and support?

Positive

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

We looked at other solutions before we purchased Zerto. We did a bake-off with a couple of other solutions. Zerto blew everything else away. The functionality is the same as everybody else, but the amount of time it takes to implement Zerto is a lot quicker. 

Making changes if you want to add another machine or another workload takes virtually seconds, whereas we found other systems took a planning time and could take hours to get implemented correctly.

How was the initial setup?

The setup was great. We had one of our newest engineers run through it because as part of the POC, the salesperson showed us how to install it. It was very straightforward. We took somebody who knew nothing about Zerto, had them install it and they had it installed and running in about fifteen minutes. It is quite easy to use. 

I can't say it's the same for SRM. There's a lot of documentation, whereas, with Zerto you point to the button, you push, and it works. 

What about the implementation team?

We did the full installation ourselves.

What was our ROI?

We got the recovery time from sixteen hours to thirty minutes. Prior, when it took sixteen hours, there would be about ten or more people who were waiting for systems to come online to be able to test. 

With Zerto, within an hour, we get the systems up, and then it's thirty minutes to test. Everybody can go home. There's a lot less time for people to be available. Zerto makes it much easier and quicker to get completed.

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

The licensing model per VM is great. It's a good way to license it because you want to protect only the devices that you're looking to protect. As far as getting the licensing and working with the sales team, they're very responsive. There's a lot of great communication, it's good all around.

Which other solutions did I evaluate?

We looked at VMware SRM. We also looked at a manual process. We chose Zerto for the simplicity and the cost ratio was phenomenal. It's easy enough that we've had nontechnical people able to failover just by clicking a button. 

For Zerto, you add the VM in the VPG or workload, point it to the target, pick where you want it to land, hit go, and it's done. With SRM, in comparison, you'd have to make sure it's being replicated between the two SANs. You have to go to a different UI, configure all of it, make sure that's working, then go into SRM and configure all the orchestration parts. It takes a lot more planning. You really have to make sure that all the different systems work together, whereas Zerto takes care of all that for you.

What other advice do I have?

I would rate Zerto a nine out of ten, there is some room for improvement. The drawback for me is that it's not compatible with every single hypervisor. If we wanted to go with another vendor for a hypervisor locally, then we'd have to look for a different solution, and there's nothing really out there that is comparable to what Zerto can do.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer2506566 - PeerSpot reviewer
Senior Server Engineer at a healthcare company with 5,001-10,000 employees
Real User
Provides continuous data protection with live test failover and has an easy setup
Pros and Cons
  • "With Zerto CDP, we can pull to our recovery objective in six seconds."
  • "The live test failover is the most valuable feature because it allows me to validate that my data is protected in the event of a failure."
  • "It's pretty expensive per server."

What is our primary use case?

We use it for continuous data protection on our mission-critical clinical systems. I work for a hospital. We use it to prevent ransomware, malware, or basic recovery for things like our patient data and imaging system. At one point, we used to do recovery once a day. With Zerto, our recovery objective right now is in six seconds.

How has it helped my organization?

We had a database failure one night at around 11 o'clock, and it had probably been about 23 hours since it had a hard backup. With Zerto, we brought it up in my DR site within ten minutes, and it controlled all of the hospital's registration features. Without that system, we can't even ingest patients into our system. So we brought up that database within ten minutes, got it back in line, and continued operations.

What is most valuable?

The live test failover is the most valuable feature because it allows me to validate that my data is protected in the event of a failure.

The near-synchronous replication Zerto provides is awesome. This feature is very important, especially because in today's age of ransomware and everything is so data-centric in a hospital, I need to be able to identify the point in time of infection and recover to the most up-to-date available point in time that I can without having to lose patient data. At one point, we used to do a 24-hour recovery. but in today's day and age, you can't lose a day's worth of data.

We use Zerto to protect our VMs in our environment. It improved our RPOs because before we had 24-hour RPO, and now I'm within ten minutes. 

Zerto's speed of recovery is fast compared to other solutions. We use Zerto and Veeam. Zerto already has the disks, which must be signed into and presented. There's a lot of rescanning involved, but Azure builds the VM, attaches the disks, and powers it up. We're leveraging RTO in under ten minutes.

What needs improvement?

The price could be improved. It's pretty expensive per server, but in the long run, it's well worth the level of protection it provides.

For how long have I used the solution?

I have been using Zerto since 2023.

What do I think about the stability of the solution?

Stability is very good.

What do I think about the scalability of the solution?

Scalability is excellent.

How are customer service and support?

Support is very good.

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

We used Veeam, which didn't offer any CDP. We use Zerto primarily for continuous protection.

How was the initial setup?

The initial setup was easy. We had a professional services engagement when we bought our first pack of licenses. They came in and worked with us. We had monthly and weekly meetings for three months to set up everything.

What other advice do I have?

We do not use disaster recovery in the cloud. We have an actual on-prem DR site. We have a multisite Zerto environment that I can bring up in multiple locations, but we do primarily on-prem recovery.

Overall, I rate the solution a nine out of ten for its ease of use, functionality, and multi-tenant support with ransomware detection.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Andrew Watts - PeerSpot reviewer
CEO at Ivrnet Inc.
Real User
Top 20
Enabled us to save tremendous amounts of time, is user-friendly, and provides peace of mind
Pros and Cons
  • "Using Zerto for the migration was incredibly valuable, enabling us to save tremendous amounts of time."
  • "Not all of the knowledge required for implementing Zerto is available in their online documentation for non-partners."

What is our primary use case?

We utilized Zerto to facilitate the migration of servers within a data center from one location to another and employed it for disaster recovery purposes.

How has it helped my organization?

Zerto is user-friendly. The feedback I received from my team during the migration was that it was effortless to use. I wasn't directly involved in the implementation, but I participated in the decision-making process for purchasing and analyzing Zerto. However, the feedback I received from our team indicated that it was quite straightforward to use.

The benefit to our company was the ease of moving our servers using Zerto, which saved us a lot of time. I would like to emphasize that during the data center migration, it saved us a significant amount of time. Additionally, during the disaster recovery tests, when we actually used it, it worked exceptionally well. Zerto provides us with peace of mind. In the event of an incident, the ability to recover our data effectively also grants us peace of mind.

We utilized Zerto to transition from one cloud to another, ensuring that all of our operations and applications are now in the cloud. Having disaster recovery in the cloud is an important necessity for business continuity.

We use Zerto to help protect our virtual machines.

Zerto has helped reduce our disaster recovery testing.

With Zerto, we would not require additional staff or hire a third party to assist with disaster recovery.

What is most valuable?

Using Zerto for the migration was incredibly valuable, enabling us to save tremendous amounts of time. Thankfully, we have never had to utilize the disaster recovery feature. However, if the need arose, Zerto would be instrumental in preserving our business.

What needs improvement?

Not all of the knowledge required for implementing Zerto is available in their online documentation for non-partners.

For how long have I used the solution?

I have been using Zerto for two years.

What do I think about the scalability of the solution?

Scalability is really good. We deployed it fairly quickly across our environment.

How are customer service and support?

The technical support is responsive and helpful.

How would you rate customer service and support?

Positive

How was the initial setup?

The feedback I received from our team was that the majority of the deployment went smoothly, but there were some technical aspects that were not covered in the deployment documentation, which they had to figure out.

The deployment required two people at times, but the majority of it was completed by one person.

What about the implementation team?

The implementation was completed in-house.

What was our ROI?

Zerto has saved time during our data center migration, and we are utilizing it for our disaster recovery. However, we have not yet calculated the return on investment for it.

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

Zerto previously had a perplexing licensing structure, but they have since resolved it by implementing a unified license.

Which other solutions did I evaluate?

We evaluated Veeam Backup and Replication before choosing Zerto. Zerto offers live recording, allowing us to rewind to the exact moment when the incident occurred. At the time of our selection, Zerto was the only company with this capability.

What other advice do I have?

I rate Zerto a nine out of ten.

For organizations planning to implement Zerto in-house, I recommend reviewing all the setup documentation beforehand.

Which deployment model are you using for this solution?

Private 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.
PeerSpot user
System Administrator at a government with 501-1,000 employees
Real User
We can recover instantly in the event of an emergency, and migrating to a new data center involves minimal downtime
Pros and Cons
  • "The most valuable feature is the ability to recover critical systems, such as public safety, within a few minutes. In addition, the RPO is six seconds of data loss, tops."
  • "I had a couple of questions after deployment, but nothing major, about a couple of ways I could tweak it."

What is our primary use case?

Our primary use case is disaster recovery, as well as data center migration when we went to a new VMware infrastructure platform.

How has it helped my organization?

The first benefit was being able to sleep better at night knowing that we can recover instantly. Because we do public safety, we have some databases that are terabytes in size, and were we to have to recover them using standard backup software, it would take a significant amount of time. With Zerto we can recover instantly in the event of an emergency. 

And when we went to a new data center, we had the ability to do a cross-center migration of the systems, and we found Zerto was much faster. We could migrate 25 to 30 servers and have them up and going in less than five minutes in the new environment, with very minimal downtime.

It has also reduced the number of staff involved in data recovery situations. We find that we really only need one person to manage it. That person was able to write up documentation so that any of the other system administrators can jump in and handle it, because of the ease of use.

What is most valuable?

For me, the most valuable feature is the ability to recover critical systems, such as public safety, within a few minutes. In addition, the RPO is six seconds of data loss, tops.

Also, the ability to adjust the journal is important. If there were a ransomware event and we were not able to recognize that ransomware event for, say, four hours, we could go back, literally per minute, to the previous 24 to 48 hours to have instant recoverability. That, to me, is the big value of the product: to have our systems up with very minimal downtime.

For how long have I used the solution?

We've been using Zerto for three to four years.

What do I think about the stability of the solution?

The stability has been excellent unless there is an issue with something on our end. For example, if a virtual replication appliance exists on a specific host and we take the host offline, Zerto will flash alerts at us, which I love. Zerto is always telling us when there's an issue with recovery. But the application itself has never gone down.

We haven't even noticed any over-utilization across our circuits, with the ability to throttle how much it's using. And once the initial sync is done, it's just kilobytes to keep it in sync. We don't see any downtime from using it. We haven't had a disaster situation recovery yet, but when we do, we're confident because our tests with it are successful.

What do I think about the scalability of the solution?

Scaling has been easy in that we had multiple data centers that we needed to combine into one. It was very easy to create "spokes," where we installed different Zerto appliances in the other data centers and then linked them to the master to migrate them over. From a VPG perspective, we've had to scale out and it's never been a problem.

We have about 250 virtual servers. We had about 100 and we recently purchased another 150 licenses so that we could protect the entire environment. We're in the process of applying those licenses to all of them. We haven't applied all of them yet because we like to categorize which Virtual Protection Groups we want them to be in, so that they spin up at certain times. We like to think that out a little.

How are customer service and support?

Their support has been very good. I haven't had to open very many tickets, but the few times I have, I have gotten a response within an hour or two. The support is good. They handle everything all the way through to completion and then they say, "We'll keep this ticket open in case you have any more issues."

How would you rate customer service and support?

Positive

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

We used VMware's SRM, which was a great solution; there was nothing wrong with it. But with Zerto, it's like riding a bike. Once I learned it and knew how to do it, I could let it run and do its thing. Maybe a month later I would have to jump in and do something, and the user interface is so easy. I don't have to relearn or remember how it works.

Zerto is quite a bit better when it comes to ease of use, compared to SRM. It's very user-friendly. With SRM, I definitely had to do some learning and read some things. With the VPG, it was almost self-explanatory, such as how to set up VPGs, how to recover things, how to do a failover, and how to do a test. Even as a proof of concept for management, I was able to take a VPG, delete a bunch of files on it, and then recover them from a few minutes prior. It was so user-friendly that even my management was able to watch me do it and understand what was going on.

SRM was just kind of there, in place, and it worked. Zerto is the one that I've really dug into and got my hands dirty with. Once we started utilizing it and realized how quickly we could recover. We realized that it could be used for migrating to a new data center. When we called Zerto we found out that that is a use case people use it for. From a speed perspective, the servers were down for less than five minutes when we migrated them. It was really fast with very little downtime.

How was the initial setup?

The whole process was extremely straightforward. I did a little bit of learning in the Zerto University on how to do a quick deployment. There are not a lot of steps to the quick deployment. After just a few steps we were up and going, almost instantly.

After the installation, it prompts you to log in, and as soon as you log in, it starts telling you what to do. It says, "You need to deploy your virtual replication appliances." And then it says, "Great. Now that you've done that, you're ready to create VPGs." It was almost like the application was literally telling me what to do next.

What about the implementation team?

We deployed it ourselves. I had a couple of questions after deployment, but nothing major, about a couple of ways I could tweak it. But the initial deployment didn't need any technical support. It was that easy to deploy.

Which other solutions did I evaluate?

We looked at a few other solutions. Zerto was the one that really stuck out, especially once we were given a proof of concept.

What other advice do I have?

Definitely try it out. I was able to leap right into it and use it immediately and do a test case within a matter of minutes. I was able to show management the ease of use and the ability to recover, and of course, that makes management happy.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer1874172 - PeerSpot reviewer
Systems Engineer at a pharma/biotech company with 501-1,000 employees
Real User
Being able to bring a system up in a matter of minutes is the next best thing to having a high-availability cluster
Pros and Cons
  • "It's one of the easiest products out there, as far as managing and using it go. The UI is pretty dead simple."
  • "The only thing we've noticed that needs improvement is the backend cleanup within VMware. There are some little issues there. I would like to see tighter integration with Vmware... orphan data is an issue within VMware. It doesn't clean up properly when you're moving stuff around."

What is our primary use case?

We've got two data centers, and for any of our applications that are not in some kind of a load-balanced or high-availability cluster, we use Zerto to replicate them, to make them as highly available as possible, without building that into the solution. We replicate between 100 and 150 different VMs from our North Carolina data center to our Chicago data center.

How has it helped my organization?

A small example of the way it's made things simpler is that we were building out a new product, and the original recommendation from the vendor when we were deploying that product was to have the application server closest to the end-users and the database server at our main data center in North Carolina. Once it was implemented, we found out that wasn't the case. We used Zerto to fail over the database to the same data center that the application server was in. We were able to do that really quickly and easily, without having to do a whole lot of extra work, such as having to rebuild the database server. That's one example of how we use Zerto, not just in a standard failover scenario. It made the process a lot easier than it would have been had we not had Zerto.

We have also used it when something happened to a configuration or a database file and it had become corrupted. It happened in the evening, after-hours. Rather than getting the backup engineer involved and trying to restore the files from a backup, we used Zerto to grab the file from a couple of hours previous, restored it, and got things back up and running really quickly. It's definitely a time-saver. We were able to handle it ourselves without needing to get anybody else involved.

What is most valuable?

One of the most valuable things about the solution is the ease of use when it comes to failing things over. The ability to easily test your failover capabilities is really nice. We can actually stand up a VM in an isolated environment, validate that the VM is up and running and that it boots properly, and we can do that in a matter of 30 seconds. Being able to show that to upper management, and that it's working the way it should, provides a lot of value.

It's one of the easiest products out there, as far as managing and using it go. The UI is pretty dead simple.

If everything is set up and configured properly, a failover of one or two systems can be done by one person. Nobody has to be involved other than the application owner, to validate everything, once the failover is done. It's a one-man show.

Continuous data protection is what it's supposed to do. Being able to bring a system up within a matter of minutes is the next best thing to having an actual high-availability cluster. If you're not building high availability into a solution itself, Zerto is the next best option. If we're talking about one or two applications or one VPG (Virtual Protected Group) a failover takes under five minutes, from the point of clicking "Start Failover" to the point of validating everything on the application end.

What needs improvement?

The only thing we've noticed that needs improvement is the backend cleanup within VMware. There are some little issues there. I would like to see tighter integration with VMware. From a recoverability standpoint, it's great when using VMware. But what we have noticed is that orphan data is an issue within VMware. It doesn't clean up properly when you're moving stuff around.

For how long have I used the solution?

Our company has been using Zerto for several years. I took over management of it within the last six months, but I've dealt with Zerto in the past as well.

What do I think about the stability of the solution?

We've had no stability issues. We've had to open one or two cases on small issues, but they've been pretty trivial. There haven't been any critical issues with its stability.

What do I think about the scalability of the solution?

It scales really well. Out of 500 VMs, we're using it for about 150 of them. That's probably not a lot compared to other Zerto customers. But as you add more ESX hosts to your environment, you just add new VRAs to the ESX host. There's not too much to have to worry about when you're scaling up.

We utilize it for everything that we don't build in a high-availability cluster. A lot of our stuff is designed as an HA cluster, but anything that is not designed that way is automatically protected by Zerto.

How are customer service and support?

The technical support is as good as, if not better than, most of the technical support that we deal with. Opening tickets is easy. The support portal is easy to use. Depending on the severity—I've never had to open a Sev 1 case—Sev 2 and Sev 3 cases are answered within 24 hours.

How would you rate customer service and support?

Positive

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

We didn't have a previous solution.

How was the initial setup?

I did not do the initial setup of the solution, but the upgrade from version 8.5 to 9.5 was very simple.

Our engineering team members, three systems engineers, are the main users of Zerto. We don't have segregated roles. I'm the point person for Zerto, and the other guys are backups for managing it and doing recoveries. Maintenance only requires one person.

What was our ROI?

We have seen ROI from a time-management standpoint.

Which other solutions did I evaluate?

I don't know if Zerto reduces the number of people that we need to have involved in a recovery scenario, but it definitely simplifies the process compared to using Commvault, which is our backup solution. If it's something that we need recovered from within a day or two, it's much simpler to recover that file with Zerto than it is from a backup solution like Commvault.

Anybody on our engineering team can probably recover a file using Zerto. I'm not so sure that's the case for Commvault. Our backup admin would probably have to get involved if we're doing a recovery from Commvault. Using Zerto, the UI is so much simpler.

There may be a small possibility that we will look at Zerto to replace Commvault whenever we do replace Commvault. That's a possibility, but it hasn't been brought up yet. We do know we are getting rid of Commvault at some point.

I've used other solutions, like Dell Avamar and Veeam. Veeam is definitely pretty easy to use and on par with Zerto. It's 100 times easier to use than Avamar. Ease of use is one of Zerto's strongest points.

What other advice do I have?

Go for it. It's the best-of-breed for high-availability replication solutions. It really is dead simple to use and easy to implement and maintain. It's not one of those solutions that you have to spend hours a day managing. You look at it for five minutes a day and forget about it.

The biggest lesson I've learned from using Zerto is that high availability, having a good replication solution in place, doesn't have to be a big, complicated, scary mess. It can be simple. It doesn't have to be some huge hurdle that you have to overcome.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
reviewer1640514 - PeerSpot reviewer
Senior Manager, Technical Services at a logistics company with 5,001-10,000 employees
Real User
Simple to set up and use, and offers continuous data protection with a five-second interval
Pros and Cons
  • "This product is impressively easy to use. It's dummy-proof, once it's set up."
  • "The long-term recovery is a little bit weak in its granularity."

What is our primary use case?

We use Zerto for real-time replication of our systems, company-wide. The main reason is disaster recovery failover.

How has it helped my organization?

We use the long-term retention functionality, although it is not deployed system-wide. We have a lot of critical systems backed up, such as our file servers. We utilize it to hold things for up to a year and we send our long-term retention to ExaGrid appliances.

When we need to failback or move workloads, this solution has decreased the time it takes and the number of people involved. The entire process is, realistically, a one-person job. We usually have an application specialist involved just to validate the health of the server. Whether it's an SQL server or application server, we have somebody that runs integrity checks on it. That said, the entire process is very painless and easily handled by one person.

I estimate that this product saves us hours in comparison to products like Veeam. Veeam would take several hours of time to fail something over. 

Our company fell victim to a ransomware attack that affected between 50 and 60 servers. Until we knew for sure that the entire situation was remediated and that we weren't going to spread the infection, we restored the servers in an offline manner, which only took a matter of minutes to complete. Then, we pushed all of that data into Teams and OneDrive directly for people to start accessing it.

From the SQL server perspective, we failed those servers over, running health checks such as anti-virus scans, just to make sure that the failed over instance didn't contain the same situations. Thankfully, they did not. We probably saved ourselves several days worth of work in the grand scheme of things. In total, it potentially would have taken weeks to resolve using a different solution.

I wouldn't necessarily say that using Zerto has meant that we can reduce the number of staff in a recovery operation. However, I think it's probably mitigated the need to hire more people. Essentially, as we've continued to grow, we've avoided adding headcount to our team. Using Veeam as my problem child to compare against, if we were using it, it would have required a lot more management from us. It would have cost us more time to recover and manage those jobs, including the management of the ExaGrid appliances, as well as the VRAs, which are basically proxies.

Definitely, there is a huge saving in time using Zerto and although we didn't reduce any headcount or repurpose anything, we've definitely mitigated at least two people from the hiring perspective.

Zerto saved us considerable downtime when we experienced the ransomware attack. It may be hard to substantiate that just on the one situation but we saved at least a couple of million dollars.

What is most valuable?

The most valuable feature is the continuous recovery with the five-second checkpoint interval. Just having those checkpoints prior to when a situation arises, we're able to get the transactional data that occurred right before the server failed. That has been a blessing for us, as we are able to provide a snapshot with no more than five seconds of data loss. This means that we don't have to recreate minutes or hours worth of data for an industry that includes fulfillment, shipping, warehousing, et cetera.

Zerto is very good at providing continuous data protection. It does a very good job keeping up with the system and it creates five-second interval checkpoints. This has been helpful when it comes to needing to fail something over, getting that last moment in time that was in a usable state.

This product is impressively easy to use. It's dummy-proof, once it's set up.

What needs improvement?

The long-term recovery is a little bit weak in its granularity. Veeam is definitely superior in that aspect, as it's able to provide a granular view of files and databases, et cetera. However, it just kind of depends on what a business' recovery strategy is.

From our business perspective, it's really not impactful to us because our recovery strategy is not based on individual files. But, I could definitely see it being a challenge if there is a very large instance of individual files, as a subset, that need to be recovered. I think that if somebody has terabytes of data then Zerto will recover it faster but navigating through the file explorer to get to files is not as easy with Zerto.

One thing I don't like about the product, and I know this is where their claim to fame is, but whenever I have a VPG that has multiple virtual machines in it, and one virtual machine falls behind, it'll pause replication on everything else in that job until the one server catches up. The goal is to keep symmetric replication processing going, so the strategy makes sense, but for our business model, that doesn't really work and it has created a challenge where I have to manage each VM individually. It means that instead of having one job that would cover multiple servers, I just have one job to one server, which allows me to manage them individually.

For how long have I used the solution?

We have been using Zerto for approximately five years.

What do I think about the stability of the solution?

From a company perspective, a few years ago, I would have said that it is very stable. It is a solution that is thriving and growing. At this time, however, HP is in the process of acquiring them. While I had assumed that was their long-term plan, I didn't quite anticipate HP being the one to pick them up. As such, I am a little bit worried about what will change in the long term.

What do I think about the scalability of the solution?

Scalability-wise, it's a very painless product. As we continue to grow out our virtual environment, Zerto is able to, in a very nimble fashion, scale with us with very little effort or overhead involved.

I'm covering approximately 400 VMs currently, which is approximately 360 terabytes worth of data. That is between two separate data centers.

How are customer service and technical support?

Rating the Zerto technical support is a little bit tough because I've had some experiences that were truly 10 of 10, but then I've had one or two experiences where it was definitely a two or a three out of 10. It really depends on who I've gotten on the phone and their level of, A, comfort with their own system, and B, comfort helping the customer.

Some people have said this isn't within their scope of work, where others have said, "No, let's absolutely do this." In that regard, it's been a little hit and miss, but it's usually been a decent quality in the end.

Overall, I would rate the technical support a seven out of ten.

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

I have worked with Veeam in the past and although I prefer Zerto, there are some advantages to using Veeam. For example, long-term recovery offers more features.

In-house, we had also used the Unitrends product, as well as a SAN-to-SAN replication using an old HPE LeftHand array.

The main reasons that we switched to Zerto were the management ability, as well as its ability to provide continuous replication. Veeam was a very cumbersome product to manage. There were a lot of instances to monitor and manage from a proxy perspective, whereas Zerto's VRAs are relatively transparent in their configuration and deployment. These are painless and I don't have to continually monitor them. I don't have to update them since they're not like standalone Windows instances. It's very low management for us.

Of course, continuous replication is critical because Veeam, even though when we had owned the product, it claimed 15-minute intervals were doable, it never seemed to actually keep up with those 15-minute snapshot intervals.

One final reason that we migrated from Veeam is that they were utilizing VM snapshots at the time. I know that they've moved away from that approach now, but it was very painful for our environment at the time. The VMware snapshots were causing some of our legacy and proprietary applications to fail.

How was the initial setup?

The initial setup is very simple.

Our implementation strategy involved setting it up for our two data centers. We have a primary and secondary data center, and Zerto keeps track of all of the VMs at the primary site and replicates them to the other site.

In the future, we plan on looking into the on-premises to cloud replication. On-premises to Azure direct is on our roadmap.

What about the implementation team?

I completed the setup myself without support or anybody else involved in the deployment.

It took approximately an hour to deploy.

I handle all of the administration and maintenance. As the senior manager of infrastructure, I oversee our work and server group. I have also retained private ownership over the disaster recovery plan and failover plan.

What was our ROI?

We have probably not seen a return on investment from using Zerto. We don't really have lots of situations where we have to use it and can substantiate any kind of financial claim to it.

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

I do not like the current pricing model because the product has been divided into different components and they are charging for them individually. I understand why they did it, but don't like the model. 

Our situation is somewhat peculiar because when we bought into it, we owned everything. Later on down the road, they split the licensing model, so you had to pay extra for the LTR and extra for the multi-site replication. However, since we were using LTR prior to that license model change, they have allowed us to retain the LTR functionality at our existing licensing level, but not have the multi-site replication.

Which other solutions did I evaluate?

We have not evaluated other options in quite a long time. We very briefly evaluated Rubrik. 

What other advice do I have?

When we first decided to implement Zerto, it wasn't very important that it provides both backup and DR in one platform. In fact, realistically, even now, while we have it and we used it on a limited scope, I'm not sure that it's needed.

With respect to our legacy solutions, I'd say that the cost of replacing them with Zerto is net neutral in the end.

My advice to anybody who is considering Zerto is that it's an awesome product and it won't steer them wrong. That said, there are some issues such as the licensing model and the situations where VPGs falling behind suspends the replication. Overall, it is a good product.

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.
PeerSpot user
Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2025
Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros sharing their opinions.