Try our new research platform with insights from 80,000+ expert users
Dov Goldman - PeerSpot reviewer
Systems Engineer at a financial services firm with 501-1,000 employees
Real User
Top 20
It saves a lot of time because we can hit a button and let it do its thing
Pros and Cons
  • "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."
  • "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."

What is our primary use case?

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. 

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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.

Buyer's Guide
HPE Zerto Software
September 2025
Learn what your peers think about HPE Zerto Software. Get advice and tips from experienced pros sharing their opinions. Updated: September 2025.
868,787 professionals have used our research since 2012.

For how long have I used the solution?

We have used Zerto for around 10 years.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

How are customer service and support?

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.

How would you rate customer service and support?

Positive

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

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.

What was our ROI?

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. 

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

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

What other advice do I have?

I rate Zerto 10 out of 10.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
reviewer2266878 - PeerSpot reviewer
Computer Services Division Manager at a government with 51-200 employees
Real User
Simple and easy to understand with a clean interface
Pros and Cons
  • "The pricing and licensing are excellent. It's very straightforward."
  • "Zerto requires these thick provision walls for virtual machines that are always running."

What is our primary use case?

We primarily use the solution for disaster recovery.

How has it helped my organization?

It’s improved our organization via providing better RPOs and excellent uptime. 

What is most valuable?

The best aspects of the solution are the simplicity of use and the way that it handles the RPOs and the RTOs. I like that we’re able to dial into exactly what we want. They've been able to give us better RPOs than we ever imagined.

It has a very clean interface and is easy to understand. You don't really need a lot of technical knowledge to understand what you're doing.

I don't know if it's the compression or what, however, we get really good RPOs. The system already knows what we're trying to do. It’ll estimate and give us better RPOs than what we've actually set.

We’ve improved our RPOs 100-fold.

Uptime is excellent. The last test fail-over recovery was within almost thirty seconds to a minute. It was very, very good, and I was very impressed. This is extremely vital. We have to maintain a lot of uptime. The data that we have is constantly being written and it is very vital that we stay up for public safety reasons. To be able to have something like this solution, that can fail over and fail back easily, makes us much more agile in the data center.

What needs improvement?

There are a few technical aspects that I didn't care much for. For example, we’ve made a transition to hyper-converged technology, which is moving more towards provisioning and being smaller and more agile. Zerto requires these thick provision walls for virtual machines that are always running. I know that they're temporary. However, they're constantly running and they eat up a lot more disk space than they need to. Maybe if there was a little more of a stronger relationship with VMware and how they operate, some of that could be better managed.

For how long have I used the solution?

I've been using the solution for three or four months.

What do I think about the scalability of the solution?

It's scalable. If we need more, we just ask for more. If we need less, we scale it down.

We're already looking at how we can leverage it on other sites. To do so, we simply just buy a few licenses, deploy a couple of VMs, and then it's off to the races.

The size of our current environment is about 40 terabytes of virtual machines that we are protecting.

How are customer service and support?

We've never had to contact technical support. 

How was the initial setup?

Our experience with the initial setup was easy. It took 15 minutes. 

What about the implementation team?

We leveraged a third party for deployment. The person we hired wasn't that technical, and only knew the basics. However, it was so easy we really didn't need him.

What was our ROI?

We're still waiting on the ROI. However, it will be very easy to calculate the minute we have a failover. 

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

The pricing and licensing are excellent. It's very straightforward. You license what you use. 

Which other solutions did I evaluate?

We also evaluated VMware's cyber recovery manager. We chose Zerto due to the fact VMware’s solution was very complicated, very difficult to use, and required a lot more effort to be able to set it up and make sure that it worked. There was a lot of debugging to make sure things were working properly. Whereas Zerto was almost effortless. I was able to implement Zerto within minutes. Without exaggerating, within ten minutes I already started replicating.

What other advice do I have?

The solution just works. It works in the background and it is very hands-off. Once you set it, it just goes. 

