Zerto Reviews

We use it for our conversion from Hyper-V to VMware. The DR purposes are being looked into as well.

We've got about 1500 to 2000 Hyper-V machines. These Hyper-V machines are used and converted to VMware, and these are the two environments that we work with now, both on-premises and in a hosted environment.

The ease of the conversion, moving from Hyper-V over to VMware, has been the most valuable feature. It's the primary reason why we chose Zerto.

We've seen a massive benefit from using Zerto in terms of time savings and consistency. You see a consistent outcome every time you do the conversions. We're moving from one platform to another, but the payloads in what we're moving are different. We see consistent delivery.

Time savings-wise, I see anywhere from 30 to 50 VMs be converted from Hyper-V to VMware on a nightly basis. We've seen some pretty good throughput on the nights that we do conversions.

Zerto has absolutely helped to reduce downtime. If we were to do this manually, the amount of time that we would have to shut down the VMs on Hyper-V to be able to do the conversions and move them over to VMware would be massive.

That amount of downtime would cost our company a lot. We've got a team of three or four guys that do the labor. If you take what they're getting paid and you compound the amount of time that it would take to do the conversion, there would be a drastic cost in labor for those conversions.

Right now, our production environment runs on-premises, and we have a DR copy of everything that we run in production. However, our development runs on that hardware. In the case of a DR event, we would need to shut down development and bring up our secondary copy of production. We're hoping that Zerto is going to be the tool to help us do that.

Zerto is primarily being used this year.

We're getting consistent results, so the product seems to be very stable.

From a DR perspective, we use multiple different facets. We have multi-site data centers in our environment, along with Cohesity. We use Cohesity from a backup and DR perspective.

I was not involved in the initial setup but have heard feedback that those involved loved the simplicity of it.

We've absolutely seen an ROI in terms of time savings with respect to downtime. When you convert a couple of thousand machines from one platform to another, the amount of downtime that it would take itself would have paid for Zerto many times over.

We get our money's worth with Zerto.

If you're in the middle of a conversion between different platforms, regardless of whether you're moving from on-premises to hosted or from one environment to another, it seems to be very agile and able to move your workloads into different environments pretty easily. I would give Zerto a rating of nine out of ten.

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.

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.

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.

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.

We are in our seventh year of using Zerto.

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.

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.

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

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. 

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.

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. 

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.

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.

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.

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.

We use Zerto for disaster recovery of our tier 1 applications from our primary data center to our secondary data center. We have also used Zerto to successfully perform server migrations from one site to another for data center moves and company acquisitions.

Our administrators love the product and it has been proven to be easier to use than VMware SRM which we were using before going with Zerto.

Zerto has given us the peace of mind to know that we have full DR protection for our critical applications.

Zerto is relatively easy to set up and administer.

We were able to create runbooks within Zerto to help with DR failovers, and testing DR failovers is pretty easy as well.

We used to use VMware SRM and it was very cumbersome to add in new virtual machines or storage volumes because they would basically "break" the SRM protection groups that were already out there. With Zerto, it takes on new additions to protection groups much easier and it saves our admins a lot of time having to care and feed it.

The most valuable feature of Zerto is its overall flexibility, where it can be used for standard DR or you can also use it for server migrations, data center consolidations, etc. You can also use it for data protection and physical to virtual migrations as well.

It is kind of a swiss-army knife.

I can't think of any major areas of improvement with Zerto. Make sure that they are building in cloud-friendly features in future releases because a lot of enterprises are starting to move workloads to the cloud and are seriously considering doing DR to the cloud as well. Our company may be moving in that direction also.

I wouldn't mind seeing Zerto sold at a cheaper price point, although the cost is comparable to VMware SRM.

We have been using Zerto for four Years.

Zerto has been rock solid for us in terms of stability.

The scalability of Zerto seems to be ok. This will depend on the size of your environment and how often you need your data replicated for BCP and SLAs.

Zerto customer service has been great so far. No complaints!

We used to use VMware SRM and we switched to Zerto because it is less expensive and easier to administer.

The initial setup of Zerto was very straight forward. The rest of the configuration will be as complex as your environment's DR needs and application stacks are.

We had an engineer from Zerto help us with the installation and initial configuration for thirty days.

It is good to do a full Disaster Recovery plan for your organization and doing a BCP plan as well. You need to figure out how many critical servers and applications you have in your environment so you will know how many Zerto licenses to buy, etc.

