Lead Site Reliability Engineer at a insurance company with 1,001-5,000 employees
Real User
Gives us a seamless, performant data center migration
Pros and Cons
  • "It gives us a seamless, performant data center migration. When we were migrating between physical data centers, we did what normally would have been a 72-hour job in about 18 hours. A large part of that was thanks to Zerto being able to rate limit and throttle how much data was being sent or transfers were happening. Being able to script around it and create governors was important. We didn't have that previously. That is one big use case that has saved an immense amount of time and effort."
  • "Analytics has a 90-day window, where it keeps data. It would be nice to have on-prem storage instead of cloud storage for that so we can keep the data for longer. Unless you discover the problem within three months, you don't know that you need the data. Then, it is gone by the time you realize there is an issue."

What is our primary use case?

Zerto is primarily used for site-to-site replication and recovery, low RTO and RPO, and migration from onsite to the cloud.

Currently, we have ZVMs installed on Windows Servers in our environment, vRAs and VRAHs installed on our vCenter environment, and ZCAs installed in our Azure environment.

I am not the primary user of Zerto. I am sort of the implementation or API specialist on it.

How has it helped my organization?

It gives us a seamless, performant data center migration. When we were migrating between physical data centers, we did what normally would have been a 72-hour job in about 18 hours. A large part of that was thanks to Zerto being able to rate limit and throttle how much data was being sent or transfers were happening. Being able to script around it and create governors was important. We didn't have that previously. That is one big use case that has saved an immense amount of time and effort. 

Previous data migrations were really tough and hard. It was high stress with late nights, no sleep, and a lot of coffee and Red Bull. We didn't have that this time. Everyone felt that we got through this in a slightly longer working day instead of 72 hours. So, we have seen a return on investment.

Another use case is being able to do disaster recovery testing at will, whenever we want to. That has been really special.

What is most valuable?

Primarily, the most valuable feature is the simplified deployment methodology, but also use the REST API and script ability for modularity. 

Zerto API Wrapper is really good. We don't use the Zerto module specifically. Instead, we use API Wrapper, which is a lot better in my opinion. The fact that we can extend the functionality of Zerto to high-level policies or processes via the API, whether it is through API Wrapper or otherwise, sort of brings out a lot of interesting usability use cases for us. We can do self-service replication of servers via ServiceNow, scripting, etc., offering extensibility. It is really easy to use. It helps to save a ton of time as far as replication goes.

There are open API calls. Things are available via the UI and API that may not be documented really well. You can open developer tools, inspect those elements, and see what those payloads are, but it is an extra step. For someone who is kind of new to the game, they may not know how to do that. 

What needs improvement?

Zerto is not an API-first company, but an API-now company. A lot of the functionality that is in Zerto UI is not in the Zerto API. That is likely because it is baked in code or compiled down DLLs. Every business has to make a decision to work on something, and I don't think Zerto has committed resources to working on that part. It is a problem to do cleanup for Azure Blob Storage, recovery site storage, or whenever you remove a VM from a VPG without deleting the VPG. That needs to be improved. 

Doing scheduled disaster recovery connection tests, e.g., being able to migrate things up and get things working on a recovery site without needing a user to do it, would be helpful.

Analytics has a 90-day window, where it keeps data. It would be nice to have on-prem storage instead of cloud storage for that so we can keep the data for longer. Unless you discover the problem within three months, you don't know that you need the data. Then, it is gone by the time you realize there is an issue. 

I would like to be able to offsite some data. We export our analytical data so we can keep it longer without having to script around it. It is possible right now, with the API, to script around it. However, I don't want to have to write a monthly process to export the last three months of data to a spreadsheet so I can just have it if I need it. 

A lot of the PowerShell documentation in some of Zerto tutorials or how-tos is a PowerShell-to-legacy sort of paradigm. It needs to be updated to at least 3, likely 5, or probably 7. It looks like it was written by someone who didn't know PowerShell, but had to learn it really fast. It does the job. If you copy and paste it, then it will work, which is something. That is way better than what a lot of people do. However, I feel like a bit more effort should be pushed towards PowerShell.

I would like them to build an alerting system. I am trying to find a way to connect it to my business continuity people, so the Zerto people don't need to be pseudo-business continuity people all the time. They can just be IT people. 

I would like more creature comforts for the scripting engineer. It would be nice if they could expand the development community around building different APIs or API structures for Zerto.

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

For how long have I used the solution?

I have been using Zerto for two and a half to three years.

What do I think about the stability of the solution?

Stability of Zerto is significantly better now than it used to be. It was a little unstable, especially when you were doing massive amounts of migrations. I think there was a disconnect with Zerto's handling of jobs and the ticketing systems inside of vCenter. I am not saying that was a Zerto problem. It might have been a vCenter problem, where vCenter was unable to communicate how much availability it has to field those jobs, then its internal tickets were consumed in a way that Zerto couldn't deal with them well. There was probably some type of internal timeout that was reached when things failed. 

If you are not prepared to rapidly click retry a bunch of times, that will be a big problem for you. You can get around it by scripting. That is how we did it. You can get around it by updating Zerto to at least version 8, maybe even 7.53. 

The stability now seems solid. If there are some disruptions of service, I am not seeing it. We have taken off restrictions on our network throttling. So, we are not throttling that at all. We fullly let it go and it doesn't seem to be having a problem.

What do I think about the scalability of the solution?

We have hundreds of terabytes up to petabytes of storage and replicated data. Triple-digits up to thousand-plus virtual machines are being replicated. There is RDM to VHD and VHDX-VMDK conversions. We have temporary disks or bypass disks involved for situations where VMs might be turned off or removed from environments without any lead time, thus pausing VPGs.

I don't think it has a problem with scalability. We haven't yet run into a problem scaling it. You could always deploy more ZVMs and ZCAs. The analytics engine has a calculator to figure out how many you should deploy. Follow that. It isn't perfect. If anything, it's a little conservative. Just don't test the waters unless you are prepared to sink a little bit. Be prepared to sink if you're going to try to min-max it. You can always tweak it. There are so many tweaks you can do on the ZVM and ZCA side. We have had to do probably a half dozen of those because our environment isn't the same as every other environment. 

You can push it to its limits. I don't think it is a problem with scalability. I think it is a nuance of your environment.

There were some hurt feelings with some of our engineers. They were told that it would just be plug and play. They didn't realize that it would actually take up a duplicate amount of storage. As a point of policy, that is how it works. I asked them, "How do you think it should work? If you don't think the storage should double, where are we putting the bits? Where is it going? How is replication happening?" It makes sense to me, but I think they were told something else. I don't know if that was a salesperson from Zerto's side or an advocate on the company's side, but they were misinformed. 

How are customer service and support?

Zerto support is usually very good. I feel like we always get those Sev 1 cases where something is wrong with the core product. For example, every time that they have released a new minor or major build, there are release notes of what has been fixed. We have had five of those line items since version 7.

We have been using it since version 5. However, since version 7, we have had five big line items for those changes since we have a big environment and script a lot more, and maybe we script more than a lot of Zerto customers. We found a lot of weirdness in our environment, and that matriculated up. I got a call from the East Coast technical representative for the dev team. Every day, I had a call on the update of those tickets. You don't see that a lot. 

Some platforms work flawlessly. Some platforms are more simple. Zerto is a complicated platform doing a lot. After that initial burn-in period with our support team, we got grade-A service, which was really great. I would probably rate them as eight or nine out of 10. There is room for improvement, but if they never improved, I would be happy with the level of service and support that we have now.

I am pretty patient. From a programming standpoint, technology is hard and environments differ greatly, and I am willing to forgive a little bit. I don't speak for all my company. There are people in my company who don't accept that. They want it fixed tomorrow (or yesterday). Personally, I understand that it is hard and takes time to understand as the logs only tell you so much. 

How would you rate customer service and support?

Positive

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

I can't even remember what the previous product was. 

How was the initial setup?

