Our use case is 100 percent disaster recovery between two different geographies. We have a very large private cloud offering. We've got about 1,200 customers and almost 10,000 VMs that are under Zerto protection. Every one of those virtual machines needs to be replicated from Waltham to Chicago, from the East Coast of the U.S. to the central U.S. Likewise, we have a European business with the exact same flow, although it's much smaller as far as number of VMs; it might be a couple of hundred. That implementation is going from Berlin to Amsterdam. We've got one-way protection in two different geographies and all of those machines are under Zerto protection.
Systems Architect - Cloud at a computer software company with 5,001-10,000 employees
We are able to show, at a customer-level of granularity, what a customer's RPO was at any point, in real time
Pros and Cons
- "Four years ago when we did a PoC between two other vendors and Zerto, there were two features of Zerto that sold it, hands-down. One was the ease of creating protection groups, the ease with which our engineers could create protection, add virtual machines into the Zerto product, and get them under DR protection."
- "The second feature that sold us was the sub-second RPO. One of the things that made Zerto's product stand out from some of the more traditional solutions four years ago was its ability to maintain sub-second RPO over a group of machines, and that group of machines could be spread over multiple storage hardware."
- "The number-one area in which they need to improve their product is what I would call "automatic self-healing." This is related to running them at scale... We have 1,000 VRAs and if any one of their VRAs has a problem, goes offline, all of the customer protection groups and all of the customers that are tied to that VRA are not replicating at all. That means the RPO is slipping until somebody makes a manual effort to fix the issue. It has become a full-time job at my company for somebody to keep Zerto running all the time, everywhere, and to keep all the customers up and going."
What is our primary use case?
How has it helped my organization?
The number-one benefit is that for the first time we could show, at a customer-level of granularity, how a customer was protected, and what their RPO was in, real time. Each one of our 1,200 or so customers has a portion of those 10,000 VMs. For the first time we were able to tell a product leader or product manager what the RPO was on Thursday at 2:00 PM for that customer. We could say, "Hey, it was 67 seconds." Our company is very customer-centric and customer-focused. There's less interest in what the overall health is, and a lot of times there's specific interest in, "Hey, how is that customer doing?" either for performance or for RPO time.
Zerto also allowed us to easily pick groups of virtual machines, group them as a whole, and have that be segregated from the storage layer. That is the storage-agnostic benefit from their product. That agnostic feature with respect to the storage layer allowed us to group VMs by customer and not only report on RPO by customer, but also to more easily sell different RPO plans. We were able to prioritize and say, "Okay, these 10 customers have platinum and these 500 have silver."
What is most valuable?
Four years ago when we did a PoC between two other vendors and Zerto, there were two features of Zerto that sold it, hands-down. One was the ease of creating protection groups, the ease with which our engineers could create protection, add virtual machines into the Zerto product, and get them under DR protection. The other products we were looking at required work from two different teams. The storage team had to get involved. With this product, the whole thing could be done by just our virtualization team, and that was a big sell for us.
The second feature that sold us was the sub-second RPO. One of the things that made Zerto's product stand out from some of the more traditional solutions four years ago was its ability to maintain sub-second RPO over a group of machines, and that group of machines could be spread over multiple storage hardware. It was the storage-agnostic features of the product.
What needs improvement?
The number-one area in which they need to improve their product is what I would call "automatic self-healing." This is related to running them at scale. If you're a small company with 50 VMs, this doesn't really become a problem for you. You don't have 1,000 blades and 1,000 of their VRAs running that you need to keep healthy. But once you get over a certain scale, it becomes a full-time job for someone to keep their products humming. We have 1,000 VRAs and if any one of their VRAs has a problem, goes offline, all of the customer protection groups and all of the customers that are tied to that VRA are not replicating at all. That means the RPO is slipping until somebody makes a manual effort to fix the issue. It has become a full-time job at my company for somebody to keep Zerto running all the time, everywhere, and to keep all the customers up and going.
They desperately need to work self-healing into the core product. If a VRA has a problem, the product needs to be able to take some sort of measure to self-heal from that; to reassign protection. Right now it doesn't do anything in that self-healing area.
Buyer's Guide
Zerto
August 2024
![PeerSpot Buyer's Guide](https://www.peerspot.com/images/peerspot_logo_lt.png)
Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: August 2024.
800,688 professionals have used our research since 2012.
For how long have I used the solution?
My company implemented Zerto in 2016, so we've been live with their product for a little over four years.
What do I think about the stability of the solution?
The stability comes back to size and scale. It depends. If you are not replicating heavy workloads—meaning you don't have a SQL server that's doing thousands and thousands of IOPS, and you don't have multiple SQL Servers on the same very large hardware blade—Zerto is incredibly stable, based on my experience with the product.
However, we are doing that. There's a one-to-one relationship between the Zerto VRA, which is essentially their chunk of code that does the replication, and a physical server. The physical server is running anywhere from one to as many virtual servers as someone can fit onto it. And that one VRA has to manage and push all the change blocks for all the workloads running on it. So if you've got five or six really heavy workloads running, that one VRA that has to handle all of that and push it to your destination can, and does, crash. VRAs in that situation crash or become unstable. We've worked a lot with Zerto over the last two years on tweaking the VRAs with advanced settings. We've directly been involved with identifying a couple of bugs with the VRAs. When the VRAs are pushed, they can only be pushed so far and then they crash.
It does perform. However, we have VRAs that crash all the time. When we go back and we look at why they crashed it's because we're pushing them too hard. We're doing things that they would say we shouldn't be doing. They would say, "Don't set six SQL Servers on the same blade. That's too much. Don't do that."
Zerto has worked with us very effectively on identifying advanced settings that we can make to the VRAs to make them perform better, and to be more stable in the "abusive" environment that we throw at their code base.
It could be more stable for really heavy use cases like that. But Zerto would come back and say, "Well, our best practices would have you put some sort of anti-affinity rule in place so that you don't end up with that many heavy I/O machines on a single blade." They would say that doing so is not best practice; don't do it. You could say that we abused their product, in that sense.
But it works. If you align with best practices, it's pretty stable.
What do I think about the scalability of the solution?
We have no concerns about the scalability, although I should qualify that statement. Zerto can scale horizontally extremely well. They've got one VRA per blade and that one VRA is their data plane. You can scale out your environment horizontally with as many blades or servers as you want, which is how people do virtualization and Zerto will scale with you. We've never hit a limit as far as its ability to scale as horizontally.
The caveat would be, as I mentioned elsewhere, the size of the pipe in your infrastructure to handle all of that replication. But that doesn't tie to the Zerto product itself.
In terms of the issue of VRAs crashing, you want to scale horizontally rather than scale vertically, because if you scale vertically you're packing more and more virtual machines into the same number of physical servers. You're stacking them up high rather than across. If you stack them up high you have concerns about the scalability of the single VRA. The VRAs do get overloaded. Don't pack them too high. Scale out, not up.
Zerto has spread out as a company. They've mushroomed out into other areas. They've started to develop a presence in backup and they've started to develop a larger presence in reporting. Their core product, however, is known as ZVR—Zerto Virtual Replication. We've implemented that core product 100 percent. There's no other way we could be consuming it differently or more effectively.
The newer stuff they've come out with—certainly the backup—we don't touch that at all. The backup product is not ready for prime time. It might be good for a small customer that may have 50 machines they want to back up. But for our use case, with SOC compliance, and having to report on the success of backups for recovery, and although we looked very closely at their backup and where they were going with it, it's not ready for us.
They're starting to go into Docker containers. None of our product right now is containerized.
A third area is analytics and reporting. The analytics and reporting would be the one new area that they've put focus on that we could be using more and getting more value out of. They've got a SaaS solution now for reporting called Zerto Analytics. We do use it. You turn on their core product and you tell it to send your reports to their SaaS offering. We've done that and we can consume the analytics product, but we just haven't really operationalized it yet. That, for us, has been a tool looking for a problem.
How was the initial setup?
It took us about two months to deploy the solution, but that was because we're a very conservative company. We purposely went extremely slowly. If we had wanted to go faster, it could have been done probably in a week or two, to get all 6,000 VMs under protection.
What about the implementation team?
When we deployed it, there were two dedicated people at our company who were involved, paired up with three people from a Professional Services team from Zerto. As a tertiary, we had a full-time person from our VAR, the reseller that sold us the licensing for Zerto. With that help from Zerto and the value added reseller, it only took two of us to install it to about 600 blades and probably 5,000 virtual machines.
Our experience was excellent. Both teams were great. It was a very painless rollout.
What's my experience with pricing, setup cost, and licensing?
I'm less involved with the pricing and licensing area now. The last time I was involved was a couple of years ago. In my opinion, their model is somewhat inflexible, especially for their backup product.
One of the reasons why we didn't pursue looking further at their backup product was, simply, licensing. Today we have to buy a Zerto license for every virtual machine that we want protected by their product. We have a lot of virtual machines that aren't production and that don't need to be protected by their product. They don't need sub-second RPOs. They do, however, need to be backed up. But Zerto's licensing model two years ago was, "Well, we don't care that you just need to back up those VMs, and you don't really need to replicate them. It's the same price."
We would have had to double our licensing costs for Zerto to adopt it as a backup solution. It was just not even within the realm of possibility financially. It made no financial sense for us to move off our current backup vendor. Their inability to diverge in any way from that was rigid.
Their licensing could be less rigid and more open to specific companies' use cases.
Which other solutions did I evaluate?
The other two vendors we evaluated back were Site Recovery Manager by VMware, and whatever Veeam's product was at the time. We also looked at CommVault lightly, but they were never considered seriously.
What other advice do I have?
Zerto can do what it says it can do. It can absolutely provide sub-second recovery point objectives, but with a couple of caveats. The caveats tend to apply to large companies like mine, and by "large" I mean if you have over 2,000 to 3,000 virtual machines, versus a small to medium-sized company that maybe has 50 to 500. Once you cross that barrier, you're getting into a larger environment that you're trying to replicate with Zerto.
A couple things can break down. Zerto's product doesn't control the path between your source production data and the destination you're trying to send it to. There can be tons of bottlenecks on that path; you can be going around the world. If the bottleneck doesn't exist there, their product can absolutely do what it says it does. It's up to the customer. The people using Zerto have to understand that they own the bottlenecks in their environment. If there is a bottleneck between production and the targeted DR, the RPOs are going to slip. You're going to go from sub-seconds to minutes or hours. That's not necessarily a fault of Zerto's product. It's the fault of the design of the customer's environment and what they brought it into.
That doesn't just exist for the pipe between the two sites. On the destination side, the side that's receiving this data, the storage layer underneath needs to be more performant than the production side. That's somewhat of a strange concept for a lot of customers and people coming into the Zerto solution. They see the marketing side of, "10 seconds to RPO" and say, "Yeah, I want that." But what it means is that you've really got to look at your hardware and you've got to have class-A hardware the whole way through that Zerto pipeline, for their product to do what it says it does. Zerto makes that very clear. They don't recommend hardware; they're not in the business of supporting other vendors. But they have a published list of best practices. The best practices clearly say everything that I just said. They also have best practices around managing your workload I/O on the source side, so that you don't overwhelm their product.
But not everyone follows best practices. Certainly, when we implemented it we said, "Yeah, we get that. We understand what you're telling us. We understand that's a best practice, but we're not going to do it anyway, because it's too expensive," or we didn't have it in budget for that year. So we knew it and we went in without following them. A couple of years later, when we got to a tipping point, we realized, "Okay, we need to go back and align with some of those best practices," things we didn't think that we had the time to align with back in 2016. We've made that journey painfully with their product, but they were very upfront with us on what the requirements for their product would be.
Overall, I would rate Zerto as a solid eight out of 10 for the core disaster recovery offering.
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.
System Engineer at American Medical Response
Enables us to move an VM from our old environment to our new environment with minimal disruption
Pros and Cons
- "The Move feature is the most valuable feature because it allows us to move the VM from our old environment to our new environment with minimal disruption."
- "Some of the features need improvement. One would be, as you're creating a Move group or a VPG, as they call it, it should either autosave or have the ability so that you can save it for coming back to later because if the setup times out, you lose all your work. That would be a nice improvement to have."
What is our primary use case?
We use Zerto for data migrations. We use it to move our virtual machines from one location or data center to another and eventually, we then switch that over to DR from our facility in one state to another. It's for the migration of existing VMs.
How has it helped my organization?
Zerto has improved my organization by allowing us to do several VM moves. It simply allows us to bring a server back up on the new side, which looks like a reboot of a server. It's a virtual move to the new stage, so it goes from existing VM host to new VM host on the other side.
It has reduced downtime for the servers that we migrate over. By how much is a hard number to put because we do a big group of them together, so we're able to group the move as opposed to doing more one-offs.
The amount the downtime would cost my company would strictly depend upon which servers we were moving because some don't really cost the business. There are others that would cost the business for having to be up as much as possible, 24/7.
What is most valuable?
The Move feature is the most valuable feature because it allows us to move the VM from our old environment to our new environment with minimal disruption.
It's extremely easy to use. It's pretty self-explanatory as you run through setting up your VPGs for your protection groups and then to do a migration or a test failover.
What needs improvement?
Some of the features need improvement. One would be, as you're creating a Move group or a VPG, as they call it, it should either autosave or have the ability so that you can save it for coming back to later because if the setup times out, you lose all your work. That would be a nice improvement to have.
For how long have I used the solution?
We have been using Zerto for three months.
What do I think about the stability of the solution?
So far, the stability has been great. We have not had any issues with that.
What do I think about the scalability of the solution?
Only two of us work on it and we're both system engineers.
We do not need dedicated staff for deployment and maintenance of the solution.
It's being used to move a total of around a couple of thousand VMs, so I don't have any issues with scalability.
Currently, we aren't planning to expand capacity because we have a total of around 500 agents to protect, so until we get the true DR, we will have to evaluate if we need to expand that. We will primarily only be using it for DR and any server migrations we may need to do from one system to another.
How are customer service and technical support?
Their technical support has been very good and prompt to get back to us with answers.
Which solution did I use previously and why did I switch?
We would either use a Veeam or VMware solution, but we haven't had a real DR product outside of Veeam.
We find Zerto to be the most beneficial right now in helping us migrate from one data center to another data center for the testing environment. And for future capabilities, for a true DR scenario.
I would say it's a lot more simple to set up and maintain than VMware and Veeam.
Replacing these legacy solutions has saved us on the costs needed to manage them.
How was the initial setup?
The implementation was really straightforward and easy. We worked with one of their support engineers and we got it up and running really quickly. The deployment took around one hour.
We didn't really have an implementation strategy. It was about getting the server manager and server up and then walk through the installation steps. We followed their guidelines.
What was our ROI?
I'm not sure if I can put a dollar amount on ROI but the biggest return is time to actually get things set up and then begin to migrate virtual machines over to the new environment.
What's my experience with pricing, setup cost, and licensing?
I'm not 100% sure about the pricing because I wasn't as much part of the pricing part of it, but it fell within our budget. Its features and price are good compared to the options we were looking at.
Which other solutions did I evaluate?
We also evaluated Rubrik and a solution from Dell. The main advantage that we found was that Zerto fit our current need for migrating from one environment to another better than others, and its good standing in the community where there are a few products.
What other advice do I have?
My advice would be to plan out your Move groups and work with your business to get everything validated so you can back up on the other side.
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.
Buyer's Guide
Zerto
August 2024
![PeerSpot Buyer's Guide](https://www.peerspot.com/images/peerspot_logo_lt.png)
Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: August 2024.
800,688 professionals have used our research since 2012.
IT Manager at a insurance company with 201-500 employees
Easy to use with a straightforward interface and menus, and provides excellent analytics, reporting, and monitoring
Pros and Cons
- "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."
- "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."
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
We've been using the solution for two years.
What do I think about the stability of the solution?
The stability is acceptable, we experienced an issue once, but the backup time is speedy.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What about the implementation team?
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.
What was our ROI?
We have seen an ROI with Zerto.
What's my experience with pricing, setup cost, and licensing?
The pricing is slightly above average, but the immediate and comprehensive support makes the price acceptable.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
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.
Last updated: Aug 28, 2024
Flag as inappropriateSpecialist supervisor at a financial services firm with 201-500 employees
Primarily used for DR situations and provides real-time backup and high uptime
Pros and Cons
- "It provides real-time backup"
- "It is a little expensive."
What is our primary use case?
We use it primarily for DR situations. Whenever we lose our primary location, we switch to another location. We also backup resources and migrating VMs in and out of different environments, cloud versus on-prem.
What is most valuable?
The most valuable feature is that it provides real-time backup. We're in the financial industry and have to have 100 percent uptime.
It helps us have a lot better uptime than what we would normally have. It's always real-time synced, with instant recovery. We can return to another location if power drops or generators don't work.
It gives us quick uptime. It also helps our customers maintain that trust, so Zerto really does help with trust. We generally use it on-premise.
The near-synchronous replication is really good. It gives us quick uptime. It helps our customers keep that trust in us.
We use Zerto to protect VMs in our environment. Until Zerto, I didn't pay much attention to RPOs. Zerto gives the ability to bring RPOs down to seconds.
For certain use cases, Zerto has a better speed of recovery compared to other solutions but it doesn't tie into our SANs like Veeam does.
What needs improvement?
It is a little expensive.
We could streamline the installation better. The other thing would be ransomware notifications, like IO anomaly notifications. If they integrate with the SAN, that would be valuable to see in terms of snapshots.
For how long have I used the solution?
I have been using Zerto for six to seven years.
What do I think about the stability of the solution?
We came up with the new version, and it's pretty good. If there's no reason for me to say it's unstable. It's been proven so far.
What do I think about the scalability of the solution?
If you buy the licensing, it will scale up to size until you will spend money on it.
How are customer service and support?
Support is helpful.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
If you want to pull from the snapshot instead of tools, then SRMs are better used for this case. It's fast and the first to market with continuous data protection.
Zerto is easier to use. There is some standup at the beginning, you must install the agents. It's easy to use when it's working right, but sometimes, it takes great effort to get it going if something goes down.
We use another solution, Veeam. We keep them both because they're both beneficial for different use cases.
How was the initial setup?
The initial setup is straightforward, but if you have it the first time, you are stranded in the industry. It could take a little figuring out, but Zerto is pretty helpful.
There have been a couple of situations which they weren't able to fix an issue right away. We move everything off to a different server until we can circle around and extend that one.
What about the implementation team?
We did it in-house.
What was our ROI?
Zerto has paid for itself in man-hours saved.
What other advice do I have?
Zerto gives you the ability to bring RPOs in seconds. We can have instant uptime for everything.
It's more expensive than other solutions but it's worth it for our environment. It has made it very easy to restore files because you can restore them down to the second. It's pretty simple. We have the agent and all the hosts.
Overall, I rate the solution an eight out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Last updated: Jul 15, 2024
Flag as inappropriateInfrastructure Architect at Krish Services Group, Inc
Application-agnostic, easy to use, and helpful for improving RPO
Pros and Cons
- "The simplicity of use is valuable. It is easy. We just click Failover and do it. It is pretty straightforward. If someone wants to do a test failover, they log in to the console and do a test failover"
- "I would like to request better reporting in Zerto. I can see the data that I need in the console, but if I need to put the data or the history into a report, it is difficult. It is something that auditors might require, so reporting is something that needs to be improved."
What is our primary use case?
We are using it for disaster recovery.
How has it helped my organization?
Zerto provides near-synchronous replication, but more importantly, we can see the status at seven seconds, six seconds, five seconds, and four seconds when we log in to the Zerto console. I found that amazing. There is probably no other disaster recovery solution available in the market that is providing this functionality. It is great and definitely a huge plus point for Zerto.
We do get alerts if suspicious activity is detected on a VPG, but we did not get an actual case where there was ransomware or any other kind of attack and we had to prevent that. I have not come across that with either of my clients, but we do get alerts when Zerto finds something suspicious. We go in and look at it. In some instances, because the application was writing more files, Zerto marked it as suspicious, but we never had to do recovery for security reasons.
We use Zerto with AWS as the target. We do the failover of the on-premises VMware virtual machines to the AWS cloud. I do not deal with the implementation. I only do the administration of the tool, but whatever I did as part of AWS administration in Zerto, it was pretty seamless and straightforward. I did not get any issues there. The documentation is helpful in identifying any issues.
We have about 70 virtual machines that are being protected by using Zerto. Zerto has drastically improved our RPO. It was 15 minutes previously, whereas now, it is in seconds.
Zerto has not had much impact on our RTO. RPO has changed, but RTO has been the same for us.
Zerto has not helped to reduce downtime in any situation. We have only done tests. We have not done any actual production failover because there was no need. Similarly, Zerto has not saved us any recovery time because we never had a requirement to do a recovery since we implemented the tool. It is a pretty new environment for us, so we have not had time.
Zerto has not reduced the number of staff involved in overall backup and DR management. It has remained the same for us.
What is most valuable?
The simplicity of use is valuable. It is easy. We just click Failover and do it. It is pretty straightforward. If someone wants to do a test failover, they log in to the console and do a test failover.
What needs improvement?
As a power user, I find the customization lacking. I feel it could be customized a little bit more, but Zerto is simple to use. It is easy to use. That is my main reason for using Zerto.
I would like to request better reporting in Zerto. I can see the data that I need in the console, but if I need to put the data or the history into a report, it is difficult. It is something that auditors might require, so reporting is something that needs to be improved.
The UI does crash a lot, and that is something that can be improved.
For how long have I used the solution?
It has been about a year. I support multiple clients with multiple backup and disaster recovery products. I was a Storage and Backup engineer, but now, I am covering the solutions for the entire infrastructure. I work on Zerto for multiple clients. We have two clients who are using Zerto as a disaster recovery solution.
What do I think about the stability of the solution?
The UI does crash, but it does not affect the functionality of the software.
What do I think about the scalability of the solution?
It is scalable. There could be 10 machines or 100 machines. I did not find any issues. It is pretty scalable.
How are customer service and support?
There were some issues for which we had to get responses from them. They were pretty much on the point. There were no issues. The response time was a bit slow, but their support was pretty good. I would rate them an eight out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We used to use Azure Site Recovery to protect all of the production instances, SAP databases, some file servers, and some basic application servers. We used to first replicate to Azure and then do a test failover and a production failover. It was a bit slow. The RPOs and RTOs were not that great, and the rate of change that Azure Site Recovery supported was not completely meeting the business requirements. The third part was that Azure Site Recovery was not application-agnostic. What we loved about Zerto was that it was application-agnostic. It did not matter to Zerto what was running behind the application. It will replicate everything across any cloud. That was our main point for going for Zerto.
Zerto was also much easier. Azure Site Recovery was a little bit hard to set up and maintain, but Zerto is pretty straightforward and easy.
I did not find much difference between Zerto and other solutions in terms of the speed of recovery. The RPO is great, but when we do a failover, it is basically the same as any other solution.
Zerto has not replaced our legacy backup solutions. Our legacy backup solution is in the same place. We are only using Zerto for DR.
How was the initial setup?
Our environment is hybrid. We are using Zerto to protect our on-prem as well as the cloud environment, but I was not involved in its deployment.
In terms of maintenance, I never had any requirements to maintain it.
Which other solutions did I evaluate?
Evaluation was done by someone else in the organization.
What other advice do I have?
I would rate Zerto an eight out of ten. Simplicity is an advantage, but customization and reporting can be better.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
Last updated: Feb 27, 2024
Flag as inappropriateServer Administrator at a government with 1,001-5,000 employees
It enables us to set the IPs and map everything out in our environment prior to migration
Pros and Cons
- "Zerto is intuitive. We could set everything up in the environment within a day and a half and start migrating on the third day."
- "Right now, if you have an error, it creates a link that takes you to a website to review information about the problem. It would be nice if Zerto could give you information within the app instead of referring you to a web application."
What is our primary use case?
We've been using Zerto for data center migration, but we will begin using it for disaster recovery. Because of some data center issues, we're still using version 9.5. One of our data centers is at 6.5 and the other one is at 7, so we can't move any or upgrade to 10.
What is most valuable?
Zerto enables us to set the IPs and map everything out in our environment prior to migration. We can create VPGs and mass migrate applications, databases, and web clients. That was the selling point for us. The product is easy to use. We had a 30-minute onboarding process from our sales engineer, who showed us how to use it.
We don't use near-synchronous replication yet. It will be essential when we start using Zerto for DR, but it isn't a big deal during our current migration. Once we have a DR site, it will be essential to have those time slots we can restore to in the event of malware and ransomware.
What needs improvement?
Right now, if you have an error, it creates a link that takes you to a website to review information about the problem. It would be nice if Zerto could give you information within the app instead of referring you to a web application.
For how long have I used the solution?
Zerto for two years.
How was the initial setup?
Zerto is intuitive. We could set everything up in the environment within a day and a half and start migrating on the third day.
What other advice do I have?
I rate Zerto 10 out of 10.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Lead Systems Engineer at a financial services firm with 51-200 employees
Good for protecting VMs, has useful, near-synchronous replication and helpful documentation
Pros and Cons
- "The time it takes to fail a server over to DR has been great."
- "There are a lot of features that it has that we don't use since we are on prem."
What is our primary use case?
I use Zerto for disaster recovery.
How has it helped my organization?
The time it takes to fail a server over to DR has been great. We've seen a reduction in time spent. We can do it in minutes. Being able to go back to certain snapshots, to failover to another location, and then go back to specific snapshots is quite useful. We can roll back easily.
What is most valuable?
The off-site replication is excellent. We have workloads that aren't DR-aware. Being able to replicate it to other data centers is great. We don't have another way to do it, currently.
The near-synchronous replication is good. You get five-second data points. It's not something we advertise to our customers, the developers, however, we've had instances where we needed to go back two hours, prior to a file being deleted, and it's helped.
We're protecting our VMs with Zerto. It's positively affected our RPOs. It meets the objective. It's the only way we can have a solution for certain applications where we send an entire application to another data server.
What needs improvement?
It's a great product. There are a lot of features that it has that we don't use since we are on prem. We strictly use it for DR between our data centers. There are a lot of cloud plugins that they have that we don't use. Our use case is limited. It does everything we need it to.
For how long have I used the solution?
I've been using the solution for probably four or five years.
What do I think about the stability of the solution?
The stability of Zerto is good. We didn't have any issues. Our biggest challenge was trying to get to the clients and I was waiting on an upgrade path - from Windows to Linux. Now there is an upgrade path. Honestly, that has been the biggest challenge we've had for five years.
What do I think about the scalability of the solution?
The scalability of Zerto is good. You can easily protect other clusters and VRAs. It's very flexible.
Our current environment has 45 VRAs in each cluster. We have two replica pairs, two sites that mirror each other.
In total, we have 70 ESX hosts.
How are customer service and support?
Technical support is great. They've shown us many things about the manager that we didn't know about. Every time I call, I take notes. They are very knowledgeable and the knowledge-based articles on the site are also helpful. Even if I thought something was broken, they've always managed to fix it.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We used to use VMware's SRM. With SRM, for us, it was overly complex. We used an array-based replication with SRM. We had issues where the storage team would go to do work on the array and they would fail the machine over and it wouldn't be right. We would have outages. Every time we did a failover it was a process and we would be missing rules.
This is not array-based and we can test our failover in a sandbox without taking the system down.
How was the initial setup?
The initial deployment was easy. We deployed VRAs to the host from the manager. It works very well. The amount of VRAs you have to deploy and the amount of time it takes is minimal. It took us about an hour.
What was our ROI?
I can't speak to if the company has witnessed any ROI.
What's my experience with pricing, setup cost, and licensing?
I don't follow the licensing. It was bought for us and we use it.
Which other solutions did I evaluate?
We evaluated SRM and a few others. I can't remember which ones we tested. We've been on Zerto since version six.
The selling point for us, coming from SRM, is that SRM was tied to vCenter. We had to pay attention to versions and there were a lot of ways you had to make sure the versions were correct and it was overly complex for what we needed. We simply needed to replicate a virtual machine and that was it. Zerto stood out as it was easy.
What other advice do I have?
I'd recommend the solution to others. I'd rate the solution ten out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
VMware Engineer Infrastructure Team at a financial services firm with 10,001+ employees
Scalable solution that reduces downtime during migrations
Pros and Cons
- "The ease of use and simplicity in moving things without having to do a cross-v set of V-motions has been most valuable. It saves time and effort and it eliminates mistakes."
- "The licensing is confusing and complicated."
What is our primary use case?
Our main use case for this solution is the data center migration. We are in the process of moving from our legacy data center and all the VMs into our new data center.
In the future, we would like to look more into disaster recovery using Zerto but that's a much longer process and we are still looking into it.
How has it helped my organization?
The speed of recovery with Zerto is at least five to ten times faster. It helped us reduce downtime during migrations. There would've been a lot more downtime had we done a standard migration across data centers, powering everything down. This downtime would have cost our company millions.
What is most valuable?
The ease of use and simplicity in moving things without having to do a cross vCenter V-motions has been most valuable. It saves time and effort and it eliminates mistakes. This project would've been years if not for Zerto. We completed it in months instead of years.
What needs improvement?
The licensing is confusing and complicated.
For how long have I used the solution?
I have been using this solution for two years.
What do I think about the stability of the solution?
This is a stable solution.
What do I think about the scalability of the solution?
This is a scalable solution. We used it for our biggest data center and it handled it just fine. We haven't personally had to scale it up, but if we needed to, we definitely could.
How are customer service and support?
Support has been pretty good. I would rate it a nine out of ten.
Which solution did I use previously and why did I switch?
I personally have not used other solutions other than just what's built into VMware. When comparing the VMware native solution versus Zerto, it's night and day. It's much simpler and straightforward to set up.
How was the initial setup?
The initial setup is straightforward. It is streamlined with simple instructions. Anybody can do it as long as they understand their infrastructure.
What about the implementation team?
We had a contractor that we brought in to help us with it.
What was our ROI?
We have seen return in our investment with Zerto due to the speed and usability and being able to do this huge project with limited hiccups.
What other advice do I have?
I would advise others that the cost of this solution is justified based on the value you receive.
I would rate Zerto a nine out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
![PeerSpot user](https://www.peerspot.com/assets/media/images/anonymous_avatar_x50-87dfede4.png)
Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros
sharing their opinions.
Updated: August 2024
Popular Comparisons
Veeam Backup & Replication
Commvault Cloud
Rubrik
Acronis Cyber Protect
Veritas NetBackup
Cohesity DataProtect
Azure Backup
VMware Live Recovery
Dell PowerProtect Data Manager
Dell Avamar
Veeam Backup for Microsoft 365
Dell NetWorker
Veritas Backup Exec
NetApp Cloud Volumes ONTAP
IBM Spectrum Protect
Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Software replication to remote sites during disaster recovery?
- What are the differences between Zerto, VMware SRM and Veeam Backup & Replication?
- Why is disaster recovery important?
- Can Continuous Data Protection (CDP) replace traditional backup?
- Can you recommend a disaster recovery automation tool?
- How does Datto compare to ShadowProtect?
- What is the difference between cyber resilience and business continuity?
- When evaluating Disaster Recovery Software, what aspect do you think is the most important to look for?
- Internal vs External DR Site: Pros and cons
- Disaster Recovery Software: Which is the Best Solution in the Market?
An additional comment that Zerto has a Long Term Recovery option built in so you could eliminate Veeam. Basically we set up a storage array, assigned it a protected share, and created a Zerto repository on it. Now our back ups both short term and long term are covered. Zerto also has the ability to restore individual files. A nice software solution for whatever hardware you want to use.