We only baked off VMware SRM and Zerto.

It is good to implement a proof of concept of Zerto to test it out. I highly recommend it for data center moves.

We use it for disaster recovery and analytics.

We use Zerto to help protect VMs in our environment. We are also using it for our Virtual Protected Group or VPG.

By implementing Zerto, we wanted disaster management, especially for our data. We did not want to lose data unnecessarily.

Over time, I keep seeing different benefits of using Zerto.

In terms of ease of use, Zerto is easy to use.

Zerto has near synchronous replication. It is okay. It has been easy for me to use.

Zerto is faster than other recovery solutions for real-time automation.

Zerto makes it easy for me to navigate and move my data to the cloud. It has had a positive effect.

Zerto has helped reduce downtime. There is about 25% reduction.

Zerto has improved the data recovery time. It has saved me time. It is faster than what I was using before. Zerto has saved me a lot of time, but I do not have the metrics.

Zerto has helped reduce our organization's DR testing by 30%. It has had a positive effect on our IT resilience.

I like the automation of transferring data in the case of any disaster to our VMs. It is also easy to use and fast. 

Its price is a little bit on the higher side. Other than the pricing, I do not have any areas for improvement. I am enjoying Zerto. Everything is working the way I want it.

I have been using Zerto for the past two years.

Its stability is okay.

Its scalability is okay. As we keep having more customers, we might have to scale it, but for now, it is good.

I contacted them once, and I got a quick response. They are fast. I wrote to them, and I quickly got a response. The response was timely and effective.

Positive

I was using Microsoft Azure backup before. I migrated to Zerto. Zerto is faster.

It is deployed in the cloud. Its deployment was not too easy and also not difficult.

Like every other team, it took us some time to get it going. It is not as easy as one, two, and three. It took us about one hour to get it going. That is why it is not too easy, but it is also not difficult.

After installation, we took the entire day because we were trying to make sure everything worked fine.

So far, I have not done any maintenance for Zerto.

We had two people involved in its deployment.

Zerto is a little bit on the higher side in terms of pricing. It would be better if they had a pay-as-you-go package.

I got a review from a friend and decided to give it a try. She asked me to give it a try to see how I could recover data fast and do other things without wasting time. I was looking for these features, and I got them with Zerto.

I would advise knowing what you want in the software and why you are going for this software. If you want fast data recovery software, you should go for Zerto. I have been using Zerto for two years, and I have not had any reason for regret. New users who are going for Zerto would not regret their decision.

I would rate Zerto an eight out of ten.

I have a main data center with a few virtual machines running. I am protecting my mission-critical VMs on a disaster recovery server that I have outside of the data center. This ensures that I have protection. If something happens with my main data center at any moment, I have a copy, and that copy is at a remote and physically separated site for disaster recovery.

By implementing Zerto, I wanted to lower the RTO and RPO. Previously, the time to restore those mission-critical VMs with the traditional backup application took too long which impacted my business. That is why I decided to evaluate and then keep Zerto to protect my mission-critical VMs. It helps to lower the time to recover when something happens with one of my data centers.

Zerto is very easy to use. I did not have to attend a multi-day training. Online training is available from Zerto. It is very easy to use in my opinion as compared to other solutions.

Near-synchronous replication was the reason why I evaluated Zerto. I then decided to use Zerto because it works effectively. It is different from the other solutions in the market. Because I did not know that technology, I evaluated it, and I found out that it effectively works. That is why I decided to use it. I am a fan of Zerto.

We have a faster recovery time. I am lucky that until now, I did not have to use it in production effectively. That means that I did not lose access to my first data center, but it gave me peace of mind. I know that if something happens, at that moment, I know what to do to recover and to fail over to that second data center. There is peace of mind for sure.

We use Zerto to protect virtual machines from VMware to VMware. Our RPOs went from hours to seconds. That is a huge improvement.

Before using Zerto, I had an issue, and we had almost a day of downtime. I had to put a lot of energy and time at that moment, not being able to do my regular job. Since moving to Zerto, I never had a big downtime, but when I evaluated Zerto and ran the tests, failovers always worked. I have not had to use it in production so far because everything has stayed online until now. I am keeping my fingers crossed.

Zerto has definitely helped to reduce our organization's DR testing. Previously, the procedure to do the testing took several hours, and now, it is all automated. The nice thing is that the testing is automated. It is a part of the solution itself, and it is very easy to perform.

