Zerto Reviews

We use Zerto for disaster recovery as a service and site-to-site migrations. 

Zerto enables us to do sandboxing failovers. You can run tests on a production environment in a sandbox and spin up a copy of your actual production environment in a few hours. When you're done with it, you can click a couple of buttons, and it's all blown away. You don't need to worry about reverting changes or interfering with your on-prem production environments.

The most valuable feature is the overview Zerto gives you, providing quick insights into where your VMs are and whether they're replicating. It's an easy interface to work with. Configuring Zerto to failover in Azure is pretty simple. The biggest challenge is moving from on-prem to the cloud, but that's not an issue with Zerto. The problem is the difference in hypervisors.

I would like to see some improvements with APIs going into the cloud so that they can more natively orchestrate the migration point-to-point without special hands-on configuration. Azure does some of that natively by having an agent on the VM, but Zerto could improve on its APIs into Azure or Google so that spinning up works more natively in that environment. It would make things smoother. 

I've been using Zerto for about a year now.

I haven't faced any stability issues. The only problems I've had have been self-inflicted, so it's pretty good.

Zerto's scalability seems pretty robust. I've had a few larger VMs that have been a little troublesome in terms of the RTO, but they are also outside of best practices. There should be no issues with scalability if you're working within the defined parameters of what's acceptable.

I rate Zerto support nine out of 10. I've used their support pretty extensively. I would say the majority of the experiences have been overwhelmingly positive. Their response times and issue resolutions are satisfactory.  

One thing I would change about Zerto support is the fact that you sometimes can't find the answer you need online. Sometimes, Zerto reaches out with an answer to that particular issue, and it's in a document that the customers can't access without going through support. It doesn't feel like that information should be limited to internal use. I should be able to find that online without going through a support channel. 

Positive

I've also used Azure's native Azure Site Recovery solution, and there are definitely some benefits to using Zerto, such as the fact that it works at a hypervisor host level over individual VMs with agents. The performance is probably a little better in most cases. 

Zerto is easier to use than ASR overall, but the setup is a little bit more involved. After the installation, the daily use is pretty simple compared to Azure. With Azure's native solution, there's a lot more that you must do repeatedly throughout the lifecycle of any virtual machine or system that you're trying to protect. Zerto is much simpler in that regard.

The on-prem deployment is super easy and works well. Migrating from on-prem to the cloud involves a lot more steps and things you have to configure so that it can communicate into the cloud and build everything that it needs to. That takes more time. It probably requires twice as much time to deploy on the cloud. 

We see the biggest ROI from Zerto's real-time test environment. If we want to do a proof of concept on a hundred servers, we can spin them up within a few hours and have them ready to start testing stuff with real data to see how that might look if we were to deploy that into production. It's an excellent, accurate test environment that we don't need to maintain.

Zerto's pricing is competitive, given the benefits and ease of setting it up. It may seem more expensive upfront, but you're going to save that over the long term by spending less engineering time configuring, reconfiguring, etc.

I rate Zerto nine out of ten.

We utilize Zerto for our disaster recovery solution, which involves replicating our virtual machines to a remote hot site to ensure failover capabilities.

Zerto's near-synchronous replication is great. 

Our RPO is around ten seconds.

I found Zerto's dashboard and features, such as the Zerto console, easy to use. It is simple to navigate and comprehend. Additionally, it is convenient to check various RPOs and BPG groups to stay informed about the current status.

We now have a robust disaster plan in place since the implementation of Zerto, which was a significant aspect we aimed to ensure.

Syncing data over to the data center for disaster recovery is easy.

I cannot provide a specific answer regarding our RTOs, but they have definitely improved significantly compared to our previous practices.

Zerto is considerably faster than our previous disaster recovery testing, which has saved us a significant amount of time.

Zerto has reduced the number of resources required for our data recovery.

It has helped reduce the number of staff for our backup.

We are utilizing a third-party company to assist us in managing Zerto. However, the RPO time for the copied-off VMs appears to be quite short. Additionally, it is straightforward to use.

