Try our new research platform with insights from 80,000+ expert users
reviewer1909311 - PeerSpot reviewer
Sr Systems Engineer at a insurance company with 1,001-5,000 employees
Real User
Top 20
With Zerto we can pick and choose what we want to fail over and at what time
Pros and Cons
  • "We have seen ROI. It reduced the time for failover and failback by 90%."
  • "You can create a VPG and put anywhere from one to 17 servers in that group. We build them one by one. If something changes in VMware, it would be nice to be able to go in and change that VPG, having it update without messing up. When you change them now, it only applies to the copies from the points when you changed it. I wish it would purge that older data from the past. Right now, we have to build a new VPG, which is not a big deal as it is just a few screens."

What is our primary use case?

We are failing over approximately 250 systems. In many ways, this could impact 3,800 insurance agents across 11 states. 

There are two sites: the source site and the production site. Those are failing over to another data center about 150 miles north of my location.

How has it helped my organization?

When we went from the original DR plan that we had with Double-Take to SRM, we were able to fail over in an hour and a half. We did all the storage groups in bundles, and we are like, "Wow, this is unbelievable. This is awesome." Then, we went to Zerto, and it was like, "Oh wow, we can pick and choose how we want to do this." So, Zerto provided us with a lot of value. 

We went from testing in a week, e.g., we would say, "Alright, we are going to set aside Monday through Thursday to test all the apps which have been deemed 'need to be tested', and make sure for DR purposes that they are working correctly." We went from that to a day. We can do it whenever we want much easier than before. Instead of having to do it in a group, you could have it where there is scratch space and all the things that are needed, where all the changes and deltas are being cached. Now, we can do a small group of people anytime that we want, or whenever. 

We haven't done it all in a day. Our plan is to have it fail over where we can get it done quickly enough in that morning, e.g., if we have all the testing, testers, and developers lined up, then they can test and we can have it done all in one day.

It has reduced staff stress. We are not big on cutting staff because we run pretty thin. We have even seen growth in the amount of staff involved in backup and DR management. There will be two leads going forward, sharing the primary duties.

What is most valuable?

The most valuable feature is the failover testing and being able to do that in a granular fashion. We can pick and choose what we want to fail over and at what time, then how quickly it fails over. We fail them over into a bubble, which means our developers and other testers can go in and do whatever they want. They are not impacting production outside of the bubble.

The reporting function is a big thing that we like. Our upper management and execs are always like, "Hey, we need to report about what you did." So, we can print out a report that is 200 or 300 pages long, and go, "Here you go." It was a little overwhelming the first time they got it. They were like, "What?" I am like, "You asked for a report. This is the report."

For the last three years, I was a secondary admin. We got into a situation where they were like, "Hey, you're the lead. You need to immediately be the lead." I was like, "Okay, alright." So, I was able to go in and create the protection groups and replication servers. We run VMware so we were able to push that out to the hosts, uninstall and decommission stuff. I was able to get that squared away within a day or two. It is very easy to use. If I can do it, anybody can do it.

The Zerto’s near-synchronous replication is very important. We used to say, "Hey, if we don't have this and if the building blew up from a gas leak, then what would we do?" Now, it is not just disaster recovery, but there are departments of insurance requirements for federal requirements going, "Hey, do you have a disaster plan in place that will successfully run? Can you provide me with those reports?" It also checks that box since we have requirements that need to meet for customer data. They need to be able to retrieve that data, either at the running site or production site. Or, in the case of a disaster, we will need to provide them with that information. So, it checks multiple boxes.

What needs improvement?

You can create a VPG and put anywhere from one to 17 servers in that group. We build them one by one. If something changes in VMware, it would be nice to be able to go in and change that VPG, having it update without messing up. When you change them now, it only applies to the copies from the points when you changed it. I wish it would purge that older data from the past. Right now, we have to build a new VPG, which is not a big deal as it is just a few screens. 

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,388 professionals have used our research since 2012.

For how long have I used the solution?

We have been in the Zerto world for four years, and I am the lead on Zerto now.

What do I think about the stability of the solution?

Stability-wise, I would probably give it 10 out of 10. It is very stable. If there is something not running correctly, then it is an outside factor. It is either the admin or a connection to the other site. With the dashboard, it will show you that you have this many protection groups built. Everything is an individual green square, but when there is a problem, then you will see red. It is very simple. If it has a problem, you will see something. I have not dealt with a problem where Zerto is just not working. It is usually user error or sort of outage. It is reliable.

As far as Zerto replication and DR purposes, it has not caused us any outages.

I have answered stuff for Zerto before, and they are like, "Why do you like it?" We say, "Because it works." For so long, we had stuff that didn't work for so long, and this solution works.

What do I think about the scalability of the solution?

As long as you have the license to protect the VMs, then you can scale it as big as you want. 

We are currently protecting 325 VMs. We have plans to expand in the future.

How are customer service and support?

My dealings with the technical support have been top-notch. They are very good. I would rate them as 10 out of 10.

How would you rate customer service and support?

Positive

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

We had Double-Take and were replicating to a site with SunGard, then we swapped. It was kind of a nightmare for us to get it working the way that we wanted. I am sure it is a great product, but the way that we needed it to work was just not working. Then, we went to VMware SRM, which worked great and went off without a hitch.

We then wanted something with a quicker recovery point objective (RPO), and that is when Zerto came in. They allowed us to failover in a granular fashion. We could pick and choose how we wanted to fail over in DR tests. That is a big part of our DR testing. Enterprises want to be able to know that they have a successful test and can run in a failed over environment, so the test is 50% of that. The other half is, “If we had to declare a disaster, where would we be?” The RPO is two to three seconds with Zerto. I have talked to people with Unitrends and several other companies who say that you can’t get an RPO that low, but that is what we have. Today, it is very fast today.

When we need to do our DR test on a specific day, Zerto has allowed us to be able to do that in granular fashion. With SRM, you had to fail a group of servers over. While that may have changed, at the time you could only do them by storage volumes. With Zerto, it didn't really matter. It has been like, “Which ones do you want to fail over? Do you want to do just your SQL servers?” This has allowed us to have a more granular approach to testing and DR testing. It ensures that we can do it in a certain way and confirms that our actual DR plan is a good plan.

We didn't have anything that worked for so long. I think Zerto kind of showed up and was in the great spot where they couldn't be any worse than what we had.

How was the initial setup?

I was not involved in the initial setup. This has been kind of thrown in my lap, and it has not been a nightmare at all.

What about the implementation team?

The prior admin hired services for updates. Going forward, I will probably do them myself.

What was our ROI?

We have seen ROI. It reduced the time for failover and failback by 90%. I am not saying that the products I mentioned earlier are bad products. They just didn't work well for what we wanted.

Zerto has had a significant impact on our RPO. It is a double-edged sword where our RTO and RPO have allowed us to almost not miss a beat. In a DR test, we are more staging and moving systems over, and this is more of a tactical approach. With some of the moves that we are making with SQL and using blue-green environments, I don't think we see a problem at all. We feel very good about it. 

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

We bought it through a reseller.

We are very fortunate because our budget is pretty big, and I am not making that up. Staffing may be a little thin at times, but as far as budgeting what we buy, the price for this solution has not been so outrageous that we don't buy it.

I think there is a support cost.

Which other solutions did I evaluate?

I was a big proponent of using SRM because I manage the VMware environment. Being a VMware product, I was more in their corner. So, it was mainly between SRM and Zerto. We also might have looked at Rubrik.

With other vendors that we used, we would sometimes start on the weekend, e.g., on a Saturday morning at 6:00 AM, then we would go through at least Thursday of the next week. It would be a long, arduous process. Sometimes, we would go only two days because we could never get past a single spot, then the entire test would be a failure. With Zerto, it has reduced our DR testing time drastically. It went down to where we think we can do a test in a single day. We were able to pull it off last year in two days with failover and failback tests as well as reports.

Zerto provides ease of use when building out jobs, then having them failover as you want, one by one or selecting five or six VPGs at a time. One of the big things that we do is with SQL. We want our databases online before doing any testing. There also needs to be domain controllers turned on for people to be able to log in. It is like, "Alright, we are going to fail over the domain controller." Next, they go, "Alright, we are going to fail over our SQL stuff." Before, when we had those SRM groupings, it would be a bit harder. You had to wait for everything to finish. Now, it is granular, where you can pick and hit one by one what you want. The database administrators can go in, and say, "Alright, we are online. There are three more that just came online." They are able to test it, and it just works. Having something that works was a big thing for us.

It has not replaced any of our legacy backup solutions. We use Veeam for any backups or system restores at this point. So, Zerto's role is just for DR.

We have luckily not had to use Zerto in a data recovery situation for ransomware. We have had one instance where we were in a spot like that, which was about two years ago, and we were able to restore it back with Veeam.

Until the last few cases, VMware support is some of the sorriest support that I have had.

What other advice do I have?

I would recommend Zerto because it works. You will need to do a PoC first though.

Immutable data copies are something that we are looking into. For example, if I have a recovery point of two, nine, or 10 seconds, then we get hit with some sort of ransomware attack or something like that. We would like to have immutable data that is unchanged. So, we are looking into this feature now.

I am sure it has enabled us to do DR in the cloud, but we are not a big fan of putting that stuff in the cloud. We are not a fan of putting it on somebody else's computer if we can put it on our computer. We have been very happy having a DR site approximately 150 to 200 miles north of our main site. We are kind of running it in our own hybrid cloud at the moment.

As far as testing, there are probably 70 people who test.

I would give it a nine out of 10. It has done what we wanted. We have been very satisfied with it. We are Zerto fans.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Director of IT at Arnott Inc
Real User
Gives us business continuity capabilities during hurricane season and in case of ransomware
Pros and Cons
  • "If we had to deal with a ransomware event, Zerto would be one of the first things I would use, because it is going to be the fastest to restore data to a certain point. If there were a fire in our building, Zerto would be a big thing too, because we would shut down everything that's in our building. In most cases, Zerto is definitely one of the front lines. It's definitely going to be one of our prevalent DRBC layers of protection."
  • "If I were to nitpick, I would say that I wish I had a better account manager. Our sales guy has changed a couple of times. I would like a little more responsiveness from our account manager. I've had a couple of issues where getting in touch with him has been a little difficult, and I end up just going around him and dealing with support and support has handled it right away."

What is our primary use case?

