I have a main data center with a few virtual machines running. I am protecting my mission-critical VMs on a disaster recovery server that I have outside of the data center. This ensures that I have protection. If something happens with my main data center at any moment, I have a copy, and that copy is at a remote and physically separated site for disaster recovery.

By implementing Zerto, I wanted to lower the RTO and RPO. Previously, the time to restore those mission-critical VMs with the traditional backup application took too long which impacted my business. That is why I decided to evaluate and then keep Zerto to protect my mission-critical VMs. It helps to lower the time to recover when something happens with one of my data centers.

Zerto is very easy to use. I did not have to attend a multi-day training. Online training is available from Zerto. It is very easy to use in my opinion as compared to other solutions.

Near-synchronous replication was the reason why I evaluated Zerto. I then decided to use Zerto because it works effectively. It is different from the other solutions in the market. Because I did not know that technology, I evaluated it, and I found out that it effectively works. That is why I decided to use it. I am a fan of Zerto.

We have a faster recovery time. I am lucky that until now, I did not have to use it in production effectively. That means that I did not lose access to my first data center, but it gave me peace of mind. I know that if something happens, at that moment, I know what to do to recover and to fail over to that second data center. There is peace of mind for sure.

We use Zerto to protect virtual machines from VMware to VMware. Our RPOs went from hours to seconds. That is a huge improvement.

Before using Zerto, I had an issue, and we had almost a day of downtime. I had to put a lot of energy and time at that moment, not being able to do my regular job. Since moving to Zerto, I never had a big downtime, but when I evaluated Zerto and ran the tests, failovers always worked. I have not had to use it in production so far because everything has stayed online until now. I am keeping my fingers crossed.

Zerto has definitely helped to reduce our organization's DR testing. Previously, the procedure to do the testing took several hours, and now, it is all automated. The nice thing is that the testing is automated. It is a part of the solution itself, and it is very easy to perform.

Zerto has enhanced our IT resiliency a lot.

I do not have many regulations to follow because I am not in finance or health care, but it simplifies my work because it clearly shows me what I have, what is supported, and what is protected. Zerto definitely enhances my visibility.

There are two main things that I like. One is the fact that my recovery time is now much lower effectively. It is also very valuable that I can test it. There is a possibility to test that failover. At a regular moment in time, I can run that test and see if it effectively works when I have a major issue in the future.

I am switching to another HPE offering called HPE GreenLake for Disaster Recovery which is using Zerto technology in the backend but has a lower entry point. The native Zerto implementation is optimal for larger environments. My environment is rather small since I do not have hundreds of virtual machines. The initial Zerto offering was for a larger environment with more than 100 VMs. At that moment, it was not that easy to talk to HPE to get a good price. HPE GreenLake for Disaster Recovery uses the same technology, so it is a really good technology, but the entry point is much more interesting for me. They have lowered the number of protected VMs. That is why I am now evaluating HPE GreenLake for Disaster Recovery.

I have been using Zerto for two years.

It is always available. So far, I never had any issues. It is very good. I would rate it a nine out of ten for stability.

It is definitely scalable, at least in my environment. I do not have the biggest environment, but based on what I saw when HPE initially presented the solution and all the new things that I see in it now, it is a very scalable solution. Why I prefer this solution compared to Veeam, for instance, is its scalability. I am convinced that the way it works with journaling makes it much more scalable than other solutions.

So far, I never had to call support because I never had issues with the platform at all. Until now, everything worked fine, and I never had to contact support. This is through HPE, and I expect the HPE support to work like before and provide the same experience for Zerto.

I am still using Veeam, but with Veeam, I was never able to go up to a few seconds of RPO. Zerto is much more scalable and flexible as compared to the Veeam solution, so I am using Zerto for the short-term retention and protection of my data, and I am still using Veeam for the mid- and long-term retention of my data.

It is for on-prem to on-prem DR. I am not using the public cloud for DR.

It took less than a day to set it up. It was very easy to deploy. In less than a day, everything was set up in two data centers.