One concern we have is the speed at which Zerto maintains compatibility with VMware and different versions of VMware. We are specifically worried about potentially major security issues with our current ESXi version and whether upgrading it would cause any problems or compatibility issues with the Zerto version we are using. It is crucial for Zerto to collaborate closely with VMware in order to promptly test updates.

I have been using Zerto for six months.

Zerto is stable. We have not had any stability issues.

We have not used Zerto in the cloud, but on our ESXi host, it appears to be scalable.

We used to back up VMs to powered-off off-site storage, but Zerto provides live disaster recovery capabilities. We had been utilizing a different disaster recovery concept, but Zerto is easier to use and provides us with an improved turnaround time in the event of a disaster.

The initial setup was straightforward. I assisted in the deployment, and a total of four people were required. The deployment took one week due to the necessary networking changes that had to be made.

We implemented using a third party.

I give Zerto a ten out of ten.

We utilize Zerto for our disaster recovery, and we employ our storage appliance for local snapshots.

No maintenance is required for Zerto.

I suggest using Zerto to have the servers in different Virtual Protection Groups so that they can prioritize the most important aspects of the business.

Our main use case for this solution is disaster recovery, migration and app testing.

Zerto helped to reduce downtime. I worked a lot in a consulting capacity and experienced DR situations where XYZ was down or a data center was down. Using Zerto to get them back up and online was a lifesaver.

Zerto reduced the staff involved in data recovery. It's a tool that allows you to do a lot just with one person at the console.

The most valuable feature of this solution is the live migration. 

This solution could be improved by being more cloud agnostic. 

I have been using this solution for eight years.

This is a very stable product. I've never heard anybody complain about its stability. I would say it's probably one of the best out there.

This is a scalable solution. 

The technical support for this solution is good and their staff are knowledgeable and able to assist quickly with resolutions. 

I would rate them a nine out of ten. 

Positive

I've used several other products including Site Recovery Manager. Zerto is the easiest to learn. There is much less of a learning curve. Other tools specific to VMware are now trying to emulate what Zerto has done to make processes easier. Zerto was a huge step in making things more simple to manage. The app works really well and integrates with VMware really well. 

The initial setup is straightforward, especially if those setting it up understand the company's infrastructure. The problems are not directly related to Zerto itself. They're always related to how the infrastructure is set up or how the network itself is segmented and having certain people that have control or access and others that don't.

The return on investment is in the ease and functionality of the tool as opposed to actually a gain from using the tool.

There may be less expensive solutions on the market but with Zerto, you get what you pay for. A lot of people don't like to think about the price until it's already happened and then the price is too high because they would be losing either way. It's better to think about it and pay for it upfront than pay for it after the problem.

We previously used and considered Site Recovery Manager.

I would rate this solution a nine out of ten. 

Its primary use case is for disaster recovery of 10 servers that we have in-house.

The testing of failover and failback is critical to any company, especially if they're certified in some platform like we are with ISO 27001. It is a necessity, and one of the main reasons I purchased Zerto.

Live replication and up to the second type of failover are valuable. The fact that we can do test failovers and failbacks is important for our ISO certification.

More user support would be best for me because I'm not in the product all the time. So, having strong support is probably the most important decision on any products that we buy.

The price is another thing that they definitely need to work on unless it has changed. I purchased mine a while back. 

When it is up and running, it is just always running, but because we're changing our infrastructure, basically, everything has to be destroyed and rebuilt.

I know it is scalable with the backup solution. I don't understand why that wasn't there early on, but it is neat that they've added that functionality in there.

It has been a long time since I've worked with them. So, I would rate them a 7 out of 10.

It is rare that I have to contact them. We are in the process of redoing our VMware infrastructure. We have to reinstall the whole product, which we haven't done for a long time. So, I'm not that familiar, and we're probably going to have to pay for services where I would like that to be handled by support to help us.

Neutral

It has been quite a while, but we used to use Double-Take to replicate some servers between offices. Zerto is much better at doing that functionality, and that's why we switched. 