We have two primary use cases. One would be to use it in reaction to a cyber-terror event, particularly ransomware, because Zerto has point-in-time backup. If we find an area that needs to be restored, as long as we figure it out within 24 hours, which is approximately the amount of time we have replicated, we can go back to a point in time. Let's say the files got encrypted at 9:30 AM. We can say restore our 9:29 AM copy of what the data looked like at that point. We have not needed to use that, thankfully, because we've been educating our users very well.

The other case that we would use it for is because we're in a hurricane area. Our particular office is actually in an evacuation area, typically, meaning that we're close enough to the coast that should a hurricane event come through, they generally force us out of the area. What we would do if we needed it, and thankfully we haven't yet, would be to shut down our primary on-prem services to make them a little bit more resistant to water damage. Obviously, if they're not running, they're a little bit less likely to get zapped if there is some water damage. Then we can bring up the copies that we have at our data center and run remotely from that if. It doesn't have a full copy of our entire environment, but it does have a copy of our ERP system, as far as sales are concerned. We wouldn't be able to ship anything, but we could look at orders and help our customers. We could even take orders if we needed to, although we wouldn't be able to process them.

Zerto is a replication solution. It copies our setup which is on-prem to our data center, which is also somewhat local, about 15 miles away. It doesn't really do anything in the cloud other than move data across it. We're not replicating to any cloud-based services like Amazon or Azure. Essentially, we're using it at two on-premises locations: Our primary location, which is what is being replicated, and the replicated copy is being stored at another on-premises location, nearby.

How has it helped my organization?

Zerto is purely a business continuity and disaster recovery tool. We don't want to have either one of our primary use case events happen, but if they should happen, it gives us an extra layer of protection. I've got Amazon backups with stuff in completely different regions, but Zerto is more for those two specific scenarios I mentioned. In addition, if somebody deletes a file and it's really important that they have the latest copy of it, Zerto gives us that option. But it really comes down to the ransomware reactions and the hurricane support, because hurricanes are fairly common in this area. The last hurricane event here was before I had Zerto and we had to shut everything down. We really couldn't do much while the hurricane came through. The business wanted something that would give us some protection in that scenario. That's the business continuity aspect. At least we can provide some business capabilities this way. With Zerto, they'll also be able to access a limited functionality version of our system. It definitely provides upper management with a little bit of comfort that we won't be completely down in either a ransomware or a hurricane event.

We're a smaller company. We're owned by a portfolio company, and they're the ones who made a lot of these extra layers of protection happen. Zerto provides me with the comfort of one of those layers. It enables me to make a strong case to my board of directors that, "Yeah, we're good." There's a guy in our board of directors who's something of a tech guy. I can look him in the eye and say, "Hey, we're not bulletproof. We can never be bulletproof, but we're about as close to bulletproof as we can be, especially for a company our size." That's important to the board because they have other companies that aren't as well-protected as we are. I've had conversations with a couple of the guys at those other companies, because they're interested in looking at something like Zerto, and I have been highly recommending it to them. It's a reasonable cost, it provides several layers of protection from ransomware, and if necessary, against natural disasters. I'm very happy to say that Zerto is one of those layers and provides us with very good protection for what it specifically does.

We had two ransomware events prior to being owned by the company that owns us now. Both were events where somebody clicked on a link that they shouldn't have and something ran and encrypted some of our stuff. Now we're much more solidly protected from that, and Zerto is definitely one of the big things protecting us.

If we had to deal with a ransomware event, Zerto would be one of the first things I would use, because it is going to be the fastest to restore data to a certain point. If there were a fire in our building, Zerto would be a big thing too, because we would shut down everything that's in our building. In most cases, Zerto is definitely one of the front lines. It's definitely going to be one of our prevalent DRBC layers of protection.

When you need to fail back or move workloads, Zerto significantly decreases the time it takes. As long as it's one of those scenarios in which we foresee using it, it's great. When we did our two failover tests, it was easy to failover to the other location where we have the replicated copies. The last time we had an actual ransomware event, which was before we had Zerto, it took me 30 hours to restore all the data that I needed to restore. I would imagine Zerto would take 10 to 20 percent of that time.

In terms of saving staff time, I only have three people on my staff, so I'm not going to save human resources by using Zerto. That being said, what it does save me is the trouble of having to use another solution that would take a lot of time. I only engage my guys who work on Zerto for six to 10 hours a year, versus having somebody on staff. That's a significant savings for us, because we don't need somebody on staff who knows how to do things with it. It is pretty easy to use for somebody who's familiar with it and uses it on a regular basis. For example, when I do the upgrade, I'll pay guys to do it because that's what they do.

We have secondary, older equipment where our Zerto backup copy resides. We moved that old hardware to our secondary location and got new stuff in our primary location. Our primary location now copies, via Zerto, to the other location that has our old equipment. It's not quite cloud, but it is in a different location. And it's definitely saving us money in the long-term by not having to pay for cloud storage because we have put it on our older stuff, and it works fine for that scenario.

We did a test turning it back on and rethinking it, and that took a reasonable amount of time. A lot of that is not actually limited by Zerto. It's more limited by your pipeline between your backup location and your primary location. Zerto was very helpful, and it's very easy to use from that standpoint. Once you reconnect the two sites, it does a snapshot check of where it left off and then it copies back over the changes that happened while it was running on your secondary site. That's not automatic. You have to touch it. But it's certainly not super-technical.

What is most valuable?

Our two primary use cases are Zerto's biggest features for us. That's what we use it for. There may be other situations where it can come in handy, but those are our two primary scenarios.

In terms of providing continuous data protection, Zerto has been great so far. Thankfully, we haven't had an event where we have really needed to rely on it, but we have done a couple of tests prior to hurricane season where we disconnect our primary facility. We then go over to our secondary facility where the replicated data is and we bring everything up and then we do remote access to that location to make sure that it's all working properly. It's very capable. I've also done a couple of test scenarios on ransomware reaction where I'll go in and restore a folder, after hours when nobody is in the system, to emulate a situation where we might need to go back and restore kit encrypted files. So far, it's been great.

Regarding the ease of use, there's a web portal that I use to verify that everything is working well. It has a lot of notifications and it emails me if there's anything going on that's out of the ordinary. For example, if the connection to one of my other sites goes down, it will let me know that it's not able to reach that site. I'm very happy with the way the interface works for my needs, and my tech has been pretty happy with it. Our installation is rather small. We only have 14 servers on it. I'm sure there are other companies that have hundreds, but I imagine that they would see the same capabilities. The web portal is pretty well organized and easy to navigate.

For how long have I used the solution?

I have been using Zerto for just about three years. We just re-upped the maintenance on it and, until that point, we had a three-year plan for it.

We're on version 7.5, but I've had some discussions with my partner where we have the replication stored. We're doing an upgrade, but we ran out of time before hurricane season so we decided to hold off until after that. We're going to move up to 8.5 as soon as hurricane season is over, but I didn't want to risk getting into a situation where we didn't have Zerto working at all. And version 7.5 has been working fine. There was no real need to do the upgrade, other than to stay current.

We're about a version behind. I generally stay at least a half-a-version behind to let everybody else do all the sorting out of anything that they might find with the new versions, and then I jump on the second-oldest version, once that's a little more mature.

What do I think about the stability of the solution?

The stability of Zerto itself has been fine. We have some network instability that affects it, but I see the alerts come through and it's not Zerto that is having trouble. Zerto itself is very stable.

What do I think about the scalability of the solution?

Scalability is not really applicable to our situation, but I would imagine that it would be easy to scale if needed. We would just buy additional licenses and strategize a little bit about how we were going to add them.

We only have 15 server licenses, but I expect we'll have some growth as we have a couple of projects upcoming. We're probably going to need another server, so even though we're retiring a few servers, I'll leave the licenses. I won't probably be in any position to make it bigger any time soon, but you never know. Our company always has its eye out for acquisitions. Last year we picked up two companies, although they didn't really result in any major increase in our infrastructure. Maybe we'll pick up somebody similar in size to us and all of a sudden we'll need to protect 10 more servers. I don't have any plans for downsizing Zerto.

How are customer service and technical support?

If I were to nitpick, I would say that I wish I had a better account manager. Our sales guy has changed a couple of times. I would like a little more responsiveness from our account manager. I've had a couple of issues where getting in touch with him has been a little difficult, and I end up just going around him and dealing with support and support has handled it right away.

I've only had to deal with their tech support a few times, and I would give them a nine out of 10. They've been pretty responsive. They've answered my questions. They've gotten things taken care of.

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

Before Zerto, I just restored backups. We have Veeam as our primary backup system. Veeam is a traditional backup system. In those ransomware events I mentioned, I literally had to go through and restore a bunch of stuff from different servers from our backup repository, which is onsite. I had to go back and restore this folder and that folder and this folder and that folder. I would sort of have to do that with Zerto, but it would be a lot easier. I could just pick the folder and pick the time, and say, "Go." With Veeam it was definitely a much more complicated process.

We didn't "switch" to Zerto, we added it. We still have our other solution. While there is disaster recovery where you're recovering from a disaster, business continuity is how fast you recover from disaster; how quickly you get the business going again. Zerto reduces our RPOs. It was more a case of added protection and it reduces our recovery times—even though thankfully we've never had to use it—compared to the last time we had to recover.

Zerto came highly recommended from our primary VAR, which is Presidio, the place we bought it from. They said it would do exactly what we needed it to do, and the price was reasonable. I took the recommendation, did some research on them. It's possible I looked at reviews on IT Central Station and someone there said, "Oh yeah, Zerto is great." That's good enough for me. I didn't need to spend a ton of time on it. As long as they've got good reviews from multiple sources, which I did find when I researched Zerto, and it came highly recommended from our VAR, those were two pros and I didn't need to go looking for a con.

What about the implementation team?

I didn't actually set up the software. I had to pay somebody else to do that because it was a little beyond my team's capabilities. Our deployment took about six hours from start to finish. The guy that I worked with said that he was pretty happy with it. He had to send in a couple of help tickets, and they were very responsive and were able to help him get through the issues that he had.

He's from an IT support firm called Creative Network Innovations, and they also have an onsite data center, so they offer data center support services in addition to regular IT support services. In this case, Zerto is data-center related. We use Creative Network Innovations because it's related to what they do for us, and they have people on staff who are comfortable working with it. Even though they don't necessarily do Zerto all the time, they were able to step in, take a look at it, and sort it out for us, so that was good.

