While we primarily function as a service provider rather than serving a direct use case, our core focus lies in disaster recovery. We employ a rigorous testing process akin to gear testing and actively engage in recovery operations using Zerto for a diverse clientele, including numerous entities in the financial and government sectors.
Cloud Engineer at a healthcare company with 10,001+ employees
Shorter disaster recovery timelines have increased client confidence
Pros and Cons
- "The most valuable aspect of Zerto is synchronized replication, which is very useful."
- "Zerto has helped significantly reduce downtime and helped reduce DR testing by over 45 percent."
- "The main issue with Zerto is its user interface, which lacks flexibility and presents a steep learning curve."
- "The main issue with Zerto is its user interface, which lacks flexibility and presents a steep learning curve."
What is our primary use case?
How has it helped my organization?
Zerto is straightforward to use.
We started to see the full benefits of Zerto one month after the implementation.
The effort on the RPOs has been excellent, greatly enhancing our operations. We have a diverse range of customers who are quite satisfied and express confidence in the timeline for recovery.
Even Zerto's RTO is low.
Zerto has helped significantly reduce downtime and helped reduce DR testing by over 45 percent.
What is most valuable?
The most valuable aspect of Zerto is synchronized replication, which is very useful. Additionally, the availability of the virtual machines is quite good. Regarding the recovery point, we achieved at least ten recovery points, and the availability of the virtual machines is particularly notable.
What needs improvement?
The main issue with Zerto is its user interface, which lacks flexibility and presents a steep learning curve. To improve usability, the UI should be simplified and streamlined, making it more accessible to technical and non-technical users. Additionally, the UI should be better aligned with the platform's various options and features, ensuring a more intuitive and efficient user experience.
Buyer's Guide
Zerto
March 2025

Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
849,190 professionals have used our research since 2012.
For how long have I used the solution?
I have been using Zerto consistently for almost four and a half years.
What do I think about the stability of the solution?
Zerto continues to be a stable solution.
What do I think about the scalability of the solution?
Zerto is scalable.
How are customer service and support?
We interacted with technical support many times. They were totally fine and very polite. We receive support around the clock, which is excellent.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
How was the initial setup?
The initial setup of Zerto was straightforward, and their customer service was instrumental in helping us achieve a stable implementation within one month.
What about the implementation team?
A team of five implemented Zerto in-house.
What's my experience with pricing, setup cost, and licensing?
One of Zerto's main disadvantages is its pricing structure, which involves significant upfront costs and limited options for startups with minimal initial funding. Although Zerto offers a comprehensive suite of features, the high cost and lack of flexible payment options, such as pay-as-you-go subscriptions, present a barrier to entry for many businesses. To increase accessibility, Zerto should consider offering lower pricing tiers or more flexible subscription models tailored to startups' needs.
Which other solutions did I evaluate?
We evaluated a lot of different solutions.
What other advice do I have?
There are some disadvantages; therefore, I rate Zerto eight out of ten.
We are not a partner, just a customer, but we are trying to collaborate with them as a reseller within one year.
No maintenance has been required as of yet.
Which deployment model are you using for this solution?
Public Cloud
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: Jan 23, 2025
Flag as inappropriate
Disaster Recovery Engineer at a tech services company with 501-1,000 employees
Replicates and recovers within minutes and enables our growth
Pros and Cons
- "There are a lot of valuable features. The basics of what it does to replicate and recover things within minutes is awesome. It's far above anything that any of the competition has. We offer other disaster recovery software but primarily use Zerto for recovery times and the number of recovery points because of how fast and easy it is. It's so much better."
- "The problem with the backup product is that it's not very mature and you really need a specific use case to be able to use it effectively. It's hard to explain to our customers, especially our large customers, that the use case is so limited."
What is our primary use case?
Our primary use case for Zerto is for disaster recovery. In the last few versions, they've offered backup, but we don't use it because it's not nearly as robust as what most of our customers are looking for. We also use it for migrations too, to migrate customers into our cloud, and things like that. But that's around 20% of our use case.
How has it helped my organization?
Zerto has enabled our growth. Five years ago we had around 20 customers and now we have 500. We protect around 15,000 VMs now.
What is most valuable?
One of the most valuable features is the analytics portal. It's still an evolving feature and has ways to go but we use that for monitoring because we have hundreds of sites. It's nice that all the alerts and everything is consolidated into that one site because we used to have to make sure that we were connected to many, many sites to make alerting work, which was a nightmare.
Our alerting is done through scripting too. They do have pre-canned alerting through but is not very robust and they're working on it. They actually included us in the study on it. For instance, if you were to have a problem at a certain site or something, there's no way that you could take it out of monitoring. If you were using their system, it would just flood you with alerts from all kinds of stuff from the site if it was down. It is great if a site is down and you don't expect it, but if you have planned maintenance, you don't want all of this coming in.
There are a lot of valuable features. The basics of what it does to replicate and recover things within minutes is awesome. It's far above anything that any of the competition has. We offer other disaster recovery software but primarily use Zerto for recovery times and the number of recovery points because of how fast and easy it is. It's so much better.
We reduced the number of people involved in recovery situations by using Zerto. We had another solution before and we had a small number of customers and it took the whole team to manage 20 customers. Now we have 400 to 500 customers and our team is relatively the same size. We're broken up into different teams, but when we managed it all ourselves with only 20 customers, we had four people. And now we have around 500 customers and we have around 20 team members.
What needs improvement?
Zerto has a really robust PowerShell and scripting that you can get lots of numbers out of but it's not exactly the easiest thing to do. Zerto has a few nice pre-canned reports but there is a need for more. Unless you script something, it's difficult to go in, click a button, and see the information that you may be looking for.
The problem with the backup product is that it's not very mature and you really need a specific use case to be able to use it effectively. It's hard to explain to our customers, especially our large customers, that the use case is so limited.
Zerto is very easy to use on the surface, especially if you're an enterprise customer, which is just like A to B replication or one site to two sites. As a cloud provider, they still have a lot of work to do. But for most customers, it would be fantastic. We have a lot of private clouds that are one site or two sites. So when it's not meshed like our larger environment is, it works fantastic. But when you get into the overall fully meshed model with vCD integration that we have, it doesn't work as well. I think Zerto is mostly concentrated on the enterprise customer and left the cloud providers by the wayside.
With the HP acquisition, product development has certainly accelerated. They recently released the first major half release and have put additional focus on cloud providers. Unfortunately, the major focus remains on Enterprise. Next year, they will force customers to move from Windows management VMs to Debian Linux. I can only hope they have a well-thought-out migration tool. My fear is that the cloud provider will be a secondary thought once again.
The major issue with Zerto development is that they refuse to patch the current software release and only patch the newest release. When you hit the bug, they expect you to upgrade right away. This is not an issue if you only have a hand full of sites. The issue when you have 100s is that there is no way to skip a minor release. Every multi-tenant customer you have must be upgraded to every minor release. Two to three upgrades every year for every customer is very intrusive and requires way more management effort than should be necessary. We often have a hand full of customers delaying the upgrade cycle and are forced to discontinue service to those customers. HP can surely develop a better model.
For how long have I used the solution?
I have been using Zerto for six and a half years. It's deployed on-premises, on the cloud, and we use it as a SaaS offering. We are the cloud provider. We also integrate with AWS and Azure.
What do I think about the stability of the solution?
It's a very stable solution, for the most part. They have a new release every six months and some releases are better than others as far as bugs. Sometimes those bugs have to do with something in Hyper-V, and sometimes they have something to do with VMware or vCenter. But many times, it's directly related to Zerto's problems. Usually, their major releases go in .0 and .5. The .0 releases have the new features in them and they're more buggy and the .5 releases are more stable.
What do I think about the scalability of the solution?
It's extremely scalable, in a small sense, but the problem is when you get very meshed, with 10 sites replicating to 10 sites, and each one of them is meshed in to be able to replicate it to the other one. Then scalability starts to become problematic.
The big thing is, we have a cloud manager that manages all our ZVMs, which enterprise customers probably wouldn't have. You can only upgrade half a release for each upgrade. So you couldn't go from Zerto 6 to Zerto 7. For instance, you have to go to 6.5 and then go to seven.
Trying to upgrade is not easy because every customer that's paired and replicating into those sites has to upgrade it in those steps. It takes us several months, twice a year, to get everybody upgraded. They have a portal called Cloud Control which makes things better as far as upgrades, but they recently broke it with version 7.5 by adding encryption. So it was useless. We just upgraded to a version in which it should be working again, so the next time we're going to try to use Cloud Control to upgrade. Hopefully, it will be better. We only really have one round of upgrades through Cloud Control to get an idea of how well it worked. 75% of the time, those upgrades work without problems.
How are customer service and support?
There was a time when they had customer service people just taking tickets and they couldn't really help you at all, which was terrible. Now, they have a level-one level-two-type model. The level-one guys are getting better, but as they grow, it can be difficult.
All of our engineers are certified and we would like to go straight to level two. A lot of times we waste a lot of time with level one, and then they put the ticket in the queue for level two. So it takes another day to get to level two unless we're really loud and escalating the ticket right away. The biggest problem that we have with Zerto is getting to level two. 90% of the time, because of our knowledge, level one is not useful to us. Although, it probably would be to the average customer.
Zerto really needs support dedicated to CSPs and large customers.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We switched from our previous solution because Zerto was so much easier than everything else that we saw. We have a team that does the tests. It was a pretty easy choice to move away from those platforms at the time and those platforms no longer exist. Today there are many alternative DRaaS solutions and we offer many of them. Zerto remains more mature and feature-rich than the competition though.
How was the initial setup?
The initial setup was pretty easy. You have to have connectivity between the sites that you're replicating, your production, and then your DR site or sites. Getting that connectivity is the biggest thing. Once that connectivity is there, it's fairly simple. You deploy Windows VM, put a small software package on it, and then pair the two. You do the same thing at the recovery site and once those sites are able to talk. In VMware, you install a VM on each ESX host that you need to replicate a VM on. Then you create a policy to do that replication. The replication policies work very well. Re-IP on failover if problematic.
The network connectivity takes the longest. It can take weeks, depending on what you have to do to connect the sites. It could be a couple of hours if you're just setting up a VPN. If you're putting in a circuit, it could take a very long time. That's the X factor with it, but assuming that's already there, within an hour you could be replicating data from one site to another.
ZCCs remain a major stumbling block. If the routing table has issues, the only fix is to delete all protection, redeploy the ZCC and rebuild. Again, avoid Zerto Cloud Manager until the product matures.
What about the implementation team?
We implemented the solution in-house.
What was our ROI?
We have seen an ROI. Otherwise, we wouldn't keep using it. The biggest thing is the number of VMs we can support with the staff that we have.
What's my experience with pricing, setup cost, and licensing?
The licensing is fair. We have an enterprise license in which Zerto gives us 20,000 licenses or something well above what they think we're going to sell for the year. Then all our customers pull from that pool and we resell the licenses. We may sell 50 licenses to a customer but at the start of their contract, they may only have 30 VMs ready for DR. We contract them for 50, but eventually, they'll get up to 50. So we don't have to go to the vendor and add and remove one license here or one license there all the time.
That part of it is easy, but we do have to license all of our sites once a year, which is a pain and all of our sites report to Zerto Analytics. I've been asking them for years since they started Zerto Analytics, why we can't just put our license key on analytics rather than logging into hundreds of sites and putting them in each site. That's a real beast. They definitely need to fix the part where the site licensing is terrible. As far as the licensing VMs to replicate, that's great. In version 9, Zerto plans on deploying a license server to address this.
Zerto 9 is out and there is still no customer-deployable license server. We regularly have issues with customers who cannot reach the Zerto license server. They cut you off at the knees after 14 days! HP really needs to work on this process.
Which other solutions did I evaluate?
Commvault was one of the big ones we looked at. Commvault is much more complex and expensive. We also looked at AWS and Azure. We offer a wide range of solutions.
Recently launched last year, Nutanix LEAP is primarily designed for people that use Nutanix, and not everybody does. Not everybody can use it. We also offer RecoverPoint for VMs. It is a Dell EMC product, so it's geared toward people that are running VxRail. And then there is vCloud Availability. You have to have vCloud Director on both sides and vCenter, which is not something that everybody has either. vCloud Availability monitoring is also a nightmare. Zerto is more the product of choice for most use cases.
What other advice do I have?
Some of the biggest problems that we've had as a cloud provider are the vCD integration and the Zerto Cloud Manager integration. If you can avoid those two things, avoid them.
I would rate Zerto an eight 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?
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. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Zerto
March 2025

Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
849,190 professionals have used our research since 2012.
Director at a energy/utilities company with 51-200 employees
Improves recovery time and DR testing efficiency, but lacks some advanced enterprise features
Pros and Cons
- "What I appreciate the most about the product is its simplicity. It's very easy to use for my staff."
- "Zerto saved us close to 90% on DR testing compared to traditional backups and restores."
- "Expanding the product to compete more fully with products such as Veeam would be a big benefit in the market."
- "Zerto gets most of the way there and would work for a smaller enterprise effectively, but for a larger enterprise, Veeam has capabilities that are beyond Zerto at this point."
What is our primary use case?
Our use cases right now are primarily for creating spot backup snapshots and things like that for recovery.
How has it helped my organization?
The near synchronous replication works very effectively. We do appreciate it as it's comparable to other vendors in that space.
Zerto has helped to reduce downtime in situations when we roll out a change and the change needs to be rolled back. Zerto has been excellent at being able to recover that prior server before the change, so it has helped significantly in those areas.
Zerto has helped us to reduce the overall DR testing. Zerto saved us close to 90% on DR testing compared to traditional backups and restores. We were able to utilize that time for anything else we wanted to. We needed the time desperately, so it was a big benefit to us.
Zerto has had an impact on our IT resiliency strategy. It has improved our IT resiliency considerably; going from traditional backups to having backups with Zerto in addition was a lifesaver.
We use Zerto to help protect virtual machines in our environment pretty much exclusively. Compared to what we were doing with traditional backups, our RTO and RPO have improved by 90%.
What is most valuable?
What I appreciate the most about the product is its simplicity. It's very easy to use for my staff.
What needs improvement?
Expanding the product to compete more fully with products such as Veeam would be a big benefit in the market.
For how long have I used the solution?
I have been using Zerto for about three years.
What do I think about the stability of the solution?
We have not seen any instability.
What do I think about the scalability of the solution?
Zerto's scalability is adequate for us. It could expand a bit more to compete with those larger products that are a little bit more scalable. We're not a big enough enterprise to test it. We haven't taken it to the point where we feel the scalability is a problem, but I suspect it probably would be; that's just a suspicion, not anything that I have concrete evidence for.
How are customer service and support?
We have not had to contact the technical support or customer support.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
I have personally used alternatives to Zerto, including Veeam, Commvault, Veritas, and several other solutions. Zerto competes effectively in the snapshot area for DR and synchronous replication. I've also used the Pure Storage system, which does asynchronous replication. It combines effectively with other products such as Zerto, Veeam, and so on, so I've used quite a few of them in the past.
Veeam is a more comprehensive backup software for an enterprise. Zerto gets most of the way there and would work for a smaller enterprise effectively, but for a larger enterprise, Veeam has capabilities that are beyond Zerto at this point. Veeam is an example of a more complete product.
Commvault also has a more complete product, even though it's not entirely as good. Zerto is progressing; they have a great start and a great product, but they probably need to expand it to compete more fully with those larger enterprise backup systems.
How was the initial setup?
Its deployment is easy. We had it fully onboard and tested in about two weeks.
After the deployment, Zerto doesn't require much maintenance at our end. You have to administer it similarly to any other system, but it's pretty low maintenance.
What about the implementation team?
We put a team on it so that everybody learned together. We put a three-man team on it from a group of seniors who would be responsible for disaster recovery anyway.
What's my experience with pricing, setup cost, and licensing?
It was pretty appropriate. It was not too cheap, not too expensive. It was just about right.
What other advice do I have?
I would rate Zerto a seven out of ten.
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: Apr 12, 2025
Flag as inappropriateSr Project Manager at a transportation company with 10,001+ employees
Improves our return to service time and supports implementation via cloud and on-premise
Pros and Cons
- "What I appreciate most about Zerto is that we can implement it via cloud now and on-premise."
- "Zerto has enabled the team to focus on engineering and spend less time developing APIs to work with custom solutions and security applications, positively impacting our IT resiliency strategy."
- "Zerto could improve the product by lowering the cost."
- "Zerto could improve the product by lowering the cost."
What is our primary use case?
My current use cases for Zerto involve the protection of data to ensure that any ransomware or threats will not impact our endpoints. I have used Zerto to help protect virtual machines in my environment. The majority of our infrastructure is virtual, while less than half is physical.
How has it helped my organization?
I've seen an impact on our RPOs and RTOs as our return to service has become much faster. We can return to business as quickly as possible.
Our DR testing has been reduced. We still do it once a year, but now it's more about checking off boxes because we know what to expect. We must ensure the certificates and all related items are good, examine the return times, RPOs, RTOs, and verify everything is still functioning properly.
Zerto has enabled the team to focus on engineering and spend less time developing APIs to work with custom solutions and security applications, positively impacting our IT resiliency strategy.
What is most valuable?
What I appreciate most about Zerto is that we can implement it via cloud now and on-premise. Mobility also stands out to me. The interface of Zerto is much easier to use.
What needs improvement?
Zerto could improve the product by lowering the cost.
For how long have I used the solution?
I've been using Zerto for about three or four years, implementing it in various scenarios.
What do I think about the stability of the solution?
I have not noticed any crashing or instability with Zerto.
What do I think about the scalability of the solution?
Zerto scales appropriately for my pretty big company.
How are customer service and support?
I have not had an occasion to contact their technical support.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
A few years ago, I used an alternative. I prefer Zerto over Veeam, which is why we switched from one to another. It's apples and oranges: Zerto has a much smoother interface and is much easier to use with better features.
How was the initial setup?
It was pretty easy. I do not recall hitting too many roadblocks.
It took around three to four months total to fully set up Zerto, including network configuration, firewalls, and all other components.
Zerto requires basically no maintenance on my end now. It's managed by Zerto tech, so we don't have to test packages and similar tasks. They inform us of product updates, plan for them, and implement them as SaaS-approved changes.
What's my experience with pricing, setup cost, and licensing?
Zerto is not overly expensive. It's worth what we're getting for it, but with tough times, a discount would be beneficial.
What other advice do I have?
I have not yet encountered a situation where I needed to perform data recovery due to ransomware or other causes. I will knock on wood as we haven't had that kind of incident yet. Thanks to Zerto and some other systems we use on the back end, though never say never.
I would rate Zerto an eight out of ten.
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: Apr 5, 2025
Flag as inappropriateTechnical Support Analyst at a non-profit with 1,001-5,000 employees
Offers continuous replication for mission-critical applications and near-synchronous replication
Pros and Cons
- "The continuous replication with a low recovery point objective (RPO) is crucial for us."
- "Better alerting is something that I feel is critical."
What is our primary use case?
We use Zerto to replicate our VMware VMs. We have two data centers in our company. We use Zerto to make sure these virtual machines which are VMware are replicated in the other data centres.
We also use Zerto as a backup tool for Windows files.
How has it helped my organization?
Zerto is already a leader in its field. I have seen the benefit of knowing that everything is protected. We've only started a disaster recovery program in the last year after running Zerto. The business is now understanding that recovering from the traditional backup software does take a long time, and it's very complex.
Using Zerto, I am the only department that can recover in minutes. The database team takes hours, the IBM platform takes hours as well. So time saving is what we see the most of Zerto.
Zerto's near-synchronous replication is very important. It's the reason we're still with Zerto. We collect blood in many hospitals, and some of our data centers are in hospitals with power grids that are not as good as commercial buildings. So, we do have servers that will crash. The servers are in the hospitals for latency reasons. And when a server crashes for any reason, it could be a chipmunk eating wires. We need to have another server with no data loss so that the clinics can keep going without having to do a whole bunch of data entry.
We don't use SAP HANA with Zerto, but we use SAP HANA with an Oracle database. These databases are replicated at the hardware storage level, not with Zerto.
Zerto has very little effect on our RPOs (Recovery Point Objectives). As long as we have the disk space, it works well. We currently have a one-hour to one-day RPO and are extending it to about four days based on recommendations.
What is most valuable?
The continuous replication with a low recovery point objective (RPO) is crucial for us.
We have mission-critical applications that, if we lose data, we lose a lot of money. Zerto's low RPO ensures minimal data loss in case of a disaster.
What needs improvement?
Zerto has the ability for us to suggest features, which we do often. We do see some of these features come to life. Better alerting is something that I feel is critical.
If you turn on the alerting of the on-prem appliances, it bombards your inbox over everything. It's too much. We had to turn that off. We use Zerto cloud analytics for alerting, and we just moved the Zerto ten about a month ago.
Some alerts, such as when one of my virtual protection groups does not have at least one day of logs configured. We find that after we do a disaster recovery failover test we recreate the virtual protection groups. Some of our junior systems admins won't specify. We need seven days of journal logs. So an alert for that would be handy.
For how long have I used the solution?
We've been using Zerto for over eight years.
What do I think about the stability of the solution?
It's excellent. The product has been solid for the entire time we've used it.
What do I think about the scalability of the solution?
We use Zerto to protect approximately 300 VMware VMs.
We have not grown Zerto in many, many years. We're likely going to double it. It should not be a problem because it's essentially almost agent-based. I feel that it can grow. We're not a very big client, so I don't know how big it can scale, but I feel that it can.
How are customer service and support?
I rarely need to contact the customer service and support. The product is very good. When I have used their support, I've never had to escalate a call.
There's nothing bad about the support. They are responsive and helpful. A 10 would mean having an experience so exceptional that I would have to tell my family about it.
How would you rate customer service and support?
Positive
How was the initial setup?
Zerto was deployed before my time, so I wasn't involved in the initial deployment. However, I have been involved in upgrades, which are very simple.
I appreciate the ability to open a case with Zerto support for assistance. For our recent Zerto 10 upgrade, we also had help from Zerto Professional Services, which is a feature that management likes.
Zerto can perform disaster recovery in the cloud, but our company is not cloud-ready yet. We do not have the governance We are still trying to figure out if we were to fail over an application, is the application team aware that they will have to pay additional funding out of their call centers. So we are at a governance stage right now of planning for recovery in the cloud.
We have two active-active data centers that replicate themselves at the VMware level. We use Microsoft Azure.
What about the implementation team?
We used Zerto Professional Services to assist us with the Zerto 10 upgrade. It was a great experience. The upgrade was done in about 15 minutes for both sites. They were well-prepared and knew exactly what they were doing.
What was our ROI?
We don't see ROI in terms of direct financial ROI, as we only started our disaster recovery testing about a year ago. However, based on client satisfaction and our decision to double our Zerto licenses, we see a return on investment in terms of overall client satisfaction.
What's my experience with pricing, setup cost, and licensing?
We have a licensing team that manages it, but it seems to be fairly easy to use.
Which other solutions did I evaluate?
We looked at Veeam and NAKIVO.
The business realized the importance of quick recovery and minimal data loss, which are the main reasons why we chose and continue to use Zerto.
From an end-user interface where you use your mouse to click, Zerto is definitely the easiest. However, for the monitoring piece, where my developers have to use the APIs, Zerto is much harder than the other tools that we've used.
Zerto's recovery is the fastest, hands down. Compared to NetBackup, which takes hours, Zerto's recovery is a matter of minutes. We also use a tool similar to Veeam called NAKIVO for non-mission-critical systems, which has a one-day RPO. Nextiva is close to Zerto in terms of recovery speed, but Zerto's interface, orchestration capabilities, and ability to run scripts make it the top choice for us.
What other advice do I have?
I would rate it a ten out of ten. There's nothing that compares to Zerto, nothing that works as well as it. My only complaint about it is the alerting. There are a lot of alerts that come through, and they are legit alerts. It's excellent.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Hybrid IT Architect at Quanture Spa
A storage software vendor that specializes in enterprise-class business continuity and disaster recovery (BC/DR) in virtual and cloud environments
Pros and Cons
- "A great Zerto feature is the non-intrusive failover of the application, similar to an actual disaster recovery test without impacting the services that are currently online. Sometimes customers need to failover to an isolated environment and validate an application without impacting the production environment: we can achieve this goal with Zerto. Again, we can do regular testing in a non-impactful way using isolated testing. For customers of our DRaaS we include once a year, a live test that is more like what would happen if the customer lost the production site. Near-synchronous replication is one of the benefits of Zerto that drove us to choose it over some others. With typical backup and recovery solutions, the recovery point typically is about 24 hours. With the near-synchronous replication, recovery point objectives tend to be minutes or a few seconds if the bandwidth is adequate. That's one of the major benefits of Zerto: there's no need to run incremental backups every xx minutes. And the recovery time is fairly quick as well, like a shutdown and reboot of a VM. Eventually, the VPGs (Virtual Protection Groups) allow to grouping of one or more VMs into a single entity, ensuring every point in time inserted into Zerto’s journal (a checkpoint) is from the same point in time for all components within the protection group. This allows easy recovery of an entire application and its dependencies to a consistent point in time. Zerto is also a very easy product to use."
- "Zerto could be considered as a backup product but this is not true. So if we could consolidate and use Zerto for disaster recovery as well as everyday backup and restore for situations where we need to recover something, that would be helpful. Anyway, we think that Zerto will win with no competition in the Disaster Recovery process, so we stay focused on this. Now we are testing version 10 which include real-time ransomware detection, a new Cyber Resilience Vault and enhanced cloud capabilities and security: we expect more from these features for superior hybrid cloud security."
What is our primary use case?
We implement Zerto as a part of a Disaster Recovery process for our valuable customers, in various environments. Most of them consist of two sites owned by the same customer, connected with campus or wan link, but both using VMware virtualization platform.
Recently we realized a dedicated infrastructure in our Datacenter, then started to propose to our customers DRaaS using those resources as a recovery site and including dedicated 24x7 support.
Few customers use the public cloud (Azure) as a recovery site: we could only implement and configure the solution or fully manage it because we are also a Microsoft Gold and Tier-1 partner.
How has it helped my organization?
Zerto helps reduce downtime in a wide number of situations because it can bring up an entire environment of 40-50 VMs in minutes.
Zerto helps to save time in a data recovery situation too. Some customers experienced VM or database corruption: using the solution's checkpoint feature, the data recovery happened within five minutes or less. A normal restore would probably be two to eight hours depending on if we had to restore from disk/tape and need or not need to apply logs.
Zerto is great at DR testing. We can spin off critical VMs or an entire environment pretty quickly and have users test against this copy with no production environment impact.
Its overall impact on our RTO has been great. It took a few hours in a very complex environment. The customer was very impressed with Zerto when we started with the PoC and then put it in production. It is great.
Zerto has reduced our downtime. Customers have minimal downtime.
We have been enabled to automate tasks with Zerto. Staff can now be dedicated to other tasks.
What is most valuable?
A great Zerto feature is the non-intrusive failover of the application, similar to an actual disaster recovery test without impacting the services that are currently online. Sometimes customers need to failover to an isolated environment and validate an application without impacting the production environment: we can achieve this goal with Zerto. Again, we can do regular testing in a non-impactful way using isolated testing. For customers of our DRaaS we include once a year, a live test that is more like what would happen if the customer lost the production site.
Eventually, the VPGs (Virtual Protection Groups) allow to grouping of one or more VMs into a single entity, ensuring every point in time inserted into Zerto’s journal (a checkpoint) is from the same point in time for all components within the protection group. This allows easy recovery of an entire application and its dependencies to a consistent point in time.
Zerto is also a very easy product to use.
We started using it a few months ago for immutable data copies for a few customers on multiple repositories like HPE.
Zerto's ability for blocking unknown threats and attacks is key in our disaster recovery process. It's the technical solution where we implement all the data. It is also the recovery plan for our customers.
We have tried experimenting implementing Zerto with the the disaster recovery site on cloud. We use an Azure. It's very useful. Zerto has enables us to do disaster recovery in the cloud, rather than in a physical data center.
We've only used Zerto two or three times to migrate an existing data center to a new one because the hardware under the machine was from a different brand. We used Zerto because the environment is quite complex and the migration using other tools did not fulfill the customers' needs. Zerto is very good at data migration.
One of its best features Zerto is the ability to maintain the data of multiple VMs using Vipro Protection Group. We can aggregate multiple VMs in a workload for specific services. They are protected at the same time.
It's very easy to manage and monitor our DR plans with Zerto. It's very easy to learn and operate. It's easier than VMware.
What needs improvement?
Zerto could be considered as a backup product but this is not true. So if we could consolidate and use Zerto for disaster recovery as well as everyday backup and restore for situations where we need to recover something, that would be helpful. Anyway, we think that Zerto will win with no competition in the Disaster Recovery process, so we stay focused on this.
Now we are testing version 10 which include real-time ransomware detection, a new Cyber Resilience Vault and enhanced cloud capabilities and security: we expect more from these features for superior hybrid cloud security.
Reports could be useful for customers. I would like to have a report that shows the latency for every single internal VM. it would be useful for troubleshooting.
For how long have I used the solution?
We started to evaluate Zerto about three years ago, then we implemented it for our valuable customers who need affordable solutions in their disaster recovery processes.
What do I think about the stability of the solution?
We haven't had any issues with any of the builds or the virtual managers, especially with the new "appliance" mode. It just runs.
What do I think about the scalability of the solution?
Zerto is a very scalable solution. We can create as many protection groups as customers need for their environment even as they growth.
Our customers are mostly medium to small sized enterprises.
How are customer service and support?
We use Zerto Quick Start service for the first installations and we use it in very complex environments: great.
We are very satisfied. We had to use it at the beginning to understand the implementation process and what we needed to do.
They are quick and professional.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We previously used Veeam (B&R + DRO) and VMware (Replication + SRM), but they could not offer all the features of Zerto.
We also sometimes still use VMware Disaster Site Recovery Manager in conjunction with VMware Backup and Recovery.
How was the initial setup?
The implementation is very straightforward. Must be considered security and lay out the network infrastructure to be more efficient.
But from the standpoint of installing and deploying the product, it's very simple.
What's my experience with pricing, setup cost, and licensing?
Pricing is adequate at the standard of the product, but there could be "always" some improvement. We would like to see a consumption model that would charge in a DR scenario, where you're failing over and consuming those resources, instead of a per-protected-node model.
What other advice do I have?
My advice is to look at what you're trying to accomplish: with Zerto you could combine resilience, mobility, and protection into a single software-only solution. It's hardware and hypervisor agnostic as to whether you're using VMware, Microsoft, or Azure.
We have built a disaster recovery landing zone in our Datacenter and we built an isolated environment so we could do non-intrusive failover tests, and still keep customers' production environment up and running.
We have recently introduced the immutable data copies feature, because of the issue of cyberattacks and because even backup systems could become corrupted and then this is still a bad situation. The ability to look at the data that is being replicated in real-time and scan it, in conjunction with immutable data, and putting that into a vault, would be a great benefit.
The 3-2-1 rule isn't so important for us when it comes to disaster recovery. We consider the backup process and then the disaster recovery process. We treat them as two different workloads that we could implement to our customers to solve different issues.
The majority of our customers use it in a hybrid environment, but they prefer to use disaster recovery in their own data center. In some cases, we provide disaster recovery as a service, where the disaster recovery site is in our data center.
Doing a proof of concept is the best way to implement and sell Zerto. The customers don't always trust our advice but when I start with a POC in their environment, they see it's benefits.
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?
Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer: I work for Quanture Spa, which is a System Integrator HPE Gold Partner in Italy
Cloud Engineering Manager at a insurance company with 1,001-5,000 employees
Can replicate data rapidly and cost-effectively and has good role-based access controls
Pros and Cons
- "We can recover both systems on-premises and in the public cloud."
- "I would like Zerto to enhance the continuous backup aspect."
What is our primary use case?
We use Zerto to replicate our gold systems. Gold systems refer to those that require recovery in a disaster recovery environment within 24 hours, with a maximum allowable data loss of one hour. Therefore, the Recovery Time Objective is 24 hours, and the Recovery Point Objective is one hour.
How has it helped my organization?
I would rate Zerto's ease of use a nine out of ten. The setup of virtual appliances required for data replication is straightforward and effortless. Some of the automation and tooling, such as changing IP addresses or running scripts after a disaster recovery process, is also very user-friendly and simple to configure.
Zerto's near-synchronous replication is commendable. Usually, the data is only a couple of minutes behind. Hence, we are not employing synchronous replication, but asynchronous replication proves to be sufficient for our needs. It does not appear to deviate too far out of sync or fall too far behind, thereby effectively maintaining up-to-date data. Near synchronous replication holds significant importance as these systems are our critical business assets.
Zerto has helped us improve our organization by enabling disaster recovery both on-premises and in the cloud. We are transitioning towards cloud-based recovery. Our previous solution, before Zerto, only allowed us to replicate data in our on-premises data center, preventing us from migrating to the cloud. Zerto has unblocked us, allowing us to leverage cloud-based recovery now. We were able to realize the benefits within three to four months. The implementation was relatively quick and completed within a couple of months. Everything tested well.
Zerto enables us to perform disaster recovery in the cloud instead of a physical data center, and this is the reason we made the switch to Zerto.
Having the capability to perform disaster recovery in the cloud is of utmost importance to our organization. We are implementing disaster recovery in the cloud to facilitate the shutdown of one of our data centers.
We use Zerto to protect VMs in our environment.
The speed of recovery using Zerto is good. The automation really helps make the recovery quick and easy.
Zerto's overall impact on our recovery time objectives is positive. It is fulfilling exactly what we needed it to do, making it a valuable tool. Additionally, it proves to be fairly cost-effective and easy to set up and use.
Although we have not experienced an actual disaster, Zerto has been instrumental in aiding our disaster recovery testing. Every year, we conduct a DR test to recover systems, conduct assessments, and validate our processes, and for this purpose, we have utilized Zerto. The results have been outstanding, as Zerto has saved us approximately 500 hours of time annually.
Zerto has automated the recovery process by utilizing those playbooks and re-IPing. This has significantly contributed to the reduction of DR testing efforts.
50 percent of the time that Zerto has saved has been allocated to value-added tasks.
What is most valuable?
Zerto can replicate data rapidly and cost-effectively. We can recover both systems on-premises and in the public cloud. We use Microsoft Azure and Amazon Web Services for cloud infrastructure, and Zerto can recover data from both of these platforms. Therefore, it is not limited to a specific cloud provider like the Azure Site Recovery Manager.
Zerto has good role-based access controls. For cloud recovery, it allows replication over the Internet instead of private networking, which is really nice.
What needs improvement?
I would like Zerto to enhance the continuous backup aspect. If Zerto could replace Veeam from a backup perspective, that would be highly beneficial. Currently, we use Veeam for backup and Zerto for disaster recovery. It would be ideal if we could consolidate both functions into a single product rather than using two separate ones.
For how long have I used the solution?
I have been using Zerto for three years.
What do I think about the stability of the solution?
I would rate Zerto's stability an eight out of ten. We encountered a problem once, but it was resolved.
What do I think about the scalability of the solution?
I would rate Zerto's scalability a nine out of ten.
Which solution did I use previously and why did I switch?
We previously used EMC's Site Recovery Manager and Recover Point. The reason we replaced them is that they utilized sand-based replication, which couldn't be used to replicate data to public clouds. As there are no sands in the public cloud.
Zerto's ease of use, when compared to EMC's Site Recovery Manager and Recover Point, is slightly better. For instance, during the setup process, we didn't require expertise in storage area networks, unlike our previous products. Therefore, it takes fewer skilled resources to set up, configure, and start using Zerto.
How was the initial setup?
The initial setup is straightforward. The deployment took two months. We identified the core machines that we were previously replicating and gradually migrated applications one set at a time. An application could consist of two servers or even five servers. We can perform these migrations in waves.
For the deployment, we had two engineers, one support person, and one architect.
What about the implementation team?
The Zerto team assisted with the implementation.
What was our ROI?
We have seen a return on investment.
What's my experience with pricing, setup cost, and licensing?
Zerto is slightly expensive, but we do see the value in it.
Which other solutions did I evaluate?
We evaluated Veeam, Commvault, and Rubrik. Among them, Zerto had the best feature set for near real-time asynchronous replication.
What other advice do I have?
I rate Zerto a nine out of ten.
The speed of the RPO using Zerto is the same as our previous solution. We haven't lost anything, but we haven't gained much from an RPO perspective either. We had good technology; it was just limited by the cloud because there hasn't been any significant change.
We use Veeam as our backup product to perform some of the point-in-time recoveries.
We have only around six end users who log in to the console in total. Zerto is deployed in our primary data center and is also replicating to a secondary data center where it is deployed.
We have people who monitor whether the synchronization is proceeding well, but there is very little day-to-day overhead in terms of maintenance.
Zerto is a solid industry-recognized quality product.
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?
Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
The ability to spin things up near-instantaneously enables us to guarantee our uptime
Pros and Cons
- "We are doing continuous data protection. It works flawlessly. Our recovery points are measured in seconds. We have all these "baby snapshots" throughout the course of the day, so we can roll a VM back to any point in time, spin it up, and away we go. We're actively using that. It works great."
- "One thing I would like to see, and I know that this is on their roadmap, is the ability to use long-term storage in the cloud, like in Azure or AWS, making that even more seamless. Whether it's stored in glacier or on-prem, being able to retrieve that data in a quick manner would be helpful. They're just not there yet."
What is our primary use case?
We're backing up VMs with it. Our company has about 200 VMs and we're using Zerto on 30 of them in the main line of business applications. We're using it to replicate all that data over to our DR site so we can do our testing and reporting against that.
Within those 30 servers we've broken out into three different SLAs on which ones get spun up first. We have it all scripted with monthly plans to fail over, spin it up, actually use it over there, spin it down, bring it back into production, etc.
How has it helped my organization?
The business that we're in means we have to run our network 365 days, 24/7, with no downtime. If there's any kind of interruption to business processes — power outage, tornado, fire, etc. — we need to be able to get certain systems up and going in almost real-time. That's how we're leveraging Zerto, to guarantee that uptime and for the ability to spin these things up near-instantaneously.
I know my networking team loves the tool and the interface and being able to roll back and do the failover stuff very easily. But for me, personally, it's how it has impacted our business. The reporting functionality showing that our DR plan is rock-solid and stable, and my ability to generate summaries for our customers, have really improved business processes for us. It gives peace of mind to our customers that our systems are stable and the services that we're providing are stable.
Also, when we need to failback or move workloads, Zerto decreases the time it takes and the number of people involved. The failback feature, from a technical standpoint, is what sold us on Zerto. One of the challenges we had with Site Recovery Manager was spinning up and being in production at DR. If everything is equal, everything is patched and everything's working, both solutions offer a very similar experience: the ability to move a workload from production to disaster recovery works with both of them, no problem. Coming back the other way was just a bear of a move with Site Recovery Manager. With Zerto, it's almost seamless. With Zerto, it takes about four or five mouse clicks and stuff fails back over, and our end-users are none the wiser. And it's just one guy doing it. When failing back from Site Recovery Manager, we'd have to get one of our sys admins involved and we'd have to let our end-users know that they all had to log out.
While it hasn't reduced staff, we have become more efficient and it has allowed me to reprioritize some projects. It's freed up some capacity, for sure. We haven't reduced headcount, but it has definitely taken a big wedge out of the daily grind of our backup and recovery; the stuff they always had to check.
What is most valuable?
Personally, what I find valuable is the executive summary that says our DR plan is operational. I can then pass that out to our customers.
Per Mar has about 75,000 customers and, more and more these days, especially given all this [COVID] pandemic, we're asked: Do you have a business continuity plan? Is it tested regularly? Do you have documentation for it? Two years ago, a simple email from me saying, "Yes, we have this," sufficed. We're finding now that people want true documentation from an independent system that generates a report. The reporting that comes out of Zerto is a lifesaver for me. I'm able to generate that up, send it out to the customers that need it, and say, "Yes. Here are our SLAs. Here is our monthly test routine. Here is where it shows us being successful," and so forth.
We are doing continuous data protection. It works flawlessly. Our recovery points are measured in seconds. We have all these "baby snapshots" throughout the course of the day, so we can roll a VM back to any point in time, spin it up, and away we go. We're actively using that. It works great.
It's easy to use and there isn't a huge learning curve. Even some of the advanced features are very intuitive to folks who have been in this space before. If you have any kind of skill sets around any kind of backup and recovery tool, the user interface for Zerto is very natural.
What needs improvement?
One thing I would like to see, and I know that this is on their roadmap, is the ability to use long-term storage in the cloud, like in Azure or AWS, making that even more seamless. Whether it's stored in glacier or on-prem, being able to retrieve that data in a quick manner would be helpful. They're just not there yet.
For how long have I used the solution?
I've been using Zerto for about a year.
What do I think about the stability of the solution?
It just works. We architected it pretty nicely. One of our licensed servers is a complete test solution for us to show that it is truly working. We're able to take a small test server, a Dev server is really what it is, and we can move from production, move it over to DR, have it run over there for a day, and then we move it back with no data loss.
It's never not worked and when you come from the SRM world, that's just unheard of. Now we're a year into this product and have gone through an upgrade, and our June test went off without a hitch. It's very rock-solid.
How are customer service and technical support?
Their tech support has been fantastic to work with. We ran into a glitch when we did our update in mid-May and our primary data center stopped talking to our secondary data center. We couldn't figure it out. We got their tech support involved right away. They identified a bug right away. They were able to roll us back and then stayed engaged with us as they figured out how to fix the bug. And once the bug was isolated and fixed, they got right back a hold of us to say, "We're ready to go," and then they walked us through upgrading both sides. There was a lot of hand-holding in that upgrade scenario. It was a fantastic experience.
It took them four or five days to fix the bug and they stayed engaged with us just about every single day, letting us know the status of it and when it went to QA. We didn't fall into a black hole. It was a very customer-centric experience.
Which solution did I use previously and why did I switch?
We were using VMware Site Recovery Manager. We're still a VMware shop. Zerto replaced SRM. It was probably cost-agnostic, but what it really came down to was that SRM breaks all the time. You apply some patches or a Windows update. Uptime and reliability for us are super-critical. We don't have a ton of time to spend on making sure it's always working. We were really looking for a solution that we could architect, deploy, and just let it run, knowing that we're protected without our always having to go back and mess around with it.
What we kept finding with Site Recovery Manager was that every time we wanted to do a full-scale, failover DR test, we would have to spend a week ahead of time prepping for it, to make sure everything would work flawlessly during our test. It always worked, we knew how to patch it and get around it. But disaster doesn't give you a two-week notice. You don't know you're going to have a tornado in two weeks. You get about a 10-minute notice and then you've got cows flying through the air. We wanted a tool that we know would just run and work and be reliable.
It was cost-neutral to the budget, the timing was right, and the solution was rock-solid so we made the change.
How was the initial setup?
Ease of use and deployment are fantastic. This is a solution that we started with a proof of concept. We threw it in a lab and said, "Hey, let's just see what it looks like." Next thing you know, we never even had to tear down the proof of concept. Once we started seeing it working we said, "This is definitely something that we want." All we really ended up doing was negotiating licenses, applying the license key, and we were off to the races.
Soup to nuts, it took us five hours to spin the whole solution up and to create our protection groups. It was very fast. That includes downloading the software, spinning the VM up, and protecting and backing up data.
We worked with one of their engineers through the proof of concept. Once we said, "Hey, this is going to work," we tested it on a few servers and then we became a paying customer. They worked with us to help us define what made sense for the 30 licenses that we bought and what machines to deploy it to. But it's really not a complicated tool to deploy. There wasn't a ton of architecting and solution-building around it. There was some, but it was a very simple solution to install.
What was our ROI?
We have seen ROI. And even when you cost-compare against Site Recovery Manager, none of these solutions is cheap. But we are folks who need to have uptime and these things have to work. When you start comparing it against Site Recovery Manager, Zerto blows it out of the water, in my opinion.
What's my experience with pricing, setup cost, and licensing?
If it were easier to license, and to scale it out a little bit more economically, that'd be a godsend. At the end of the day, my druthers would be to have all 200 of our servers protected by this platform. But for a company of our size, that stretches our IT budget and it just doesn't make economic sense. I would really love to be able to just apply Zerto to every virtual machine that we spin up, drop it into the right SLA bucket, and just be done with it, knowing that it's protected, soup to nuts. Unfortunately, that's just cost prohibitive.
My advice would definitely be to leverage the number of VMs. It's not a cheap solution by any stretch, but it delivers on its promise. There's definitely value in the investment. With hindsight, I would have gotten a better cost per VM if I was able to buy, say, 100 licenses. It would have been easier for me to put other servers under the protection of Zerto. I wish I would have had that flexibility at the time. Eventually, budgets will open up and I'll be able to go get another 50 or so licenses, but I'll still be paying a higher price, more than if I would have negotiated a higher quantity to begin with.
Which other solutions did I evaluate?
We took a look at a couple of other solutions. The other ones fell off the table pretty quickly. We're based in Iowa. We have a good account team here in Iowa from Zerto that knew our account from previous relationships. They came around and said, "This is a tool that you guys really need to take a hard look at."
The sales process took about six months. They came in about six months before my renewal with VMware. We had a few conversations and, about two to three months before the renewal, designed a proof of concept to see if it was actually going to work. They came in and did that. My guys were raving about it and I saw some of the reporting out of it. At that point I said, "Okay, done deal." It was cost neutral. When Site Recovery Manager came up, we canceled that portion of the renewal. There wasn't really a need for us to go out to market. I just trusted the account guys. They knew who we were. The tool worked the way they called it. I don't get too picky. If it works, it's good enough for me.
What other advice do I have?
Take a hard look at it. Don't pass it by, don't be scared off by the price. Definitely take them up on the proof of concept. Have the team come in and do that. You'll be pleasantly surprised.
They talk about technology that can just actually do what it promises. I've been doing this for over 20 years and sometimes you get jaded by the fact that people over-promise and under-deliver. Zerto was definitely on the opposite end of that spectrum. The solution went in so easily that I had to do a double-take when my guys were telling me, "Hey, it's already up and running." I said, "It can't be done already." I'm used to complicated deployments. They promised and it does exactly what they said it would do. Don't be so skeptical. Keep an open mind to it and explore the possibilities.
I just sat through ZertoCON. They put a lot of emphasis on long-term retention. It really started putting a question out there as to whether you need a different backup and recovery solution. We use a different partner called Rubrik for backup and recovery. The challenge that we have with Zerto is that we're only protecting 30 VMs, whereas with Rubrik, we're protecting all 200. There's a little bit of a dance between value and return. So we're not using Zerto for long-term storage right now. We're evaluating it. I don't know if it makes economic sense to do so, but we are taking a look at it. And we're not protecting all 200 servers because of cost.
In terms of using the solution for a data recovery situation due to ransomware or other causes, knock on wood, we have not had to use it in that capacity just yet. We have a very mature cyber security posture and we haven't been popped by ransomware in the last year. But it does give me peace of mind that we also have that ability. That's just another layer of our cyber security posture and we know that we're protected against those threats. So there's definitely a peace of mind around that.
The only folks using it are on our IT team, about five or six of us. Five of my guys use it on a regular basis and know how to manage it. I'm the sixth guy. If I ever have to get in there, we're in trouble.
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.

Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros
sharing their opinions.
Updated: March 2025
Popular Comparisons
Veeam Data Platform
Commvault Cloud
Rubrik
VMware Live Recovery
BDRSuite Backup & Replication
Nasuni
NAKIVO Backup & Replication
Arcserve UDP
Dell RecoverPoint for Virtual Machines
Hornetsecurity Altaro VM Backup
AWS Elastic Disaster Recovery
Datto Cloud Continuity
Druva Phoenix
Precisely Assure MIMIX
Infrascale Backup & Disaster Recovery
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?
- When evaluating Disaster Recovery Software, what aspect do you think is the most important to look for?
- What is the difference between cyber resilience and business continuity?
- Internal vs External DR Site: Pros and cons
- Disaster Recovery Software: Which is the Best Solution in the Market?