I'd rate the solution nine out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Buyer's Guide
HPE Zerto Software
September 2025
Learn what your peers think about HPE Zerto Software. Get advice and tips from experienced pros sharing their opinions. Updated: September 2025.
868,787 professionals have used our research since 2012.
reviewer2098281 - PeerSpot reviewer
Sr Storage Adminstrator at a manufacturing company with 10,001+ employees
Real User
Reduced downtime and time to deploy new servers in an easy-to-use solution
Pros and Cons
  • "The solution's most valuable aspect is allowing a failover from our remote sites to our data center. Our remote sites have failed several times, and on each occasion, we were able to bring a plant back online within 30 minutes, even though the hardware repair took many days."
  • "I want to have an OVF or some local deployment where I can deploy the ZVRA rather than having to push it from the console. Some of our smaller remote sites have relatively poor bandwidth, and they can't keep up with the constant deployment stream from our center console, meaning we have to find some creative hours to get around the bandwidth bottlenecks. If I could push out a small install file, install it locally, and then reach back to the console, that would be excellent."

What is our primary use case?

We have critical servers at remote sites that failover or are replicated to our main data center in case of an emergency. If a remote site has a failure, we can spin up that virtual machine from our data center.

We operate a hub and spoke design with a centralized data center hosting our main instance, reaching out to roughly 78 remote locations. We handle the VPGs through the centralized management console at our data center.

We also use the Zerto to replicate from a primary host to a secondary host in case the primary goes down; we have a kind of cold box to which the solution replicates.

Our final use case is if we are updating a plant's entire server rack, and we use Zerto to replicate the old servers onto the new ones, which results in less downtime.  

How has it helped my organization?

The product significantly decreased the time it takes to deploy new servers; we can work on them, build them, and then failover the old VMs to the new server with minimal business impact. What previously took hours to migrate the VMs with vMotion typically takes 30 minutes with Zerto, which is a phenomenal time saving for us. Our plants also have the reassurance that when we replicate their main servers back to a data center, we can keep their business running even if they have a total loss of a server rack or power.

The solution has helped to reduce downtime; we had a situation where a plant had its server fail, and we could failover their server to our data center and had them back up and running within 30 minutes. The required parts for a fix took three days to arrive, but thanks to Zerto, they did not have three days of downtime. Additionally, we just updated our hardware at our plants from HP servers to Dell, and we had to move 10 to 15 VMs per location from the old servers to the new ones. We completed this relatively significant move- roughly eight TB worth of data- in 30 to 45 minutes versus multiple hours, a remarkable reduction of potential downtime. Depending on the plant, downtime can cost $100/minute and potentially much higher if they are into online sales.   

The product helped to reduce our organization's DR testing; we previously used a Hitachi failover or manual VM move, but now we have Zerto VPGs at all sites. We can click the failover button, and it's done about 30 minutes later. It's good not to have to failover manually. Regarding time saved, we can get testing for a plant done in 30-45 minutes, resulting in between two and six hours' worth of savings.

What is most valuable?

The solution's most valuable aspect is allowing a failover from our remote sites to our data center. Our remote sites have failed several times, and on each occasion, we were able to bring a plant back online within 30 minutes, even though the hardware repair took many days.

The solution is very straightforward, especially after using it a few times. We had users who were daunted by it, but once we walked them through how easy it is to failover, they felt pretty comfortable. Zerto is easy to use and doesn't take long to learn, which is nice.  

We like the near-synchronous replication feature, and it's essential as we want to reduce the amount of data lost during a failover. The RPO and RTO are excellent, thanks to Zerto, and we have some sites with poor bandwidth, so we understand the limitations we're working with. Near-synchronous replication allows us to roll back to a specific hour or minute in case of a failure, which is a great feature.  

One of our primary uses for the solution is to protect VMs in our environment, which has an excellent effect on our RPOs. We had a data breach several years ago, and Zerto helped us quickly get back up. We like it a lot because we can failover within minutes once we detect an issue.  

What needs improvement?

I want to have an OVF or some local deployment where I can deploy the ZVRA rather than having to push it from the console. Some of our smaller remote sites have relatively poor bandwidth, and they can't keep up with the constant deployment stream from our center console, meaning we have to find some creative hours to get around the bandwidth bottlenecks. If I could push out a small install file, install it locally, and then reach back to the console, that would be excellent.

For how long have I used the solution?

We've been using the solution for over five years. 

What do I think about the stability of the solution?

Zerto is very stable; we only have problems with sites with poor bandwidth, and there's little we can do to get around that. Sometimes VPGs get outdated because those sites can't copy the data fast enough, but the application is very stable.

What do I think about the scalability of the solution?

The solution scales exceptionally well; we add more licenses when required and keep running. We currently have over 400 licenses.

How are customer service and support?