Zerto has enhanced our IT resiliency a lot.

I do not have many regulations to follow because I am not in finance or health care, but it simplifies my work because it clearly shows me what I have, what is supported, and what is protected. Zerto definitely enhances my visibility.

There are two main things that I like. One is the fact that my recovery time is now much lower effectively. It is also very valuable that I can test it. There is a possibility to test that failover. At a regular moment in time, I can run that test and see if it effectively works when I have a major issue in the future.

I am switching to another HPE offering called HPE GreenLake for Disaster Recovery which is using Zerto technology in the backend but has a lower entry point. The native Zerto implementation is optimal for larger environments. My environment is rather small since I do not have hundreds of virtual machines. The initial Zerto offering was for a larger environment with more than 100 VMs. At that moment, it was not that easy to talk to HPE to get a good price. HPE GreenLake for Disaster Recovery uses the same technology, so it is a really good technology, but the entry point is much more interesting for me. They have lowered the number of protected VMs. That is why I am now evaluating HPE GreenLake for Disaster Recovery.

I have been using Zerto for two years.

It is always available. So far, I never had any issues. It is very good. I would rate it a nine out of ten for stability.

It is definitely scalable, at least in my environment. I do not have the biggest environment, but based on what I saw when HPE initially presented the solution and all the new things that I see in it now, it is a very scalable solution. Why I prefer this solution compared to Veeam, for instance, is its scalability. I am convinced that the way it works with journaling makes it much more scalable than other solutions.

So far, I never had to call support because I never had issues with the platform at all. Until now, everything worked fine, and I never had to contact support. This is through HPE, and I expect the HPE support to work like before and provide the same experience for Zerto.

Positive

I am still using Veeam, but with Veeam, I was never able to go up to a few seconds of RPO. Zerto is much more scalable and flexible as compared to the Veeam solution, so I am using Zerto for the short-term retention and protection of my data, and I am still using Veeam for the mid- and long-term retention of my data.

It is for on-prem to on-prem DR. I am not using the public cloud for DR.

It took less than a day to set it up. It was very easy to deploy. In less than a day, everything was set up in two data centers.

In terms of maintenance, it is self-maintaining, so I do not have to put a lot of time into it. It is part of my testing. Every two or three months, I do a failover test, and at that time, I also check if everything is working fine and if any new updates need to be applied. When there are new updates, which do not happen that often, it is very easy to deploy the updates.

Only one person was involved in its deployment. It was just me. To set up and maintain it, there is just me. I do not need several people because it integrates with my compute and my storage. I can see my hypervisor. Technically, there is one storage person who is responsible for all this.

We are a small company. Zerto is being used by one team, but there are two physical buildings. Here on-site, we have our main data center, which is highly available with multiple servers, and on our DR site, there is just one server. It is one big server where we have copies of the mission-critical VMs that we are protecting.

It is hard to measure because I have not had a real disaster since I have been using Zerto. If I consider the time while testing the procedure, it went down from hours and days to less than an hour. I see large gains, but it is hard to say in the percentage. It is effectively much better.

I think the price is fair for what it is offering. It gives me the peace of mind that my data is protected. It is worth the cost.
It is like insurance for a car. You do not get the value until you have an accident.

I am now evaluating HPE GreenLake for Disaster Recovery, which is using Zerto in the backend.

I would definitely recommend Zerto. I have really low RPOs of seconds since I started using Zerto, and it works effectively. That is why I love Zerto. It does what it should be doing.

I like the tool because you can go from anywhere to anywhere. I am currently using it for on-prem to on-prem DR, but it can go from anywhere to anywhere. It shows the flexibility and the scalability of the tool. It is a no-brainer to evaluate Zerto because you can also go perfectly to the public cloud from your on-premises so that the public cloud is your DR site. I did not use it myself, but you can even use it as a migration tool for migration from an old environment to a new environment. It is a very flexible tool. That is why I was impressed with it and how HPE integrated Zerto into its portfolio. It was a smart move to do the acquisition of Zerto.

I recently started looking into the AI insights that was added in the latest version. Need to evaluate further but it looks very promising from what I can see now already.

I would rate Zerto a nine out of ten.

Zerto is our main application for curbing risks. We use it to protect our workflows on applications from threats that can come from the cloud and on-premises.

Before Zerto, our organization kept experiencing some attacks. Our data was not safe. There were frequent attacks on our data, and that is why we decided to deploy Zerto.

