Zerto Reviews

Zerto is our primary means of failing over our critical production loads that have a relatively low RPO/RTO. This is our use case for this solution.

What we like best about Zerto is its fast failover to another data center. It is simple and it works.

The limitation with Zerto is that you're required to have one Zerto Manager per virtual center, and this means that we're only able to replicate one way using this solution. Now, we are evaluating the clustering of Zerto with Microsoft clustering, so we can replicate both ways and both data centers, and have the management server in both data centers.

Historically, Zerto has started going into the backup space, and that is when they lost focus on keeping their replication product good. Now, it seems they're finally leaving that backup space, and they're just sticking with replication, so in version 9, they have fixed all of my gripes about the product, e.g. they now support VMware tags, Windows bringing over the time on the target side, etc. All of these little things, they are all correcting, because they're now sticking with the replication product.

It's been five years since I started using Zerto.

Zerto is a single use case product and it works flawlessly. It is stable.

Technical support for this product was absolutely fantastic, but that was before they were acquired by HP. They are still good, but I can tell the company is becoming too big.

We didn't previously use a different solution, as this was the first use case or first requirement that we needed to have under a 24-hour RPO/RTO.

The setup for Zerto was very simple.

We implemented this solution in-house. Implementation only took less than a day to complete. Zerto was ready to use in our environment for a DR (disaster recovery) exercise weeks later.

The return on investment from Zerto was immediate. Instead of having legacy DR failover exercises that involved multiple teams and weekends work of activity, now a single user can fail over everything and get reports to prove that it was failed over and the data integrity was all done. As far as people hours and time, the ROI was instant.

Zerto is fairly expensive. We are on a perpetual three-year subscription, but for my less than 300 VMs that we needed this functionality for, it is worth it. I'm not aware of any additional costs beyond the standard fees for this product.

We did evaluate Commvault LiveSync, Veeam, and Dell solutions, though I don't even remember what the Dell product was. We did go through RFP. We went with Zerto because it was simple and it worked, and we didn't have to worry about doing anything else.

We're a Commvault and Zerto customer.

We are on Zerto 8.5, and we are evaluating version 9 update 3.

I have no impression on the scalability of this solution, because we haven't really grown yet. We have 300 endpoints and we've always been in that range. I can't tell how Zerto fares if there's more than 300 endpoints.

We have a primary asset owner who uses this solution, who gets feedback from other IT infrastructure teams of whether their servers need to have a low RPO/RTO. That single asset owner will then put those in Zerto. For deployment and maintenance, we have the primary asset owner, then there's a backup person. The primary asset owner does everything, but if the asset owner isn't available, the backup person will help with support roles.

We don't have plans of increasing Zerto usage, as we've always had a relatively static critical VM count of around 300, e.g. we've gone down to 260, we've gone up to 300, but it's always in a range that's close to 300.

My advice to people looking into implementing this product is that if you have less than a 24-hour RPO/RTO and you need it to work in your target location, then there's no other product for it other than Zerto.

My rating for Zerto is a nine out of ten, because nothing is perfect. Nine is the best rating I could give for this solution, but the key takeaway is that it is a single use case product and it does the job.

We use Zerto for backups and DR; we back up to a StoreOnce unit and then offsite. We have over 11 servers, including three Oracle servers, one Oracle database, and an Active Directory. 

Before Zerto, we used another solution that caused database crashes and did not offer certainty regarding disaster recovery. Zerto is more configurable and stable.

A DR site reduces downtime, especially with full VM backup and online synchronization. Zerto accomplishes this without affecting network efficiency, as synchronization occurs at specific intervals.

Zerto's ease of use is outstanding; it's easy to set up and has a clear interface and menus. The reporting, analytics, and online monitoring are also excellent.  

Compared to other solutions, the speed of recovery with Zerto is faster. Our last backup solution, Data Protector, was very slow, but Zerto is rapid even in file retrieval. 

The solution helped reduce our organization's DR testing; it's hard to say precisely how much, but Zerto does faster DR testing than other products.

Improvements in stability would be welcome; there are some software bugs that can affect RPOs. We want more of a guarantee that we won't lose any of our backups, even in the event of a disaster. 

The platform measures the right speed of storage devices and gives an alert on the VPG if there is latency, but the nature of the alert suggests the solution isn't meeting the SLA. However, this shouldn't affect the health status of the backup. It should provide an express report that we should enhance our hardware rather than express latency as a threat to the backup capability.

We've been using the solution for two years. 

The stability is acceptable, we experienced an issue once, but the backup time is speedy.

The solution's architecture supports business owners to expand their disaster recovery capabilities as their infrastructure grows. Additionally, Zerto's ability to integrate with various cloud platforms and on-premises environments further enhances its scalability, offering a flexible and robust solution for organizations with evolving needs.