I wouldn't necessarily say that they're experts in the software, because they learned it for us. They're not typical Zerto implementers, but that speaks to how easy Zerto is to use. They had never really used it, but they were able to pick it up, plug it in, and get it working for us.

In terms of deployment time, the Zerto piece didn't take long. It was about six hours. What we had to do in terms of setting up networking, that was a little different. The whole project, including Zerto, took about 12 to 16 hours. And when we did our first failover test, that probably took another six hours, because we had to figure out all the nuances of how to make it handle the various servers that we have.

It depends on the size of your installation. Because we're fairly small, it didn't require a lot of involvement. Most of it is Windows-based, so it's not that hard to install and set up. Things like getting access through the VPN, which weren't necessarily Zerto-specific, are what took a little time, but the Zerto piece was pretty fast.

It's a backup piece for us. We didn't really get that fancy. We basically identified the servers we needed to replicate offsite. Then we installed Zerto on our primary location and we installed Zerto on our secondary location. And we created the communication.

In terms of users, I'm the only one in our organization who monitors Zerto, and I do very little of that.

What was our ROI?

I would estimate that if I had to recover from a scenario like the last one that affected us, it would take me 10 to 20 percent of the time it took me at that time. That reduces the amount of time that our system is down and, therefore, the amount of money we're losing because our system is down. It does provide some cost-benefit, but it's hard to quantify, because nobody has said, "In our company, we lose $X an hour when we're down." But when things are down, people are not happy. If nothing else, it means I hear less griping, and that makes me happier.

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

They have an enterprise-type of licensing scenario, which we didn't qualify for because we don't have enough. Ours is pretty straightforward. It is site-based, but the payment concepts are based on the number of servers. In our case, we have a quantity of 15. When we bought it, there was an initial purchase amount plus maintenance. When it came up for renewal, we did three more years, and it was under $10,000 for my 15 servers.

It's very reasonably priced. It's a little more than $3,000 annually. That works out to about $20 per server per month.

Which other solutions did I evaluate?

Our backup recovery software, Veeam, is working on a product that will compete with Zerto. But it's still very new. It has not been out for very long, so I don't anticipate us going away from Zerto any time soon. That being said, when our renewal comes up with Zerto, I might reevaluate and look at Veeam and see if their solution is going to cover what Zerto does, because then I have one vendor to deal with, not that I dislike dealing with Zerto. It's just sometimes it's nicer to put all of your stuff into one package because the interfaces are uniform.

At this point in time, Zerto is safe with us. We've got them for three more years, and it does exactly what we need it to. Is it going to be our daily backup and our long-term retention? At this point in time, no. I'm pretty happy with what Veeam does and how it integrates with VMware, not that Zerto does a poor job. Zerto covers a different area.

It's kind of like if you were wearing armor, as a knight of old, but you were missing a piece on your back. If somebody stabbed you in the back, if you had armor there, you wouldn't worry about it. Zerto covers our "back." It covers stuff that Veeam doesn't. It handles point-in-time backups and it gives us a faster recovery in certain scenarios. It's not going to necessarily protect us from a full on-premises failure, because I don't have it doing that. I bought it specifically to defend us from certain types of attacks. We have Zerto handling 14 servers but we have a total of 20 servers. It's not backing up the other six, Veeam is, but that's because I don't need those to be protected from ransomware. I need them to be protected from system failure or catastrophic disaster where our primary location is under 20 feet of water from a hurricane, or the whole thing burns down. Zerto is not going to protect us from that, although it possibly could. We just don't use it for that.

It provides us some niche protection and we're happy with the niche that it protects.

What other advice do I have?

Because we're a smaller company, I would never need a full-time person to do disaster recovery, whereas a company with several thousand employees and multiple billions of dollars of revenue would probably have a team for that. I would imagine those guys would save people if they had Zerto, but that's just me imagining that, rather than it being fact.

If I had 1,000 servers, it might require more of my time, but we have 14. We have a board of directors that wants things to be bulletproof, and they're willing to pay for it. Do we need Zerto? Probably not. Is it nice to have? For sure. But we certainly don't use it in the typical use environment, which I'm sure is a lot more servers than we have. That being said, we still use it, and I highly recommend it, even for companies of our size, although it's probably not the sweet spot for a lot of companies like ours. It's kind of pricey for smaller companies, but for what it does, I think the value is exceptional.

For companies of our size, if you don't have somebody on staff who can use Zerto, you want to find the right help. Your VMware person should be able to help you with it. Make sure that you're comfortable with what you're trying to accomplish. I thought it was a pretty smooth implementation, as you can tell from the time that it took. That might be in part due to the people we enlisted to help us. I can't say that everybody's installation will go that smoothly, but I would imagine that if you have a pretty solid VMware-type person, you should be pretty good with the Zerto piece. It's really a matter of working on the VMware side of it. There is also a little bit of networking, depending on where you're backing up to.

If you're backing up to the cloud, you obviously need somebody who is cloud-savvy who can get the proper connections to your AWS and secure them.

Overall, make sure you have somebody who is VMware-savvy. You don't necessarily need somebody who is specifically Zerto-savvy. The guys that I worked with said that it was pretty easy to work with, even though they hadn't worked with it before. But again, ours was a smaller installation. A Fortune 500 company is going to need a little bit more capability. They're going to want to look for a Zerto-certified implementer, which I presume there are. We didn't bother with that because we're smaller and we didn't really have anything particularly difficult in our implementation.

In terms of preventing downtime, in our situation Zerto hasn't helped reduce that, but it's not because Zerto is not capable of doing so. It's just that we haven't had a situation like that in which it has needed to be used. We haven't had any incidents that required the use of the Zerto fallback.

The biggest lesson I've learned from using Zerto is that I wish I had known about it six years ago. I wish that I had known about its capabilities. Given that it's on version 8.5, it's been around for a while. I really wish we would have had it when we actually had a need for it.

If we ever need it, we're confident in it, given the test scenarios we've gone through where it's been great. It's a nice "warm blanket," and it's good to "cuddle" underneath it, because I don't have to worry about it. If I have an event, I'm pretty confident that I can get us back up and running quickly. Is it going to be instantaneous? Of course not. But it's going to take significantly less time than it would take if I had to react via a manual backup.

Zerto is "the bomb." I'm definitely happy we got it. Overall, it's reasonably priced. It's one of the less expensive business continuity and disaster recovery layers that we have. That being said, it doesn't do everything. We're a smaller shop. There are only three people on my IT team, including me. It's definitely been a very helpful tool and comforting to know that we have it in place. It makes it easier to sleep at night. For what we need it for, it does everything we need.

Zerto is a nine out of 10 and maybe even close to a 10. It's solid. It's a good product. It does what we need it to do. Since we haven't actually had a live event, I can't say that it's perfect, but in the tests we have run it through it has been great. The only blemish has been dealing with the account manager, which could be situational. I've only had to deal with him a few times. The last time he didn't even respond to me. That being said, it's been three years, and maybe he's moved on and nobody is monitoring his email box. And when I reached out to support, they took care of me right away. So the account management is a minor blemish. Everything else, as far as the product and support go, has been fantabulous.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Buyer's Guide
Zerto
March 2025
Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
842,388 professionals have used our research since 2012.
Enterprise data management supervisor at a insurance company with 1,001-5,000 employees
Real User
Instead of one mass disaster recovery exercise, we're easily able to perform up to 12 in the year
Pros and Cons
  • "In situations of failback or moving workloads, it saves us hours. If I were to have to move a four or five terabyte machine using something like VMware's virtual copy it has to install on the machine and copy the data over. Then it has to shut the machine down and do a final copy, which means there's a lot of downtime while it's doing the final copy."
  • "The interface is the only thing that we've ever really had an issue with. It's gone through some revisions. The UI, it's not clunky, but it's not as streamlined as it could be. Some of the workflow things are not as nice as they could be."

What is our primary use case?

We use it for disaster recovery and to migrate machines from one location to another.

How has it helped my organization?

The big thing for us was our disaster recovery. At that point, we were only able to do a disaster recovery test once a year. Now, we officially do a disaster recovery test once a quarter and we do a subsequent test once a month to verify that it's doing what it's doing and the IP address is changed. Instead of one mass disaster recovery exercise, we're easily able to perform up to 12 in the year.

It allows us to verify in a much more granular aspect whether our data is being migrated or not. Once a year, if we find some issues, we're at least 11, 12 months behind at that point. Every 30 days, if we do a test and we find an issue, we're able to correct that. The time between tests is shorter, which means that if there is a problem we're able to resolve it in a much shorter amount of time versus an entire year, and then waiting another year to see if everything is working again.

When we need to failback or move workloads Zerto decreases the time it takes and the number of people involved. We are able to put a machine into Zerto, let it do its magic in migrating the data from one side to the other. We've had instances where we've got machines that are four or five terabytes that we can move from one side to another after it's done synchronizing in 15 minutes or less. Sometimes it takes DNS longer to update than it does for us to move the machine.

Instead of me having a server person, a network person, and a storage person, I can put it into Zerto, let Zerto do its job, fail it over, and then just have the application owner verify that the server is up and running, and away we go. So on a weekend, I don't have to engage a team of people, it can just be myself and one other person to verify that the machine is up and running. It really cuts down on overhead for personnel.

In situations of failback or moving workloads, it saves us hours. If I were to have to move a four or five terabyte machine using something like VMware's virtual copy it has to install on the machine and copy the data over. Then it has to shut the machine down and do a final copy, which means there's a lot of downtime while it's doing the final copy. As far as downtime from an application standpoint, with Zerto, we're from hours down to minutes, which is great when you have applications that are supposed to be the five nines of a time kind of thing.

We have not had any ransomware issues. But we have had an instance where somebody installed something that messed something up. It was a new version of Java and we were able to roll back. Thankfully they realized it fairly quickly because we only keep a 12-hour window. We were able to roll back to almost a per minute instance prior to that installation and recover the server in minutes. Our backup was as of midnight, but they did it at 8:00 in the morning. So we didn't lose eight hours' worth of processing.

If we were going to use our backup solution, it would have taken minutes to restore the actual server, but then from an SQL perspective, we would have had to roll the transaction logs from backups. I couldn't even tell how long that would have taken because we had to do all of the transaction logs, which are taken every five minutes from midnight, all the way to 8:00 AM in five-minute increments. It would have taken considerably longer using traditional methods versus Zerto.

