Zerto Reviews

We use Zerto for disaster recovery, backup, and ransomware protection. The 3-2-1 backup strategy requires us to have two backups of our production data on different media. One copy is on disk and tape backup, and the other is hosted off-site for disaster recovery. With journaling and the persistent backups we take nightly, it almost obviates 3-2-1 because it renders some unnecessary aspects. 

We adopted Zerto, hoping to speed up our recovery time and improve the overall security of our environment and data. We haven't realized the full benefits, but I expect we will improve our security posture and disaster recovery speed.  

Zerto would enable us to do cloud-based DR instead of a physical data center, but we are based in a very rural area of Colorado. We're deep in the mountains, so leveraging the cloud is challenging. We have little-to-no cloud presence, but Zerto can enable us to move our disaster recovery into the cloud because it is agnostic to the backup target. That could easily be a cloud provider. We only need redundant and reliable circuits to the cloud.

The impact on our RTO is theoretical because we haven't had to do any critical recovery. Based on our testing, it should significantly improve our RTO because the backup technology is more efficient than our previous solution. RTO is one of Zerto's strengths. Zerto enabled us to test our DR plan. Our disaster recovery needed a lot of help when I joined two years ago, and it's one of the projects I have been working on. Zerto is central to our DR plan. It's the primary cog in that machine. Zerto cut our hardware and maintenance costs by about 50 percent.

I like the fact that Zerto is target agnostic. It doesn't care what type of storage it writes to. The journaling is also excellent. You can easily and quickly restore to seconds before an event. The immutable data copies feature is one reason we adopted Zerto. That's one of its selling points.

Zerto is easy enough to use. It's as usable as any other backup solution. We're accustomed to dealing with complex options and everything available to us in the suite. 

I tried a file-level recovery, which should work on any server. However, the server we need to protect the most is the one giving us problems. We couldn't do a file recovery without restoring the entire server to a recovery partition that isn't part of the production and pulling the files off it that way.

Zerto's near-synchronous replication is excellent when it works. I'm trying to be nice to them because I like the product a lot, but we're having a lot of difficulty with it in our environment.

There is a disconnect between the sales pitch and what we can do with Zerto in practice. We've been trying to reconcile that for most of the year. There should be more continuity between sales and implementation to ensure the solution is implemented how our presales engineer pitched it to us. 

They need to have some accountability. Maybe the implementation engineer should be on the line so that they know what is presented and agreed upon regarding the implementation in our environment. The implementation should have been precisely what we were expecting. 

I was part of the pre-purchase team as the information security manager. I handed it off to my infrastructure team to implement, and they practically had to start from scratch. Zerto handed it off to their professional services to implement, and I assigned the job to my team. 

There were a lot of questions and things Zerto couldn't do on its end. HP purchased Zerto as we were engaging with them. I don't know if that was related to our frustrations, but I know that acquisitions can make a product messy for a bit. I don't want to blast Zerto. It's an excellent product, and I would love it if it could work as advertised. I've seen it do some of that for us. We've had a rough start, and we're still trying to find that sweet spot.

I have used Zerto for nearly a year.

Zerto isn't reliable in our current environment. We keep running into these weird little issues. At one point, we didn't have complete backups on a couple of key servers for more than a week because of this issue. If we had gone down that week, it would have been ugly.

Zerto seems pretty scalable. We bought something that we can add on to and increase the horsepower. Every change we've made has been smooth.

Their support and account management teams have been pretty amazing. They are bending over backward to make it right with us, so they deserve a lot of credit for that.

We used Avamar. Zerto's recovery is faster, and it's a little more straightforward. Zerto is an improvement in RPO, RTO, ransomware protection, immutability, and cost. Avamar costs nearly 75 percent more. There's no significant difference in ease of use. 

I wasn't involved in the initial setup. After the deployment, there is a lot of maintenance. It throws out lots of errors, and we sometimes need to rebuild some of its components. Our backup guy is a little frustrated at times. 

We haven't seen a return aside from saving money on the annual license because we've had to invest so much time into getting it to work.

Zerto's price seems fair. It's competitive. 

