We use Zerto for disaster recovery and cloud migration.

We are an MSP, so we have Zerto deployed on multiple public clouds, private clouds, and on-premises.

We implemented Zerto because its continuous data protection significantly reduces data loss and downtime costs. In the event of a production issue, we can quickly recover using the user-friendly Check Point feature. Zerto also offers flexible support for storage models, primary and disaster recovery, and hypervisors.

Zerto's user-friendly interface simplifies data protection tasks. It allows users to create virtual protection groups easily, configure failover and recovery processes, and manage licenses.

Zerto's near-synchronous replication can replicate our primary data center services related to PR, which is essential. But somehow, we are facing some pros and cons on this. If we face any challenge like a ransomware attack on our PR site, with the synchronous mode, it is also replicated on DR. That can affect us. So, if we use an asynchronous model, our data will not be replicated continuously from the PR site to the DR site. There is a specific time bracket where the data has been replicated after a particular time frame. So, there are different types of business cases and business requirements. However, we are comfortable with the near-synchronous model.

Zerto helps us set up any disaster recovery site on a cloud-based model and establish an on-premises-to-cloud migration plan. The continuous data protection feature protects our infrastructure services from ransomware and other bugs.

Our virtual protection groups safeguard virtual machines across various models, including hypervisors and virtualized environments. When configured to route to our disaster recovery site after synchronization between sites A and B, VPGs achieve our desired Recovery Time Objective and Recovery Point Objective, meeting our Service Level Agreement. Flexible protection models range from 250MB to 350MB, with varying time slots to facilitate data recovery between the PR and DR sites.

Zerto provides two functionalities: live migration and test failover. Live migration allows a seamless transition of our primary machine to the disaster recovery site within ten minutes.

Zerto has reduced our RTO from 30 seconds to three to nine seconds and has helped reduce downtime.

Zerto has helped save time in a data recovery situation and helped reduce our DR testing.

It has improved our IT resiliency strategy by 90 percent.

The ability to perform disaster recovery in the cloud is helpful because it can reduce our DR footprint and time.

Continuous protection is Zerto's most valuable aspect.

Zerto can improve by offering bare metal recovery for our physical infrastructure.

I have been using Zerto for three years.

Zerto is stable.

Zerto is scalable, and if we need to scale down the line, we know it can handle it.

The technical support is good.

We previously used VMware's Site Recovery Manager. We switched to Zerto because it is easier to use and requires less set-up time.

The initial deployment of Zerto is straightforward. We must set up a VM server and install the VR agents, followed by the PR site.

The deployment times vary depending on the business model, but for someone with full knowledge of Zerto, it can be completed within 30 to 90 minutes.

The implementation was completed in-house.

I would rate Zerto ten out of ten, but I would like it to offer bare metal recovery as well.

No maintenance is required for Zerto.

We utilize Zerto as part of our disaster recovery toolset. We employ a multi-tiered model, catering to a select group of customers, primarily hospital clusters. These customers maintain on-premise networks with cloud-based disaster recovery. In this managed service offering, we leverage Zerto to facilitate their cloud recovery.

The replication is quick. We encountered some challenges replicating the data during the first full copy. Since we weren't using Zerto, I suspect the bandwidth requirements for replication were a bottleneck for us. However, once the initial copy was complete, the process became seamless. The recovery was near zero after the first replication. Zerto worked perfectly.

We implemented Zerto because it supports a multi-tenant model, which was a critical requirement for us. We have five tenants located on-premises across five different data centers. However, we only have a single disaster recovery site in the cloud. Zerto's solution enabled us to consolidate our disaster recovery needs. Previously, managing five separate data protection solutions for each data center and five different cloud recovery subscriptions would have been incredibly expensive. Zerto significantly reduced our costs. Additionally, Zerto provides a single-pane-of-glass dashboard, allowing us to manage our infrastructure efficiently and effectively. This comprehensive view offers full control over our applications and complete visibility into all our tenants. As an infrastructure manager, I believe these features are the most valuable contributions Zerto has made to our organization.

Zerto has helped save around 30 percent of our time.

Zerto has helped achieve significant cost savings.