I recently contacted technical support, and I rate them seven out of ten.

How would you rate customer service and support?

Neutral

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

We previously used Veeam, Commvault, and a Hitachi solution. We switched because Zerto has a better RTO and RP, and it's much easier to use than Veeam. The Hitachi solution was very cumbersome as it was CLI only, and we had to unmount and remount storage.

Comparing the ease of use with other solutions, Zerto is excellent; once we have the VPG, there's a large failover button which allows our entire team to carry out the function. It's elementary. After showing a team member once or twice, they can operate the tool independently. The graphics and GUI show us the failover progression, so we don't have to wonder if it has taken place or how long is left. The tool keeps good stats and informs us of the step it's on. 

How was the initial setup?

I wasn't involved in the initial deployment, but we operate the solution with one team, our server team. Regarding maintenance, a minimal amount is required to keep up to date with patches etc. We occasionally run into an issue that necessitates upgrading to a newer version; for example, we were trying to move some vast data stores, and Zerto support said we needed to increase the timeout count. We keep fully up to date with security patches, and two staff members are responsible for maintenance. 

What was our ROI?

We have seen an ROI with Zerto, though it's hard to quantify precisely how much. It saved us a significant amount of downtime, and plants lose money when they're down, so it's a hidden ROI in that respect.

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

As far as I know, the pricing is around $1,000 per VM, but Zerto is changing the pricing model to more of an enterprise-class license. I don't know if there are any additional costs or fees.

What other advice do I have?

I rate the solution nine out of ten. 

Zerto did not reduce the number of staff involved in data recovery, overall backup, and DR management because we already run a very lean staff; there are eight of us on the server team, and we manage over 3000 servers across the company. On the other hand, Zerto enables multiple staff to do the failovers rather than one of two specialized employees. 

None of the time saved in DR testing has been allocated to value-add tasks because the time saved occurs outside our regular business hours.

Comparing the solution's speed of recovery with other disaster recovery tools, Zerto is excellent and rapid; we can restore everything in the VPG simultaneously. A tool like Commvault is single-threaded, so we would have to restore VM by VM, which is very limiting. VPGs are excellent because we can restore everything within them and get on with life.  

We have not used the tool for immutable data copies; we use our pure storage.

When we had a ransomware attack, the solution didn't initially save us time as they attacked our Zerto environment and took it down. Once we had it back online, we could speed up the recovery, and we've since hardened the product with additional security.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
SatyendraSingh1 - PeerSpot reviewer
Recruiter at Digital Janet
Real User
Top 20
The non-destructive testing enables businesses to test their disaster recoveries without impacting production
Pros and Cons
  • "It's good for reliability, timing, and simplification. For reliability, it's a logical construction that behaves productively. It's a critical system where timing and coordination are necessary. It also offers simplicity to design and analyze the system by clearly defining the relationship between events and conditions."
  • "Sometimes we require extra storage for Zerto."

What is our primary use case?

We use Zerto to recover cloud services hosted on Azure and AWS and on-prem servers. We also use it to protect VMs. Our company has a small data operation, so we can upload all the data to the server. 

How has it helped my organization?

Zerto helps recover documents and protect data. It has excellent security and is easy to set up. We can make multiple backups and replicate different public or private cloud sites. It gives you versatility and confidence. It's because it's easy to manage and configure. There are no challenges using this tool.

We have near-zero data loss, and it has manual recovery checkpoints. We can create frequent recovery checkpoints in business for in-time backups. The second one is automated and non-destructive testing. 

The recovery time is very fast. I don't think another tool can deliver a recovery team that fast. When we ran a DR test on Zerto, it migrated quickly and efficiently. It has drastically reduced the time we spend on DR testing. We're less dependent on Hypervisor for storage resources. Our recovery time has been reduced to 30 minutes on average. It depends on the data. Sometimes, it may take only 15 to 20 minutes, but if we're uploading all of the company's data, it will take 35 to 40 minutes.   

What is most valuable?

The HR recovery is valuable because I work with the HR manager to recover the HR system first. The data will synchronize with the cloud. I also like Zerto's non-destructive testing, which enables businesses to test their disaster recoveries without impacting production. 

It has a user-friendly interface, so we can manage data protection and recovery tasks quickly. It's also cost-effective because it reduces the infrastructure cost. It's easy to integrate. Sometimes, I integrate it by myself when the manager isn't there. 