Dell Avamar for Data Domain offers functionality similar to Zerto, but we weren't taking advantage of it. We also looked at Rubrik, but it's a cloud-based solution, and it's a little costly. We're not in a position to leverage cloud solutions at this time. Avamar costs too much to get the same features. Doing a rip and replace was more economical than keeping the hardware in place and adding the functionality.

I rate Zerto a six out of ten. I only give it a low rating because of the issues we've faced lately in our environment. If we didn't have those issues, I'd probably give it an eight.

If you plan to implement Zerto, I suggest double-checking everything. Confirm the configurations and ensure your backup targets are sufficiently sized. You must know what you want from the product, and that requires guidance from the sales engineer. Make sure the plan is solidified and you have a document that spells the whole thing out.

We use it for migrations and VM protection.

The near-synchronous replication is very good. It's very critical for us. For example, with SQL, we used to use Always On to protect databases at the database level, to give us high availability and DR. But now, in Azure, we don't do that. If we wanted to do that, we would have to have a SQL Server on the protected site and another up and running on the DR site and those machines would always have to be up and running. To save on costs, instead of using Always On, we're now protecting the VM as a whole, thanks to Zerto.

It's also the main tool that we use for our annual DR tests for all of our production applications. Once a year, for one week only, we do a failover of those critical production applications from the primary site to the DR site and we let them run there for that week. Zerto does the failover and the DR site becomes the active site while everything replicates to the former primary site. Once the week is over, we do a failback and Zerto is the main tool that we use for that, and we repeat the whole process. We're then good for the whole year. Zerto is protecting those VMs.

Another advantage is that Zerto has decreased downtime for us. It could have been a situation where we were down for weeks because of something that Azure did on their end. Even though Zerto has a partnership with Microsoft Azure, sometimes Azure makes changes that are disruptive. There was one change that affected our ability to replicate our critical workloads and it was a rough one. For that week, Zerto found a workaround because they were not getting any progress on resolving the situation from the Azure team. Zerto applied the workaround in their code and we were good, but that was a rough situation. Zerto goes out of its way to help its customers. We've had issues but Zerto has been very responsive.

The quickness and efficiency of creating snapshots, on a real-time basis, is one of the most valuable features. Whenever changes are made on a server, Zerto starts taking snapshots right away and replicating them to the DR site. It's very effective and very quick. Our SLAs are 24 hours, but Zerto could do what we needed, on-prem, in seconds, and in the cloud, in minutes. Zerto is way ahead of what our SLAs are.

Sometimes we do failover tests to make sure that we will potentially have a successful failover or migration. It's very flexible and does its job very well. And one of the things I love about the product is that whenever you do a failover, it gives you the ability to either commit or roll back. Some of Zerto's competitors don't have that ability, at least in Azure. That's critical for us because after we have DR tests on a weekend, we have users sign off on their applications that everything is fine. If something isn't right, we can always roll back to how everything was right before we started the DR test. And if everything is working great, then we commit.

Since we are primarily in the cloud now, Zerto definitely needs to update its platform. When we were decommissioning one of our on-prem data centers and going to Azure, there were issues. And with Azure, it's still limited in the way we can manage our resources there. Zerto hasn't quite kept up to date with how certain elements run within Azure.

In Azure, there is something called resource groups. You cannot create a resource without a resource group. You can apply tags to resource groups and that tagging information is very critical to our company because we now have 95 percent of our production environment workloads running in the cloud. We have to make sure that every resource group is tagged correctly, with the correct team and department because we have to bill them at the end of the month. The problem is that Zerto does not have that ability. When the product fails over or migrates a VM from on-prem, or even within Azure, to another site, it does not give you the option of selecting an existing resource group.

When it fails over, it uses the name of the group that you created within Zerto. The VM is failed over with no problem in a reasonable amount of time. But the problem then becomes that the resources are part of a resource group that has no tags. It does not follow our naming commission for resource groups and then we're stuck. It's not as easy just renaming the resource groups.