In terms of maintenance, it is self-maintaining, so I do not have to put a lot of time into it. It is part of my testing. Every two or three months, I do a failover test, and at that time, I also check if everything is working fine and if any new updates need to be applied. When there are new updates, which do not happen that often, it is very easy to deploy the updates.

Only one person was involved in its deployment. It was just me. To set up and maintain it, there is just me. I do not need several people because it integrates with my compute and my storage. I can see my hypervisor. Technically, there is one storage person who is responsible for all this.

We are a small company. Zerto is being used by one team, but there are two physical buildings. Here on-site, we have our main data center, which is highly available with multiple servers, and on our DR site, there is just one server. It is one big server where we have copies of the mission-critical VMs that we are protecting.

It is hard to measure because I have not had a real disaster since I have been using Zerto. If I consider the time while testing the procedure, it went down from hours and days to less than an hour. I see large gains, but it is hard to say in the percentage. It is effectively much better.

I think the price is fair for what it is offering. It gives me the peace of mind that my data is protected. It is worth the cost.
It is like insurance for a car. You do not get the value until you have an accident.

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

I would definitely recommend Zerto. I have really low RPOs of seconds since I started using Zerto, and it works effectively. That is why I love Zerto. It does what it should be doing.

I like the tool because you can go from anywhere to anywhere. I am currently using it for on-prem to on-prem DR, but it can go from anywhere to anywhere. It shows the flexibility and the scalability of the tool. It is a no-brainer to evaluate Zerto because you can also go perfectly to the public cloud from your on-premises so that the public cloud is your DR site. I did not use it myself, but you can even use it as a migration tool for migration from an old environment to a new environment. It is a very flexible tool. That is why I was impressed with it and how HPE integrated Zerto into its portfolio. It was a smart move to do the acquisition of Zerto.

I recently started looking into the AI insights that was added in the latest version. Need to evaluate further but it looks very promising from what I can see now already.

I would rate Zerto a nine out of ten.

We implemented Zerto to improve our backup speeds and data recovery time. Zerto is deployed across multiple departments, and around 12 admins and analysts currently use it.

Zerto has improved my organization in multiple ways, particularly its ability to scale. We have a massive environment that is undergoing cloud development because we are not a very old company, and we needed something that could help us. It's doing its job. Zerto supports multifocal scenarios across the cloud and on-premise.

The solution has had a positive effect on our RPOs. The time is faster with Zerto. Another benefit is reduced downtime. Compared to what we used before, I'd estimate it reduces downtime by 25 percent. The solution has saved us time in a data recovery situation. I'm unsure how much, but it's a lot of time. Zerto has reduced our DR testing time by about 30 percent.

Zerto has simplified compliance with industry regulations by including audit logs and official reporting to support regulatory compliance. It has also simplified our workload because it can do so many jobs.

The best feature of Zerto is the fast, automated backup and recovery. The data lift for applications is short, with minimal data loss. Zerto has improved my RTO because we can replicate and easily manage our data, which has positively impacted my company.

Zerto is easy to use if the installation is done properly. Its near-synchronous replication is wonderful, but I'm still learning how to use it.

Zerto's analytics could be more detailed. The analytics report seems to be more difficult to read.

I have used Zerto for 19 months.

I rate Zerton nine out of 10 for stability. It's highly stable.

I rate Zerto seven out of 10 for scalability.

I rate Zerto support eight out of 10.

We previously used Microsoft Azure's backup option. It was a little bit cheaper, but Zerto's recovery is faster. It's a little bit more expensive but much quicker.

I wasn't part of deploying Zerto, but I believe it was straightforward for them. It required a four-person team and took around two hours. After deployment, we occasionally experience some software bugs that must be investigated.

We've seen a 10 percent ROI with Zerto compared to what we had before.

I rate Zerto two out of 10 for affordability. The licensing model is somewhat complex. Adding more flexible and less costly options would help.

I rate Zerto nine out of 10. I would recommend Zerto to others.

The primary use case for Zerto in my company is to manage disaster recovery.

My organization has experienced the benefits of using the tool, which include the ability to test our disaster recovery quickly.