The ease of use is definitely better with Zerto. The data recovery with Zerto is very fast. You just push buttons for recovery and flip back.

The initial setup was straightforward, but I had a team, probably from Zerto and not the consultant, that helped us with the installation. So, I had somebody right there holding my hand, and it was very easy to do.

That's hard to say because we haven't had a catastrophe. If we have a failure, hands down, I can't complain about that, but we haven't had any incidents.

Even though there is a fast speed of recovery and ease of use, I haven't measured the time savings and resource savings with Zerto. That's analytics, and we're not that detailed. We're user support focused.

It is very expensive. It is overpriced. No doubt. What held us up for many years from committing to buying it was always the cost. That's also why we only have 10 licenses.

We probably looked at other solutions, but I don't recall what they were at this time.

I know that they have a backup now, which they didn't have when I purchased originally, but we don't use that today. It may be something we'll look into. 

The solution is great. I'd rate it a 10 out of 10.

We use it primarily for backup and recovery of individual servers and databases. We also use it for long-term retention.

It helps us

• achieve our RPOs
• conduct successful DR tests
• provide functionality for some of our key, critical customers.

Fortunately, we haven't gone through an unplanned DR situation, but if we were to go into one Zerto would be the top technology that we would use to recover. We would expect it to function as designed to get everything back to working as normal. Otherwise, obviously, it would be a big problem for our company. Zerto is a critical, core piece of infrastructure for the IT infrastructure team. I estimate it would save us hundreds of thousands of dollars in a DR situation.

In addition, when we need to fail back or move workloads, Zerto decreases the time involved. It's hard to quantify how much time it would save us because we haven't compared it to other DR products. But if we were to use our in-house data protection backup solution or our storage solution, Zerto would save weeks of man-hours when it comes to setup, compared to those other solutions. And it could save minutes in terms of the recovery point objectives.

The instant recovery at DR locations is the most valuable feature. We're required to do periodic DR tests of critical databases, including Oracle and Microsoft SQL. We have recovery point objectives set for specific databases and we need to be able to achieve them. Zerto helps solve that business problem.

Zerto is also pretty simple and straightforward when it comes to ease of use. There were no big surprises.

I would like the ability to monitor the performance of some specific components. Right now we're having an issue with local and remote replications with some of the VPGs. Being able to look at individual VPG performance would be helpful. 

Another thing that would help would be a recommender, or some type of tool that says, "Hey, you're not conforming to best practices." It would do a conformance or compliance check to tell you if your VPGs are set up according to best practices and whether your Zerto clusters are set up optimally. It would see if you have HA enabled and whether your alerting is turned on.

Another area for improvement is alerts. We're getting so much noise right now in the 8.5 version. The problem is that we don't know which are the ones we need to act on. We don't know which ones are severe versus those that are informational or notice or debug. They have told us that when we upgrade to version 9 we'll be able to tune some of the alerts. That type of alert tuning, where we can get just the emergency and error alerts, would be helpful, while not necessarily tuning out the informational or notice or debug alerts. If alerts could be channeled to a syslog server where we could filter and see which alerts are the priority that would be an improvement.

We have a network operation center and for us to operationalize this tool with them, we have to be able to deliver each alert along with an action plan for it. That way they can take the appropriate action if Zerto has some type of error. It would help if the alerts didn't just fall on our storage and data protection team. If we could transfer some knowledge and have other level-one teams look at some of the more basic Zerto alerts and try to resolve them, that would help.

I've known about Zerto for several years but I've been actively using it for the last two months.

The stability is pretty good. I haven't seen the software itself break, or the services stop for unknown reasons. 

We did have an issue with a VPG the other day, where it went belly-up, and we had to rethink and do a bunch of baselines. So some type of health monitor that shows both the servers and the VPGs would be helpful.

I haven't worked with the scaling functionality because we only have it in our two major data centers. But I think it would be pretty straightforward and simple to set up scaling.

Currently we're protecting about one petabyte with Zerto. We have some room to grow still with Zerto.