These components are very critical for us but they are missing in Zerto. They're aware of it because we've had feature-request meetings with our Zerto account team. They're working on it for the next release and have mentioned that they are going to be making improvements to the product. But for now, it's lacking.

Also, a downside with Zerto is that there is a lot of management overhead when running it in the cloud. On-prem, we used to have one Zerto management appliance, but in the cloud, we have about 20 to manage to protect our VMs. Zerto has mentioned to me that, for the next release, they're building it from the ground up and it will be much better in the cloud, with more cloud focus.

Because of the experience that I had with Zerto running on-prem, where we only had one appliance in each of our data centers, I deployed one in Azure as well. Little did I know that there were limitations and that more appliances had to be deployed because of all the replication of the traffic and the number of VMs that we were trying to replicate. But Zerto stepped in and helped when it came to that.

I have been using Zerto for four years.

The stability is an eight out of 10.

The scalability is also an eight out of 10.

They're very helpful. They always want to understand your situation and, even if they're not sure, they do their best to help and fix the problem. 

For on-prem, there were always references, but for the cloud there is a bit of a knowledge gap. I would always get workarounds, fixes, or KB articles for on-prem, but the cloud implementation is where the documentation is lacking. But the team does its best. It depends on who you get. Some know Azure, or cloud, and some still lack that knowledge. But if they don't know, they get the right person on the call.

Positive

We were a VMware shop on-prem and we were migrating to the cloud from on-prem VMware to Azure, so the tool that we were using to protect VMs through DR would no longer work. We used VMware SRM (Site Recovery Manager) for years when we used to be solely on-prem. 

We started looking for a product to help and, at the time, Zerto was the one that stood out among the competitors, and it was a solid product, so we started using it. Zerto is definitely a more effective product. It is a lot quicker when bringing our VMs up on the DR side, and even when we do a fallback. And Zerto is a lot easier to use than VMware.

The initial setup was not straightforward.

And maintenance is required for upgrades when there are newer releases, especially when it comes to Azure. There are newer releases that contain fixes and improvements and we do update the version of the Zerto appliance. They are running on Windows Servers, so we also have to patch the operating system. In Azure, there are a lot of SKUs with different pricing. Depending on the utilization of a VM, we sometimes make changes to the family types to save on costs at the VM level.

I did it with our Zerto account team, which included our sales engineer. Just the two of us were involved.

Zerto saves us a lot of time. One team member alone can handle the DR test using Zerto, whereas before, when we used SRM, at least two or three people were involved from the VM perspective and from storage. VMware was integrated with our NetApp environment and that meant at least two or three team members were involved. But with Zerto, just one person uses the product for a DR test.

We looked at Azure Site Recovery. We were close to going with it. It did have the ability to do resource group selection, but there were two showstoppers at the time that prevented us from going forward with it.

When we were looking at Azure Site Recovery, it seemed that it had a better cost per VM, but Zerto was not that far off. And we were more comfortable using Zerto to protect our VMs than the other products we were testing.

My advice is that if you're in the cloud, you really should test the failover of your VMs. If tagging is not a key component, you'll be fine. But if it is, that is a huge problem. And expect a lot more management overhead when it comes to managing Zerto in the cloud.

In terms of our RPOs, Zerto is consistent. From time to time, it may run past our SLAs, but that's because there are network or VM issues. And that happens very rarely. It almost always meets our RPOs.

The ease of moving data varies on the size. A good thing about Zerto is that it does give you a little chart indicating the step that it's at in the replication process.  But even if it's a small VM, it does take some time, including setting it all up and starting the synchronization. It's not instant.

We are using Zerto as a disaster recovery solution.

We utilize Zerto for three replication scenarios: on-premises to on-premises, on-premises to cloud, and planned cloud-to-cloud replication.

Zerto is easy to use and implement, especially when performing a failover.

Zerto's near synchronous replication is valuable for our SQL database.

The benefits of Zerto were immediately apparent. After implementation, we quickly realized we were protected against any disaster. Zerto also provides visibility into the health of replication, allowing us to identify and address any potential issues.