The onboarding is simple because when we're backing up, we have a copy of production running on the secondary side. We have real-time DR, meaning we can automatically remove and replace the data on the server.

It's good for reliability, timing, and simplification. For reliability, it's a logical construction that behaves productively. It's a critical system where timing and coordination are necessary. It also offers simplicity to design and analyze the system by clearly defining the relationship between events and conditions.

What needs improvement?

Sometimes we require extra storage for Zerto. 

For how long have I used the solution?

We have used Zerto for five to 10 months. 

What do I think about the stability of the solution?

Zerto is highly stable. We've never had any performance issues. 

What do I think about the scalability of the solution?

Zerto is scalable. 

How are customer service and support?

I rate Zerto 10 out of 10. Sometimes, we encounter errors, my manager talks with the support. They are helpful and always resolve our issues quickly.

How would you rate customer service and support?

Positive

What other advice do I have?

I rate Zerto nine out of 10. I would recommend Zerto. My sister company also plans to implement it. To those considering Zerto, I would suggest using the trial version. The UI seems complex the first few times you use it, but after you work with it a little, it's easy to understand. 

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
reviewer2507049 - PeerSpot reviewer
Chief Technology Officer at a healthcare company with 10,001+ employees
Real User
Faster and more cost-effective than other solutions
Pros and Cons
  • "The solution's most valuable features are its user interface, ease of implementation, and ease of execution."
  • "In the future, the tool's user interface needs to be refreshed since it seems to be becoming somewhat antiquated."

What is our primary use case?

I use the Zerto in my company for all of our applications built on it. There are around 1,600 applications.

How has it helped my organization?

Zerto has enabled us to move and replicate systems much faster than we ever had before. We could move entire data centers in six months versus what would have taken three years.

What is most valuable?

The solution's most valuable features are its user interface, ease of implementation, and ease of execution.

Zerto's near-synchronous replication works. I work in the healthcare industry, where systems have to be up and working and are mission-critical, and Zerto is a part of that journey.

I have used Zerto to help protect VMs in your environment.

Zerto is an effective tool for bringing systems back at a pace. The limiting factor in Zerto is sometimes the application, but it has certainly allowed us to deliver more streamlined SLAs to our business.

In terms of comparing the speed of recovery of Zerto versus the speed of recovery with other disaster recovery solutions that I have used, I can say that my company moved from an old Commvault-based solution to a Zerto-based solution since the latter was far superior to the former.

Based on my usage or evaluations of other solutions, I would compare the ease of use Zerto provides with a product named Commvault. Compared to Commvault, Zerto is faster and more cost-effective.

What needs improvement?

Zerto can reduce its price.

In the future, the tool's user interface needs to be refreshed since it seems to be becoming somewhat antiquated.

For how long have I used the solution?

I have been using Zerto since 2017.

What do I think about the stability of the solution?

The tool has been 100 percent stable for our company. In reality, the tool has been up since 2017.

What do I think about the scalability of the solution?

I have not seen any problems with the product's scalability, especially since we run 1,600 applications with it. There don't seem to be any problems with scaling up.

How are customer service and support?

The solution's technical support is excellent. The tool's technical support team is responsive, easy to get a hold of, and kind, and the team also listens. I rate the technical support a nine out of ten. For me, to rate the support team ten out of ten, in a perfect world, there are more SLAs at fixed times.

How would you rate customer service and support?

Positive

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

I have used Commvault. My company chose Zerto because it was modern and easy to implement, and the demonstrations we saw indicated that it should be part of our organization's future.

How was the initial setup?

The product's ease of setup made things straightforward, especially with good customer support, and backup when trying to get it all implemented.

My company uses the hybrid cloud services offered by GCP but hasn't added Zerto to it. My company also uses AWS and Microsoft Azure, but we haven't added Zerto to it.

What about the implementation team?

For the setup phase, my company bought some professional services because, obviously, my team hadn't had training, but now they are trained. My company bought some professional services, and my team got some hands-on training, so we now run the system in-house. I believe that Zerto's team should receive more training about the tool. I rate my experience with the tool's system integrator, WWT, as seven out of ten.

What was our ROI?

It offers more cost-avoidance than the return on investment, although the return on investment is possible to a certain extent.

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

At the time I had purchased the product, the pricing was fair and reasonable. Over the years, costs have certainly gone up, which makes it hard for healthcare companies to use the solution.