Although it hasn't reduced the number of staff involved in overall backup and disaster recovery, what it has allowed us to do is actually focus on other things. Since Zerto is doing what it's doing, we're able to not have to stare at it all day every day and make sure that it's working. We have the screen up to make sure there are no errors, but we're able to focus on learning how the APIs work, working on the other products that we own for backup and storage. That's mainly what my group does, we do disaster recovery and storage backups. We have six pieces of our enterprise and before it was just the main piece that we were working on. Now, we're able to actually work with the other five or six entities and start doing their backups and disaster recovery because we have a lot more time.

What is most valuable?

The failover capabilities are definitely the high spot for us. Previously, when we did disaster recovery it would take us easily a day or two to restore all of our servers. We can do the same thing with Zerto in about an hour and a half.

We're about six or seven seconds behind our production site and it does a really good job of keeping up, making sure that we're up to date. That's one of the other things that we think is just phenomenal about the product, we're able to get in there and put a server in and within usually a few minutes we're protected. Six or seven seconds behind is a pretty good RPO.

Currently, we are using another product for longterm retention, so I don't think we really have any plans on switching over at this point.

Zerto is very easy to use. We did a proof of concept and it took longer to build the Windows servers that had to be installed than it did to actually install it and roll off the product. Our proof of concept became production in minutes.

What needs improvement?

The interface is the only thing that we've ever really had an issue with. It's gone through some revisions. The UI, it's not clunky, but it's not as streamlined as it could be. Some of the workflow things are not as nice as they could be.

I like the fact that Zerto does what it does and it does it very well. I have had Zerto since version four, so the longterm retention and things like that were never a part of it at that point. I just like the fact that I can install it, I can protect my virtual machines, and I'm comfortable and confident that it's doing things correctly because of the amount of testing that we've done with it.

For how long have I used the solution?

We have been using Zerto for a little over three years. 

What do I think about the stability of the solution?

It's very stable. Once a month we verify that the internal mechanisms of Zerto are working. When I do a test failover we check if VMware tools come up, if the IP addresses change, and the things that Zerto is configured to do automatically. Usually, if there's an issue, it's either I did something wrong when I configured it, or I put in the wrong IP address or the VM itself has an issue, the tools aren't loading correctly or at all, or it was trying to do an upgrade and failed. We've actually been able to identify other issues inside the environment that we would not have realized were an issue by doing these tests.

What do I think about the scalability of the solution?

Our next step is not so much increasing the capacity but protecting things to the cloud. We'd like to be able to take those same 350 machines or so do we have, and definitely, if not the important 50 that we have, but all of them, have them not only go to our disaster recovery site but also split to AWS. It's where we have both of the sites, one in one location and one in a vastly different location and if for some reason, one were to go offline, we would have those objects in AWS to be able to spin up and do what we need to do.

We ramped up from that 50 to 350 within a year and Zerto just took it and kept on running. We are still about the same RPO as we were before, we're protecting 60 plus terabytes of data at this point with those 350. It did what it had to do to create new virtual machines, depending on how many disks there are. I think that I was able to scale with our needs really easily. 73 terabytes are what we're protecting right now across 357 VMs, and we have a seven-second RPO. It went from a small number to a very large number. The issues that we've had around Zerto protection has either been that networking wasn't sufficient, or the storage itself had to be increased.

There are three of us who work with Zerto, that's it. We do contact other teams, often our networking team to get an IP address for something. But when it comes to doing the testing, when it comes to doing the implementation, and when it comes to doing verification processes, it's all my team of three people.

I am the data management supervisor and then I have a lead storage administrator and a senior storage administrator.

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

Prior to Zerto becoming our disaster recovery product, we were using Dell EMC's Avamar for backup recovery and for disaster recovery, which we quickly realized was not going to work out very well. We used it for about four or five years. When your disaster recovery test is five days and you take one and a half to two days to do restores only, that doesn't leave a lot of time for testing. Now, we're able to do the restore in an hour and a half. Then we actually can start testing the exact same day that we did the restores. In most instances, we're able to actually finish everything within 24 hours.

When we first purchased it, the backup portion did not exist. So having backup and DR in one platform really wasn't that important to us. We use Rubrik for backups and longterm retention at this point. We really don't have any intent on using Zerto for longterm retention, as we're extremely happy with Rubrik. But time will tell if we decide to switch over to the LTR portion of the product.

Compared to Avamar, Zerto is extremely easy to use. I can bring Zerto up and start recovering, failing over, or testing machines before I can even log into Avamar. Avamar was very clunky from its interface. It's very easy for Zerto to go in and recover a machine to a certain point in time. Where moving around in Avamar, since it was Java based, would take quite a long time to get from screen to screen. And the workflow was not user friendly at all.

We have different use cases for Zerto and Rubrik but I think that the interface and functionality, as far as what I get out of that particular product, what its purpose is, they're both about on par. Honestly, we've told both companies before, we would love for one to buy the other so that we can get the best of the disaster recovery with Zerto and the best of backup and recovery, longterm retention type things with Rubrik. Because they definitely are probably the two best products for their market segment.

Replacing Avamar has saved us on the cost needed to manage them. As far as management goes, we still use the same three people. But as far as renewal maintenance costs, definitely. Dell EMC is very proud of their products and their renewal maintenance costs were rather large compared to what we do with Zerto.

Initially, we saved about $1,000,000 three years ago by switching to Zerto. Zerto and Rubrik replaced Avamar. But buying both products together, versus what the renewal/upgrade costs would have cost us for Avamar, with all the hardware, was a savings of $1,000,000.

How was the initial setup?

The initial setup is very straightforward. I built a couple of virtual machines to run the manager on, deployed some VRAs, and then attached it to VMware and checked what I wanted to protect. We probably had it up and running in about an hour total. Then we tested protecting some machines, and we had some test boxes that we tested back and forth. It was a very easy setup. People are definitely sold about how easy it is to install and configure.

Initially, our deployment strategy was to protect a small subset of very important machines for an enterprise. And then once we saw how easy it was to implement, how easy it was to put things in there, and how easy it was to protect them, it went from a handful of machines to 350 or so. The initial intent was to protect a very small number. That went from that to a very large number very quickly. Zerto was able to handle it no problem. We actually had to end up buying more storage on the target side because we had not planned on doing that many machines from the initial implementation.

What about the implementation team?

We worked with our account team. We were able to get the proof of concept software, a link to download it. They gave us a key, they gave us a little Excel sheet stating how many machines and IP addresses we needed. Then they basically sat on the phone with us for the hour with WebEx. And we set it up just that moment. That's really the only implementation help that we've ever gotten from them. Everything else has just been pretty much us on our own.

Their support has been very, very good. We've had some technical issues that we've been able to work through with them. Nothing major, but if I have a question or if we run into an issue, we're able to either open up a support ticket and they respond fairly quickly, or we are able to do some searching in their knowledge base. We've had an instance where we did the upgrade to a new version and it caused some problems. But within, I'd say a few hours, we were able to correct it because they had already experienced that. And they had that logged in their internal database of issues. So, they were able to log in, and give us the fix that we needed and get us back on track.

What was our ROI?

It definitely is a very robust product. The feature set from 4.0, 4.5 to now has increased greatly. We do like the fact, even though we're not using it, that as long as I pay my maintenance when the new features come out like longterm retention, analytics, the monitoring, the reporting, the things that were not there when we first purchased it that are there now, is all part of maintenance. It's not a bolt-on price. They don't charge extra. It was one of the things with Dell EMC that was always a pain was. They had additional costs. With Zerto it's like, "You paid your maintenance, here's a new feature, enjoy!"

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

They have licensing breaks as far as 50 users, or 50 VMs, 100 VMs, 250 VMs. We ended up with a bunch of 50 at first, and all of our maintenance renewal dates were all different. It ended up costing us more because we didn't just make the investment up front to say that we wanted 250. We had to end up going back and resetting all of our maintenance dates to the same date. It was just a nightmare for our maintenance renewal person. If you did a proof of concept and you like it, definitely make the license investment upfront. That way, you're not trying to piecemeal it afterwards.

Licensing is all-inclusive, there are no hidden fees.

Which other solutions did I evaluate?

We looked at RecoverPoint for VMs. A long time ago, one of the companies inside this enterprise had used RecoverPoint and it worked really well when it was the physical RecoverPoint. But as things became more virtual, it no longer was as good as it had been, so they had discontinued it. RecoverPoint for VMs was definitely not as easy to set up. It was not as easy to use. It took a lot more resources. This is three-year-old information, but I feel like we would have had to have had more people on our team than we do now with just the three of us. We didn't feel like it was as stable. It certainly wasn't as easy to use, test, or get to work as Zerto was.

What other advice do I have?

My advice would be to do the proof of concept. They're very willing to help you with the installation. Do a proof of concept. If you're not amazed by it, I would be surprised. Everybody that we've ever talked to about this and have done a test of it says, "I can't believe it's just that easy."

I would rate Zerto 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.
PeerSpot user
Shri Sharan - PeerSpot reviewer
Solutions architect at Kyndryl
Real User
Top 20
Is user-friendly, saves us time, and costs
Pros and Cons
  • "Zerto's most valuable features include its user-friendly interface, multi-tenancy capabilities, and near-zero downtime recovery."
  • "We encountered some issues during Active Directory recovery."

What is our primary use case?

We utilize Zerto as part of our disaster recovery toolset. We employ a multi-tiered model, catering to a select group of customers, primarily hospital clusters. These customers maintain on-premise networks with cloud-based disaster recovery. In this managed service offering, we leverage Zerto to facilitate their cloud recovery.

How has it helped my organization?

The replication is quick. We encountered some challenges replicating the data during the first full copy. Since we weren't using Zerto, I suspect the bandwidth requirements for replication were a bottleneck for us. However, once the initial copy was complete, the process became seamless. The recovery was near zero after the first replication. Zerto worked perfectly.

We implemented Zerto because it supports a multi-tenant model, which was a critical requirement for us. We have five tenants located on-premises across five different data centers. However, we only have a single disaster recovery site in the cloud. Zerto's solution enabled us to consolidate our disaster recovery needs. Previously, managing five separate data protection solutions for each data center and five different cloud recovery subscriptions would have been incredibly expensive. Zerto significantly reduced our costs. Additionally, Zerto provides a single-pane-of-glass dashboard, allowing us to manage our infrastructure efficiently and effectively. This comprehensive view offers full control over our applications and complete visibility into all our tenants. As an infrastructure manager, I believe these features are the most valuable contributions Zerto has made to our organization.