The most valuable feature of the solution is the constant synchronization, ensuring that we have the most up-to-date information should a disaster occur and we need to handle failovers.

Zerto's near-synchronous replication is why we first acquired the product.

Zerto's overall effect on our RPOs is such that it improves them significantly, and it is the reason why we purchased the product. Rather than having to recover from backup, which is time-consuming, it is available instantly.

If I compare the speed of recovery with Zerto versus the speed of recovery with other disaster recovery solutions, Zerto is at least five times faster than other products.

It turns out that my organization has not been using all the capabilities of Zerto and we just found from the session, HPE Discover'24, that the things we were looking for already existed within Zerto. I don't have anything to ask for improvement in Zerto.

I don't want any additional features in the product as I would be busy employing the functionalities I recently found out are available in the solution.

I have been using Zerto for seven years.

The tool is very stable.

The scalability is fine for our company. We are a relatively small organization, but it has done everything we needed.

The solution's technical support has been solid and very good, and we hope it stays that way under HPE.

In our company, we would recover from our backup software, so things depended on whatever backup tool was used at the time.

When it comes to the product's initial setup phase, Zerto's support has been very strong and relatively straightforward.

I have experienced a return on investment from the use of Zerto. The exercises associated with disaster recovery are faster and we are able to save time now in our company.

Fortunately, the tool's pricing and licensing are not a concern for me at the moment. Other teams handle it.

The evaluation of other solutions against Zerto was pretty quick. In our company, after we saw a Zerto in use, we couldn't find anything else like it in the market.

I have used Zerto to protect VMs in our company's environment.

Considering that there is always someplace to go from where our company is currently, I rate the tool a nine out of ten.

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

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

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

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

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

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

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

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

Zerto can reduce its price.

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

I have been using Zerto since 2017.

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

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

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

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

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

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

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

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

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

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

I rate the tool a nine out of ten.

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.

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.

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.

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.

We've been using Zerto for over eight years.

It's excellent. The product has been solid for the entire time we've used it.

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.

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.

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.

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.

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.

We have a licensing team that manages it, but it seems to be fairly easy to use.

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.

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.

We plan to use Zerto for migrating our external customers from their private data centers to our data center and Zerto's application services or other cloud services.

Zerto has improved our migration capabilities. Before Zerto, we used other applications, but they had some limitations in terms of platform compatibility. With Zerto, we have platform freedom and can migrate any customer to our data center.

The migration capabilities are very good. The platform flexibility allows us to migrate customer resources and virtual machines from any platform, like Hyper-V or VMware, and it's fast and reliable.

We're in the process of a proof of concept. It's been about three or four months.

The stability is strong and reliable.

It's scalable.

We will provide support with the help of HPE or Arlanje. We are just preparing that model.

The customer service and support are very helpful. Whenever we ask something, they respond very fast and quick. Their technical knowledge is really good.

Zerto is faster and more reliable. In the POC process, we compared it with other technologies and brands, and Zerto is very nice.

We compared it to Veeam.

We still use our previous solution. In fact, we are not replacing that solution. We are just enriching our replication products with Zerto.

Zerto is more user-friendly.

It was easy and fast. The point is, it's really easy.

We used a consultant. The experience was very nice. They were very helpful.

It's very new for us, so we don't have that information yet.

We evaluated Acronis, Veeam, and Commvault. We chose Zerto for two reasons.

• First, our customers want it. They always ask if we do replications with Zerto.
• Second, we compared it with other products.

Zerto is user-friendly, fast, and reliable. We wanted to improve our replication cycle.

It's also platform-free. I can migrate resources from my customers' on-premises data centers, public clouds, and other cloud service providers' data centers to my data center. That's the biggest advantage for us.

Up to now, I would give it an eight out of ten. It's platform-free, which is the most important thing for us.

It's also easy to use, fast, reliable, and the replication process is really nice.

We use Zerto to replicate critical VMs between data centers. We also use it to do local replication whenever the servers do not have shared storage. We have recently used it to migrate some workloads from Azure down to our on-premises data center.