What other advice do I have?

I believe that Zerto's team should have more training.

I rate the tool a nine out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud

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

Google
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
BartHeungens - PeerSpot reviewer
IT Specialist at Bitcon
Real User
Top 5
Our recovery time went from hours to seconds and our DR testing is all automated
Pros and Cons
  • "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."
  • "The native Zerto implementation requires quite a big environment. My environment is rather small. I do not have hundreds of virtual machines."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using Zerto for two years.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are customer service and support?

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.

How would you rate customer service and support?

Positive

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

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.

How was the initial setup?

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.

What about the implementation team?

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.

What was our ROI?

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.

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

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.

Which other solutions did I evaluate?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Support Engineer at BIOS Middle East
Real User
Top 20
Helps block unknown threats, ensures minimal downtime, and fast recovery times
Pros and Cons
  • "Zerto's user-friendliness is valuable."
  • "It would be great if Zerto could automate replication more."

What is our primary use case?

We use Zerto for replication.

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

How has it helped my organization?

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.

What is most valuable?

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

What needs improvement?

It would be great if Zerto could automate replication more.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

How are customer service and support?

The technical support is good.

How would you rate customer service and support?

Positive

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

I also use Carbonite but Zerto offers faster speeds.

How was the initial setup?

The deployment of Zerto took a few weeks.

What other advice do I have?

I would rate Zerto nine out of ten.

We have over 300 clients using our web applications.

Which deployment model are you using for this solution?

Hybrid Cloud

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

Other
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Accountant at TEE TEE
Real User
Helps our organization block threats, is user-friendly, and effective in storage
Pros and Cons
  • "Zerto is truly inspiring."
  • "The performance was generally good, but occasional lag disrupted the flow, leaving room for improvement."

What is our primary use case?

I use Zerto to store and protect my files. Whether I'm working on a project or just need to access old files, Zerto ensures everything is safe. This makes it very convenient, as I can easily access any information I need with just a single click.

How has it helped my organization?

Zerto is effective at blocking unknown threats and attacks. We might consider using it on the business website as well, but it's important to understand how it might impact our operations. It helps with blocking threats, which is certainly valuable. So, in terms of its effectiveness, I'd say it's close to 99% guaranteed.

Zerto has helped our organization block threats, is user-friendly, is effective in storage, and inspires users.

Zerto's Cloud disaster recovery is impressive, and recovering most of our data can be relatively straightforward. However, it requires careful planning and understanding. Navigating the recovery site is crucial, so ensure we read and comprehend the instructions thoroughly before clicking anything. This way, we'll know which box to choose and where to click to achieve our desired outcome.

It is easy to migrate data using Zerto.

It helps reduce downtime.

It has helped reduce our disaster recovery time. Before Zerto, we needed ten people for disaster recovery and now with Zerto, we are down to three. 

What is most valuable?

Zerto is truly inspiring. Sometimes, when I provide information and receive it back, it can be remarkably refreshing and motivate me to get the most out of it. There might be instances where I initially think something isn't applicable, but then I try it out and say "wow" as I realize I am getting something positive from it. it becomes quite inspiring and brings out my best creative potential. Witnessing these features makes me naturally want to explore and create more.

What needs improvement?

The performance was generally good, but occasional lag disrupted the flow, leaving room for improvement.

For how long have I used the solution?

I have been using Zerto for four months.

What do I think about the stability of the solution?

While Zerto is stable, it can sometimes be slow to retrieve the data we need.

What do I think about the scalability of the solution?

Zerto is scalable.

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

We used to complete tasks manually, which consumed a lot of manpower, before adopting Zerto.

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

Zerto is affordable.

What other advice do I have?

I would rate Zerto a nine out of ten.

No matter what we choose to do, there will always be potential positives and negatives. When aiming for the best outcome, focus on visualizing success and avoid dwelling on negativity. However, even while striving for the positive, acknowledge that occasional setbacks like technology issues or unexpected problems might occur. Don't get discouraged in the present; trust that Zerto will ultimately lead to something beneficial and fulfilling.

Which deployment model are you using for this solution?

Public Cloud

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

Google
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Buyer's Guide
Download our free HPE Zerto Software Report and get advice and tips from experienced pros sharing their opinions.
Updated: September 2025
Buyer's Guide
Download our free HPE Zerto Software Report and get advice and tips from experienced pros sharing their opinions.