In the VMS portal, we had a relatively small amount of data overall. We also had multiple tenants, each with a maximum of 20 to 30 virtual machines on-premises. These VMs weren't particularly large. As a result, recovery was quick, typically taking less than a minute. My Recovery Time Objective would be less than a minute for any VM, even for a complete migration of all on-premises VMs to the cloud.

While I wasn't privy to the details of the client's previous DR solution before implementing Zerto, our discussions revealed significant time savings with Zerto's recovery process. Compared to their prior on-premises DR approach, Zerto offers a substantial reduction in recovery time – at least 15 to 20 minutes faster. This improvement stems from eliminating the need to coordinate with personnel and the time required for on-premises recovery procedures at their dedicated DR site. Previously, they relied on manual, on-premises to on-premises recovery, which inherently took longer. However, a direct comparison between their old solution and Zerto wouldn't be entirely accurate. Zerto offers significant efficiency gains, boasting up to 200 percent improvement.

Migrating data through Zerto is straightforward with careful planning. Our first experience involved Zerto's support throughout the process. While initially challenging due to our lack of experience, we were able to navigate the initial setup. One hurdle we faced was optimizing network traffic for the initial data replication from on-premises to the cloud. However, we embraced the learning curve, documenting everything as we gained control of the environment. This ensured a smooth integration for subsequent tenants. While the first migration presented some difficulties, as is to be expected, Zerto's excellent support made the process manageable. Their responsiveness in explaining and resolving issues made it a positive experience overall.

The RPO was very close to zero, meaning there was minimal data loss between replications. However, this could be impacted by the specific database being hosted and other factors. For application servers or virtual machines replicated on-premises to the cloud, I believe there was negligible lag or delay, assuming no network issues. Bandwidth and network traffic did play a role – we observed instances of slower RPO due to traffic spikes or network events. However, with Zerto providing the recommended data bandwidth, we encountered minimal challenges. In most cases, I'd say 90 percent of the data was synchronized almost constantly. The only exception was when network issues arose.

Our data center experienced an issue, necessitating a disaster recovery procedure. Fortunately, data loss seems minimal, and the impact on our clients appears negligible. This is partly due to the managed service we provide for a tenant, who fortunately didn't perceive any significant data loss. The success of the recovery is also attributed to our user-friendly, always-in-sync system. Upon receiving alerts and notifications, we promptly informed the client, who then quickly authorized the recovery process. From our perspective, the recovery went smoothly with minimal challenges. In the actual scenario, we believe data loss was negligible. While some data loss might have occurred technically, it wasn't significant enough to cause any noticeable impact on the client. It's important to note that our monitoring team maintained complete control of the situation, allowing for swift decision-making and a speedy recovery.

In a data recovery scenario, we'll still have our database administrator, Linux administrator, storage administrator, and Zerto operator available. While Zerto can automate disaster recovery and VM restoration, it's important to remember that it's not a foolproof solution. Even though Zerto streamlines the process, a well-prepared organization will always maintain backups and ensure a dedicated team is in place for data recovery. Zerto doesn't reduce the number of personnel involved; rather, it enhances their productivity by freeing them up for other tasks during a recovery event. During a recovery, it's still recommended to have everyone on call. While Zerto handles most recoveries, there may be situations where manual intervention is necessary. By being fully prepared, our organization can effectively address any data recovery situation.

It is easy to manage and monitor the DR plans using the Zerto GUI.

Zerto's most valuable features include its user-friendly interface, multi-tenancy capabilities, and near-zero downtime recovery. Zerto is easy to learn and use, even for those with limited technical experience. Additionally, Zerto's failover testing functionality allows us to run tests in real time without impacting production systems.

We encountered some issues during Active Directory recovery. When we implemented Active Directory, we provided feedback to Zerto regarding the challenges of recovering AD from the on-premises environment to the disaster recovery site. Unlike other virtual machines, AD recovery presents unique difficulties due to its active-active nature. It's unclear whether these challenges stem from Zerto itself or limitations within Microsoft Active Directory. However, in our experience using Zerto for AD recovery compared to other technologies, we faced data discrepancies that necessitated workarounds to bring AD online at the DR site.

Certain applications we migrated from production relied on Active Directory authentication. To ensure successful application functionality at the DR site, a functional AD environment was a prerequisite to application migration. Therefore, our initial step involved copying and guaranteeing a running AD instance on the DR side before application recovery.