Since implementing Zerto, we have observed a positive impact on our Recovery Point Objectives, which have been reduced by half.  Zerto's ability to easily group servers by application and configure protection groups streamlined our processes. Moreover, Zerto's support for on-premises to cloud replication is invaluable. We've leveraged this capability to replicate all systems to the cloud, establishing a robust disaster recovery solution. Zerto has proven to be an effective cloud migration and disaster recovery planning tool.

Our Recovery Time Objective determines how quickly we can restore our infrastructure. Zerto has been instrumental in reducing our RTO by enabling rapid recovery in any disaster recovery scenario.

Zerto has significantly reduced our downtime. For example, some servers have a recovery point objective of just five seconds. During disaster recovery tests conducted last year, we recovered 60 servers within eight hours, including server delivery, startup, and operating system verification by our team.

Zerto is our primary tool for achieving all disaster recovery objectives.

Zerto is a flexible and resilient business continuity and disaster recovery solution. Its industry-leading replication technology enables seamless data protection across cloud, on-premise, and hybrid environments.

Another valuable feature is the failover capability. Unlike many other tools we tested, Zerto allows us to perform a disaster recovery test without risk to our production environment.

Zerto's current reporting capabilities are insufficient for our needs. We require detailed reports to analyze the performance of our environments. To achieve this, we have developed a custom reporting solution using Zerto and other tools to thoroughly assess VPG configurations and overall environment health against specified parameters. Unfortunately, Zerto does not natively provide this level of reporting functionality.

I have been using Zerto for seven years.

Zerto is highly stable, and I do not recall encountering any crashes.

Scaling Zerto is easy. We just need to add additional virtual/appliances servers.

Zerto provides excellent support, but response times to our issues can sometimes be a concern, possibly due to the size and complexity of our environment.

Positive

We currently utilize both SRM and Zerto, but SRM's replication capabilities are limited to data centers, while Zerto offers additional cloud replication options. Unlike SRM, which is exclusively designed for VMware infrastructure, Zerto is compatible with other virtual platforms, providing greater flexibility.

Zerto is easier to use than SRM.

The initial deployment is straightforward. We only need to deploy a few servers to build an environment and start to replicate.

Deploying Zerto in a single region required three months. One contributing factor to this timeline was the time-intensive process of collecting Virtual Recovery Appliances and deploying them across 500 ESXi servers. A team of ten architects and engineers was dedicated to this project.

The implementation was completed in-house by my team and me. As the architect, I oversaw the project's planning, construction, and deployment. We consulted with Zerto to identify potential areas for improvement.

Compared to other options like SRM, Zerto is a more expensive solution, making it primarily suitable for larger organizations. Smaller and medium-sized businesses might find Zerto's cost expensive. While Azure Site Recovery is free for users of Azure cloud services, Zerto offers a broader range of features.

I would rate Zerto nine out of ten.

Our organization takes a unique approach to disaster recovery testing, conducting 15 tests annually to meet policy and audit requirements. Zerto is the cornerstone of our DR testing strategy, enabling us to validate between five and seven applications in each test.

Zerto requires ongoing maintenance and a dedicated person monitors it daily. However, we must still test and deploy updates into our production environment.

Potential users should be knowledgeable of virtual environments and clearly understand their disaster recovery needs, including the required replication type, desired recovery strategy, and whether Zerto aligns with their specific requirements.

We do many data-related activities for various government ministries in India. We use Zerto to back up and recover data in many training and capacity-building activities.

We implemented Zerto to address challenges with data centralization in our complex platform environment. Previously, pulling data from a central source was impossible due to the need to feed it into an internal location before deployment. This limitation hindered customization and integration efforts. Additionally, integrating our primary data source, previously used with IBM, into the new platform proved difficult due to compatibility issues. Zerto's capabilities were seen as a potential solution to these problems.

The remarkable benefits of Zerto have yet to manifest fully. The software operates efficiently without significant bugs or issues, and Zerto's customer support has been responsive. While real-time reporting is a standout feature compared to other trial products, its impact on our ongoing projects remains to be determined. A full assessment of Zerto's potential will require an additional six months.