Customer support is one of Zerto's best aspects; the support is excellent, and we can quickly get through to them. I rate them ten out of ten. The support staff are very kind and always solve a problem. I feel secure knowing I have access to such good support.

Positive

We previously used Micro Focus Data Protector and Veeam Backup & Replication. Zerto is easier to use and more straightforward to configure. 

Zerto replaced our legacy backup solution, Data Protector. This not only saved on the cost of the old product but also provided more stability and security to our company. We now have a new backup methodology, and it's a significant upgrade.  

I carried out the initial setup with support from Zerto, which was very straightforward.

The only requirement for maintenance is monitoring the solution and updating versions.

I have 20 years of experience in IT, so I was well-positioned to carry out the deployment myself, with the assistance of Zerto support.

We have seen an ROI with Zerto. 

The pricing is slightly above average, but the immediate and comprehensive support makes the price acceptable.

We evaluated many other options but found Zerto the best, especially for our HPE environment. It's the most stable and straightforward tool, and even those with limited experience can operate it.

I rate the solution eight out of ten. 

I strongly recommend Zerto; I've tried many other solutions, but it's the most stable.

We use the product to help protect VMs in our environment, and regarding RPOs, I carry out the test for them every six months, and it's working correctly.

I advise those evaluating the solution to use it, especially in an HPE environment, as it's fully compatible and easy to manage. There is no requirement for special drivers or configurations.

I use Zerto for disaster recovery and data protection.

It is very easy and user-friendly. You do not need too much knowledge about it before you navigate around it. It is not complex. It is easy for users to use.

We can see its benefits from time to time. Every time we use it, we keep seeing the benefits of Zerto.

We have seen a positive effect on our RTOs and RPOs. We will keep using Zerto. We do not have any plan to change the brand.

Zerto helps me save time. It helps do things slightly faster. 

Zerto has helped me with my time management. It helps me save time. It makes my work easier. It is easy to navigate through.

I find it to be the best. It has had a positive effect on everything I do in my daily activity.

Zerto is easy to use and user-friendly. It is not complex, so I find it easy to use. I do not need to have much knowledge about it before using it.

Its price should be improved.

I have been using Zerto for three years.

I have had a crash once or twice.

I feel it is very good because it supports virtual machines.

I have not contacted their support.

I have not used any other solution. Zerto is the first one.

It was easy. I have not tried any other product, so I cannot compare it with others. This was my first time using Zerto, and I found it to be easy.

It did not take much of my time. It probably took two to three days, but I am not sure because it has been three years.

I had a little assistance with the deployment. It was not just me. We had three people involved in its deployment.

It needs to be maintained. You need to check whether any user or anything else requires attention.

They should adjust the pricing because I feel its price is too much. If they reduce the price, there will be more users and customers.

If you have not deployed it before, you should seek assistance before the deployment.

I would rate Zerto an eight out of ten.

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.

Currently, our use case is to create a replicated system. We have no access to the internal VMs. We can manage the VMs up to a point, but we cannot get inside to do any kind of corrective actions to the servers themselves. We had no backup solution in place, so we needed to get something there. That is what we are using it for. It is replicating out to Azure. This way we have some place in case the ones on-site get compromised or have issues.

We are moving to a new data center. There are several VMs that we have to move over there that have RDM disks or SQL clusters. Those are the hardest things to move at this point in time, but now that I have the setup and it is ready to go, all we have to do is just flip the switch and get everything over where they are supposed to be. It is going to be a lifesaver for me. It will save me a whole lot of time in putting things back together.

Its initial setup can be better. It looks easy, but if you do not have things in the right place, it is not as easy as it looks. Some of the instructions were not clear. They were a little bit confusing. For example, while setting up SSH initially, it was a little bit unclear if I needed to use a regular credential or some other credential. This was one of the things that was a little fuzzy, and we had to get somebody else involved to help us out.

I have been using Zerto for about a year.

It seems to be pretty stable provided our network stays up and the firewalls do not go down.

I have not had to scale it yet, but we are planning to replicate an environment of roughly a thousand machines.

I would rate their support an eight out of ten because it took a while for the communications back and forth to get it set up. We could not always get together at the same time. We would also run into an issue, and we had to go to development or somebody else to figure out what was going on with it. We would then wait for that response. There were a lot of issues that we had that required a lot of back and forth.

Positive

We did have SRM in place for a little while for about 75 machines. Most of the machines that were being replicated with SRM went away when we had a dissolution with another part of our facilities, so we pulled that out and stopped using it. We then went to Zerto about that same time. 

We are not using it for a full DR. We have another solution in place for doing the DR work. Zerto, at this point, is primarily for replication. 

We are also not using Zerto to help protect VMs in our environment. We are using another solution for that.