However, upon attempting application authentication on the DR side, data inconsistencies prevented successful authentication. To address this, we created an isolated clone of the AD environment and conducted tests. Through trial and error, we were able to develop workarounds to resolve the issue. Notably, these challenges were specific to Active Directory; other VMs didn't exhibit similar problems.

I have been using Zerto for over 3 years.

Zerto has been very stable for us. We do apply patch releases and upgrades whenever necessary to ensure continued stability. Fortunately, we haven't encountered any major bugs or issues that would cause significant downtime, unlike what we've experienced with some other tools. Zerto has been a reliable choice for us.

I would rate the stability of Zerto 9 out of 10.

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

The technical support is fantastic. They offer same-day assistance, and their documentation is clear and comprehensive.

Before implementing Zerto, the client's disaster recovery relied on an on-premises to on-premises failover strategy. Seeking a cloud-based solution, they chose Zerto to leverage its expertise in this area.

We previously used another tool for DR orchestration. While Zerto can also perform recoveries, it focuses on virtual machines and doesn't extend to the operating system or database level for starting and stopping applications within those VMs. Despite these limitations, Zerto excelled in its support. The Zerto team provided excellent assistance whenever we faced challenges, joined calls to help us troubleshoot, and offered clear timelines for resolving issues. Their documentation was also thorough. In contrast, the previous DR tool lacked comparable support and documentation. This stark difference in support quality is why we favored Zerto and ultimately removed the other tool from our project. Currently, we rely solely on Zerto for our existing tenants, and we plan to continue using it for future ones as well.

We encountered some challenges during the initial setup. Zerto offers several data replication options, I believe 2 or 3. These include copying data to our hard drive or storage box, copying it to the DSR site, and replicating it over the network. However, only network replication worked for us.

The issue might have been related to bandwidth requirements. It's possible that either Zerto itself or our network infrastructure wasn't up to par. We faced some challenges during that initial phase.

However, after the initial setup and the application of delta copying, which happens daily, we rarely experienced any replication issues. Most of the time, network glitches and fluctuations caused brief disconnections, but overall, replication ran smoothly.

We went into the Zerto deployment with a clean slate. Both team members were new to Zerto, so we were all learning as we went. This initial deployment was challenging, but it gave us valuable hands-on experience. Once we had a firm grasp of the environment, onboarding subsequent tenants became seamless. We developed a clear plan and approach, which streamlined the process for future deployments. Technically, the challenges weren't ongoing. The main hurdle was understanding how to integrate Zerto with our existing infrastructure. While that initial learning curve was steep, Zerto's excellent support helped us navigate it successfully.

The deployment time for Zerto varies depending on the complexity of your environment. More complex environments will require a longer replication process. However, on average, we can onboard a new customer within 1 month. This timeframe encompasses the entire process, from the initial planning phase to the deployment of up to 30 VMs within a tenant.

Our project involved 2 separate IT teams at 2 different locations. One team acted as the managed service provider, while the other represented the client side. The client-side team, located on-premises, provided us with essential information about their data centers. This included details on virtual machines, such as their size, quantity, and basic data collection metrics. They also helped us identify their storage requirements. Based on this information, we planned our cloud storage procurement and other necessary actions. The project team comprised approximately 10 to 15 people, including project managers, IT personnel, storage specialists, network engineers, and development experts.

I would rate Zerto 10 out of 10.

Our organization uses Zerto to manage the replication of data centers from 7 on-premises locations to the IBM cloud for our midsize clients.

Our environment consists of VMware, data storage, and a network, with Zerto deployed for disaster recovery. While VCDM and VMware are managed by our cloud provider, we maintain 5 additional technologies with a team of 8 people.

We experienced a brief on-premises outage. Fortunately, we were able to recover quickly using Zerto. The software triggered an alert, notifying our monitoring team. These features proved to be very helpful. Additionally, we were able to promptly contact our clients and explain the situation. They responded quickly and effectively, minimizing the impact on their end. Our clients were pleased with the response.

I recommend Zerto to others.

We use Zerto for the disaster recovery capabilities that it provides us. It is for our Tier 1 applications.