Zerto has helped save around 30 percent of our time.

Zerto has helped achieve significant cost savings.

In the VMS portal, we had a relatively small amount of data overall. We also had multiple tenants, each with a maximum of 20 to 30 virtual machines on-premises. These VMs weren't particularly large. As a result, recovery was quick, typically taking less than a minute. My Recovery Time Objective would be less than a minute for any VM, even for a complete migration of all on-premises VMs to the cloud.

While I wasn't privy to the details of the client's previous DR solution before implementing Zerto, our discussions revealed significant time savings with Zerto's recovery process. Compared to their prior on-premises DR approach, Zerto offers a substantial reduction in recovery time – at least 15 to 20 minutes faster. This improvement stems from eliminating the need to coordinate with personnel and the time required for on-premises recovery procedures at their dedicated DR site. Previously, they relied on manual, on-premises to on-premises recovery, which inherently took longer. However, a direct comparison between their old solution and Zerto wouldn't be entirely accurate. Zerto offers significant efficiency gains, boasting up to 200 percent improvement.

Migrating data through Zerto is straightforward with careful planning. Our first experience involved Zerto's support throughout the process. While initially challenging due to our lack of experience, we were able to navigate the initial setup. One hurdle we faced was optimizing network traffic for the initial data replication from on-premises to the cloud. However, we embraced the learning curve, documenting everything as we gained control of the environment. This ensured a smooth integration for subsequent tenants. While the first migration presented some difficulties, as is to be expected, Zerto's excellent support made the process manageable. Their responsiveness in explaining and resolving issues made it a positive experience overall.

The RPO was very close to zero, meaning there was minimal data loss between replications. However, this could be impacted by the specific database being hosted and other factors. For application servers or virtual machines replicated on-premises to the cloud, I believe there was negligible lag or delay, assuming no network issues. Bandwidth and network traffic did play a role – we observed instances of slower RPO due to traffic spikes or network events. However, with Zerto providing the recommended data bandwidth, we encountered minimal challenges. In most cases, I'd say 90 percent of the data was synchronized almost constantly. The only exception was when network issues arose.

Our data center experienced an issue, necessitating a disaster recovery procedure. Fortunately, data loss seems minimal, and the impact on our clients appears negligible. This is partly due to the managed service we provide for a tenant, who fortunately didn't perceive any significant data loss. The success of the recovery is also attributed to our user-friendly, always-in-sync system. Upon receiving alerts and notifications, we promptly informed the client, who then quickly authorized the recovery process. From our perspective, the recovery went smoothly with minimal challenges. In the actual scenario, we believe data loss was negligible. While some data loss might have occurred technically, it wasn't significant enough to cause any noticeable impact on the client. It's important to note that our monitoring team maintained complete control of the situation, allowing for swift decision-making and a speedy recovery.

In a data recovery scenario, we'll still have our database administrator, Linux administrator, storage administrator, and Zerto operator available. While Zerto can automate disaster recovery and VM restoration, it's important to remember that it's not a foolproof solution. Even though Zerto streamlines the process, a well-prepared organization will always maintain backups and ensure a dedicated team is in place for data recovery. Zerto doesn't reduce the number of personnel involved; rather, it enhances their productivity by freeing them up for other tasks during a recovery event. During a recovery, it's still recommended to have everyone on call. While Zerto handles most recoveries, there may be situations where manual intervention is necessary. By being fully prepared, our organization can effectively address any data recovery situation.

It is easy to manage and monitor the DR plans using the Zerto GUI. 

What is most valuable?

Zerto's most valuable features include its user-friendly interface, multi-tenancy capabilities, and near-zero downtime recovery. Zerto is easy to learn and use, even for those with limited technical experience. Additionally, Zerto's failover testing functionality allows us to run tests in real time without impacting production systems.

What needs improvement?

We encountered some issues during Active Directory recovery. When we implemented Active Directory, we provided feedback to Zerto regarding the challenges of recovering AD from the on-premises environment to the disaster recovery site. Unlike other virtual machines, AD recovery presents unique difficulties due to its active-active nature. It's unclear whether these challenges stem from Zerto itself or limitations within Microsoft Active Directory. However, in our experience using Zerto for AD recovery compared to other technologies, we faced data discrepancies that necessitated workarounds to bring AD online at the DR site.

Certain applications we migrated from production relied on Active Directory authentication. To ensure successful application functionality at the DR site, a functional AD environment was a prerequisite to application migration. Therefore, our initial step involved copying and guaranteeing a running AD instance on the DR side before application recovery.

However, upon attempting application authentication on the DR side, data inconsistencies prevented successful authentication. To address this, we created an isolated clone of the AD environment and conducted tests. Through trial and error, we were able to develop workarounds to resolve the issue. Notably, these challenges were specific to Active Directory; other VMs didn't exhibit similar problems.

For how long have I used the solution?

I have been using Zerto for over 3 years.

What do I think about the stability of the solution?

Zerto has been very stable for us. We do apply patch releases and upgrades whenever necessary to ensure continued stability. Fortunately, we haven't encountered any major bugs or issues that would cause significant downtime, unlike what we've experienced with some other tools. Zerto has been a reliable choice for us.

I would rate the stability of Zerto 9 out of 10.

What do I think about the scalability of the solution?

I would rate the scalability of Zerto nine out of ten.

How are customer service and support?

The technical support is fantastic. They offer same-day assistance, and their documentation is clear and comprehensive.

How would you rate customer service and support?

Positive

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

Before implementing Zerto, the client's disaster recovery relied on an on-premises to on-premises failover strategy. Seeking a cloud-based solution, they chose Zerto to leverage its expertise in this area.

We previously used another tool for DR orchestration. While Zerto can also perform recoveries, it focuses on virtual machines and doesn't extend to the operating system or database level for starting and stopping applications within those VMs. Despite these limitations, Zerto excelled in its support. The Zerto team provided excellent assistance whenever we faced challenges, joined calls to help us troubleshoot, and offered clear timelines for resolving issues. Their documentation was also thorough. In contrast, the previous DR tool lacked comparable support and documentation. This stark difference in support quality is why we favored Zerto and ultimately removed the other tool from our project. Currently, we rely solely on Zerto for our existing tenants, and we plan to continue using it for future ones as well.

How was the initial setup?

We encountered some challenges during the initial setup. Zerto offers several data replication options, I believe 2 or 3. These include copying data to our hard drive or storage box, copying it to the DSR site, and replicating it over the network. However, only network replication worked for us.

The issue might have been related to bandwidth requirements. It's possible that either Zerto itself or our network infrastructure wasn't up to par. We faced some challenges during that initial phase.

However, after the initial setup and the application of delta copying, which happens daily, we rarely experienced any replication issues. Most of the time, network glitches and fluctuations caused brief disconnections, but overall, replication ran smoothly.

We went into the Zerto deployment with a clean slate. Both team members were new to Zerto, so we were all learning as we went. This initial deployment was challenging, but it gave us valuable hands-on experience. Once we had a firm grasp of the environment, onboarding subsequent tenants became seamless. We developed a clear plan and approach, which streamlined the process for future deployments. Technically, the challenges weren't ongoing. The main hurdle was understanding how to integrate Zerto with our existing infrastructure. While that initial learning curve was steep, Zerto's excellent support helped us navigate it successfully.

The deployment time for Zerto varies depending on the complexity of your environment. More complex environments will require a longer replication process. However, on average, we can onboard a new customer within 1 month. This timeframe encompasses the entire process, from the initial planning phase to the deployment of up to 30 VMs within a tenant.

Our project involved 2 separate IT teams at 2 different locations. One team acted as the managed service provider, while the other represented the client side. The client-side team, located on-premises, provided us with essential information about their data centers. This included details on virtual machines, such as their size, quantity, and basic data collection metrics. They also helped us identify their storage requirements. Based on this information, we planned our cloud storage procurement and other necessary actions. The project team comprised approximately 10 to 15 people, including project managers, IT personnel, storage specialists, network engineers, and development experts.

What other advice do I have?

I would rate Zerto 10 out of 10.

Our organization uses Zerto to manage the replication of data centers from 7 on-premises locations to the IBM cloud for our midsize clients.

Our environment consists of VMware, data storage, and a network, with Zerto deployed for disaster recovery. While VCDM and VMware are managed by our cloud provider, we maintain 5 additional technologies with a team of 8 people.

We experienced a brief on-premises outage. Fortunately, we were able to recover quickly using Zerto. The software triggered an alert, notifying our monitoring team. These features proved to be very helpful. Additionally, we were able to promptly contact our clients and explain the situation. They responded quickly and effectively, minimizing the impact on their end. Our clients were pleased with the response.

I recommend Zerto to others.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

IBM
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
IT Director at C1
Real User
Real-time information through the portal helps with security
Pros and Cons
  • "The portal is a valuable feature. I am here in Baton Rouge, and I can get into the Vegas data center and see real-time replication on the portal."
  • "We have kept renewing Zerto because it seems to get better."
  • "I always get some blowback about the cost. It does not seem too bad to me. We had to upgrade to a premium subscription to get some other features. Maybe a one-size-fits-all option would be better."
  • "I always get some blowback about the cost."

What is our primary use case?

We use it in our data center. We have two data centers, one in Baton Rouge and one in Las Vegas, and we use it for replication. It is all used in the data center.

How has it helped my organization?

We did not have replication previously. Once we got Zerto, we started seeing everything backed up and replicated, and we saw its benefits pretty early. Over the years, we have kept renewing Zerto because it seems to get better. There have not been any issues with it.

Near-synchronous replication works very well. We use pretty big storage with them and never had a problem. If it is close to going over, we always get an email, and it is easy to keep up with all that, which is pretty important here at Credit Union. I have nothing but positive to say about Zerto.

Zerto is easy to use. When we first started using it, we used the emails they sent at the end of the night to see everything was fine. About five years ago, they got their own portal. Since then, we have been able to see everything in real-time. It has been super easy. I automatically get notifications on my phone or email. That has been a real high point for me with them.

We have several VMs, and Zerto has been a part of the protection plan for them.

Knowing what is going on in real-time has helped with breaches and things like that. Recently, there have been no issues. Luckily, over the last year or two, we have not had any security issues. Zerto and VMware are what we count on in our data center. As long as the data center is up and running safely, we are good here at the branch.

We run reports on XDR and get an idea of anything that has been going on. Luckily, we have been safe for the last year or two, but in 2022, there was an issue. Zerto was right on it, and we were able to get it cleaned up. Zerto has definitely helped in the ransomware aspect.