I wasn't involved in the initial deployment. I have been involved with subsequent deployments, which were straightforward. Originally, I babysat it, then I owned it in tandem with another engineer who was actually the owner of it. I helped with the scripting part since I had more scripting knowledge. 

Subsequent deployments take 15 minutes, which is not long. With ZVM installers, they ask you a question, then you put it in. If you don't have the answers, then you go get them. You have no business deploying Zerto if you don't have those answers to begin with. ZCM is just as easy.

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

Don't buy Zerto expecting to save money and get 100% performance. That is not how it works. That is not what you are buying. You are buying a solution that you have to invest in. Don't invest in buying the license, but none of the technology to support it. Ask the hard questions and expect answers that aren't, "Yeah, it will do that. No questions asked." 

Which other solutions did I evaluate?

I don't have a lot of experience with other solutions, but I have used a lot of technology. I know what approachable and unapproachable platforms look like. Zerto is an approachable platform. If you know the concepts of data replication and data recovery and know what those data protections look like, then you should be able to pick up Zerto with relative ease. 

Generally speaking, things in Zerto are where I would expect them to be. That is hard to do sometimes on other platforms. Sometimes, you get designers, UI developers, or user-experience people who don't really understand how engineers will approach a product. The Zerto platform seems tailored for people who are full code, low-code, or no-code, which is really special. I don't feel like you see that a lot. You start to get more of it now. However, having someone who is not specifically geared towards data replication, data recovery, or data protection accessing Zerto, they can use it if they have some of the nomenclature. They need to know a very small vocabulary in order to be able to navigate Zerto since things are where you think they will be.

What other advice do I have?

Determine your questions in advance and ask them to the Zerto sales team. Get them to engage the engineering team as best they can. It does what it is supposed to do. It is not a magic silver bullet that just takes out everything. Everything is in layers. Zerto is only as good as your storage, back-end network, and replication infrastructure layer. It is only as good as the things allowing it to be good.

It has done a great job for what we needed it to do. I don't really have to worry about it doing the job. It is already doing it.

I would rate Zerto as eight or nine out of 10.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Disaster Recovery Engineer at a tech services company with 501-1,000 employees
Real User
Replicates and recovers within minutes and enables our growth
Pros and Cons
  • "There are a lot of valuable features. The basics of what it does to replicate and recover things within minutes is awesome. It's far above anything that any of the competition has. We offer other disaster recovery software but primarily use Zerto for recovery times and the number of recovery points because of how fast and easy it is. It's so much better."
  • "The problem with the backup product is that it's not very mature and you really need a specific use case to be able to use it effectively. It's hard to explain to our customers, especially our large customers, that the use case is so limited."

What is our primary use case?

Our primary use case for Zerto is for disaster recovery. In the last few versions, they've offered backup, but we don't use it because it's not nearly as robust as what most of our customers are looking for. We also use it for migrations too, to migrate customers into our cloud, and things like that. But that's around 20% of our use case.

How has it helped my organization?

Zerto has enabled our growth. Five years ago we had around 20 customers and now we have 500. We protect around 15,000 VMs now.

What is most valuable?

One of the most valuable features is the analytics portal. It's still an evolving feature and has ways to go but we use that for monitoring because we have hundreds of sites. It's nice that all the alerts and everything is consolidated into that one site because we used to have to make sure that we were connected to many, many sites to make alerting work, which was a nightmare. 

Our alerting is done through scripting too. They do have pre-canned alerting through but is not very robust and they're working on it. They actually included us in the study on it. For instance, if you were to have a problem at a certain site or something, there's no way that you could take it out of monitoring. If you were using their system, it would just flood you with alerts from all kinds of stuff from the site if it was down. It is great if a site is down and you don't expect it, but if you have planned maintenance, you don't want all of this coming in.

There are a lot of valuable features. The basics of what it does to replicate and recover things within minutes is awesome. It's far above anything that any of the competition has. We offer other disaster recovery software but primarily use Zerto for recovery times and the number of recovery points because of how fast and easy it is. It's so much better.

We reduced the number of people involved in recovery situations by using Zerto. We had another solution before and we had a small number of customers and it took the whole team to manage 20 customers. Now we have 400 to 500 customers and our team is relatively the same size. We're broken up into different teams, but when we managed it all ourselves with only 20 customers, we had four people. And now we have around 500 customers and we have around 20 team members.

What needs improvement?

Zerto has a really robust PowerShell and scripting that you can get lots of numbers out of but it's not exactly the easiest thing to do. Zerto has a few nice pre-canned reports but there is a need for more. Unless you script something, it's difficult to go in, click a button, and see the information that you may be looking for.

The problem with the backup product is that it's not very mature and you really need a specific use case to be able to use it effectively. It's hard to explain to our customers, especially our large customers, that the use case is so limited.

Zerto is very easy to use on the surface, especially if you're an enterprise customer, which is just like A to B replication or one site to two sites. As a cloud provider, they still have a lot of work to do. But for most customers, it would be fantastic. We have a lot of private clouds that are one site or two sites. So when it's not meshed like our larger environment is, it works fantastic. But when you get into the overall fully meshed model with vCD integration that we have, it doesn't work as well. I think Zerto is mostly concentrated on the enterprise customer and left the cloud providers by the wayside.

With the HP acquisition, product development has certainly accelerated. They recently released the first major half release and have put additional focus on cloud providers. Unfortunately, the major focus remains on Enterprise. Next year, they will force customers to move from Windows management VMs to Debian Linux. I can only hope they have a well-thought-out migration tool. My fear is that the cloud provider will be a secondary thought once again.

The major issue with Zerto development is that they refuse to patch the current software release and only patch the newest release. When you hit the bug, they expect you to upgrade right away. This is not an issue if you only have a hand full of sites. The issue when you have 100s is that there is no way to skip a minor release. Every multi-tenant customer you have must be upgraded to every minor release. Two to three upgrades every year for every customer is very intrusive and requires way more management effort than should be necessary. We often have a hand full of customers delaying the upgrade cycle and are forced to discontinue service to those customers. HP can surely develop a better model.

For how long have I used the solution?

I have been using Zerto for six and a half years. It's deployed on-premises, on the cloud, and we use it as a SaaS offering. We are the cloud provider. We also integrate with AWS and Azure.

What do I think about the stability of the solution?

It's a very stable solution, for the most part. They have a new release every six months and some releases are better than others as far as bugs. Sometimes those bugs have to do with something in Hyper-V, and sometimes they have something to do with VMware or vCenter. But many times, it's directly related to Zerto's problems. Usually, their major releases go in .0 and .5. The .0 releases have the new features in them and they're more buggy and the .5 releases are more stable.

What do I think about the scalability of the solution?

It's extremely scalable, in a small sense, but the problem is when you get very meshed, with 10 sites replicating to 10 sites, and each one of them is meshed in to be able to replicate it to the other one. Then scalability starts to become problematic.

The big thing is, we have a cloud manager that manages all our ZVMs, which enterprise customers probably wouldn't have. You can only upgrade half a release for each upgrade. So you couldn't go from Zerto 6 to Zerto 7. For instance, you have to go to 6.5 and then go to seven.

Trying to upgrade is not easy because every customer that's paired and replicating into those sites has to upgrade it in those steps. It takes us several months, twice a year, to get everybody upgraded. They have a portal called Cloud Control which makes things better as far as upgrades, but they recently broke it with version 7.5 by adding encryption. So it was useless. We just upgraded to a version in which it should be working again, so the next time we're going to try to use Cloud Control to upgrade. Hopefully, it will be better. We only really have one round of upgrades through Cloud Control to get an idea of how well it worked. 75% of the time, those upgrades work without problems.

How are customer service and support?

There was a time when they had customer service people just taking tickets and they couldn't really help you at all, which was terrible. Now, they have a level-one level-two-type model. The level-one guys are getting better, but as they grow, it can be difficult. 