Much like with any technical support—and this is true whether you're talking about IBM, Microsoft, Dell EMC, or any of the big tech players—their level-two guys are definitely good, if you can get one of them. But the level-one guys seem not to be as good. Zerto was acquired by Hewlett Packard Enterprise and it shows with their level-one guys. They're not as vested in the product. All the level-one people who were vested in the product probably left. So a lot of the level-one guys aren't very technical. 

We oftentimes have to work with our technical account manager to get cases moved up to level two. Once they're there, they seem to get some movement, which is good. And, obviously, their level-two support team in Israel is very good.

Positive

I was not part of the initial installation, but I've heard that some of the initial pieces are straightforward. Where it gets complex is that I don't know if it was set up according to their best practices.

The pricing follows normal industry standards.

In a previous company, I was involved in the evaluation process that ended with choosing to go with Zerto.

Zerto sits on top of a lot of other technologies. It's like a "Layer 3" for lack of a better term. Some of the other solutions that are "Layer 2" can be more attractive, solutions like Commvault, Rubrik, and Cohesity. They're able to do more native operations at the OS level, like replication. They have more hooks into the operating system to enable you to do that.

However, Zerto's user interface is good. It's simple, it's straightforward, and it gives you the RPOs and RTOs right then and there. It requires some administration from the VPG perspective, but it's able to bridge a lot of gaps.

My advice would be to work with your Zerto technical account manager for the setup and best practices.

Zerto is good when it comes to continuous data protection. We're currently in the middle of some technical support cases with them, cases that I'm watching, regarding some of our larger databases. But so far, there have been no issues with the smaller databases. It's doing its job.

We haven't yet enabled Zerto to do DR in the cloud, but that's something we are pursuing currently. We have had a demo of it but we haven't done a PoC.

Our primary use case is for our Tier 1 application environment, we're an SQL environment. We have around 25 VMs that are replicated to a hot site or warm site. And we're a VMware shop and we use Pure Storage as our SAN, but that doesn't matter because Zerto's agnostic. 

We're a small shop. I am the only Zerto user and my official title is Senior Systems Engineer. I handle anything data center-related as far as information stack, the blades, networking, VMware Hypervisor, and Pure Storage. We also have a Citrix environment as well we have to support. I do all of the data center work.

Zerto is a set it and forget it kind of thing. At least it's more of an insurance policy for us. We don't have a good DR plan, but the peace of mind knowing that the data is replicated off-site, like a repository or offsite environment, there is value to that. We just haven't been able to fully embrace the actual testing of the failover and failback process. The testing has worked, but we haven't done a full production failover yet. We've been planning for around a year to do one but it keeps getting pushed back.

Being hardware agnostic is nice in that we don't really need a 15 second recovery time. It's easy to use. It's always doing updates behind the scenes. These are the positive things. The setup is pretty easy. Building out the VPGs is pretty easy. And it works like it's supposed to.

Zerto does what it says it will do when it comes to providing continuous data protection. It gives me all my recovery points up to 15 seconds or less. So if need be, we could recover to that point in time that it says it can do.

Zerto is easy to use for the most part. It's pretty simplistic. The UI is pretty simplistic. There are some things that I'm waiting for newer releases to address some functionality that I'm curious to see has been fixed or not in the new version.

There are still some pieces in testing that aren't automated. There are still some built-in scripts or workflows I wish Zerto would do out-of-the-box, versus having to PowerShell or have a vendor create it, or create it myself. We haven't done a full failback yet of production so I couldn't really say. The failover process is a lot of manual steps, but Zerto is a mechanism that gets the data there. In that aspect, it does what it's supposed to do. But I wish they would expand on their out-of-the-box functionality for the VM. When you fail it over, there are DNS and SQL changes and there are reboots. There are some things I wish that Zerto would facilitate with a checkbox that would do some of these things for me versus having to PowerShell it and put the scripts in a certain place and have support run it. I want it more automated if possible.