What is most valuable?

The portal is a valuable feature. I am here in Baton Rouge, and I can get into the Vegas data center and see real-time replication on the portal. The portal has been upgraded over the past several years, and it is probably the most helpful part of it.

What needs improvement?

I always get some blowback about the cost. It does not seem too bad to me. We had to upgrade to a premium subscription to get some other features. Maybe a one-size-fits-all option would be better. 

For how long have I used the solution?

I have used Zerto for eight to ten years.

What do I think about the stability of the solution?

I have not experienced any stability issues. We are a heavy usage bank, and it has always been steady for us. I do not have anything bad to say about that.

What do I think about the scalability of the solution?

Scalability has been good too. We started with the one in Baton Rouge and added the one in Vegas about five years ago. It was very easy to connect them and get them mirroring each other. Scalability has been good for us.

How are customer service and support?

When my staff member went to Vegas, there were some issues with logging into the device. He called the tech line and was able to talk to someone. We have had luck getting in touch with those guys. Their customer service deserves a good score, at least an eight out of ten.

How would you rate customer service and support?

Positive

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

At the previous bank, it was a big Cisco shop, but I have been here for almost ten years, and we have had Zerto for that long. Zerto is what I am used to.

How was the initial setup?

I did not personally do the initial setup. A guy who works for me went to Vegas, called it in, and got it set up pretty well. I do not go to Vegas much, but I have been to Baton Rouge. I have tested it and played with it, and every time I have done that, it seems easy to use. My network administrator has never complained about any difficulty. For the most part, it is easy. They have a good tech support line, and if we have any trouble, they are easy to get in touch with. We are happy with that.

We have a maintenance contract with them, but I did not have to use it except for one instance a few years ago when we thought that we were going to get ransomware. We had maintenance on that. The good thing is that it is a part of the renewal. It is safe to have it, but luckily, we have not had to use it over the last few years.

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

Price-wise, it works fine for me, but my budgetary team is always looking for ways to cut costs, and it seems like they first look at the data center and the IT side to find savings.

What other advice do I have?

Take advantage of the maintenance plan; even if it is not required, it is definitely worth getting. The techs there are really good. There are local Zerto reps who come around. Use the tech support when needed because they are always very good. 

I would rate Zerto a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
PeerSpot user
Steve McFate - PeerSpot reviewer
Systems Analyst III at St. Luke's
Real User
Top 10
Helped us streamline our DR testing and notably reduce associated downtime
Pros and Cons
  • "The replication works really well. We perform multiple tests a month and annual tests for our tier-one and many of our tier-two apps... Migrating systems as a failover rollback or a system move are two of the functions that I like the most."
  • "When building out a VPG and doing the machine types within Azure, they were not coming across correctly. It would say it had a CPU and memory of a specific type, but it was not accurate... It was a bug and they were working on it."

What is our primary use case?

We use Zerto as our disaster recovery solution for our servers in the multiple data centers we have. It allows us to replicate our servers from one data center to another and perform disaster recovery testing to ensure compliance with our organization's DR requirements.

Our organization wanted a solution for replication, whether for VMs or Azure sites, and the ability to migrate servers or VPGs in case of a disaster or for testing purposes. And we wanted something reliable.

How has it helped my organization?

We're migrating out of one of our older data centers currently, and sending them to either Azure or one of our two VM data centers. We've been working on getting all the servers out of the old data center for a year. Being able to migrate those servers, with the help of the service teams, is one of the best features. Instead of having to do them one at a time, we can build a VPG. That is especially helpful with some of these really large VPGs. We did one a couple of months ago that was 36 terabytes. We were able to migrate that entire VPG at one time, watch it replicate once it was there, and then do the reverse replication. That process has been amazing.

We use Zerto to protect VMs and our RPOs are very solid. The RPO is a little slower for Azure, but that was expected and it was covered in the documentation that Zerto provided. But the RPOs from one VM center to another are solid. The same is true for our RTOs. We have no complaints in that regard at all.

And it will definitely help reduce downtime if we have to migrate from one data center to another due to a disaster (which we have not had to do so far). Downtime would cost us a lot, no doubt. We have not had any major disasters as of yet or problems with spyware or ransomware. But we have had instances where a server was corrupted in one data center and because it was backed up with Zerto, we were able to fail over to the secondary site and get the VPG back up very quickly. From the time that the decision was made that we needed to fail over, it took around 30 minutes. It was very quick, especially compared to trying to troubleshoot and rebuild. Our patients weren't affected.

The platform has also helped us to streamline our DR testing. We're able to do our annual test as quickly as possible, whether it's a failover rollback or a system move. It has made that process much much quicker and a lot less painful.

I've only been in this position for a year, but from what I've heard, DR testing was not a pleasant experience prior to moving to Zerto. They were always having failures and then would have to set up another downtime and test again. With a lot of our applications, those that are tier-ones, we're having to do the DR test at 1 AM or 2 AM. Nobody wants to have to do a four-hour downtime test multiple times.

And not having long downtimes for DR has helped a lot. Our customers and service teams know that we have to do these tests once a year to stay compliant. We plan for a four-hour downtime every time we do a DR test. Very rarely do we need four hours. We block out that time just in case there are issues we didn't expect but we're usually done in under two hours, including failing over, doing the testing, rolling back, and testing again. I don't know if you can actually put a number on not having downtime, in terms of the impact on the service teams, nurses, or patients.

Right now, our DR team is just me and my boss. At one point, there were three people on the team. It says a lot about Zerto when it can be used with a minimal staff for DR. Prior to moving to Zerto, the team had four members. So it was double what it is now.

What is most valuable?

The replication works really well. We perform multiple tests a month and annual tests for our tier-one and many of our tier-two apps. We need to make sure we can quickly and reliably migrate VPGs to the backup data center in a disaster scenario. Migrating systems as a failover rollback or a system move are two of the functions that I like the most.

It's also very simple to use. For example, when we need to move data so that our users can keep collaborating with one another, using Zerto is very simple. Putting the servers into maintenance mode and either moving or testing them for our teams, has worked very well. We have found very few hiccups with any part of the solution, especially with the new version that they released recently.

The near-synchronous replication-also works really well. When you move or have just built a VPG, watching it step through things is great. It's a well-made product. Near-synchronous replication is very important, making sure that it's done properly and that it's complete.

We have Azure data centers. When migrating out of our older data center, if we find that Azure is the best place for those new servers, we have been migrating them there and doing the DR test at the same time. I haven't found any problems with migration to the cloud. For our applications that will work in Azure, Zerto's disaster recovery in the cloud has worked really well.

What needs improvement?

I turned in a ticket a while back when I found a glitch within Zerto. When building out a VPG and doing the machine types within Azure, they were not coming across correctly. It would say it had a CPU and memory of a specific type, but it was not accurate. When I sent that ticket in, the support manager said that it hadn't been found before, but that my report was accurate and that it was a bug, and that they were working on it. 

But I've been very pleased with the updates that they put out and the service. I don't have a lot of negative things to say about Zerto.

For how long have I used the solution?

I've been in this position for a little over a year and have been using Zerto during that time.

What do I think about the stability of the solution?

I've never seen it go down. It has been stable and easy to use, which are some of the main reasons we're still with them. We haven't had any large bugs with it. The software seems to be well-tested before new updates go out.

What do I think about the scalability of the solution?

We have it deployed across three on-prem data centers in two different states, plus the two different Azure sites that are also out of state.

We've added a couple of new data centers since I've been in my position and adding them to our Zerto interface was not very difficult. The scalability is good.

How are customer service and support?

Whenever I have had any issues, I have contacted support and they have been knowledgeable. Getting a hold of Zerto's support has been easy. In general, compared to all the other applications that I've ever supported in my career, Zerto has been one of the easiest to contact and actually get help with. I've worked with some vendors that were really difficult to work with.

Overall, Zerto's technical support has been fantastic. When I've had issues, submitting a ticket online is fast. In all but maybe one instance, I had a callback within just a couple of hours. Their support has been awesome.

How would you rate customer service and support?

Positive

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

Our organization migrated away from a couple of other solutions prior to my starting this position. But the disaster recovery manager that I work for has said multiple times that Zerto is the easiest solution and has the most robust features compared to whatever they were using prior.

I know our organization still uses Veeam, but they do so in tandem with Zerto.

What was our ROI?

There is an annual cost for Zerto, but that is something that our director level works through. Our organization, St. Luke's, goes through all vendor contracts looking for the best value. The fact that we have been using Zerto for a few years says that the value must be there compared to other vendors.

Not having to take down our tier-one system for an extended period of time for DR testing is invaluable. You can't put a dollar value on the impact on a patient's life. We need our systems to stay up constantly because they are what keep people alive.

What other advice do I have?

In terms of maintenance of Zerto, we do our monthly reboots of the servers so that they stay up to date with the Microsoft patching. And anytime that Zerto has updates to their software, we make sure that we stay compliant with that. And once every year or 18 months, we update the cert on the servers.

My advice is to look for a product that is easy to use and easy to learn and allows for scalability and DR testing that works well.

Which deployment model are you using for this solution?

On-premises

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Paul Mickenbecker - PeerSpot reviewer
Senior Analyst, IS Infrastructure at a energy/utilities company with 1,001-5,000 employees
Real User
Top 10
We have centralized and simplified our DR processes, and DR in Azure has enabled us to consolidate DCs
Pros and Cons
  • "We can failover to an isolated environment and validate the application without impacting the production environment. We can do more testing in a non-impactful way..."
  • "We do have some sites that are very low-bandwidth sites. Zerto is able to set throttling in the solution, but the throttling is set at a site-wide level. In those instances that have very low bandwidth, I can't reduce the throttling on that site. It would be nice if there were a way to control the throttling by the protection group for a specific workload."

What is our primary use case?

In my previous company, I used it for disaster recovery. We protected our critical workloads in another data center where we would replicate our primary workloads.

In my current company, we're in the middle of a data center consolidation project and we're using Zerto in two ways. First, we're migrating the workloads we had in one data center to another, about 250 servers. It took us about three months to complete the migration. We had to schedule all of our moves and work with the business to validate that the services were fine and accessible, once they were moved to the other data center. We've completed the migration and a data center has been shut down, and we're working on building disaster recovery for our primary workloads in Azure.

How has it helped my organization?