All of our engineers are certified and we would like to go straight to level two. A lot of times we waste a lot of time with level one, and then they put the ticket in the queue for level two. So it takes another day to get to level two unless we're really loud and escalating the ticket right away. The biggest problem that we have with Zerto is getting to level two. 90% of the time, because of our knowledge, level one is not useful to us. Although, it probably would be to the average customer. 

Zerto really needs support dedicated to CSPs and large customers.

How would you rate customer service and support?

Positive

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

We switched from our previous solution because Zerto was so much easier than everything else that we saw. We have a team that does the tests. It was a pretty easy choice to move away from those platforms at the time and those platforms no longer exist. Today there are many alternative DRaaS solutions and we offer many of them. Zerto remains more mature and feature-rich than the competition though.

How was the initial setup?

The initial setup was pretty easy. You have to have connectivity between the sites that you're replicating, your production, and then your DR site or sites. Getting that connectivity is the biggest thing. Once that connectivity is there, it's fairly simple. You deploy Windows VM, put a small software package on it, and then pair the two. You do the same thing at the recovery site and once those sites are able to talk. In VMware, you install a VM on each ESX host that you need to replicate a VM on. Then you create a policy to do that replication. The replication policies work very well. Re-IP on failover if problematic.

The network connectivity takes the longest. It can take weeks, depending on what you have to do to connect the sites. It could be a couple of hours if you're just setting up a VPN. If you're putting in a circuit, it could take a very long time. That's the X factor with it, but assuming that's already there, within an hour you could be replicating data from one site to another.

ZCCs remain a major stumbling block. If the routing table has issues, the only fix is to delete all protection, redeploy the ZCC and rebuild. Again, avoid Zerto Cloud Manager until the product matures.

What about the implementation team?

We implemented the solution in-house.

What was our ROI?

We have seen an ROI. Otherwise, we wouldn't keep using it. The biggest thing is the number of VMs we can support with the staff that we have. 

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

The licensing is fair. We have an enterprise license in which Zerto gives us 20,000 licenses or something well above what they think we're going to sell for the year. Then all our customers pull from that pool and we resell the licenses. We may sell 50 licenses to a customer but at the start of their contract, they may only have 30 VMs ready for DR. We contract them for 50, but eventually, they'll get up to 50. So we don't have to go to the vendor and add and remove one license here or one license there all the time.

That part of it is easy, but we do have to license all of our sites once a year, which is a pain and all of our sites report to Zerto Analytics. I've been asking them for years since they started Zerto Analytics, why we can't just put our license key on analytics rather than logging into hundreds of sites and putting them in each site. That's a real beast. They definitely need to fix the part where the site licensing is terrible. As far as the licensing VMs to replicate, that's great.  In version 9, Zerto plans on deploying a license server to address this.

Zerto 9 is out and there is still no customer-deployable license server. We regularly have issues with customers who cannot reach the Zerto license server. They cut you off at the knees after 14 days! HP really needs to work on this process.

Which other solutions did I evaluate?

Commvault was one of the big ones we looked at. Commvault is much more complex and expensive. We also looked at AWS and Azure. We offer a wide range of solutions. 

Recently launched last year, Nutanix LEAP is primarily designed for people that use Nutanix, and not everybody does. Not everybody can use it. We also offer RecoverPoint for VMs. It is a Dell EMC product, so it's geared toward people that are running VxRail. And then there is vCloud Availability. You have to have vCloud Director on both sides and vCenter, which is not something that everybody has either. vCloud Availability monitoring is also a nightmare. Zerto is more the product of choice for most use cases. 

What other advice do I have?

Some of the biggest problems that we've had as a cloud provider are the vCD integration and the Zerto Cloud Manager integration. If you can avoid those two things, avoid them.

I would rate Zerto an eight out of ten. 

Which deployment model are you using for this solution?

Hybrid Cloud

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

Other
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
PeerSpot user
Buyer's Guide
Zerto
May 2023
Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: May 2023.
708,461 professionals have used our research since 2012.
Network Administrator at a financial services firm with 51-200 employees
Real User
Easy to set up and use with a nice GUI, good support, and the automated failover works well
Pros and Cons
  • "Zerto is extremely easy to use. You set it and forget it."
  • "The reporting could be improved in terms of the reports that you can show to auditors to prove that you have done the testing. I provide the reports that it generates now but, it would be great if, at the end of a DR test, it would generate a report of everything that Zerto did."

What is our primary use case?

Zerto runs on a Windows Virtual Server and we have it installed at two sites. There is the production site, as well as the failover DR site.

We use this product almost exclusively for disaster recovery. It is responsible for the automated recovery of what we deem to be our mission-critical servers.

How has it helped my organization?

In terms of its ability to provide continuous data protection, this is a product that I trust. We test it quarterly to make sure that what the dashboard is telling us is correct. But, I've used it long enough to know that when I see the dashboard telling me that the virtual protection groups (VPGs) health are all green, then things are working correctly. Our average RPO is usually somewhere between three and 10 seconds.

We used to perform a disaster recovery test once a year, and it was painful because everything was manual. Now that we do it quarterly, we're able to provide management with reports of the tests, which not only makes management happy but also makes various governing bodies happy. We're a financial advisory firm, so it's the SEC that oversees us. That said, I'm sure this holds true in many industries. It allows you to have the reports to prove that you've done the tests. We don't have to ask them to take our word for it.

When we need to failback or move workloads, Zerto has absolutely decreased the time and number of people that are required to do so. For example, if I just want to test and prove that the network is up, it's something that I can do by myself. If I want to have people log in and test applications and stuff like that, I would need additional people. However, it has a built-in test function, so it will create a complete test network that you can run workloads on to show that the tests are successful. Afterward, you can delete the network and you're back just running, waiting for the next time you want to do that. In a situation like this, using Zerto saves eight hours or more and I can set it up and test it on my own unless I want people actually testing applications.

Thankfully, we have not had to use this product to recover from a ransomware attack or other disaster, but it would absolutely work in that case. By replicating the data, if ransomware were to hit the production side, it most likely would not also lock the disaster recovery side. This means that we would certainly be able to bring it up from there. Alternatively, it lets us pick points in time, so we can just go back to the moment in time before the ransomware happened. In a situation like this, I can't say that it would take fewer people but it would take fewer hours.

What is most valuable?

The most valuable feature is the automated failover, as it allows us to get the essential servers up at our DR site with little intervention.

Zerto is extremely easy to use. You set it and forget it.

It has a nice graphical interface.

What needs improvement?

The reporting could be improved in terms of the reports that you can show to auditors to prove that you have done the testing. I provide the reports that it generates now but, it would be great if, at the end of a DR test, it would generate a report of everything that Zerto did.

This would include details like what systems were up. Currently, that's not how the report reads. You would have to be an IT person to read the current reports that it produces. I would like for them to be the type of reports that I can put in front of an auditor or the president of our firm that would make sense to them, without me having to interpret and explain the results.

For how long have I used the solution?

We are in our seventh year of using Zerto.

What do I think about the stability of the solution?

Stability-wise, this solution is rock-solid. If it fails, it's not going to be Zerto that fails. It's going to be either that your storage has failed or the bandwidth, or connectivity, is not there. I don't see a way where Zerto would be the culprit in a failure-type instance.

What do I think about the scalability of the solution?

Our company is fairly small and the entire firm relies on it. That said, only one person actively uses it. We have three or four IT staff but Zerto has always been my responsibility.

In terms of scalability, I bet it would be no issue whatsoever. It's licensed according to the virtual machines that you want to protect. The only limitation of the scalability would be how deep your pockets are because it's going to be license costs.

We're a registered financial advisory firm, and we are growing. In the past year to 18 months, we have grown from approximately 52 employees to 70 employees. Everybody relies on it because if we have a disaster recovery type of situation, then everybody is going to expect to be able to work.

It is still a very small number of IT staff, so I can see that as we hire more IT staff to support a larger user base, we will certainly have more users.  At least, I hope not to be the only one responsible for this solution as we grow.

How are customer service and support?