Zerto has significantly improved our Recovery Time Objective, particularly regarding project timelines. The expedited turnaround during critical project phases has been instrumental in streamlining our processes. By accelerating these stages, we've reduced the need for additional developer resources and eliminated time-consuming tasks associated with establishing essential parameters and metrics. As a result, projects that previously took six months can now be completed in as little as four. This accelerated timeline has enhanced profitability and optimized resource allocation, allowing us to maximize project revenue.

Zerto has significantly reduced our disaster recovery testing efforts. By consolidating software and streamlining processes, we've dramatically decreased the required manpower. Multiple teams efficiently utilize a single platform, eliminating the need for disparate services and reducing costs. This centralized approach has markedly decreased the time and resources invested in disaster recovery testing and pre-testing activities.

Zerto's greatest strength is its speed. We never encountered lag or interruptions, even when working remotely from home or other locations with potentially limited internet bandwidth. The software's streaming performance was exceptional, without buffering or connectivity issues. This was a primary factor in our decision, as Zerto emphasized its ability to operate effectively on lower bandwidth connections during the initial demo. Deploying the software in any remote location is straightforward and hassle-free.

The primary concern expressed by all server users is the lack of robust integration features. While Zerto offers some integration capabilities, the smooth and efficient data flow between portals remains a significant challenge. The support and technical teams know this issue and actively seek user feedback, but progress has been slow. The current process, involving multiple platforms and a database management system bottleneck, is time-consuming and inefficient. Additionally, while reporting and dashboard features exist, real-time reporting and mobile functionality require improvement. The user interface could be more intuitive and user-friendly. Customization, a critical requirement for government clients, is another concern. Implementing requested changes is often time-consuming and expensive, hindering adaptability. Addressing these integration, reporting, user experience, and customization issues is essential for improving customer satisfaction and retention.

Currently, Zerto only offers an annual subscription, but it would be beneficial to provide quarterly and semi-annual subscriptions to help retain clients.

I have been using Zerto for one year.

I have not encountered any performance issues, such as lagging or crashing. The system operates efficiently and reliably under various conditions, even with significantly lower bandwidth. Zerto has consistently demonstrated stability and high speed, ensuring uninterrupted application performance.

Approximately 50 to 60 individuals within our ecosystem utilize Zerto directly or indirectly. Given its operational efficiency, which I estimate to be between 95 percent, I confidently assert its scalability. While we haven't encountered a scenario within our ecosystem that necessitates testing its scalability limits, its exceptional performance thus far strongly suggests its capacity to handle increased demands.

Zerto uses a ticketing system and offers support through a help desk accessible via chat or phone. A dedicated technical team is assigned to address customer issues, which are typically resolved within 24 hours. We have not experienced any significant delays in issue resolution.

Positive

We find the Zerto pricing fits our budget.

I would rate Zerto nine out of ten.

Maintenance is required quarterly. The Zerto technical and business teams collaborate with us on the backend to remove all the repeated queries that make the system sluggish. This service is charged additionally.

I strongly recommend that anyone considering purchasing Zerto begin with the 30-day trial, which can be extended to 60 days. This ample timeframe allows a thorough evaluation of all features and functionalities. Understanding Zerto's customization and integration capabilities to align with specific business needs is crucial. Had I followed this approach and shared my feedback earlier, the outcome might have been different. Therefore, it's essential to fully explore the trial version before committing to an annual subscription. Close collaboration with the Zerto technical team is vital to ensure successful implementation. While sales teams often present an optimistic view, real-world experiences from existing users provide the most valuable insights. I encourage potential customers to connect with other Zerto users through industry networks to gather honest feedback before purchasing.

Our primary use case is to continuously replicate our VMs to our DR site. Having the ability to recover them at almost any point in time, mostly back thirty days, is the main purpose of Zerto. 

We didn't previously have a continuous replication tool and now we have the ability to recover to any number of points in time. That's really beneficial to us. It cuts down our recovery time. 

The most valuable feature is how quickly it powers down the original source VMs and the speed at which it powers up the new VMs. The amount of time it takes to put up the operating system is valuable. The speed is what I like the best. 