Zerto allows us to protect individual VMs. With the other solutions, we are protecting the storage that the VMs live on, which is costly, so Zerto does save us money.

Zerto has near-synchronous replication. It works very well. Our RPO or recovery point objective time was 20 minutes, and we were doing thousands of VMs. We not only met the RPO; we exceeded it. There were many times when it was just seconds behind.

We have used Zerto to help protect thousands of VMs in our environment. Zerto has had a good effect on our RPO. It has helped to exceed our RPO. Our RPO on some of our critical systems is 20 minutes, and we exceed that. Most of the time, we are under 2 to 3 minutes.

It is very easy to migrate data. We ended up migrating from one data center to another data center, and we moved 20,000 virtual machines with Zerto. It was great.

Zerto lowered our RTOs as well. As a part of the solution analysis that we did for the RPO and RTO, Zerto's interface to do a DR test or a DR recovery was the fastest. We had a 24-hour window to recover 5,000 virtual machines, and we were doing them in three to four hours.

Zerto has helped us to reduce downtime multiple times. We had one incident where we used it to do a recovery. The downtime was roughly about 20 minutes. We do not have a value on that because it is customers' health information. I do not know how it affected the end users or customers outside of our company, but it does affect them.

Zerto has saved us time. When files were deleted, we were able to recover the files quickly. While doing OS patching on the servers, when the servers failed on the reboot, we were able to recover all good things when it came to quick recovery on it. As opposed to pulling it from our backup, it has cut our time probably in three quarters.

Zerto has helped to reduce our organization's DR testing. A DR test or a recovery used to take us days, whereas now, it takes us hours. The system that we were using before took multiple engineers to do the DR test, whereas today, a single engineer can do the DR test, and then we need just a couple of engineers to do checks on it, so it saves us a lot.

Zerto has reduced the number of staff involved in a data recovery situation. Instead of a group of people, we now just need one.

We used Zerto for immutable data copies. It was good, and they were on a course, but they shifted their focus. They were doing DR specifically, and then Zerto started shifting over towards doing backups. We were very excited about their long-term backups, but when HPE bought them, HPE stopped that part of it because they were directly competing against their solution. At the time they were doing it, we were very excited about it.

The DR testing capabilities that it has are valuable.

Its ability to roll back if the VM or the server that you are recovering does not come up right is also valuable. You have the ability to roll back a few seconds or a few minutes. The rollback feature is great.

While going in, we were looking at the backup tool so that we had a DR tool and a backup tool, but they stopped developing their backup solution built into it. That was a bummer for us, so now, we have a DR solution, and we have a backup solution.

For the actual application itself, we have put in our request for certain features, and so far, they seem to be adding those features. In their latest one going to version 10, they did an appliance, which we had asked about 6 years ago. It is great to see that they are doing an appliance. There would be even more savings for us now because we do not have to pay licensing for a Windows VM.

I have been using Zerto for about 7 years. I have used Zerto a few times at different companies.

We have seen very few issues. It is one of the few solutions that actually runs. If you do your leg work and implement it right and go through all the design and other things, you do not have to babysit the solution. Care and feeding is what it amounts to. That is all you have to do, whereas with a lot of the other solutions, you have to babysit them.

Its scalability is very good. It scales very easily.

They could do better in regards to escalating an issue. I would rate them an 8 out of 10. In defense of support, I know it is hard because they are talking to somebody who has got 28 years of IT support. When I get on the call, I am probably dealing with someone who is just starting out. He has to go through his standard process. However, somebody like me is looking for faster support and would like to get to a real smart guy quicker.

For disaster recovery, we were using VMware Site Recovery Manager, and it was not able to provide the recovery, the RTO, or the RPO that the company required. I went out and did a discovery for different DR solutions, and that is where I came across Zerto. Zerto replaced VMware Site Recovery Manager, and it saved us millions.

Our deployment model is hybrid. I was involved in the initial deployment. It was straightforward. It was a lot easier than VMware Site Recovery Manager. It took us a week to deploy it.

In terms of maintenance, other than typical patching and upgrades, it does not require any maintenance. VMware Site Recovery Manager required a lot of ongoing maintenance.

We implemented it in-house. There were just three of us involved in its implementation.