The issue I have with ransomware is if I don't know I have ransomware in all my recovery points, and if it goes three months, I wish Zerto somehow either bought a company or could tell me that we're infected with ransomware. If I don't know how ransomware and everything gets encrypted, there's nothing to restore back to if all my recovery points have been corrupted. So I wish Zerto somehow had a mechanism to alert me of suspicious activity.

We have a Trend product that does that for us. We can get alerts of things that Trend finds, but it's always nice to have layers for your security. We have alternatives, but it would be nice if Zerto had a mechanism to alert me as well.

Alerting has also been a pain but it was supposed to be fixed in the newer version and that's. I would like to have more granular alerts.

I have been using Zerto for about four years now. 

When it comes to stability, it does what it says it's going to do. 

I do some babysitting because the alerts are relentless. My biggest pain point is the endless amount of alerts that are just noise. I have to log in and see what actually is an issue because the alerts are just endless. There's not much maintenance I have to do besides logging in and babysitting from time to time.

We keep wanting to test it. It's our main DR strategy, but we just haven't had a window to vet full failover and failback. As far as increasing, I think we're pretty stagnant at the point with what we're backing up with it.

I would rate Zerto support a seven out of ten. 

The initial setup was straightforward. You could deploy the VRAs pretty simplistically as long as you set an IP via the UI, so that was pretty easy. We were up and running in a day.

Our implementation strategy was rushed. We were doing a data center move and we just wanted an extra copy of the data. So this was a stop-gap solution that we stuck with.

We used a reseller for the deployment. They met our expectations. They provide the product, but outside the product, we have to get a stronger resource. If it goes above and beyond like if it's broken, they call Zerto support. If I want some PowerShell scripts and some cool stuff to be done, they need to find a resource. They provide the basic service, which is great. Above and beyond that, they're average or below average.

We pay monthly for the CPU, memory, disk space, the Zerto replication, and then there's a Microsoft charge as well on top of that for the operating system. We pay month to month and we go year to year.

There are additional VM resource costs.

My advice would be to think about the large VMs that you're backing up. Think about the wasted disk space and wasted resources on your production environment, and if you replicate that to a hot or warm site, you have to pay for those resources. The Zerto price is what it is, so you need to work with the business and ensure your Tier 1 or most critical VMs are what you're backing up or want to back up, not just everything. Then scale that to something manageable for replication and find out if you can have minimum resources while replicating and then scale up in a true DR scenario and only pay for the resources as you need them.

It's not really Zerto's fault, but you don't have full visibility on the protected site so you have to rely on your vendor for visibility if an issue arises.

I would advise asking a lot of questions. If you're an SQL environment, make sure you failover all the key components in the correct way. If you want it fully automated, make sure you buy some extra hours to get professional support.

I would rate Zerto an eight out of ten. 

We needed Zerto in order to provide a disaster recovery solution for the entire organization. We use it to replicate some resources on-prem and for quick recovery. We also use Azure to replicate for disaster. If we ever have a catastrophic failure or attack at our main headquarters, we could failover and run our resources in Azure. 

We don't use Zerto for backup, we use Veeam. Once the new long-term retention features are added to Zerto, then we will investigate using it for that and possibly dropping Veeam.

There wasn't anything in place that compares to what we're getting from Zerto. Before Zerto, we didn't have a proper disaster recovery program or application in place. We had a simple backup solution where we could back up our data every 24 hours. So we went from that to being able to recover full systems within a matter of minutes. With Zerto, if we do have an event or disaster, we know that we can recover from that much quicker than we were able to before.

We use Veeam Backup for data and not for replication so this is purely just for disaster recovery and replication. We don't use it for data backup, we're still using Veeam for that.

Zerto definitely decreases the time and people it takes when we need to failback or move workloads. The benefit of using it with the Cloud is that we don't have to maintain extra hard work or an extra infrastructure for disaster recovery. With Zerto and Azure, it can all be done essentially by one person. If we're restoring data and systems from the cloud, it can all be controlled from the Zerto interface, whether it's on-premise or in the Cloud. To move the data back, depending on the size of the disaster, if we were to have to rebuild our hardware on-premise, that would obviously require more people. But if it's just a matter of restoring data from the Cloud, it would only need one person. Whereas before, you could probably still do it with one person, but the amount of time that would take would be a lot longer. We would have had to rebuild servers to restore the data. With Zerto, we can restore entire servers from our Cloud repository and have them up and running, it would just be dependent on the speed of the internet. Zerto could easily save us days of time.