It helps to ensure that our organization's data is safe from any latest threats.

It ensures that our applications are protected. We have high-security firewalls that cannot be attacked or broken by ransomware attacks.

Zerto can block unknown threats and attacks. It has security measures in place to stop any threats that can harm our data.

When it comes to data capacity, Zerto provides an assessment of data replication that can be orchestrated to feed the data protection models.

We used to mostly have on-premises applications, but after the deployment of Zerto, we are able to move to the cloud and ensure that our data is secure from both sides.

When it comes to cloud recovery, Zerto ensures that data transfer from the cloud to our organization is safe. It cannot be easily attacked with malware or by cybercriminals. It is very important to us that our database is safe and the data on our cloud servers cannot be interfered with by external or anonymous users. It ensures that the data for the organization is channeled for the right purpose and through the right infrastructure.

We use Zerto to support DR on the AWS platform. The support has been very good, and I would recommend it. The performance has been good, and our data has always been safe.

I have not had any difficulties with data migration. Since we deployed Zerto, data migration has not been a challenge.

Zerto helps our organization to be in the right direction when it comes to data protection and recovery from both on-premise and cloud servers. When there is anything crucial or any challenge, their customer support team provides a timely solution, which helps with performance.

The recovery management has been efficient. We can use the tools to accommodate any form of data for future retrieval. Our data is safe.

Zerto has been excellent for our RPOs. When it comes to disaster recovery, the company makes sure that we have the right tools at the right time to ensure that we do not have any data recovery challenges across the enterprise.

Zerto has saved a lot of time. We used to take eight hours, but now, it takes us six hours to accomplish most tasks and projects based on the data flow.

Zerto has reduced the number of staff involved in a data recovery situation. We have 20% less staff.

Zerto has also reduced the number of staff involved in overall backup and DR management.

Its user interface is excellent, and when it comes to data duplication, Zerto is very fast.

Their customer support team ensures that we get timely updates and provides status or data on threats to help us ensure that our applications are safe.

The cost of deploying and running this platform is also good as compared to other platforms.

Overall, Zerto is doing a very good job. We have experienced a few downtimes on networking. Most of the time, they come up with a solution immediately to sort out any challenge that may affect data flow or data migration. It does not happen frequently. We might experience it once in two months, but when we face any downtime, it does not impact the data. 

I have been using Zerto for the last six months.

It is a stable product. I would rate it a nine out of ten for stability.

It is very scalable. I would rate it a ten out of ten for scalability.

Their support is good. Their technical support team has been doing well. I would rate them a nine out of ten.

Positive

We were not using a similar solution previously.

It was not complex. It was simple. The deployment was simple and clear. It took a few hours.

We had four people involved in its deployment. Overall, we have eight people who work with this solution.

We have seen positive returns on investment. We have achieved a lot, and our performance keeps on improving. We have seen an 80% ROI in the past six months.

Its price can be better, but it is not bad. Most small-scale organizations can afford it, but they can come up with more customer-friendly packages.

We did not evaluate other options. For now, we are okay with Zerto. 

Overall, its performance has been good, and I would recommend it to other organizations. It is a good solution that can help any organization to achieve projects based on data management.

Overall, I would rate Zerto a nine out of ten.

We primarily use Zerto for DR as a service but also for high availability purposes. It's mostly deployed at our on-prem colocation data center. We also do a little on the cloud, as well. 

Zerto makes DR a lot easier. We don't have to spin up copies of VMs or copy applications and databases. Zurto just takes care of all that for us. We just did our annual DR test, and it worked exactly how we expected it to. We're big fans. We like the fact that when you migrate DR, it will automatically be configured for us. For example, it sets the IP addresses because they have different IP ranges and various data centers.

It saves a lot of time during disaster recovery. In our tests, we just hit a button on Zerto, it did its thing, and the solution just let us know when it's done. In the meantime, we could go do other things instead of having to, copy app configs, .ini files, etc.

The near-synchronous replication is great. That's one of the reasons that we went with Zerto. I've had a great experience with it and never had an issue. Having this functionality is critical, especially for DR. If our main data center goes down, we need to flip it and have everything almost identical to what it was when the data center went down. We use it for production high availability, so if that host goes down, Zerto will just automatically forward to the replica that it has on another data store.

The post-configuration part could be improved. For example, it would be super helpful to have the ability to modify DNS. Once the migration is done, we want to do some more modifications to the endpoint.