The near-synchronous replication is awesome. When you get hit by a cyberattack, you never know where the clean VM resides, and at what point in time it actually exists. Having the ability to find the point in time when we are clean is a good thing.

We are going from a physical data center to a physical data center at the moment.

We use Zerto to protect VMs in our environment. It increased our ability to restore at a point in time. We didn't have it before, and now we have it.

Compared to other tools, Zerto is a lot faster. There are tools with your primary block storage backup, but they're just not as fast.

I'm having a problem with CentOS 7 and with VMs with multiple network adapters. Zerto recognizes those multiple network adapters on CentOS 7 vm but it will not give me the option to specify a failover IP, for that particular VM. Something's not working right, but Zerto is going to follow up. 

Zerto has been in production for three months. 

It seems stable so far. 

The scalability seems pretty easy. 

Customer service is really good. Technical technical support is lacking. At least from who I've been talking to. Maybe my case has not gotten bumped up to the higher level technicians. Customer support is great, and they're really responsive but their technical knowledge is just not quite there.

Zerto's documentation is outdated. I'm finding it hard to find documents related to my questions. Their documentation is bad.

Neutral

The initial setup was very easy. We needed a little help with the initial configuration, but it was pretty straightforward. 

We worked with Eagle Technologies for the deployment. We loved them.

I wasn't involved in negotiating any pricing. It evidently worked into our budget.

We also looked at Cohesity and Rubrik. I don't know that there's anything like Zerto. We went with Zerto because our third-party vendor recommended it. We also did a proof of concept two years ago. We liked what we saw with Zerto so we went with it. 

Everybody taunts their one pane of glass but Zerto is simple to use. I really like the GUI, the interface is not too busy. 

I would rate Zerto a nine out of ten. We don't have a test network setup. I know with Zerto, you can simulate a recovery. 

Zerto would be a perfect ten if the documentation was easier and if level 1 support would be more knowledgeable.

Zerto is deployed on a VM, and we use it to replicate the database for our POS system in our data center.

Zerto helps us when our server has an emergency. When we needed to get something from a server that had a corrupt file, it saved us from needing to go back to a tape or a backup to use that server. The recovery works better than our backup. I would rate that nine out of a 10.

It works great because we only use it in VMware for our virtual machines. We use Zerto Instead of snapshots. Zerto is a lot quicker than other solutions. It cuts our downtime in half when we need to recover data.

Data replication is the most valuable feature. The near-synchronous replication works in the background, so it does not interfere with the production usage of the server. Zerto is challenging to set up but easy to use. It's not difficult to configure once you see how it works. I'd give it at least eight out of 10 for ease of use.

I've been using Zerto for about a year.

Zerto is highly scalable. Even though we only have it on a couple of servers, we could do all of them if we want to.

Customer support is great. I'd say it is at least a nine. When I have a technical question, it sometimes takes a while for tech support to respond. That's a problem everywhere.

Positive

I've used backup solutions like Veeam in the past, but Zerto seemed like a better, faster solution. We adopted Zerto because of the speed, and because we wanted to do everything in-house. I would rate Zerto eight out of ten for ease of use, but Veeam seven out of 10. 

Setting up Zerto is straightforward, but I needed to call tech support a few times with some basic questions. I handled the setup by myself because I'm in charge of servers and VMware. It doesn't require much maintenance aside from updates. 

It reduces the time and effort needed to get our data. 

I rate Zerto a nine out of ten. When I first installed it, I learned a lot about how it worked and how to integrate it with my storage. I needed to configure our storage to work with this because we do everything in-house. It's crucial to understand how everything works together.

You need to read the installation instructions thoroughly and prepare your VMware environment. I jumped right into it and didn't go through everything. Read everything and watch some videos first to prepare. If I do it again, I will watch the videos a few times to make sure I understand what's required and go from there.

I use Zerto to monitor replication, configure protection, and manage disaster recovery and performance.

We implemented Zerto to manage disaster recovery and also for faster performance on backups and failovers.

Learning how to use Zerto can be easily achieved with some training and practice.