It saves us time in data recovery situations due to ransomware. If we had a ransomware attack, we could have our systems available for investigation and run our environment entirely in Azure, separate from our on-prem network. With Zerto as well, we could also recover our systems to the point in time before the ransomware attack happened, ensuring that it doesn't happen again. With our resources in the Cloud, we can scan it for infections and pull it out if it's been lying dormant. The big benefit against ransomware is that we can easily just go back in time to the point before the attack.

The ability to do DR in the Cloud rather than in a physical data center has enabled us to save money. It has saved us quite a bit of money by utilizing Cloud resources, instead of buying a whole new recovery site on-premise. We did an analysis of the buy and one of the reasons why we went with Zerto on Azure is because of the amount of money that we would save over a five-year period. Based on our analysis, it saved us roughly $25,000 a year.

The one-click failover feature is very valuable because of the ease of use as well as the little to no data loss with the constant replication in journaling technologies that it has.

The one-click failover feature is really valuable to us because we need a solution that's easy to use. There's the potential that myself or other staff may not be available at the point of the disaster and it would be possible to have somebody who may not know the technology be able to initiate a failover on our behalf by simply just asking them to click a button.

The important features of having little to no loss of data are extra valuable because if we do have a failover event or an event where we need to initiate a failover for disaster, having no data loss is really important because if we were to have a disaster where we needed to initiate the failover for recovery, and if there was data loss, that's lost time from staff. It's also really hard to tell what data is lost and what has to be made up. We have certain resources here that can't afford any sort of downtime or loss of data.

Its journaling technologies are always sending replicated data up so that we can view what the recovery point objectives would be in real-time. We can see it could be a matter of six seconds to a couple of minutes, and that gives us peace of mind that things are moving constantly so that when we do have a failure, we can go back to pretty much any point in time that we want and have our systems available again.

Zerto is very easy to use, the interface makes it really easy. The wizards that are available, the how-to guides, and the support from Zerto has made it really easy to use. With little to no training, we were able to get it up and running in the test environment in under a day. The interface makes it really easy to use from using it from day to day, setting up new jobs for replications, or even restoring data.

Long-term retention of files is a function that isn't available yet that I'm looking forward to them providing. The long-term retention is the only other thing that I think needs improvement.

We have been using Zerto for around nine months. 

Zerto is very stable, we have not had any issues with it so far.

Scalability is fantastic. It can go from a very small number of machines up to a very large number of machines without any issue. We started small and they included more and more to it and I haven't had any issues. We have not had any problems scaling across sites to other sites within the organization and integrating it all together. It's as advertised that it can be in any environment of any size. It scales very well.

Only one or two people are required for the maintenance of this solution. As the manager of technology and infrastructure, I and the system administrators do the maintenance. I mostly work with it. One of my other staff works with it from time to time, but for the most part, it just does its thing and we don't really need to do a whole lot with it.

Zerto is used extensively in my company in the sense that it is our primary disaster recovery solution. It is used for servers throughout the County for all departments. Every system that we have in place relies on Zerto for DR. As servers increase, we will add those servers to Zerto, for disaster recovery purposes. It's completely integrated into our system.

Zerto hasn't reduced the number of staff involved in overall backup and DR management only because we have a small team to begin with. Our infrastructure team that I'm in charge of is only six staff. So DR and backup is one job amongst many, for all the staff here. The amount of time dedicated hasn't changed a whole lot for us.

Their support is fantastic. Anytime we've had an issue, which has been not too many, they've been very good to resolve any issues.