It was a little rough, but it was not terrible. When we were setting this up, I was working with several machines that were 30 or 40 terabytes in size. Moving that data out to that other location was a long, slow, and ongoing process. There were several times when we had to reach out to their support to try and figure out what was going on. We had to make some adjustments to how they were configured, but that was the biggest challenge we had with that the whole time.

It is slow initially, but once you get it all up there, it is not so bad. It took days to get that data moved. Once it got up or synced, it was down to seven or eight minutes, but it took days to get everything up there to begin with. It took about a week from start to finish to have it fully deployed.

We worked with a Zerto rep. They said that this is what we need, and we got everything in place, but then as we were trying to deploy it, we had issues. We had to pull in support to help us straighten out what we were having problems with. They have been pretty good. Fortunately, I have not had to call them much. Once we got it set up, it was fairly easy to figure out, but doing that initial configuration was a little difficult.

We have not yet seen an ROI. We are going to be moving to a new environment and a new data center. I am sure I would see a big return on investment at that point.

I did not evaluate other options, but there were some higher-up managers who were involved in those conversations. They had neglected to involve the guy who was going to manage it. I heard that they evaluated Veeam, an IBM solution, and Zerto.

I would rate Zerto an eight out of ten only because I have not used it a lot. When we move to the new environment, I am sure I will use it a lot.

We use Zerto for server migrations between data centers during the role swap that we do. We use it from a recovery standpoint as well.

We currently do not have disaster recovery to the cloud. We go between our data centers. That is what Zerto helps us accomplish.

Zerto works very well. We have not had any faults while using it. We are a financial institution, so we have to make sure the systems we have are available with very minimal downtime.

It has helped out a lot in man-hours. It has saved us a lot of overnight work. We can literally change our production servers in a matter of minutes to hours. Rather than having to do this gradually or a couple of weeks in advance and have several teams and business partners involved, we can literally do it live on the same day.

Zerto is probably one of the faster ones in terms of recovery. You can just go into the console, and because it is always replicating over to the other side, it takes minutes.

Being able to do our recovery and being able to migrate between data centers during the role swap is valuable just because of the amount of time it takes. It takes 55 hours or so. Right now, we are doing this in a VDI environment. We are going to experiment with it as a proof of concept because we have a thousand machines that we have to move and do all the assignments. Zerto would lessen that down by a few hours, and then we can use some scripts to do everything on the Horizon's side. We have not done it yet, but we are hoping to reduce it down to about 3 hours instead of 55 hours. We will also be able to manage our host better and be in a better recovery state. If the host happens to go down, we can quickly recover.

It is very user-friendly. There is no wondering about what a feature does. It is easy to use.

If they already do not have it, they can have some APIs for the Horizon environment. Instead of having to use some scripts to get around, they can make it a lot more user-friendly for integration.

We have been using Zerto for two years.

It has been very stable. We have not had any issues while using it. When we need it to do its job, it is always dependable.

It scales very quickly. We can set up a whole new environment in an hour. We can get the server setup and all the VMs that are required for it to function in an hour or two.

I have not used their support. My peers had to use it. They seem very responsive and knowledgeable. 

The other DR tool that I have used is from Symantec. It was an old-school recovery tool. It was back in the day when it took a whole day to get things back up.

It was deployed before I joined the company.

Its price is fair. It is very cost-effective compared to the cost of the labor for your workers and associates. 

We selected Zerto over others primarily for the ability to replicate and help with our role swap. It cuts the downtime of the production systems by a large volume. This way, we can meet the deadline and not have that much client impact. In the financial side of banking, you do not want bad performance.

I would rate Zerto a nine out of ten. There is always room for improvement, but it definitely makes your life a lot easier.

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.

I am the global lead for infrastructure for the VMware and Windows Server environments. We are mainly using Zerto for disaster recovery. We have a prime site in Missouri, and we have plants in Taiwan, Malaysia, Japan, Italy, and Korea. We have 400 to 500 users in the environment. 

We have installed Zerto software on the DR site and the production site. We will be using Zerto for the production site for all the centrally used applications, such as SAP, file servers, and Exchange. Because this is a central site, a lot of other sites come to this site for various things. 

We also have Zerto on the DR site. In manufacturing, there are 60 or 70 tools, and each tool costs around $500,000. When the site goes down, you cannot transfer these tools very easily. It takes time. These are big tools, and it takes time for them to go somewhere else. You have to do a test again and go through the qualifications procedure, which takes time. As the IT department, we are interested in getting the applications that are used by all the sites centrally located, and if anything happens to the primary site, we want all the applications to be already there on the disaster recovery site. We just bring them up, and we are good to go.

Zerto will help to protect VMs in our environment. We have tried that in the test environment. That would be another reason for using Zerto.