Zerto has helped us reduce downtime, retrieve backups faster, and manage our workload more efficiently.

Zerto has reduced downtime by 20 percent and helps protect the VMs in our environment.

It is 25 percent faster at recovering data compared to IBM Spectrum Protect.

Zerto has helped save four hours per week in recovery situations and has reduced our disaster recovery testing by 30 percent. We have used five percent of those savings towards other value-added tasks.

It has positively impacted our IT resiliency strategy.

Zerto enables disaster recovery in the cloud which is important.

Zerto provides real-time analytics and monitoring, enabling our organization to quickly identify and resolve issues. 

Zerto makes my work easier. Replicating my settings helps me recover point objectives faster and retain policies.

The most valuable feature is the customization that allows me to set my protection group myself.

While Zerto provides good service, I find the pricing to be high and believe there is room for improvement. I would like to see Zerto implement a pay-as-you-go model.

While Zerto offers scalability, its implementation can be more challenging in larger organizations, indicating room for improvement in its scalability features.

I have been using Zerto for three years.

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

I would rate the scalability of Zerto seven out of ten.

The technical support responds promptly to our requests.

Positive

I previously used IBM Spectrum Protect but Zerto provides a quicker recovery time. With IBM the recovery process for particular data is manual but with Zerto it is automated.

The initial deployment of Zerto was straightforward and took two hours to complete. Two people were involved in the deployment.

We have seen a 20 percent return on investment.

Zerto is priced high.

I would rate Zerto eight out of ten.

Zerto is deployed in multiple departments and we have ten users.

I recommend Zerto because it helps recover data faster and improves its overall quality.

We use Zerto for disaster recovery. That is our main use for it.

Everybody at the top wants to be able to hear about our disaster recovery timelines. The ability to restore our Practice Management systems several states away in a matter of 45 minutes is phenomenal.

I love the near-synchronous replication of Zerto. We are based out of Alabama but we have our off-site disaster recovery in Colorado. Being able to have data very quickly over in Colorado is phenomenal.

Zerto has enabled us to do disaster recovery in the cloud, rather than in a physical data center. Having DR in the cloud is super important for our organization. That is where our business intelligence center lives. Without that data, we do not make money.

We have used Zerto to help protect VMs in our environment. It has been a huge contributor and has made a world of difference in terms of timelines. It helps spin up our Practice Management systems in a very quick time frame.

The ease of adding additional servers is valuable. We have a portal that we can go into to add those new servers, and then outside of that, the overall time that it took for disaster recovery simulation is also good.

They are doing a lot of great things, but I have heard that Zerto is expensive.

I have been using Zerto for two years.

I would rate it nine out of ten for stability because we had one virtual machine that was not backing up properly, but we did work with support. We got phenomenal support. They helped us fix it.

I like the scalability. Because we are in the acquisition space, we wanted adaptability. As new engineers are coming in and adding more to our data center, they can go through and they can just add it to Zerto. That is a part of their process. 

They are fantastic. I would rate them a ten out of ten.

Positive

We had a different platform previously, and we swapped it with Zerto about two years ago. 

We had Commvault. We were not getting consistent backups. We were not getting consistent disaster recovery. Each of our simulations did not match up, and nothing made sense.

I would rate Zerto a ten out of ten in terms of speed of recovery versus other solutions. 

It was super easy. We did partner with Verinext to come in and help implement it, so the swapover was instantaneous. It was super quick.

Our experience with Verinext was fantastic.

We have seen an ROI. We had an outage in our data center, and we were able to use Zerto to spin up in Colorado to be able to continue to operate, which is multi-million dollars at 450 animal hospitals.

I have heard that it is expensive, but that is not my world.

N-able was a solution we looked at, but it did not fit our needs. We had previously been using Commvault, and then we found Zerto. Our solutions partners were the ones that recommended it to us. After we saw what it was able to do, we made the swap.

If someone is considering Zerto, I would advise them to go ahead and swap to Zerto. I would share my entire experience with it with them and how it has been phenomenal for us.

I would rate Zerto a ten out of ten because of the recovery time.