The pricing is based on virtual machines. They need to do better in regards to their tiering pricing rather than one price per VM. A lot of times we have VMs that are lower tier, such as Tier 2 or Tier 3, but we pay the same price as for Tier 1. I know they are developing this out, but it would be nice if they could provide a little better pricing in regards to their tiering protection.

We tested four different solutions, and Zerto was the only one that was able to meet our requirements. We did PoC on Zerto and two other solutions. Zerto was by far the leader when it came to disaster recovery.

To those evaluating this solution, I would recommend doing a PoC on it. Deploy it in your environment and test it. Most of the problems you are going to see are due to the replication, and that is the site-to-site connection. One of the problems that I have experienced with Zerto has been related to replication, not the solution itself.

We have not used Zerto for blocking unknown threats and attacks. Thankfully, we have not had that. We do not have experience of that, thankfully.

We have used Zerto to do DR to both AWS and Azure, but the ability to do disaster recovery (DR) in the cloud is not something critical for us because the health insurance requirements for certification do not allow us to put our Tier 1 data in the cloud. Also, because our applications are multi-tiered where they reach out to the mainframe, Solaris, and other equipment outside of the virtual environment, it did not make sense to go to the cloud with it, but we do have it. We have a development environment there. A lot of times, we will use it to refresh the development environment. So, it is important, but in our case, it is not critical for us.

We have not had any issues utilizing Zerto to support DR on AWS, but AWS is on the slower side. The reason is that for the connection to AWS, even though it is a direct connection, the speed does vary for us.

I would rate Zerto a 10 out of 10.

We use Zerto for our application data recovery.

Zerto's near-synchronous replication delivers exceptional results. The data at our recovery site is kept nearly identical to production in real-time, minimizing data loss to near zero.

By utilizing Zerto's immutable data copies and adhering to the three-two-one rule, we have established a highly effective recovery strategy.

While Zerto doesn't inherently block unknown threats or attacks, its detailed history logs enable us to revert to a pre-attack state, essentially restoring a clean system.

Our production machine experienced changes that caused the application to crash. To resolve this quickly, we restored the machine to its previous state using a recovery copy located at the recovery site that was made by Zerto. After powering on the restored machine, we changed its IP address, making it accessible again.

Zerto has a positive effect on our RPOs.

It boasts impressive recovery speed. As a customer, all we need to do is power on the machines at the recovery site - that's how simple and fast it is. Even if the recovered state isn't ideal, we can easily rewind to a specific point in time and power up another instance of the machine at that moment.

Zerto makes it easy to migrate data. The total configuration is user-friendly.

While our current RTO is three hours, Zerto can significantly reduce it to just five minutes.

Zerto helps us significantly reduce downtime during hardware failures, software updates, and natural disasters.

While we haven't experienced a ransomware attack, we have a recovery plan in place. If one were to occur, we could quickly restore production to a previous point in time, minimizing downtime and data loss.

Zerto helps us reduce the amount of disaster recovery testing we need to perform, which also allows us to reduce the number of staff required for the testing down to two.

The Zerto application is licensed per VM. However, the amount of data stored on each VM does not affect the licensing cost. Whether we have terabytes or just a few bytes on each VM, the licensing fee remains the same. This means we only pay for the machines we are replicating, which can lead to significant cost savings.

Real-time replication is a valuable feature, ensuring that changes made to the production site are immediately reflected at the recovery site.

Another feature I appreciate in Zerto is its detailed logging. This functionality allows us to easily access past data and reconstruct the machine's state at any given point in time.

We can recover the replicated machine at the recovery site by simply clicking it back up from the replicated machine. This allows us to keep the original machine running while the recovered machine is active. It's also vendor-agnostic, meaning it works with different hardware vendors like HP or NetApp. In other words, Zerto adapts to the specific hardware we have regardless of the vendor.

Zerto's solution could benefit from additional security features, such as malware scanning tools at the recovery site.

I have been using Zerto for five years.

Zerto is stable.

Zerto is scalable. We just need to add a license and they provide a new key.

The technical support team offers an excellent service. They empower customers by providing comprehensive documentation and guidance, helping them resolve future issues independently.

The initial deployment was straightforward, and I handled it independently. My only reference was the provided documentation; I required no further assistance.