Zerto has improved our organization by simplifying everything because the storage is agnostic. We used SRM (Site Recovery Manager) from VMware, and it's very tied to the storage, and it has to be the same storage on both sides. The whole replication is at the storage level unless you use vSphere in the middle, which defeats the purpose. This is data storage, and you can use it if you can see it, which is very convenient.

We use the solution for one-to-one replication from data center one to data center two, from server one to server two, or from the cloud to on-premises.

We have used Zerto to help protect VMs in our environment, and its overall effect on your RPOs has been fantastic.

The speed of recovery with Zerto is simple and amazing compared to other disaster recovery solutions.

I have previously used Site Recovery Manager.

We chose to use Zerto because of the RPO and because we wanted to eliminate the dependency on storage. Everybody on my team is familiar with the tool, and it's easy to use.

The new licensing model didn't work out for us because we used one-to-one replication. The other problem is that the Linux appliance is not available for everybody, and you must have a certain license. It's very important for us that if, at some point, those servers get compromised, or that server gets patches, I don't want to rely on Windows to protect Windows.

You want this hardened appliance to protect our critical workloads. If they can make that available from version one, it shouldn't matter what license you have. This is the best way to do it, and we are going to deprecate Windows support.

I have been using Zerto for five to six years.

Besides running it on Windows, Zerto is a stable solution.

If they need more space, they grab it. If you move the SLA or want to keep more logs or history for the DVR function, you have to check everything before making your claim.

The solution’s technical support is very good.

The solution's deployment is very easy.

Overall, I rate the solution a nine out of ten.

We have multiple plans across the US. We use Zerto to transfer VMs from one plant to another plant, from east to west.

Zerto is a really great fallback software that gives us the redundancy we need.

Overall, the solution is really efficient. Zerto really helped us prevent the delay in bringing up the VM once it transfers because we wanted to ensure everything works.

Zerto's near-synchronous replication works great. We've had some issues before trying to synchronize VMs across long territory ranges, but Zerto did everything we needed it to do. Zerto's near-synchronous replication is extremely important to our organization. Our production line to uptime is almost 99.99%, so the near-synchronous replication really helps out.

We use SAP HANA with Zerto.

We use Zerto to protect VMs in our environment. The solution helps with recovery and ensures that we can transfer our VMs when we have a host failure. We have plants all over the US, and Zerto has really helped us keep everything running at almost 100% capacity.

Because of its near-synchronous uptime and recovery, Zerto's speed of recovery is ten times better than that of other disaster recovery solutions like Veeam and Commvault.

Compared to other solutions, Zerto's ease of use is pretty straightforward. I'm really excited to see how GreenLake has integrated Zerto and made it even more seamless.

It would be good if we could store a snapshot of the images coming through so that we can always go back and have a vision history.

I have been using Zerto for four years.

Zerto is pretty stable software, and it's always been up when we needed it.

I don't see any issues with the solution's scalability. We have 100 plants across the US and hundreds of other plants worldwide and have never had an issue adding any hosts or notes to the tool.

We deployed the solution through a consultant.

We have seen a return on investment with Zerto.

Zerto is really good software. It has all the features that I need. I love Zerto's integration with GreenLake, and now that we know more about it, we'll start utilizing it more. Zerto synchronized our VMs and delivered reliability by ensuring our hosts in different plants had a reliable backup.

Overall, I rate the solution an eight or nine out of ten.

Our primary use cases are for disaster recovery, data center movement, long-term recovery, and backup recovery.

Zerto took our disaster recovery practice from sixteen hours down to thirty minutes.

The most valuable feature is the fully automated failover. The orchestration made the failover very easy for anyone who wasn't necessarily technically knowledgeable to be able to failover a machine.

I love Zerto's near-synchronous replication. I've been using Zerto for three years at my current employer and many years before that. It's been great. Anywhere I've used it, it's made the failover process a lot easier so that pretty much anybody can do it. This feature is our number one priority because we can keep our critical apps running if we have a failure, or even if we have a misconfiguration, it's very easy to recover something quickly.