We have used Zerto for around 10 years.

Zerto is highly stable. We've never had any issues or lost connections between the agents on the VMware host.

Zerto is scalable. We're running it in five different data centers worldwide, and we haven't had any performance issues. It covers 70 hosts across all our data centers.

I rate Zerto support nine out of 10. We haven't had to use support much because it just works. Once we had an issue with a VM that wouldn't upgrade, and they sorted it out for us pretty quickly. I've only used it once, but it wasn't a time-critical situation. If I contacted them during an actual disaster or DR test, then I could see how quickly they can work.

Positive

I've never used anything besides Zerto, but I've done the failover process manually. Zerto just makes it much easier and faster than a manual failover process.

In our DR testing, Zerto allows us to go work on other things while it takes care of everything. That's valuable because we know that we can still hit all of our SLAs in a real disaster. 

Zerto is reasonably priced for the product that you're getting. We keep on buying more licenses, so it's a good price. 

I rate Zerto 10 out of 10.

Our primary use cases include replication and disaster recovery. 

We use Zerto to help protect VMs in our environment. We are really happy with RPOs (Recovery Point Objectives).

Both the Recovery Point Objective (RPO) and Recovery Time Objective (RTO) are fine. They always meet our requirements. Their significance is not driven by a single factor but rather by the customers. Some customers require an RPO of a few hours, while others require up to 24 hours. It depends on the specific needs of the customer.

The most valuable feature for us and for my company is that we are replicating most of our production customers to the DR site, and we can do testing whenever we want. The customers are very happy with the way we do the testing while the primary is still running. There's no disturbance to the primary production site. 

The most important function right now is that we have another DR site, which is in a very old environment that is non-Zerto. We were log shipping there through another method. We are migrating over to the Zerto platform so we can replicate it to the new DR site so we can shut it down. That's going to be a lot of savings for us, shutting down the old replication with the other way. That will be one of the benefits too.

Zerto offers near-synchronous replication, which is always on and constantly replicates only the changed data to the recovery sites within seconds. It doesn't really bother us because we have enough bandwidth. Since we do a 24-hour recovery, it does not take a lot of disk space. It's an issue sometimes because I have to constantly increase the space on the disks at the DR site. On the VPG (Virtual Protection Groups), I have to constantly increase the space. That's where the alerts are being generated too.  

Someone suggested to me that I should turn off this feature, but that's not the way to do it. Turning it off temporarily is similar to applying a bandage.

Moreover, we have plans for DR recovery in the cloud. That's our next step, and it's likely to be on the agenda. We probably will use the license we have for that, which we can use as of today.

Zerto generates many false positive alerts, which is annoying. I still have thousands of alerts in my inbox, and those are false alerts. When I check there's actually no problem.

I have been using Zerto for four-plus years. 

It's very stable as far as we're running. Even though I'm running it on a very old Windows Server 2012 server, it's still running fine without any issues. 

Scalability-wise, it's pretty good, too, but we're not there yet. We are using it for small 50+ VMs we are protecting right now, but we are continuously growing. We may have to expand with multiple ZVMs (Virtual Managers). We're going to install multiple. We just have one on each side, which we don't have an issue with.

The customer service and support are really good. I wish they had phone support too right away, but we have to go through their website and open a ticket.

Moreover, there's always going to be something a person is not one hundred percent knowledgeable about. He has to escalate to the top tier. 

Positive

Somebody else did the deployment in the company and I took it over after that. I just recently upgraded to the latest version without any issues. Zerto is very easy to upgrade.

There is an area of improvement for Zerto folks. Every time we do an upgrade, if we are three or four releases behind, we have to go to the next level, then the next level, and then the latest. This is a pain. We would like the ability to skip to the newest version. 

ROI is pretty good compared to the recovery compared to the investment we have. The solution is worth it. If we go to the cloud, the ROI is definitely going to be much more.

The pricing is pretty decent. We got a good deal. 

I really like Zerto. I've been using it for many years. It's a quick recovery. I failed over the complete site to the DR many times and then failed back to the production without any issues. 

We have VMware SRM but we are not using it. We have a license, we can use it, but we're not using it because Zerto is our primary right now. 

Zerto is very easy to use. It's not dependent on the hardware. It can decouple from any hardware. You can use it, even if you have different hardware at the source and the destination. That was the biggest attraction when we got into Zerto. It's pretty decent. 

I would rate Zerto a ten out of ten.