The main benefit is that we are centralizing our disaster recovery solution. Before, we were doing replication for some services and RecoverPoint for other services. We had a mix of tools for disaster recovery and we're trying to simplify that process with a product we can use for both. We're even contemplating using Zerto for backups as well, because we use other tools for that. But the main focus is having a specific tool, Zerto, that we can use to achieve our disaster recovery goals for on-prem services.

We also have a big push to move our DR solutions into Azure as a result of a decision from our upper levels to use Azure as our primary solution for building applications. That has allowed us to reduce costs and consolidate from three data centers to one, with our disaster recovery solution in Azure. Our focus on one tool has made it simple. We're still working through that process. Whereas the failover solutions in Azure are somewhat the same as any other data center, building out the rules and requirements for firewalls is a little more complex. We have some third-party vendors that are helping us design and build out our security into Azure.

Near-synchronous replication is one of the benefits of Zerto that drove us to choose it over some others. With typical backup and recovery, your recovery point can be 24 hours. With the near-synchronous replication, our recovery point objectives are in the seconds. That's one of the major benefits of Zerto. We don't have to run incremental backups every half hour or 15 minutes. And the recovery time is fairly quick as well. It's essentially just a shutdown and reboot of a VM.

Near-synchronous replication is incredibly important for us because we have transactional applications that work on financial and transactional databases. The fewer the number of transactions that are potentially lost, the better it is for our organization. It means we don't have to go through rebuilding those transactions. It limits the amount of data that we could possibly lose in a disaster recovery situation, amounting to just a few seconds' worth.

The near-synchronous replication with Zerto has enabled us to reduce our RPOs to two seconds instead of hours and, sometimes, days.

And Zerto really improves RTOs for moving applications. You're not waiting for restores to happen. In some cases, if you have large amounts of data on the order of hundreds of terabytes, it could literally take you a week to recover certain applications, especially if you're pulling the data down from Azure or offsite storage. Zerto greatly improves the amount of time that it takes to recover. And you don't have to do one at a time. You can move over a large chunk of servers at once and get those recoveries running and mounting in your disaster recovery environment. It's a lot quicker than running a restore from a restore product.

In addition, the solution reduces the amount of downtime we have in applications during migration. We had a large number of servers, including some critical production applications. But we didn't have to find windows where we could have those systems interrupted for a short period of time. A few minutes of downtime, compared to having the application down for hours, helped move our migration project along. We moved about 250 servers in a three-month period, and we didn't have any issues with any of the applications related to data or the like. We had two instances where there was an issue related to licensing but they were our only issues when moving these applications.

What is most valuable?

The auto-connect feature is valuable because we can set the amount of time that we delay before committing a move from one location to another, giving application teams time to validate that the move went well and everything is working before we commit those changes. That gives us the ability to roll back to the same point we were at before we shut things down, if needed. 

Another nice aspect of the product is the non-intrusive failover of the application, similar to an actual disaster recovery test without impacting the services that are currently online. We can failover to an isolated environment and validate the application without impacting the production environment. We can do more testing in a non-impactful way using isolated testing. And once or twice a year, we'll do a live test that is more like what would happen if we lost a data center.

Zerto is also a very easy product to use. Although I've used it before in other environments, we introduced it to some engineers on our team and, after a couple of hours of training to go through the product, it's fairly intuitive. It's not something that takes a five-day training course to understand. You just drive through the checkboxes to build a protection group and that's pretty easy to do. You don't really have to understand coding or the like. It's GUI-driven, so it's fairly easy for an engineer to create protection groups.

What needs improvement?

You can use Zerto as a backup product, but in the discussions that I have had with them about the product, they don't really sell or talk about that feature as much. So I would be interested in improvements related to using it as a backup. If I could consolidate and use Zerto for disaster recovery as well as everyday backup and restore for situations where I need to recover something, that would be helpful. It has some of that functionality, but it's not something they promote a lot. They should point out the benefits of using Zerto as a backup and recovery product instead of just a DR product.

With Cohesity, we keep a limited amount of backups, about 14 days. That way, we can recover an individual server within the same site or we can restore data or databases that we need, in a non-DR way. We use it for typical day-to-day backup and restore. If we could use Zerto in a similar fashion for everyday backup and recovery scenarios, that would be another area where we could consolidate into a single application.

For how long have I used the solution?

At my old company, I used it for several years, and at the company I'm now at we've been using it for about a year.

What do I think about the stability of the solution?

It has been rock-solid. I haven't had any issues with any of the builds or the virtual managers. It just runs.

What do I think about the scalability of the solution?

It's really scalable. You can create as many protection groups as you need, and a lot more than we have in our environment. 

We do have some sites that are very low-bandwidth sites. Zerto is able to set throttling in the solution, but the throttling is set at a site-wide level. In those instances that have very low bandwidth, I can't reduce the throttling on that site. It would be nice if there were a way to control the throttling by the protection group for a specific workload.

How are customer service and support?

Our experience with their tech support has been good. I have never called them with an issue that they couldn't resolve fairly quickly. 

I did call them a few times on some migrations that we were doing off-hours where certain aspects of the migration didn't work, particularly on the reverse protection. I always got a callback within 30 minutes and most of the time it was quicker. The support has always been great.

How would you rate customer service and support?

Positive

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

One of the main issues was handling large data migrations. It wasn't feasible to do a big-bang move where we could move everything at one time, so we needed to schedule moves. We were able to at least replicate the information and work through a schedule for the migrations quickly. One of the major things we were trying to adjust was having to schedule the migrations and working with the team to validate that everything was functional. We were also looking to minimize the amount of time that that service would be offline during migration.

In addition, we use a combination of tools. We were doing replication with RecoverPoint, and straight backup and restore with Cohesity. While we still use Cohesity, we did get rid of RecoverPoint and we don't use VMware Site Recovery Manager because we're not recovering from VMware to VMware anymore. Cohesity does certain things and Zerto does certain things very well.

How was the initial setup?

The implementation of the migration was very straightforward. The implementation of disaster recovery into Azure was a little more complex. In part, that was because of the way our company built our Azure subscription and the rules we have in place for installation and dividing things and networks within Azure. 

But from the standpoint of installing and deploying the product, it's very simple.

What about the implementation team?

We did it in-house, but we did have a Zerto engineer run through the installation into Azure with us because we did run into some issues related to permissions in Azure and some of the custom roles that are defined. We also worked with an engineer from Azure to help us, mainly around the identity portion in Azure.

On our side, it was just me and one of our other engineers involved.

What was our ROI?

We have seen ROI on the migration project which didn't require a whole bunch of people involved. We rotated two people who were able to facilitate the migrations when we scheduled them in the evenings. Sometimes, we would do up to six or seven migrations in an evening. 

The main thing that held us up a little in that project was the validation process required by the business. If we had been able to just run through it, we probably would have completed it a lot more quickly.

Still, we didn't require a lot of resources to do it. It was just one engineer to handle a migration and the applications teams to validate. We didn't have to go outside the company to hire services to help us with the migration. That was helpful from a cost perspective.

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

Pricing is one area where there could be some improvement. We would like to see a consumption model that would charge in a DR scenario, where you're failing over and consuming those resources, instead of a per-protected-node model. Or it could be a model based on the amount of storage space you're protecting.

Others in our organization have raised the issue of how it's licensed, where you need one for every VM you're protecting.

Which other solutions did I evaluate?

We looked at RecoverPoint and Site Recovery Manager in VMware, but they just didn't fit the type of scenario that we were looking to set up with replication and recovery into Azure. We couldn't really find too many tools that were doing it in a way that was not too intrusive. There are ways you can migrate things into Azure and run them, but there's a technical process that you have to go through to make it happen. 

We were looking for a solution where we wouldn't have to flip all the switches for Azure. We wanted something straightforward that was much simpler to use. Zerto was really the only tool that we could find to do it. Others that we looked at briefly just didn't do what we wanted to do, so we didn't spend too much time on them.

Recovery with Zerto is a little more straightforward compared to other solutions, and the amount of time it takes is fairly short. You can recover with Cohesity fairly quickly, but there are a bunch of other things that you need to do, depending on how the recovery is done. If you're mounting a new virtual machine from a snapshot, which would give you a fairly quick recovery, you would still have to re-synchronize that data to keep it as a replication, and that takes some time. 

Zerto is just a more straightforward solution. You're getting pretty much the same server restored in under a minute, which is the time it takes to reboot, sync, and bring it back online. Other tasks you have to do, when bringing something up in another data center, like re-IP the machine, can be automated in the Zerto replication. It makes things easier.

What other advice do I have?

My advice is to look at what you're trying to accomplish. If you're looking for a migration tool, this is a great migration tool that will help you move workloads between data centers. It's agnostic as to whether you're using VMware, Microsoft, or Azure.

And you have to look at whether you're moving a large amount of data or a large number of servers. Think about how much downtime your business can afford for moving those applications. If you're looking for something that can move an application with minimal downtime, this may be a solution for you. Or if you're moving large amounts of data, but you don't want to be down for the whole time you're restoring or moving, a synchronous product like this may be a solution for you.

We have built a disaster recovery landing zone in our Azure environment and we built an isolated environment so we could do non-intrusive failover tests into Azure, and still keep our production environment up and running. We've tested certain workloads failing over into Azure, including a standard Windows or Linux box, and specific things like SQL Server, Oracle, et cetera. It has been going well so far and we're at the point where we're defining our protection groups and security in Azure for all of our critical workloads.

We have not yet used the immutable data copies feature, but I was just at a conference and had some meetings with Zerto, some of the product professionals and engineers, and that is something that we are strongly looking into. That's because of the issue of cyberattacks and because even backup systems could become corrupted and then you're still in a bad situation. Putting the data into an immutable repository is something that we are definitely looking into. Especially in the industry that we are in, cybersecurity is a big issue.

We have also not used it for blocking threats and attacks. But the ability, in conjunction with immutable data and putting that into a vault, to look at the data that is being replicated in real time and scan it, would be a great benefit. We do use some of the best-in-class tools for that kind of protection, but this would just be another layer to help with that. It's an interesting feature and another tool that would add a layer to our cyber protection.