I would rate the technical support a ten out of ten.

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

Prior to Zerto, we used VMware Site Recovery Manager (SRM). We switched because it requires a lot of manual upkeep, and there is no automation involved unless you write the scripts. There are lots of freeware sites where you can download scripts, but aside from that, we were spending a lot of time manually writing scripts and maintaining everything. This was really counterproductive for the amount of time we had available in a day.

Essentially, SRM was replaced because of better interface automation and ease of use. 

How was the initial setup?

The setup is very easily done because you tie it into your VMware vCenter. When you put in your credentials, it will recognize everything on your networks. It will recognize storage, whether it be cloud-based or as in our case, at another data center. Once you have those defined, it's just a matter of creating groups that you want to recover, server-wise.

The reason that you would want to do it in groups is that you can set it up in the automation such that it will bring up groups in a certain order. That way, you have a network where the domain controllers come up in the first group, and you can automate stuff from there.

Seven years ago, when I first started to use it, I found it more difficult. I wouldn't say that it was complex but they have certainly made improvements over the years. Where it stands now, if I had to set it up from scratch, I could probably do it in about an hour. Of course, that is because of the way I know the application but in terms of how they have changed the setup, it is certainly more user-friendly than it was compared to where it started.

I remember running into a couple of issues during the deployment, and I contacted their support. They were fantastic and helped me get through it. They made sure that all of my questions were answered, and that it was up and running how we intended it to be used. A lot of it probably had to do with me being a novice at that point, in terms of using the application.

It was a multi-site deployment, with a production site and a DR site, with dedicated storage for each. We have changed the storage that it uses over the years and if I had to do it again, I would use another vendor for storage. A lot of the issues that we ran into were related to the initial storage that we used, as opposed to Zerto issues, even though it was Zerto support that helped me fix them. 

Overall, the deployment was fairly easy. Not because everything went great, but because of the combination of the application being pretty well-written and the support. I would rate the deployment an eight out of ten.

What about the implementation team?

I deployed Zerto with the help of a consultant, contacting support as we needed to. The consultant was NetGain Technologies and they're based out of Lexington, Kentucky. Their service was phenomenal and I would use them again in a heartbeat for this type of deployment. Ultimately, any issues that we ran into boiled down to some issues with the storage we chose to run it on.

I am responsible for the maintenance. 

What was our ROI?

We have absolutely seen a return on investment in terms of the manhours that have to be put into maintaining and testing this type of product. Thankfully, we have never had to use it in a true DR situation. However, I can guarantee that if something were to happen, even beyond the manhours and ease of automation, that it would pay for itself.

Our network infrastructure runs pretty smoothly most of the time. That said, Zerto has helped us to reduce downtime by approximately 20%. It is difficult to equate this with a monetary value because we have to consider what happens when a client misses a trade or cannot get a hold of their portfolio manager.

If it were an outage of a couple of hours then the person might pay a little more or a little less for a stock that they were trying to purchase. Overall, however, it is difficult to estimate. We aren't a day trading-type firm, so ultimately, I'm not sure that a short outage has any effect on our revenue stream whatsoever.

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

As a small company, we own the smallest license that Zerto offers, which is 15 VMs. I've not had to contact them or my reseller about purchasing additional licenses or to find out how much they cost.

Which other solutions did I evaluate?

We spoke with VMware to see what their pipeline was for upgrades or changes to Site Recovery Manager and we also looked at both Cohesity and Rubrik.

I like the separation of the software and the storage, whereas some of those other products are all-in-one. You're buying the software and storage together on the same platform. This means that the scalability would be different.

Sometimes, this is a case of adding shelves for storage. In that situation, for example, you have to start taking the data center rack space into account. Whereas with Zerto, it lets us build upon hardware we already had, even though we use dedicated storage.

What other advice do I have?

Version 9 of this product is out. However, we have not yet upgraded. We're not leveraging the cloud the way a lot of companies do these days, and I know from the release notes that I've read that most of the new features are related to the cloud. There's not a lot of research and development being done on physical data centers anymore.

At this point, I'm very happy with where the product sits for my network. We are now just starting to move things to the cloud, which will take place over the next couple of years, so my assessment in this regard may change in perhaps a few years.

At the moment, we don't have plans to use it for long-term retention. We keep about three days' worth of data in Zerto and then it rolls off. We have other systems in place for long-term retention.

My advice for anybody who is looking into implementing Zerto is to do your homework. In the end, this product checks all of the boxes and it's the one that I would go with.

In the way that we use this solution, which I know is not how everybody uses it, we have storage that is specifically used for Zerto and two data centers. The way it works in that scenario, as long the bandwidth is there, meaning some sort of dedicated circuit between the two sites, it's flawless in my opinion.

The biggest lesson that I have learned from using Zerto is that disaster recovery doesn't have to be a giant pain. I certainly used to look at it that way in the past.