We have used it for VMs. We know that it is a very good product. So far, we have only synced SAP and tested a few things. For SAP, there were two guys doing that, and they like Zerto very well. They have the test databases up there. It was smooth, and they liked it. The part that we still need to test is the Windows VMs where we can spin up a domain controller, change the IP, etc.

We can move data that is needed to keep our users collaborating with one another using Zerto because we are doing a continuous sync of the site. Once it is synced, we do not have to worry because everything happens in the background.

The replication feature where it constantly replicates and sees that data is always in sync is valuable. 

The ease of moving all the VMs is valuable. All we have to do is change the IP address and the VMs are all up and running there. There is a passive sync with all the VMs. That is what we like about Zerto. VMware has its own tool, but you need to do a lot of scripting. In manufacturing, we have a one-man team, so we do not have time for all the specialized work. We needed an application that is more GUI-based so that we can pinpoint and easily move VMs. We can bring up all the VMs and make sure the data is in sync, and we are up and running, so the ease of implementation is what attracted us to Zerto.

Zerto is very easy to use. It is very professional. We had no issues at all. Even for bringing up a new ESX host, they have a standard procedure. It is very easy. With a few clicks, you can do the ESX installation. 

There should be an automatic installation in a cluster. When I add a virtual client or ESX source to the cluster, it should automatically install that. There should be automatic installation. Currently, I have to do that manually.

They can give us a few training classes.

We installed Zerto just three months back. We have not yet started using it properly.  

Zerto is a very stable product. We have no issues. So far, it is working as planned. It is very stable. We will soon be working on it full-fledged. 

It is very scalable. We buy new licenses, and we just add another ESX or VM. We manually install it, and then we are good to go. It is pretty easy.

We have not contacted support yet. So far, so good. Everything is working as planned.

I tried VMware replication, but it was too hectic with all the scripts, so I gave it up. 

We implemented it recently. There was the ease of implementation. It was easy and straightforward. 

In manufacturing, we have to make sure that everything is on-prem. The data has to be on-prem because all the tools write immediately to the servers. There are two types of manufacturing. For the type of manufacturing where your tools are constantly writing, cloud applications are not good. For example, when we scan wafers, there is a set of data, and when we go through another tool, there is another set of data. This has to be instantaneous. There is nothing called a cache or buffer on those tools. It has to be instantaneous. We cannot say that the cloud is down, and we lost the data. We cannot stop the tool because this is a manufacturing facility with 24-hour operations on 365 days. We cannot have any downtime where the full site has gone down because this site is used for central applications.

I am the one who implemented it. Overall, there were just two people involved from our side. There was me and one more person. Because it was a new product, we also had a representative from Zerto as a standby. He would just watch our screen while we were implementing it. When we got stuck somewhere, he would help us. Because this was a DR site and it was a little far off, we wanted to make sure that everything went smoothly.

In terms of maintenance, so far, it did not require any maintenance from our side.

Having a solution like this is similar to having insurance. When you have a car accident, that is when you know the value of your insurance. Similarly, you cannot put a definite value on a solution like this till something happens, but there is peace of mind in knowing that the software is there, the VMs are there, and we can test it anytime. That is the true value.

It is economical as compared to other brands. 

We are an HPE shop. Zerto was procured by HPE, and we were looking for a DR solution. We went for Zerto because of its simplicity and ease of installation. We did an on-site proof of concept of Zerto for a year. We liked it and purchased it.

The only other product that we looked at was the VMware one because of the orchestrator. We did not look at any other products. I know that Veeam also has the same features that Zerto has. We had some discussions, but we never looked into it. Once we had a product that was easy to install, we did not feel the need to compare. It was doing what we wanted it to do.

Another factor for going for Zerto was that its price was economical. My boss, who is the CTO, liked its licensing scheme. It was much more economical as compared to VMware, and that is why we went ahead with Zerto.

Before implementing this solution, in terms of preparation for disaster recovery, you have to identify the business applications that are critical to your environment. You have to scope that out and make sure you have your VMs accounted for because licensing depends on the number of VMs. With a product like Zerto, you have to know the number of VMs and the size of data you are going to sync. These are the two factors that you have to look into for disaster recovery. 

Zerto is way better than other products. Installation is done with the click of a button. Everything happens in the background. You do not have to worry about it. As a product, we have not had any issues so far. However, we have not yet done a full-fledged disaster recovery. We have done minor testing, and we want to do major testing. As of now, I am very happy with the product. It does not need any further modifications. It is simple. It is nice. It is easy to execute, so I would keep it that way.

We have not yet used Zerto for immutable data copies. I have been playing around to migrate a VM and see how it works. So far, we have only used it to sync up the SAP side. Our SAP stuff is already synced up, and we have done some testing of it, but we have not done any disaster recovery.  

I have not had a chance to assess Zerto for blocking unknown threats and attacks. We are mainly interested in using it for disaster recovery.

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