We've moved some of our workloads to the cloud and back from the cloud using Zerto. The native tools provided by the cloud provider were not as seamless. Having DR in the cloud is very important to us because we trust that the cloud provider will provide a solution, but we also want to make sure that for our business purposes, we have a backup to disaster recoveries so that we're able to recover somewhere else if necessary.

We use Zerto to support DR on the AWS platform. We go between two different clouds. We go from VMware to Azure and also AWS.

Zerto made this quite seamless, especially going between two different clouds. It's just a matter of a couple of clicks. You don't need to understand what's happening on the back end.

We use Zerto to help protect VMs in our environment. It took our RPO from around four hours and now it could be seconds. We can recover the machine in under a minute as far as the boot time. We're between five and ten seconds RPO.

The magnitude of Zerto is much faster. We used to do a disaster recovery failover of our critical systems. It took about sixteen hours and once we had implemented Zerto, it took around thirty minutes to do for the same exact systems.

I would like for them to support additional hypervisor options. They support VMware but if they supported Hyper-V or Nutanix, it would be beneficial.

We have been using Zerto for three years.

It's been great. We've had it for three years. The only time we reboot the machines is for normal patches. We don't have to do anything else. It just works. We don't have to think about it. We've never had any issues over the three years we've been running.

We started Zerto with a small footprint. We only did a few VMs as a POC with two nodes on each side. Then we've grown it to 34 nodes on each side, including the cloud. It's always the same amount of resources. We're running 150 protected VMs in there. It runs really well.

The few times we've had to use customer service, it's never been for anything that was really broken. It's more informational or because we didn't understand how the product works. They've been great with communication, they get back to us, and even if they don't get an answer right away in one day, they'll let us know with the ticket updates that they're still working on it.

It's been really good as far as the little interaction we've had. The one nice thing is that we've never had to use it for anything that's been broken or that it's not working.

They have great communication. They don't just send you links to KB articles.

We looked at other solutions before we purchased Zerto. We did a bake-off with a couple of other solutions. Zerto blew everything else away. The functionality is the same as everybody else, but the amount of time it takes to implement Zerto is a lot quicker.

Making changes if you want to add another machine or another workload takes virtually seconds, whereas we found other systems took a planning time and could take hours to get implemented correctly.

The setup was great. We had one of our newest engineers run through it because as part of the POC, the salesperson showed us how to install it. It was very straightforward. We took somebody who knew nothing about Zerto, had them install it and they had it installed and running in about fifteen minutes. It is quite easy to use.

I can't say it's the same for SRM. There's a lot of documentation, whereas, with Zerto you point to the button, you push, and it works.

We did the full installation ourselves.

We got the recovery time from sixteen hours to thirty minutes. Prior, when it took sixteen hours, there would be about ten or more people who were waiting for systems to come online to be able to test.

With Zerto, within an hour, we get the systems up, and then it's thirty minutes to test. Everybody can go home. There's a lot less time for people to be available. Zerto makes it much easier and quicker to get completed.

The licensing model per VM is great. It's a good way to license it because you want to protect only the devices that you're looking to protect. As far as getting the licensing and working with the sales team, they're very responsive. There's a lot of great communication, it's good all around.

We looked at VMware SRM. We also looked at a manual process. We chose Zerto for the simplicity and the cost ratio was phenomenal. It's easy enough that we've had nontechnical people able to failover just by clicking a button.

For Zerto, you add the VM in the VPG or workload, point it to the target, pick where you want it to land, hit go, and it's done. With SRM, in comparison, you'd have to make sure it's being replicated between the two SANs. You have to go to a different UI, configure all of it, make sure that's working, then go into SRM and configure all the orchestration parts. It takes a lot more planning. You really have to make sure that all the different systems work together, whereas Zerto takes care of all that for you.

I would rate Zerto a nine out of ten, there is some room for improvement. The drawback for me is that it's not compatible with every single hypervisor. If we wanted to go with another vendor for a hypervisor locally, then we'd have to look for a different solution, and there's nothing really out there that is comparable to what Zerto can do.