Zerto's pricing doesn't depend on the number of virtual applications. Even if we have a server with 200 terabytes of data, we'll only pay for protecting that single server, not for the total size of the replicated data. This simplifies our cost structure.

The licensing cost is fair.

I evaluated Veeam and SIM before choosing Zerto. Zerto's interface is much easier to use than the other solutions I tested. Integrating into our environment is also seamless.

I would rate Zerto a ten out of ten.

No maintenance is required.

You can save a lot of time researching solutions by choosing Zerto. It's efficient, easy to deploy, and easy to maintain. Additionally, Zerto offers excellent support, including comprehensive documentation, breach and RCM coverage information, and a knowledgeable customer support team.

We use Zerto for offsite disaster recovery. We have over 70 VM servers, several of which are our mission-critical servers that are replicated to our VMware hosts at an offsite location.

We also replicate our Citrix environment and Disaster Recovery Zen App servers with Zerto to our offsite location as well. Most of our servers are Windows-based operating systems. However, this doesn't matter because we are replicating the VM servers. Further down the line, we may invoke extended retention for some of our more important servers.

It gives us peace of mind that our data, servers, and environment are protected. We can easily restore VMs quickly and have confidence that the replicated data will be current.

We are able to show proof in tests, reports, and live data to our owners, showing that our most sensitive data and servers are being replicated to an offsite facility, and we can restore it in case of a natural disaster or from our system being compromised by ransomware.

Our IT staff can easily navigate through Zerto and test failover, see if there are issues with replications, and create offline copies of the data.

Being able to test our VPGs and prove that our disaster recovery setup is in place and functional.

Our business owners can be assured that our data is protected, and in case a serious problem occurs, they know that we will be able to recover easily.

Zerto is fast to restore our mission-critical servers when needed. We also use Zerto to make copies of our VM servers for our offsite Citrix Zen App Servers. Zerto has helped simplify the process of disaster recovery setup and made the tasks more efficient for our IT Staff.

Zerto could add text alerts if there are critical problems and alerts if changes affect our replication. We do receive emails, and they will alert us to issues that we are having with VPG SLAs.

I don't have any complaints about Zerto, and I hope they continue to develop new features. If they had classes on using Zerto, that would help with onboarding new IT staff. They may already have them, and I am not aware that they do. Overall, Zerto works out great, and they do a good job.

I've used the solution for five years.

I use Zerto for disaster recovery.

The time it takes to fail a server over to DR has been great. We've seen a reduction in time spent. We can do it in minutes. Being able to go back to certain snapshots, to failover to another location, and then go back to specific snapshots is quite useful. We can roll back easily.

The off-site replication is excellent. We have workloads that aren't DR-aware. Being able to replicate it to other data centers is great. We don't have another way to do it, currently.

The near-synchronous replication is good. You get five-second data points. It's not something we advertise to our customers, the developers, however, we've had instances where we needed to go back two hours, prior to a file being deleted, and it's helped.

We're protecting our VMs with Zerto. It's positively affected our RPOs. It meets the objective. It's the only way we can have a solution for certain applications where we send an entire application to another data server.

It's a great product. There are a lot of features that it has that we don't use since we are on prem. We strictly use it for DR between our data centers. There are a lot of cloud plugins that they have that we don't use. Our use case is limited. It does everything we need it to.

I've been using the solution for probably four or five years.

The stability of Zerto is good. We didn't have any issues. Our biggest challenge was trying to get to the clients and I was waiting on an upgrade path - from Windows to Linux. Now there is an upgrade path. Honestly, that has been the biggest challenge we've had for five years.

The scalability of Zerto is good. You can easily protect other clusters and VRAs. It's very flexible.

Our current environment has 45 VRAs in each cluster. We have two replica pairs, two sites that mirror each other.

In total, we have 70 ESX hosts.

Technical support is great. They've shown us many things about the manager that we didn't know about. Every time I call, I take notes. They are very knowledgeable and the knowledge-based articles on the site are also helpful. Even if I thought something was broken, they've always managed to fix it.

We used to use VMware's SRM. With SRM, for us, it was overly complex. We used an array-based replication with SRM. We had issues where the storage team would go to do work on the array and they would fail the machine over and it wouldn't be right. We would have outages. Every time we did a failover it was a process and we would be missing rules.