I would rate this solution a ten out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Manager System Administrators at a financial services firm with 51-200 employees
Real User
Top 20
Decreases the time it takes to recover and the number of people needed to do so
Pros and Cons
  • "Zerto is so easy to use that when I showed it to my manager, he said jokingly, 'Huh. I could use it myself, I don't need you.' Zerto is most elegant."

    What is our primary use case?

    It's deployed on private cloud. I have two data centers, one in New Jersey, one in Ohio, which is my job site. I'm using a Zerto instance for my servers and another for my VDI machines. I can replicate everything.

    How has it helped my organization?

    When COVID started, everybody started to work from home and the internet connection to our New Jersey data center was saturated. But we had the same internet connection in Ohio, so why not use it? We needed to spread the load between data centers, so I used Zerto to failover 60 of our 175 users in New Jersey to Ohio, and they were able to work for nine months from Ohio. They were able to connect to their machines from home via Ohio, and it worked perfectly. Later, when we realized that the COVID situation would continue, we increased our internet connection to New Jersey and, using Zerto, I migrated all 60 users back. When COVID happened, Zerto saved the day. We didn't have to stop our business for a minute. It was seamless.

    We also had problems, a few times, with SQL Server. That was pretty early on in our use of Zerto, and I used Zerto to recover it from our other site. We were on SQL on the other site for a week until they figured out what was going on and fixed everything. After that, I used Zerto and migrated back to New Jersey. That was a big save.

    When I started with this company we used the Double-Take solution. It was very cumbersome and very difficult and we could only back up some servers. And when something happened, we could only have a limited number of people connect. When we started using Zerto, I was able to give every user a machine. Everybody could now log in to their machines and see all the applications, everything the same as it was before. People couldn't believe that was possible. To do it we created a fully virtualized environment.

    In addition, we are a very heavily regulated organization because we're working under SEC guidelines. We have large institutional clients like Morgan Stanley and Goldman Sachs. For them, we have to prove our resilience and our ability to work in any situation. If we cannot do that, they will pull their money out. We run DR tests and we share the test results with them. Our clients want to see them. We couldn't do that without this solution. Zerto gives us the easiest and the most reliable way to do it. When we ran DR tests before we had Zerto, it was always very difficult. It would take almost a day to bring things back. With Zerto, I can have everything back in 15 minutes. In 15 minutes everyone can connect and start to work.

    With our old solution, in a DR situation, we would need three system administrators working for hours before they got things to a point where a few people could start working again. And it took almost 24 hours to get everything back. And at the end of that time, we were exhausted. The first time we did it with Zerto, for practice, we clicked a couple of times and just sat back and watched.

    It decreases the time it takes to recover and the number of people needed to do it. We were planning to hire a person who would be dedicated to our DR solution, before Zerto, because that was the only way we had found it could be done. When we installed Zerto for a DR test, we were surprised how easy it was to do it. When we hired another system administrator, because we had grown as a company, I gave him something like a half-hour lesson on how to use Zerto and he started to use it himself.

    What is most valuable?

    The continuous data protection is very important. Even if it's synchronous, right now we are at seven seconds difference, so we practically have all our data available, always.

    Our old solution, Double-Take, required a lot of scripts and they were prone to mistakes. Zerto is so easy to use that when I showed it to my manager, he said jokingly, "Huh. I could use it myself, I don't need you." Zerto is most elegant. When I look at what's going inside Zerto, I see there is a ton of scripting but it's hidden from me. I just need to specify what I want to protect and where I want to protect it; very simple stuff. When they first brought in the solution, I saw what they were doing, how they were running all these commands, but again, I don't need to do any of that. If you do things right and you test it, it will just work with no issues at all. Nobody can come close to the elegance of Zerto.

    For how long have I used the solution?

    I have been using Zerto since 2010 or 2011. We got Zerto when it was at version 1.2. They had just started.

    I just upgraded to 9.0 U1. We ran our tests for IT a few days ago, because we made some network changes. And Zerto just worked perfectly.

    What do I think about the scalability of the solution?

    From what I understand, if instead of 15 servers you need to protect 100 servers or 2,000 servers, if you properly plan everything it doesn't matter how many servers you have. To bring back 15 servers or 115, 15 VMs for 115 VMs, there is no difference. It will take the same amount of time.

    How are customer service and support?

    Their technical support is great. When we have issues they work with us and troubleshoot until we figure out what is going on. I have no complaints. 

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

    Initially, we used Double-Take on physical servers. We had five physical servers in our data center at that time. Later, we migrated all our servers from physical to virtual, using Compellent storage at the time. We were able to replicate our storage for DR, but it took a long time because there was a lot of manual work that was not scriptable. After that we found another solution, but it also required a lot of scripting and it was pretty cumbersome. It worked but it was pretty difficult.

    Finally, Zerto came to us and we tried it. It was just day and night, a big difference between the previous solution and Zerto.

    How was the initial setup?

    If you give me two Windows Servers, it will take less than 24 hours to replicate everything and you can already run a DR test. It's really amazing.

    Initially with Zerto, every time there was an upgrade, I practically had to do everything from scratch. I had to recreate the groups and everything else. It didn't work well and I told them, "This is a big issue." In version 5, I believe, they resolved this and I could pick up my environment and restore it. When I upgraded my Zerto from version 8 to 9, it worked great and automatically. After half an hour I was running a brand new environment.

    What was our ROI?

    Every single penny we have invested in Zerto has been worth it. It has allowed us to grow our business and acquire more clients. Our clients are very happy with our DR solution. That's why they give us more money. For a company like ours, the more money we manage, the more revenue we have. From that perspective, Zerto has paid for itself 100 times.

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

    It was a little bit expensive. It took a long time for us to get DR for our workstations. It's one thing when you have 15 servers, but when we needed to bring on almost another 200 users, and each was the same price as the servers, it was too expensive. But Zerto worked with us and gave us a solution that was pretty decent in terms of price. For my company, it was a good solution.

    We bought those initial 200 licenses and we pay for maintenance every year, but it's stable. We don't have any issues. We get support, we can upgrade to a new version when we want, and they will support the changes on the ESX host.

    Which other solutions did I evaluate?

    I have looked at Commvault and HPE but I haven't found anything I like, so far, as much as Zerto.

    Initially, when we looked at some of the other solutions, before Zerto, we were thinking that we would have a special person who would constantly build scripts. But Zerto is so simple that I  don't spend much time on this side of things anymore. My manager said, "I don't need to worry if you go on vacation because I can just open the console and click 'Failover,' and that's it. Everything will be done in the background." Zerto is an incredible solution.

    It's not only about how much easier it is to install, set up, configure and, after that, run tests for DR. It also works. With previous solutions, DR tests failed a few times because they didn't work well or took too long. We would start a DR test at nine o'clock in the morning and we still couldn't bring things up until three in the afternoon. People couldn't wait that long. They hated those DR tests. Now, when we run DR tests at nine o'clock, everybody is back by 10 o'clock. We're really happy with this kind of scenario.

    When we talk to other vendors I say to them, "Okay, you want me to try your solution. Can you promise me, when it comes to DR tests or real DR, that in 15 minutes I can start to use my DR system?" They ask me, "Who gives you this ability to run in 15 minutes?" I tell them, "Zerto. I've done DR tests with Zerto for many years, and within 15 minutes we are up and running." They are surprised.

    What other advice do I have?

    The main thing to figure out before going with Zerto is, from a business point of view, what your company needs. What level of protection do you need? What regulations do you have to conform to? Can you survive with a seven-second difference in the data? Is 15 minutes enough or not?

    Also, you need to take into consideration, from the licensing perspective, not only the Zerto licenses, but that you need to have a license for ESX, vCenter, hosts, and hardware. You need to count everything before you decide to go with Zerto. In our case, we're doing private cloud, and we needed to build that private cloud first. You have to decide if that is workable for you or you're okay using Azure or some other public cloud provider. Once you work through all that, Zerto will definitely be very good for you.

    One issue we decided on, from a business perspective, was to divide our users into two groups: level one and level two. Level one users should be able to connect after 15 minutes and level-two users will be brought back after all level-one issues have been resolved, which should be within a couple of hours. When the business made that decision, we created the groups.

    We're also working with Zerto as a ransomware backup solution. Right now we are using seven-day journaling but we're putting it on external storage or cloud. We're thinking about a one-year solution where we can go back to any particular point in time, bring the server back, and get all the files. We upgraded our version so we can start to use external storage. Zerto is one of the greatest applications we have for security and vigilance.

    They did everything so well that I don't know how it can be improved. It's one of the best solutions among all the different components I have. I would rate most of the other solutions we're using between seven and nine out of 10. Only Zerto is a 10, along with my malware solution, Minerva Labs. Both companies are from Israel and I always grade both a 10 when I talk to others.

    Which deployment model are you using for this solution?

    Private Cloud
    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    PeerSpot user
    Manager of Information Services at a energy/utilities company with 51-200 employees
    Real User
    Top 10
    Good rollback capabilities, easy to use with an intuitive interface, and it has good integration with VMware
    Pros and Cons
    • "Zerto is easy to use and the interface is very intuitive."
    • "It would be nice if we were able to purchase single licenses for Zerto. As it is now, scaling requires that we purchase a multi-pack."

    What is our primary use case?

    We are an electric utility and we have some pretty critical workloads. We have identified the most critical workloads in our environment and have implemented Zerto as a protective measure for them.

    We try to keep our critical workloads protected, which are a subset of our systems. For example, we're not going to protect a print server with Zerto.

    How has it helped my organization?

    The fact that Zerto provides continuous data protection is key for us. We have tested on a regular basis, and in one case, we tested our entire ERP system. It is a pretty big workload that includes Linux servers, databases, and other components. It's about a 45-minute window to get it back up and running. For our test, we moved the entire system to our DR facility on a weekend, ran it for an entire week from the DR site, and then brought it back the following Sunday. It worked flawlessly.

    What is most valuable?

    I really like the 24-hour DVR-like rollback. For example, we had an issue a few years ago, when we still had an Exchange server on-premises. One of my staff came in for the morning to do vulnerability management, saw that some updates needed to be applied, applied the updates to the Exchange server, and it totally broke it. Everybody's email was down. To resolve things, we went to Zerto, rolled back to before the updates, and it was all done in less than five or 10 minutes. It was really quick. All of the email functionality was restored and it popped up and said, "Hey, you need an update." I said, "Please do not do that update." It was pretty good.

    Zerto is easy to use and the interface is very intuitive. We have never had an issue with using it. We just have a one-man team to perform failbacks or workloads. It is very simple to do and during our test with the Exchange server, it was only a matter of a few clicks. It's always been an excellent product and they've only improved it over time. We're really pleased with it.

    The integration with VMware is really good.

    What needs improvement?

    It would be nice if we were able to purchase single licenses for Zerto. As it is now, scaling requires that we purchase a multi-pack. It hasn't been a big deal for us but it would still be helpful to have a little bit more granularity on the license count.

    The only timeline or limiting factor, in my opinion, is how long it takes to replicate. That all depends on your infrastructure, and we happen to be pretty fortunate that we have a nice pipe in between the two locations, between here and our DR site. If you don't have that limiting factor, it's just a matter of time. You just wait long enough for it to replicate over and then you're covered.

    For how long have I used the solution?

    I have been using Zerto for approximately seven years.

    What do I think about the stability of the solution?

    We do the updates regularly and Zerto has never given us problems. We work with a lot of different technologies and we have a lot of problems, but Zerto has not been one of them.

    What do I think about the scalability of the solution?

    We haven't had much opportunity to explore scalability at this point. We're responsible for another organization's IT, as well. They're a sister company of ours and they're smaller than us, so we do all of their IT and we have them on Zerto. They're using us as a DR point.

    From an expansion perspective, we scaled up from our initial install to include theirs as well, which I think we got pretty close to doubling our license count.

    We are 100% deployed at this point. If we were ever to add another sister company, which is possible because we have other sister companies where opportunities may arise. A lot of the time, they're so small that they can't afford IT, so it's easier to have us manage it. In cases like this, we may have an opportunity to deploy Zerto.

    We have a very small team of three people, so Zerto does not affect our headcount. There is me, who is the manager of IT or manager of information services. Then, we have our desktop technician, and then we have our network administrator.

    How are customer service and technical support?

    We have never had to use Zerto's technical support for anything major. Any time that we have had to contact them, it has been for minor stuff and it's worked out fine.

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

    A long time ago, when we had an EMC SAN, there was a VMware plugin that served as a replication solution. However, it was terrible and it never worked.

    Zerto is a major upgrade that is easier to use and switching was excellent.

    Replacing our legacy solution with Zerto has definitely saved us time and improved the quality of our process. I never felt like I could trust our previous solution, which was a big deal because when you're talking about backups, trust is a major factor. You have to be able to trust your solution and feel like it's going to work in a bad situation.

    Zerto is one of those things that you love to have but you hate to have to use because it means that something bad is going on. That said, if there are serious problems then you want to have something that's rock solid. For us, that's Zerto, and we feel strongly about that.

    How was the initial setup?

    The initial setup was very straightforward. We had some training with some Zerto engineers on how to set up the recovery groups and other things, but once that was set up, we made several changes later on as we played with it. Overall, it was very straightforward to configure and I think that we only had an hour of training.

    The deployment took us a couple of weeks to get everything figured out, although it wasn't necessarily Zerto that was the hold-up. We only had a certain number of licenses, perhaps 15 in total. We spent time trying to determine which were our critical workloads, and there was some internal debate about it. From the Zerto perspective, there weren't a lot of issues.

    It didn't take a lot of time, just a couple of weeks to get us up and going. We were actually up and technically running within that same day, but to truly boot it and get it where it needed to be, it took a couple of weeks. It was a new technology to us at the time, so it took a while to get up to speed with it.

    In terms of our implementation strategy, we just tried to identify the critical workloads, find the ones that really needed to be protected and start to make those recovery groups. Then, we organized them in such a way that things worked properly. For example, the components of our ERP system do have to come up in a certain order. Finding all of that stuff out and fine-tuning the process was part of our strategy. Then, we slowly started moving those workloads across. We broke it down into groups and we did those groups one at a time until the implementation was complete.

    What about the implementation team?

    Our in-house team was responsible for implementation.

    Maintenance-wise, we just keep it updated. Our network administrator applies the updates and checks the health from time to time. We have a dashboard on our big screen if we feel the need to monitor it. If we walk by and it looks like a protection group is in the red or yellow, then we look at what needs to be done to get the problem straightened out.

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

    Price-wise, it's right in line with what we would figure. For what you get for it, it's really a good value, and we've never had any problem renewing it or anything like that.

    License-wise, we budgeted $1,000 per VM. The minimum spend on it, in the beginning, can sometimes be a little bit of a headache for people, and they might have to budget creatively to get there, but once you're there, the renewals are worth it.

    Licensing requires purchasing packages that consist of several licenses, and they cannot be purchased one at a time.

    We paid for an hour of training that we took but otherwise, there have been no costs in addition to the standard licensing fees.

    Which other solutions did I evaluate?

    We began looking at Zerto for several reasons including the cost, ease of use, and really, the flexibility of it. When you want to switch it over and do a different workload, it's not that big of a deal.

    When we first began to consider using Zerto, we had a discussion with a grocery chain that is close to us. It's a specialty grocery chain and they have exotic foods sold out of two different locations. Christmas is their busiest time of year and they have several cash registers at each location doing transactions constantly.

    They had to use Zerto during the middle of that Christmastime rush and failover, from one site to the other, all of their point of sale systems. They never lost a penny in transactions. For us, that was a big testimonial. They have a similar size of environment to ours as far as server infrastructure goes, so we didn't even look at anything else.

    What other advice do I have?

    At this time, we don't use Zerto for long-term data retention. Instead, we have some other technologies in place for that. We have Veem and we have some SAN replication and we have some network-attached storage, as well. We use Zerto as our first line of defense. For example, in response to a ransomware attack, we would use Zerto for sure to roll back before that event happened.

    We have not had a ransomware attack, at least not yet. We fully expect that, if it ever does happen, we'll definitely utilize Zerto. It is essentially our insurance policy. If we ever have a ransomware incident, that would be our first line of defense to recover from it. In fact, we really haven't had many opportunities to use Zerto, thankfully. Zerto is one of those things that are great, and we're glad we have it, but you hope we never have to use it.

    At this time, everything we do is on-premises but having DR in the cloud with Zerto is definitely something that we want to do in the future.

    It is not important to us that Zerto offers both backup and DR functionality. For backup, we have it covered in other ways. Being in the utility business, we're very big on redundancy. In fact, we have backups to cover the backups and we have about five different levels of them that we utilize. Zerto covers the front line, and when something bad happens, we can roll back within a 24-hour period using it. Then, we have deeper levels handled by other products like Veeam. Funnily enough, Veeam kept telling us that they would add Zerto-like features, and at the same time, Zerto kept telling us that they would add Veeam-like features. We continue to use both of them.

    I've recommended Zerto to several IT professionals that I've talked to because it's such a good product. I give them examples of what we have done.

    Overall, it's a fantastic product.

    I would rate this solution a ten out of ten.

    Which deployment model are you using for this solution?

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

    What is our primary use case?

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

    How has it helped my organization?

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

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

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

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

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

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

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

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

    What is most valuable?

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

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

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

    What needs improvement?

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

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

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

    For how long have I used the solution?

    We have been using Zerto for approximately five years.

    What do I think about the stability of the solution?

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

    What do I think about the scalability of the solution?

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

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

    How are customer service and technical support?

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

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

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

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

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

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

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

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

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

    How was the initial setup?

    The initial setup is very simple.

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

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

    What about the implementation team?

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

    It took approximately an hour to deploy.

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

    What was our ROI?

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

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

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

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

    Which other solutions did I evaluate?

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

    What other advice do I have?

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

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

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

    I would rate this solution an eight out of ten.

    Which deployment model are you using for this solution?

    On-premises
    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    PeerSpot user
    Raymond Rosario - PeerSpot reviewer
    Senior Network Administrator at a financial services firm with 1,001-5,000 employees
    Real User
    Top 10
    The level of disaster recovery RPO that we can now offer has been a game-changer
    Pros and Cons
    • "The near-synchronous replication is key. That has allowed us to provide the low RPOs that we promise. For key systems, that has been the deciding factor."
    • "I would like to see improvement on the Zerto Virtual Replication appliances, so that they are a little bit more streamlined as opposed to now where they just span multiple ZVR appliances like there were gremlins... as this thing grows it just spawns unlimited numbers of additional ZVR appliances and you end up with a bunch so that you can't really tell which is which."

    What is our primary use case?

    Zerto is used as our go-to disaster recovery failover software for the replication of key systems from our main office to our main data center. We primarily use it to protect VMs.

    How has it helped my organization?

    Being able to offer the level of disaster recovery RPO that we do has been a game-changer. Offering that level of RPO would have taken other methods to accomplish, but this has been straightforward.

    It has been compatible with our VMware environments as time has progressed. We started using this in 2013. To make it easy and even more seamless, they spanned a Layer 2 subnet from one site to another using networking strategies. That way, when we fail over a VM or an asset, it does not change IPs at all. It has definitely given us a level of recovery that we would not have been able to accomplish as easily otherwise.

    Recovery with Zerto is faster because, in the past, I believe our organization implemented asynchronous replication and used replication methods that were specific for storage. Having synchronous replication and an RPO that is essentially nothing, between sites, has definitely increased our response time. It allows us to immediately fail over seamlessly. It has also reduced RTOs throughout, since the recovery point objective in general is just a second. The smaller our RPO gap, the faster the RTOs we get.

    In terms of downtime, there was a particular situation where we had an unexpected double outage of our WAN link. Unbeknownst to us, both of the fiber runs, although they were from the same company, ran through the same place, along the same train tracks where there was maintenance going. We were able immediately to fail over to our secondary site and keep downtime to zero.

    That was an outage that I now know, in hindsight, lasted a couple of hours and it was during the peak closing of the US market for trading. It would have cost us millions. It would've been bad if something had gone wrong, since we needed to trade "now, now, now," but would not have been available. Thankfully we were able to trade.

    Another benefit is that it allows for automated testing and non-impactful testing with the ability to spawn VMs in a test. We can perform any type of DR and integrity testing at will without impacting our production. I can't really quantify it but I know that DR tests definitely move a lot quicker now. Normally, DR testing would happen over a weekend. And it used to be the case that we would fail over everything immediately. We still have tests where we do live failovers with Zerto, because they really want to say we have done them. But we have averted investing time in monthly and quarterly tests over a weekend because we can present the automated testing that happens by Zerto with that test network. Without that, we would have to do monthly live testing, so it saves us time.

    What is most valuable?

    The most valuable feature is its ability to do failovers from one site to another.

    It's also very intuitive, simple, and very straightforward. Its layout doesn't seem very complicated. It shows its features upfront. When I first started using it in 2016, I had not heard about the product, but coming to this company and having to take over managing it was not challenging at all. I was able to intuitively start using it. I have not had any issues with the interface. It's a clean interface and that has allowed me to intuitively use and configure it.

    The near-synchronous replication is key. That has allowed us to provide the low RPOs that we promise. For key systems, that has been the deciding factor. The other option would have been establishing VMware's native HA approach, where you have to spawn new VMs. It's not as transparent as Zerto, it's more under the woodwork. Zerto's ability to offer that level of synchronicity and immediateness has enabled us to offer that level of SLA for our processes in case of a disaster.

    What needs improvement?

    Recently, I started to try to deploy vVols instead of VMFS volumes in my VMware environment and I did encounter an incompatibility. It seems that for Zerto volumes to be protected, there's some sort of limitation with drives having to be either thick-provisioned or thin-provisioned, I forget which. But there's some sort of inherent limitation that causes an incompatibility with vVols and VMware. That has to be overcome somehow. It has to be flexible enough to be able to do its thing.

    And for an additional feature, and I'm not sure if this is already in the works, I would like to see improvement on the Zerto Virtual Replication appliances, so that they are a little bit more streamlined as opposed to now where they just span multiple ZVR appliances like there were gremlins. We have our three main ZVR appliances, each one of them associated with one of the hosts, but as this thing grows it just spawns unlimited numbers of additional ZVR appliances and you end up with a bunch so that you can't really tell which is which. Better management of those ZVR appliances would help, if you have to vMotion them off of something.

    If you want to migrate a ZVR appliance from one storage to another, you can't really tell what's what and there are multiple pieces related to this ZVR appliance. I would like to see that cleaned up a little bit with better management features for ZVR appliance maintenance overall.

    For how long have I used the solution?

    I've been with the company since May of 2016, so I've been using Zerto for that long—going on seven years. Through the years, I have become a Zerto-Certified administrator because Zerto offers a free course on it.

    What do I think about the stability of the solution?

    It's very stable and very hands-off. I have so many other things to do and the last thing I need to be doing is babysitting Zerto, and that's not the case. Thankfully, it's one of those solutions that you set and forget. You pop in every once in a while and make sure the VPGs are still green and thinking. 

    The only thing that has happened over the years is that the data store that this thing was on might have run out of space, but that was for other reasons. As long as you keep an eye on it, it will probably always be green and you'll never have to do anything.

    How are customer service and support?

    I've been able to engage with their support many times over the years and I have not had bad experiences with them. They've always been very efficient and prompt in taking me out of very sticky situations.

    How would you rate customer service and support?

    Positive

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

    We already have solutions in place for backup, such as Rubric. We used to be a Veeam shop.

    How was the initial setup?

    I wasn't involved in the initial setup.

    We have two environments, one in our main office and the other in a data center. We have virtual protection groups that protect VMs in the main office and we are able to move them from failover to the data center as a DR strategy. That will change in the future when we move all assets that currently exist in our practice office into the data center as its native location. For now, it's office and data center, but in the future it will be data center and data center.

    Our Zerto environment is VMware vSphere 7, and ESXi 7. It's mostly Windows VMs but there are some Linux VMs in there. It's a mixture of thick and thin-provisioned drives, all on VMFS data stores. Those are VMs that it protects and that it is able to move from one place to another.

    As for maintenance, Zerto is really hands-off. It's just the usual software updates and that's about it. 

    I believe the next step is that the recovery ZVMs (Zerto Virtual Managers) will turn into appliances, so they will be full Linux appliances. That will be great because we won't have to patch the Windows box underneath. Once that migration happens, it'll be even easier to manage. The only other thing that I have to do every once in a while is when we have another VM to protect. I edit the VPG and keep moving.

    What was our ROI?

    We have seen ROI due to the lack of losses from downtime that has been avoided.

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

    The pricing seems reasonable. It's still within what we consider to be value-add. Currently, we're running 50 licenses. We're probably going to downsize because there have been organizational changes in our environment and we don't protect as many VMs as we used to.

    Which other solutions did I evaluate?

    We have not looked to change over since I got here because Zerto has been that good.

    What other advice do I have?

    We don't really leverage the restore point backup capabilities of Zerto, although we do, in our virtual protection groups, configure it to have at least two hours' worth of restore points since the last RPO. We also haven't ventured toward DR in the cloud, although there will be initiatives in the future, but it's just something we have not done yet. At least for the assets we're covering with Zerto right now, we've limited ourselves to being able to pivot between data centers.

    Currently, we are using it to provide DR coverage for key assets, but I am also going to use it to move all these assets from the practice office in downtown Chicago to the data center, which will be its permanent location. I am going to leverage Zerto's move capabilities to relocate those VMs, Windows Servers, and Linux boxes to the data center permanently. And then I'll establish a recovery relationship between data centers.

    For the cost of the product, its value-add, and the return on investment, which is twofold, you should definitely consider Zerto. The hands-off approach and stability of the product alone will give additional dividends. Invest in the solution. It's pretty great.

    Zerto is a 10 out of 10 for me. It's one of the easiest pieces of software that I have to manage and one of the most reliable over the years.

    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
    Flag as inappropriate
    PeerSpot user
    Network Engineer at PRICE TRANSFER, INC
    Real User
    Allows rapid RTO and great customer support, in the simplest DR solution I have ever every deployed
    Pros and Cons
    • "The whole package is valuable. The most useful feature for the company is the rapid RTO, which offers a faster return to operations and brings us back online quicker. The last time we had an issue, we recovered within about 36 minutes, which was probably the most valuable thing for us because, previously, it took four to seven days."
    • "There are quite a few elements in the long-term retention areas that I wish were better. The bio-level recovery indexing of backups is the area I struggle with the most. That's probably because I desire to do tasks that ordinary users wouldn't do with the solution. The standard medium to large customer would probably never ask for anything like I ask for, so I think it's pretty good the way it is. I'm excited to see some of the new improvements coming in the 9.5 version. Some of the streamlines and how the product presents itself for some of the recovery features could be better."

    What is our primary use case?

    We're currently doing a two-tiered on-site and off-site replication, with one long-term retention being displaced into a cloud and one long-term retention being displaced to a third data center. We were looking to make our recovery solution more streamlined and efficient, that's why we implemented this product.

    We're not as huge as everybody else. We just have large devices. We have four SQL servers running, each of which is about six terabytes, so our continuous replication is a lot larger than others. We also have multiple secured file storages in the two-terabyte range, so we replicate around 140 terabytes continuously, utilizing about 60 VM servers. Our primary and secondary production is VMware, and our third-tier backup area is a hypervisor. 

    How has it helped my organization?

    The most significant improvement is the reduced stress of running our operation. Before deploying the solution, we had two people on-call 24/7, one on-shift and one off-shift. Now our workload has been reduced, and we only have to give support over the phone, which rarely happens.

    For this deployment, I realized the benefits very quickly. I already knew how the solution would provide a reliable safety net and offer a better risk-reward profile for our cybersecurity insurance. I knew this three deployments ago. The main selling points I presented for this deployment are the continuous replication, plus the reduction in man-hours and cybersecurity risk.

    What is most valuable?

    The whole package is valuable. The most useful feature for the company is the rapid RTO, which offers a faster return to operations and brings us back online quicker. The last time we had an issue, we recovered within about 36 minutes, which was probably the most valuable thing for us because, previously, it took four to seven days.

    I've worked with Zerto since the beginning; I think it was when we were still on version one. Having that continuous replication, as we call it, where we have just a small delta point is paramount to being able to create that multiple mine backup solution or recovery solution. It's absolutely the product's selling point. 

    Zerto is the simplest disaster recovery and data recovery solution I've ever deployed, and I've been doing this for 30-plus years. 

    We have used Zerto to protect VMs in our environment. That's the entire solution for us; it's all virtual. They can even calculate a number now, and I have 30-day testing documentation that gives them real-time data that shows a 15 to 40-minute recovery. It's astronomical because they now have a number they can guarantee to the stakeholders. 

    There isn't much comparison with other disaster recovery solutions, though it depends on the configuration. A more dramatic or complex multi-tiered recovery would expand the time, but we went from four to seven days down to under an hour. For that reason, it's almost incomparable to other solutions. Depending on the deployment, even the VMware Site Recovery Manager takes four, eight, or even 12 hours. We can bring things back online in under an hour. I don't know any other solutions that can do cross-breed virtual environments or multi-hypervisors with VMware, with different types of cloud. We can go with Microsoft Cloud, VM Cloud, or Google Cloud. It's not even a comparison. If you have a good product seller and a buy-in from your network engineer and your software engineer, it's an easy sell. 

    We currently have over 600 days of saved downtime. It's almost two years now without a single moment of downtime, because we utilized the failover to do maintenance cycles.  

    Our last collapse was when we were hit by ransomware just about two years ago. It took out 80% of our systems, and we were back online in 36 minutes. 

    I use the orchestrator for DR testing. I run a simulated test every 30 days, and we do two live tests a year. Before my arrival, they had never done a test, but that's what we do as a standard now. It only takes two members of staff, me and one other, for the entire test. It's very low-volume in terms of staff requirements.

    The solution dramatically reduced the number of staff involved in recoveries. Before my deployment of Zerto in this organization, they had one disaster recovery and had to hire 19 people to do it. When we had the ransomware attack, two of us recovered the entire solution within an hour without having to hire anyone. The previous recovery costs were around $20,000 for the staffing alone, not counting the loss of revenue. I implemented the recovery during my regular work shift.

    What needs improvement?

    There are quite a few elements in the long-term retention areas that I wish were better. The bio-level recovery indexing of backups is the area I struggle with the most. That's probably because I desire to do tasks that ordinary users wouldn't do with the solution. The standard medium to the large customer would probably never ask for anything like I ask for, so I think it's pretty good the way it is. I'm excited to see some of the new improvements coming in the 9.5 version. Some of the streamlines and how the product presents itself for some of the recovery features could be better.

    For how long have I used the solution?

    We have been using the solution for two and a half years, and I've assisted in the deployment at three other companies. I personally have close to ten years of experience with it.

    What do I think about the stability of the solution?

    I've been using Zerto for close to 10 or 11 years, and the stability is probably in the 95% to 98% range. That's pretty good, and I give it an A.

    What do I think about the scalability of the solution?

    This is the smallest solution I've ever deployed. It scales very well across multiple platforms and at a long-range. It's very scalable; I've implemented substantial deployments and deployments over huge areas. I'm impressed with the solution's scalability, especially the integration with vCloud environments.

    How are customer service and support?

    I dealt with them recently, and they're pretty solid. The process is mainly automated, they connect remotely, and I don't have to explain much as they can look at the logs. With that capability, it does work very nicely.

    How would you rate customer service and support?

    Positive

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

    I replaced the VMware Site Recovery Manager and a Symantec backup solution when I came in. I also replaced the third-tier snapshot replication, which they had never successfully tested or recovered from.

    We switched because I begged them to. I've used Zerto extensively, and the amount of fluidity and flexibility it offers is necessary. It gives me peace of mind and allows me to sleep well at night knowing it will be alright, which is uncommon in this business. I said as much to the company and was able to convince them within about six months.

    I used Veeam and some other bare-metal backup solutions before. Since virtual servers have been in place, Veeam and SRM are pretty much the two standards, with Symantec being the tape backup solution or virtual hard drive backup solution. Since Zerto came around and I saw what the product could do, it's all I ever push for when I get called in for a company that needs a DR plan.

    How was the initial setup?

    I designed it all and already knew what I wanted to accomplish and what the product could do. Once we knew what direction we were going in and where the critical applications aligned, it was just a point of picking things up and putting them into placeholders already in the required image I designed for our purposes. It was pretty easy. It might take a little longer without prior experience and an idea of what I want to accomplish. It would still be pretty easy as Zerto provides excellent documentation. This is one of the most straightforward designs out there. End-to-end, with testing and approvals at each step, I think it took two and a half weeks.

    What about the implementation team?

    I implemented the solution on my own.

    What was our ROI?

    I can't give an exact figure, but I would say that protection from Ransomware tech alone paid for the initial startup process and most of the maintenance needed. 

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

    I wouldn't say I like the licensing pricing structure. Every year, it increases exponentially, which bothers me a little. It's worth it in terms of the value, but I worry the price will increase even more often after the Zerto merger. I still think it's worth it and that the solution is cheaper than the others. 

    Which other solutions did I evaluate?

    We evaluated Symantec, and NetApp, and we brought in Veeam.

    The main differences between Zerto and the other solutions are the continuous replication capabilities and the ability to have two continuous replications simultaneously. These were major selling points for the company. With snap replication from NetApp or even Veeam, there isn't that consistency between multiple divisions. I showed the company we don't have to have VMware at the low MBR; we can have a hypervisor at a much-reduced cost, as the price was the last hope for the other solutions. 

    What other advice do I have?

    I would rate this solution an eight out of ten. I don't give anybody a ten, as nobody is perfect. The best score I give is an eight, and they get that.

    We don't necessarily use Zerto for immutable data copies as it's never been a requirement. I know it's there and what we can do with it if we need to.

    We only use the physical solution because of the nature of our business, but we do long-term retention in the cloud. It is nice to have that long-term cloud retention, as it gives us another tier of data available for worst-case scenarios. 

    I wanted to replace our legacy solutions, but we still have old-school solutions for legacy data recovery. We use Symantec for backup exec. on our bare metal, but I don't think it's critical because it's more for our legacy data recovery. After all, we're not like most companies. We have to keep our data for 24 years. 

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