We also use Veeam and it is really easy to use too. They're both easy programs to use. If anyone can use Veeam, they can use Zerto. I wouldn't say Zerto's any easier or Veeam's any harder. They do different things; Veeam does back up really well. If you need a backup solution, Veeam is far cheaper. Whereas Zerto is fantastic at disaster recovery and replication, but when it comes to backup, that's not really what it's made for. Moving forward that may change. But Zerto is definitely a much costlier program compared to Veeam but it does a lot more.

Zerto itself was straightforward to set up. There was good documentation available and we utilized some of their engineering services to help set up as well. For the size of the products and the complexity that it can do, the actual setup and operations over this are quite easy. It took a couple of days, which included getting everything in Azure set up properly.

The implementation strategy that we did was to create the on-premise environment for a dedicated network, virtual machines, and the installation. Then Azure would become our disaster recovery site in the event that we needed it if we had a disaster on-premise, we could failover all of our services and servers that we needed to in Azure. Then our client computers would connect to them while in the Cloud while be prepared for recovery on-premise.

We utilized a third-party consultant to assist with setting up our Azure environments and Zerto technicians helped us set up Zerto on Azure. Our experience was really good. There were some challenges and there was lots of learning to do, but overall, the experience was good. The staff from Zerto were exceptionally good. They really know the product well, helped quite a bit, and provided instructions and training on how to use it outside of that.

I think that return on investment will come in the event that we do have a disaster that we need to recover from. We have seen some ROI from Zerto by moving virtual machines between data centers, where that has saved us a lot of time. The technology not only is useful for disaster recovery, but also for server maintenance and moving resources between posts and impairments. Before, it could take hours to copy virtual machines, even days. We use Zerto to move resources around with little to no downtime in a lot quicker time. So we were able to save staff time and resources by using Zerto.

It wouldn't have cost us too much with the government. It's hard to equate a lot of downtime to dollars and cents for us because it's more so around staff time and convenience. We have long-term care homes that we need that are up all the time. And any of those maintenance windows we usually schedule after hours. So it's more of an inconvenience for IT staff to work overnight instead of during regular business hours.

Zerto is not cheap; however, it is worth the cost. The licensing model is easy. You buy based on the amount of virtual machines you want to protect and go from there. Even though it is not a cheap program, you do get what you pay for, but overall it became cheaper than maintaining a separate data center.

We looked at Cohesity, Rubrik, and Commvault. Veeam does replication as well, but it doesn't do it nearly as well. We looked at a few other solutions from Dell. We went with Zerto because it had all the disaster recovery functions that we needed, the ability to recover within minutes with minimal to no data loss, and is integrated well with Azure.

I would recommend doing the free proof of concept exercise with Zerto pre-sales engineers and work with them to discuss your environment and then review their recommendations on implementation. From time to time do the free training. I highly recommend doing that. Get your hands on this software and try it out first before doing the production implementation.

The biggest lesson I have learned is that disaster recovery doesn't have to be hard.

I would rate Zerto a ten out of ten. I don't rate many things ten, but Zerto offered me exactly what they're upfront with, what it will do, and it's doing exactly what they said it would do.

We use Zerto for replication.

We implemented Zerto to help with the high bandwidth required for the live application replication.

In my minimal experience with Zerto, the near synchronization replication is good.

Zerto does a good job of blocking unknown threats and attacks.

Its easy-to-use application server has helped our organization improve its bandwidth.

Zerto has made disaster recovery in the cloud much easier for us than in physical data centers.

We've seen significantly faster recovery times compared to other recovery tools we've used, like Carbonite.

Zerto makes it much easier for us to conduct and manage our DR testing.

The replication feature ensures minimal downtime during disaster scenarios.

Zerto's failback capability automatically recovered one of our live applications after it disconnected.

Zerto helps us monitor our disaster recovery.

Zerto's user-friendliness is valuable. It's easy to use.

It would be great if Zerto could automate replication more.

I have been using Zerto for four months. I joined the company when they were already using it.

I would rate the stability of Zerto ten out of ten.

The technical support is good.

Positive

I also use Carbonite but Zerto offers faster speeds.

The deployment of Zerto took a few weeks.

I would rate Zerto nine out of ten.

We have over 300 clients using our web applications.