This is not array-based and we can test our failover in a sandbox without taking the system down.

The initial deployment was easy. We deployed VRAs to the host from the manager. It works very well. The amount of VRAs you have to deploy and the amount of time it takes is minimal. It took us about an hour.

I can't speak to if the company has witnessed any ROI.

I don't follow the licensing. It was bought for us and we use it.

We evaluated SRM and a few others. I can't remember which ones we tested. We've been on Zerto since version six.

The selling point for us, coming from SRM, is that SRM was tied to vCenter. We had to pay attention to versions and there were a lot of ways you had to make sure the versions were correct and it was overly complex for what we needed. We simply needed to replicate a virtual machine and that was it. Zerto stood out as it was easy.

I'd recommend the solution to others. I'd rate the solution ten out of ten.

We are primarily using it for migration and data protection. We use it for protection of the VM and data protection.

It's the easiest way to support DR as it does the conversion for you. After converting, it protects again. If you don't want Azure, you can just go back on-premises, for example.

We can monitor VMs more easily with Zerto. We can always check if they aren't properly syncing. The migrations are also easy.

The overall impact on our RPOs has been amazing. The ease of using it is great. Everyone is embracing it in our company.

The ease of use is ten out of ten. It's the easiest to use.

The speed of recovery is great, especially the failover/failback. It helps our company a lot.

The most valuable feature is the GUI. It's very simple.

Setting it up is very easy.

Everything is automated using scripts.

The solution saves a lot of time and there is no downtime based on how the product is designed. If there's any downtime, it's only a second or two if we move.

The near-synchronous replication is great. It just works. I'm a big fan of Zerto.

Right now, the solution is perfect. They shouldn't try to do everything. Zerto is DR and needs to focus on that. Everything works for us. There is nothing to improve.

They already released the features that we want. We aren't missing any features.

I've been using it for almost five years now.

At first, when Zerto was bought by HP, we thought it was just going to be HP. However, Zerto is really working out and the stability is great. I hope they continue what they are doing and refrain from making major changes.

Zerto scales pretty well. They have a lot of customers. The word of mouth is helping with growth.

It scales well with our environment with the conversion from VM to Azure and vice versa. It's so easy. There's no middle-man involved. It's just Zerto.

The technical support is hit or miss. If it is a high-priority ticket, you get great Zerto support, however, if you just have a question, they redirect you to their documents.

We previously used SRM before Zerto.

The initial setup was not hard at all. We deployed a VM and had our team open the ports and we were all set.

It only takes about an hour or two if you have the proper people helping you with the networking.

We have witnessed a lot of ROI. Being technical, I always ask to make sure management is happy with the product we are trying to use. With the migration feature, it's way better now. We are able to migrate from the old data center without any disruption. That's a big win.

The pricing is fair. The pricing is very competitive and it works well. You are paying for a product that is easy to use and just works.

We've evaluated multiple DRs and some VMware products. Zerto was the winner due to the GUI. Also, it just works.

I have colleagues who are doing a POC with Zerto and will begin using it based on my recommendation.

I'd rate the solution ten out of ten. If I could give it eleven out of ten I would.

We primarily use Zerto for DR as a service but also for high availability purposes. It's mostly deployed at our on-prem colocation data center. We also do a little on the cloud, as well.

Zerto makes DR a lot easier. We don't have to spin up copies of VMs or copy applications and databases. Zurto just takes care of all that for us. We just did our annual DR test, and it worked exactly how we expected it to. We're big fans. We like the fact that when you migrate DR, it will automatically be configured for us. For example, it sets the IP addresses because they have different IP ranges and various data centers.

It saves a lot of time during disaster recovery. In our tests, we just hit a button on Zerto, it did its thing, and the solution just let us know when it's done. In the meantime, we could go do other things instead of having to, copy app configs, .ini files, etc.

The near-synchronous replication is great. That's one of the reasons that we went with Zerto. I've had a great experience with it and never had an issue. Having this functionality is critical, especially for DR. If our main data center goes down, we need to flip it and have everything almost identical to what it was when the data center went down. We use it for production high availability, so if that host goes down, Zerto will just automatically forward to the replica that it has on another data store.