Zerto hasn't reduced the number of staff involved in backup and DR management. We have a pretty lean team. We try to cross-train our employees on the different products that we use. But Zerto did help to simplify the process because we can get people trained on it. They can assist in covering for other people in the group when they're out. The training only takes a couple of hours to go through the tutorials.

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
Head of IT at TWM Solicitors LLP
Real User
Top 20
The integration with the mobile app is seamless, and helps to monitor the system from wherever
Pros and Cons
  • "Continuous replication is the primary feature we use now because we originally purchased Zerto. I'm starting to utilize the long-term retention and instantaneous file restoration features, which have been introduced since the original purchase in 2015. Initially, we deployed Zerto as a second data storage point, but ultimately it will probably facilitate some of the migration of my workloads up to the cloud. It's evolving with the network and how we deliver computation."
  • "It would be nice if Zerto offered OVFs, which are custom-built VMs that you can install on your virtualized environment. At the moment, I have the Zerto sitting on two custom-built Windows servers, which creates a lot of overhead. I'm waiting for them to create an OVF file, which is a built and hardened version of their Zerto server that I can just install wherever with a couple of mouse clicks."

What is our primary use case?

Our use case has evolved over the years. Initially, we strictly used Zerto for its original purpose: continuous replication of our virtual machines. We had a ransomware attack and needed to instantly restore virtual machines on or off-site without too much aggravation. That has been successful. The product expanded since then, and we're using many other features now.

We haven't replaced our other backup solutions yet, but we're considering it. I need to do some more testing of my databases and mail servers. It depends on how we utilize the cloud in the business. We're currently using an on-prem data center with a reserve disaster recovery site, but we're contemplating a transition to Azure. For example, if we are using Exchange Online, I'll need to find an appropriate backup solution. It may be something in the Azure stack, but I don't know yet.

We plan to use Zerto for cloud disaster recovery eventually. I'm in an upgrade cycle because I need to upgrade various backend elements to put me on 9.5, which I think is the latest release. That will give me immutable storage and benefits like single sign-on and multifactor authentication, which insurance companies increasingly request for all our applications. I plan to start shifting workloads into the cloud, and Zerto is one of the tools that will help me with that.

Zerto is deployed across my organization's entire computing infrastructure. We've got several different departments in the firm, so it handles many workloads. That sits on a Windows environment, and it replicates a data center where we just buy some shelving space. Including equity partners, consultants, and other visiting members of staff, we have around 250 users over seven sites.

How has it helped my organization?

Zerto is the ideal solution from a technical perspective. I have confidence that I can quickly and effortlessly restore data and train my IT colleagues to do the same. Ultimately, the benefit to the firm is knowing that everything's protected. My colleagues don't need to dive deeply into what I do because it's my specialty. It has been a massive game-changer to have that confidence in data recoverability. The rest of the firm considers it part of the suite of tools I've implemented. 

I've been working in IT for nearly 30 years. In the old days, you would need to know precisely the configuration, whereas now you only have to press a few buttons, and you're in the same situation that you would've been after maybe hours or days in the past. That's happened in a short period of my career. 

We've seen a massive improvement in our RPOs. It used to take hours, if not days. When I started working here 17 years ago, recovery took weeks because of the lack of preparation. Now, it's done in a matter of minutes. You've got to practice it, and the Zerto tool has a timer where it asks you to check your DR every six months. I do that religiously. The RPO is theoretically in minutes, but I've never had to do it. 

Zerto has also had an overall positive impact on RTOs. You don't need to maintain a massive set of documents to recover your systems. You can spin them all back up in your reserve site. Obviously, you must do them in the correct order. Then, you can then test your functionality, and you should be good to go. It massively reduced our RTOs.

Our RPO went down by about four hours, and the recovery time may have gone down from five or six hours to less than an hour. Some firms that invest in this can get it a lot lower than that, but I would say we're well below an hour now to restore the entire system.

Downtime comes in so many varieties, and you need a Swiss Army knife with the tools you need to deal with them all. Zerto is only one piece of a toolset I use, but it's one of the major elements. It offers the basic flexibility to have different destinations for your data and the ability to spin it up quickly. When recovering from a disaster, you typically deal with an issue you've never seen before.

Sometimes, you might have a failure that only affects a third of your network, or it's a ransomware attack that only affects specific VMs. You have no idea what will hit, so flexibility is essential. You need to be able to do it and get on with trying to recover your data rather than having to remind yourself how to do it. I've had to do that a few times with software. You practice it because you can't remember it, whereas you don't need to do that with Zerto.

The cost of downtime is hard to quantify with a law firm. There's an evident revenue impact when the system is not running. It means people are not earning fees because we're a professional services firm. However, the effect's size depends on the disaster type and how long you are down. If you're down for weeks, that will damage your reputation, which is everything in the legal field. It's a massive advantage if we can get our services online quickly. 

The solution has also reduced our DR testing time considerably. You're prompted to test every six months, and I can run through the test in a couple of clicks. I go into the reserve site and ensure the servers are spun up. I verified that all the services are running as expected, and they can see each other. Completing the test cycle takes me maybe 30 minutes.

Previously, it might have taken a few days to do a disaster recovery trial because I had no way to restore data accurately without affecting the live data. Zerto creates a sandbox environment where you can test without affecting operations. In the past, I might have needed to disrupt business for a couple of days to run a full test. 

I can allocate that saved time to more valuable tasks. When I'm not maintaining the system, my role is to be a Solutions Architect, deliver new projects, and provide third-line support to help users with their day-to-day tasks. Zerto frees me up to concentrate on developing my team and working on value-added business projects. I estimate that it reduced my system management overhead by 15 percent. 

I can't say with certainty that it would reduce the staff need in a real-life disaster recovery situation because we never know what we'll get. We take disaster recovery seriously because we don't see the form disaster will take. People from marketing will be involved in communicating with our client base. Elements of management need to intervene to ensure the staff members are safe. "Disaster" is such a broad term. You could have a fire in one of your buildings or a ransomware attack. However, it would be easy for me to perform the disaster recovery by myself from the Zerto control panel.

What is most valuable?

Continuous replication is the primary feature we use now because we originally purchased Zerto. I'm starting to utilize the long-term retention and instantaneous file restoration features, which have been introduced since the original purchase in 2015. Initially, we deployed Zerto as a second data storage point, but ultimately it will probably facilitate some of the migration of my workloads up to the cloud. It's evolving with the network and how we deliver computation.

Near-synchronous replication is handy for instantaneous file restores. Over the next few years, I think I will have to be more flexible about how I run my network. We're transitioning from an on-premises to a hybrid setup and, finally, a cloud environment. It's crucial to have the ability to move around data recovery points, some of which are local, and it's becoming increasingly important as we move away from traditional backups. 

Currently, I'm still maintaining another backup regime due to the complexity of recovering some of my applications. Near-synchronous replication isn't one of the most vital factors yet. Continuous replication to remote sites is the primary concern and reason for the purchase. We are waiting to upgrade to version 9.5 before we start using immutable data copies, but I'm excited about that feature. Immutable backups will be a real game-changer because we'll have an incorruptible backup sitting in the background.

What needs improvement?

It would be nice if Zerto offered OVFs, which are custom-built VMs that you can install on your virtualized environment. At the moment, I have the Zerto sitting on two custom-built Windows servers, which creates a lot of overhead. I'm waiting for them to create an OVF file, which is a built and hardened version of their Zerto server that I can just install wherever with a couple of mouse clicks. 

For how long have I used the solution?

I have been using Zerto for around seven years.

What do I think about the stability of the solution?

The stability is excellent. I've never had a problem with it.

What do I think about the scalability of the solution?

The scalability's been fine. I increased my licenses from 20 to 35 or 40. It scales horizontally too. I used to replicate to one destination: my data center. Now I replicate to two destinations, and I'm starting to replicate into Azure Blob storage, as well.

How are customer service and support?

I rate Zerto's support 10 out of 10. They always answer my questions, but I have very few issues because it's so simple and flexible to use. It's well thought out. Software often isn't designed with the user in mind, but this one has been. It's aimed at the right professional level. It's obvious if you've got enough technical knowledge. It's so robust and easy to use that I rarely contact technical support.

How would you rate customer service and support?

Positive

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

I did use a different solution that was part of the EMC stack for my storage area networks. Zerto is probably 10 times easier to use. When you work for a small or medium-sized organization, you aren't generally exposed to a variety of solutions because there are higher opportunity costs for time spent learning and setting it up. 

When I was doing the assessment, I got some experience with SAN-based recovery tools integrated with VMware, but those didn't seem to work well. Zerto is simple and actually works. 

How was the initial setup?

I purchased Zerto to simplify installation and configuration. I set aside a couple of weeks to install it, and I managed to do it in one afternoon. Managing the solution is pretty straightforward for someone with technical skills and experience. I find it simple to use, which is one of the reasons I like it. A lot of the products in the legal sector where I work are incredibly complicated and hard to use. This isn't one of them.

I couldn't believe how easy it was to install. Based on my previous experience with the EMC solution, I expected to be deploying it full-time for two weeks. I set up the prerequisites in advance, which included creating a couple of Windows VMs. We installed, set it up, and started replication within a couple of hours. I have a team of people, but I completed the installation myself.

Zerto is relatively low maintenance, which is another bonus. It just churns away. You need occasional upgrades and bug fixes. I spend an hour or two on maintenance every six months or so. Apart from that, the only other maintenance I do is testing every six months. 

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

Obviously, it would be nice to have it for free. Nevertheless, a lot of effort has gone into making it a top-notch product. An excellent product with expert support is never going to be cheap. I think it's fairly priced for what it does and the benefit it brings to our business.

I've gone from a standard license to an enterprise license with an increasing number of VMs. Enterprise covers on-prem and the cloud, whereas the standard license is strictly on-premise. I'm not an expert on Zerto's licensing, but I know that I've increased my VMs and the range of destinations as part of an upgrade.

Which other solutions did I evaluate?

I didn't evaluate any other solutions because I instantly liked Zerto. I'd been given permission to look for new products to protect us in the future, but when I saw a demo of Zerto, it was pretty much over.

Virtually everything is fairly straightforward. The upgrade cycle is painful in other products, but easy to do in Zerto. The integration with the mobile app is seamless, so I can monitor the system from wherever. 

What other advice do I have?

I rate Zerto 10 out of 10. It's given me tremendous peace of mind and confidence that the network can be recovered quickly and accurately. I would suggest future users take some time to do an in-depth trial. 

If that doesn't convince you, I don't know what will. In my job, a decision is sometimes obvious, but it's tricky in other instances. You might need to draw up a weighted scoring model and check a couple of suppliers. This time, it was so clear. It's hard to quantify the pleasure of getting a nice piece of software that just works.

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.