The post-configuration part could be improved. For example, it would be super helpful to have the ability to modify DNS. Once the migration is done, we want to do some more modifications to the endpoint.

We have used Zerto for around 10 years.

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

Zerto is scalable. We're running it in five different data centers worldwide, and we haven't had any performance issues. It covers 70 hosts across all our data centers.

I rate Zerto support nine out of 10. We haven't had to use support much because it just works. Once we had an issue with a VM that wouldn't upgrade, and they sorted it out for us pretty quickly. I've only used it once, but it wasn't a time-critical situation. If I contacted them during an actual disaster or DR test, then I could see how quickly they can work.

I've never used anything besides Zerto, but I've done the failover process manually. Zerto just makes it much easier and faster than a manual failover process.

In our DR testing, Zerto allows us to go work on other things while it takes care of everything. That's valuable because we know that we can still hit all of our SLAs in a real disaster.

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

I rate Zerto 10 out of 10.

We've been using Zerto for data center migration, but we will begin using it for disaster recovery. Because of some data center issues, we're still using version 9.5. One of our data centers is at 6.5 and the other one is at 7, so we can't move any or upgrade to 10.

Zerto enables us to set the IPs and map everything out in our environment prior to migration. We can create VPGs and mass migrate applications, databases, and web clients. That was the selling point for us. The product is easy to use. We had a 30-minute onboarding process from our sales engineer, who showed us how to use it.

We don't use near-synchronous replication yet. It will be essential when we start using Zerto for DR, but it isn't a big deal during our current migration. Once we have a DR site, it will be essential to have those time slots we can restore to in the event of malware and ransomware.

Right now, if you have an error, it creates a link that takes you to a website to review information about the problem. It would be nice if Zerto could give you information within the app instead of referring you to a web application.

Zerto for two years.

Zerto is intuitive. We could set everything up in the environment within a day and a half and start migrating on the third day.

I rate Zerto 10 out of 10.

Our primary use case is for disaster recovery. We replicate up to Azure, and that's essentially disaster recovery as a service.

Overall, the effects of RPO have been great. They are never more than a minute or two, even throughout the production day.

If we can replicate from our native VMware environment up to native Azure, it converts the machines for us. We don't have to maintain another VMware environment somewhere. It's really given us the ability to eliminate the entire data center.

Moreover, there are cost savings tied to this. We don't pay for the rack space, power, or hardware; all of that is gone. Because the machines aren't active, all we're paying for is storage in Azure. So it has saved us quite a bit of money.

Zerto's near-synchronous certification has positively impacted our operations. Any recovery point that's too far in the past, we'll lose transactions when we fail over. We really don't want to do that. Real-time replication gives us a much better sense of security for the enterprise. It simplifies things for us and reduces costs. It makes management feel really good, too.

Using DR in a cloud environment has been a positive experience. We're saving money. We don't have to maintain the hardware. We don't have the rack space at the other data center. It just simplifies things for us and reduces costs. It's been a positive experience overall. It's pretty easy to use. Once it's up and running, it stays running. We have had a few times when we called support and the support has been very, very good.

Maybe the reporting for the failover test could be a little better.

I have been using Zerto since 2020, so it's been three years.

It's very good. It's very stable. It doesn't require a lot of intervention.

We haven't had any problems with scalability. We have 75 machines protected by Zerto and it does a fine job.

Support has been very good.

We used to use Site Recovery Manager when we had two data centers, and it was VMware to VMware. We were using EMC storage. Zerto is a lot easier to use than Site Recovery Manager. It requires less care and feeding.

Site Recovery Manager occasionally would lose virtual machines, and it was kind of a pain, but Zerto just kept running. So overall, we're really happy with the switch to Zerto.

The initial setup was easy.

Since we don't have to maintain all of the hardware and the second data center, one person can manage the entire Azure environment by themselves. As a result, Zerto has helped us reduce staff.

We did an assisted setup with Zerto tech on the line, and It was really painless. It was simple and straightforward. The initial process including getting the servers and everything set up, was pretty short. The process included getting the VMs all added to the recovery groups and things like that.

The whole process from start to finish took less than a week.

It has proven to be a cost-effective solution for us.

It could always be less money.

Overall, I would rate the solution a ten out of ten. It requires little care and feeding. Not a lot goes wrong with it. It just works.