HPE Zerto Software Reviews

Currently, our use case is to create a replicated system. We have no access to the internal VMs. We can manage the VMs up to a point, but we cannot get inside to do any kind of corrective actions to the servers themselves. We had no backup solution in place, so we needed to get something there. That is what we are using it for. It is replicating out to Azure. This way we have some place in case the ones on-site get compromised or have issues.

We are moving to a new data center. There are several VMs that we have to move over there that have RDM disks or SQL clusters. Those are the hardest things to move at this point in time, but now that I have the setup and it is ready to go, all we have to do is just flip the switch and get everything over where they are supposed to be. It is going to be a lifesaver for me. It will save me a whole lot of time in putting things back together.

Its initial setup can be better. It looks easy, but if you do not have things in the right place, it is not as easy as it looks. Some of the instructions were not clear. They were a little bit confusing. For example, while setting up SSH initially, it was a little bit unclear if I needed to use a regular credential or some other credential. This was one of the things that was a little fuzzy, and we had to get somebody else involved to help us out.

I have been using Zerto for about a year.

It seems to be pretty stable provided our network stays up and the firewalls do not go down.

I have not had to scale it yet, but we are planning to replicate an environment of roughly a thousand machines.

I would rate their support an eight out of ten because it took a while for the communications back and forth to get it set up. We could not always get together at the same time. We would also run into an issue, and we had to go to development or somebody else to figure out what was going on with it. We would then wait for that response. There were a lot of issues that we had that required a lot of back and forth.

Positive

We did have SRM in place for a little while for about 75 machines. Most of the machines that were being replicated with SRM went away when we had a dissolution with another part of our facilities, so we pulled that out and stopped using it. We then went to Zerto about that same time. 

We are not using it for a full DR. We have another solution in place for doing the DR work. Zerto, at this point, is primarily for replication. 

We are also not using Zerto to help protect VMs in our environment. We are using another solution for that.

It was a little rough, but it was not terrible. When we were setting this up, I was working with several machines that were 30 or 40 terabytes in size. Moving that data out to that other location was a long, slow, and ongoing process. There were several times when we had to reach out to their support to try and figure out what was going on. We had to make some adjustments to how they were configured, but that was the biggest challenge we had with that the whole time.

It is slow initially, but once you get it all up there, it is not so bad. It took days to get that data moved. Once it got up or synced, it was down to seven or eight minutes, but it took days to get everything up there to begin with. It took about a week from start to finish to have it fully deployed.

We worked with a Zerto rep. They said that this is what we need, and we got everything in place, but then as we were trying to deploy it, we had issues. We had to pull in support to help us straighten out what we were having problems with. They have been pretty good. Fortunately, I have not had to call them much. Once we got it set up, it was fairly easy to figure out, but doing that initial configuration was a little difficult.

We have not yet seen an ROI. We are going to be moving to a new environment and a new data center. I am sure I would see a big return on investment at that point.

I did not evaluate other options, but there were some higher-up managers who were involved in those conversations. They had neglected to involve the guy who was going to manage it. I heard that they evaluated Veeam, an IBM solution, and Zerto.

I would rate Zerto an eight out of ten only because I have not used it a lot. When we move to the new environment, I am sure I will use it a lot.

We use Zerto for server migrations between data centers during the role swap that we do. We use it from a recovery standpoint as well.

We currently do not have disaster recovery to the cloud. We go between our data centers. That is what Zerto helps us accomplish.

Zerto works very well. We have not had any faults while using it. We are a financial institution, so we have to make sure the systems we have are available with very minimal downtime.

It has helped out a lot in man-hours. It has saved us a lot of overnight work. We can literally change our production servers in a matter of minutes to hours. Rather than having to do this gradually or a couple of weeks in advance and have several teams and business partners involved, we can literally do it live on the same day.

Zerto is probably one of the faster ones in terms of recovery. You can just go into the console, and because it is always replicating over to the other side, it takes minutes.

Being able to do our recovery and being able to migrate between data centers during the role swap is valuable just because of the amount of time it takes. It takes 55 hours or so. Right now, we are doing this in a VDI environment. We are going to experiment with it as a proof of concept because we have a thousand machines that we have to move and do all the assignments. Zerto would lessen that down by a few hours, and then we can use some scripts to do everything on the Horizon's side. We have not done it yet, but we are hoping to reduce it down to about 3 hours instead of 55 hours. We will also be able to manage our host better and be in a better recovery state. If the host happens to go down, we can quickly recover.

It is very user-friendly. There is no wondering about what a feature does. It is easy to use.

If they already do not have it, they can have some APIs for the Horizon environment. Instead of having to use some scripts to get around, they can make it a lot more user-friendly for integration.

We have been using Zerto for two years.

It has been very stable. We have not had any issues while using it. When we need it to do its job, it is always dependable.

It scales very quickly. We can set up a whole new environment in an hour. We can get the server setup and all the VMs that are required for it to function in an hour or two.

I have not used their support. My peers had to use it. They seem very responsive and knowledgeable. 

The other DR tool that I have used is from Symantec. It was an old-school recovery tool. It was back in the day when it took a whole day to get things back up.

It was deployed before I joined the company.

Its price is fair. It is very cost-effective compared to the cost of the labor for your workers and associates. 

We selected Zerto over others primarily for the ability to replicate and help with our role swap. It cuts the downtime of the production systems by a large volume. This way, we can meet the deadline and not have that much client impact. In the financial side of banking, you do not want bad performance.

I would rate Zerto a nine out of ten. There is always room for improvement, but it definitely makes your life a lot easier.

We use the product solely for disaster recovery.

The solution has helped with zero data loss from a transactional perspective. We have about forty servers in there today and they all serve a core function for our business. With Zerto, it's a matter of just being able to achieve zero data loss in minutes in terms of recovery time. That's amazing, and it really enables our business from a disaster recovery perspective.

The key benefit for us, and why we transitioned to Zerto years ago was really the recovery time. We went from hours to days on some of these applications, to minutes.

I like the granularity of the checkpoints. That's been extremely beneficial for us in testing. The near synchronous replication of Zerto is great. Knowing that it's within seconds or minutes allows us to achieve our goals from an RPO perspective. 

I like the live failovers. 

It's also a very easy-to-use product and very easy to administer from just a time perspective. 

We're able to stand up our DR site within an hour if we need to. 

We've been able to use it to do kind VM migrations from site to site in the past. Just it doing it behind the scenes allowed us to dramatically reduce any downtime for private cloud to a private cloud or even on-premise to private cloud migrations.

When handling migrations, it's fairly intuitive. There's a progress bar with percentages. Sometimes the timing fluctuates based on bandwidth. However, it's going completely in the background. It doesn't interfere with anything. When you are live, you can cut over with minimal downtime.

It's improved our RTOs. It's dramatically improved RTOs compared to what we had before.

We've had multiple unplanned failovers and the solution worked as expected. It's probably saved us 24 hours per instance.

The product has reduced the amount of staff involved in data recovery situations. Before the solution, we had two or three different mechanisms for different types of systems in different applications. Now it's just one click, one interface, and one administrator. 

When we do failover and failback, it doesn't maintain some of the settings that it should and I don't really understand why that happens. Quite regularly, anytime we do a failover or a fallback, we have to confirm all the settings for each VM. That takes a little bit of time. There is some power shell for that, so we've been able to automate that or at least optimize that. That said, that's my only complaint. Maybe that's a VMware limitation. I'm not sure.

We've been a customer of Zerto for several years. We started using it around 2017 or 2018.

The stability is good. Of course, from a maintenance perspective, sometimes with the failover, we have to re-sync or set up the settings again for whatever reason. I'm not sure if that is a limitation of the product or a limitation of VMware. 

We have six or seven users that use the solution, and typically just two or three administrators. 

We've scaled in that we have increased our VM count or VPG count. However, if we had thousands of VMs, I'd question the RTO or RPO capabilities at that point. However, ours is fairly small, under 40 VMs, and it has worked well for us. 

Technical support has been great. In our last DR failover, we needed to put in an urgent ticket and we got a very prompt response on that. Based on my interactions with them, by far they have the best support. 

Positive

We did use other solutions before, however, they were not as comprehensive as Zerto. We moved to Zerto so we could get our RTO and RPO down to minutes. Just being able to do everything with one administrator makes it much easier than before since we were doing some things from backups.

From a desk disaster recovery perspective, Zerto has replaced all legacy backups. From an administration and time perspective, we're definitely seeing some savings there. 

The initial deployment was not very straightforward. We were able to deploy in a matter of hours. The foundational aspects of Zerto are pretty easy, however, managing VRAs and getting the replication going can be a bit more work.

For the initial deployment, we only needed a single administrator. 

The solution definitely requires maintenance, just to keep everything up to date. However, it's very intuitive and everything happens very quickly, based on how many VRAs you have. We have three administrators capable of managing Zerto as needed. 

We have three sites, either on private cloud or on-premises. They are all VMware-based. 

Initially, a consultant assisted us with the base installation.

We have not calculated the ROI of the solution.

I was a little disappointed this year with the pricing, especially being a legacy customer of Zerto. 

They changed the licensing structure as a result of the HP acquisition. We had a significant increase that was not very well communicated to us and wasn't planned for us and it hit us pretty hard. From a budgeting standpoint, we only got notified a couple of months before, however, we were already in our calendar year. We couldn't plan for it properly due to the timing. It was frustrating for us. The costs were up significantly for us this year. That is definitely something we will be mindful of and keep an eye on going forward. We may need to find an alternative if the costs keep increasing.

We did explore other solutions, such as VMware and other competitors. However, the ease of use and ease of implementation were good selling points and became a key deciding factor for us. 

We have not used the immutable data copies as of yet.

In terms of dealing with threats or attacks, I've read a lot of the white papers, however, we haven't really had to have a need or a use case for that at this point. We're aware of that functionality, however, we haven't had a need to really utilize that, thankfully.

It took us a while to realize the benefits of the product. The initial phase for us was to cover about twenty different servers, which had interdependencies within the application. It was quite difficult. It took us about a year and a half to fully utilize our application or our initial phase of productivity. That said, that wasn't a Zerto limitation. That was the fact that we were changing IP addresses between our sites, so it was more of an application configuration delay. Zerto was ready to go on day one, basically.

We don't use Zerto to support disaster recovery on AWS. We're strictly on-premises hypervisors. We use virtual machines.

We haven't used Zerto's data recovery testing functionality. 

I'd advise new users to utilize the failover testing. You really have to make sure the application functions. Within our use case, for example, we have very interdependent applications. Each piece requires lots of communication, lots of databases, lots of other application transactions that are interdependent, and lots of integrations within our application. Utilizing the failover testing was critical for us.

I'd rate the solution eight out of ten.

We utilize Zerto for our disaster recovery solution, which involves replicating our virtual machines to a remote hot site to ensure failover capabilities.

Zerto's near-synchronous replication is great. 

Our RPO is around ten seconds.

I found Zerto's dashboard and features, such as the Zerto console, easy to use. It is simple to navigate and comprehend. Additionally, it is convenient to check various RPOs and BPG groups to stay informed about the current status.

We now have a robust disaster plan in place since the implementation of Zerto, which was a significant aspect we aimed to ensure.

Syncing data over to the data center for disaster recovery is easy.

I cannot provide a specific answer regarding our RTOs, but they have definitely improved significantly compared to our previous practices.

Zerto is considerably faster than our previous disaster recovery testing, which has saved us a significant amount of time.

Zerto has reduced the number of resources required for our data recovery.

It has helped reduce the number of staff for our backup.

We are utilizing a third-party company to assist us in managing Zerto. However, the RPO time for the copied-off VMs appears to be quite short. Additionally, it is straightforward to use.

One concern we have is the speed at which Zerto maintains compatibility with VMware and different versions of VMware. We are specifically worried about potentially major security issues with our current ESXi version and whether upgrading it would cause any problems or compatibility issues with the Zerto version we are using. It is crucial for Zerto to collaborate closely with VMware in order to promptly test updates.

I have been using Zerto for six months.

Zerto is stable. We have not had any stability issues.

We have not used Zerto in the cloud, but on our ESXi host, it appears to be scalable.

We used to back up VMs to powered-off off-site storage, but Zerto provides live disaster recovery capabilities. We had been utilizing a different disaster recovery concept, but Zerto is easier to use and provides us with an improved turnaround time in the event of a disaster.

The initial setup was straightforward. I assisted in the deployment, and a total of four people were required. The deployment took one week due to the necessary networking changes that had to be made.

We implemented using a third party.

I give Zerto a ten out of ten.

We utilize Zerto for our disaster recovery, and we employ our storage appliance for local snapshots.

No maintenance is required for Zerto.

I suggest using Zerto to have the servers in different Virtual Protection Groups so that they can prioritize the most important aspects of the business.

I am the global lead for infrastructure for the VMware and Windows Server environments. We are mainly using Zerto for disaster recovery. We have a prime site in Missouri, and we have plants in Taiwan, Malaysia, Japan, Italy, and Korea. We have 400 to 500 users in the environment. 

We have installed Zerto software on the DR site and the production site. We will be using Zerto for the production site for all the centrally used applications, such as SAP, file servers, and Exchange. Because this is a central site, a lot of other sites come to this site for various things. 

We also have Zerto on the DR site. In manufacturing, there are 60 or 70 tools, and each tool costs around $500,000. When the site goes down, you cannot transfer these tools very easily. It takes time. These are big tools, and it takes time for them to go somewhere else. You have to do a test again and go through the qualifications procedure, which takes time. As the IT department, we are interested in getting the applications that are used by all the sites centrally located, and if anything happens to the primary site, we want all the applications to be already there on the disaster recovery site. We just bring them up, and we are good to go.

Zerto will help to protect VMs in our environment. We have tried that in the test environment. That would be another reason for using Zerto.

We have used it for VMs. We know that it is a very good product. So far, we have only synced SAP and tested a few things. For SAP, there were two guys doing that, and they like Zerto very well. They have the test databases up there. It was smooth, and they liked it. The part that we still need to test is the Windows VMs where we can spin up a domain controller, change the IP, etc.

We can move data that is needed to keep our users collaborating with one another using Zerto because we are doing a continuous sync of the site. Once it is synced, we do not have to worry because everything happens in the background.

The replication feature where it constantly replicates and sees that data is always in sync is valuable. 

The ease of moving all the VMs is valuable. All we have to do is change the IP address and the VMs are all up and running there. There is a passive sync with all the VMs. That is what we like about Zerto. VMware has its own tool, but you need to do a lot of scripting. In manufacturing, we have a one-man team, so we do not have time for all the specialized work. We needed an application that is more GUI-based so that we can pinpoint and easily move VMs. We can bring up all the VMs and make sure the data is in sync, and we are up and running, so the ease of implementation is what attracted us to Zerto.

Zerto is very easy to use. It is very professional. We had no issues at all. Even for bringing up a new ESX host, they have a standard procedure. It is very easy. With a few clicks, you can do the ESX installation. 

There should be an automatic installation in a cluster. When I add a virtual client or ESX source to the cluster, it should automatically install that. There should be automatic installation. Currently, I have to do that manually.

They can give us a few training classes.

We installed Zerto just three months back. We have not yet started using it properly.  

Zerto is a very stable product. We have no issues. So far, it is working as planned. It is very stable. We will soon be working on it full-fledged. 

It is very scalable. We buy new licenses, and we just add another ESX or VM. We manually install it, and then we are good to go. It is pretty easy.

We have not contacted support yet. So far, so good. Everything is working as planned.

I tried VMware replication, but it was too hectic with all the scripts, so I gave it up. 

We implemented it recently. There was the ease of implementation. It was easy and straightforward. 

In manufacturing, we have to make sure that everything is on-prem. The data has to be on-prem because all the tools write immediately to the servers. There are two types of manufacturing. For the type of manufacturing where your tools are constantly writing, cloud applications are not good. For example, when we scan wafers, there is a set of data, and when we go through another tool, there is another set of data. This has to be instantaneous. There is nothing called a cache or buffer on those tools. It has to be instantaneous. We cannot say that the cloud is down, and we lost the data. We cannot stop the tool because this is a manufacturing facility with 24-hour operations on 365 days. We cannot have any downtime where the full site has gone down because this site is used for central applications.

I am the one who implemented it. Overall, there were just two people involved from our side. There was me and one more person. Because it was a new product, we also had a representative from Zerto as a standby. He would just watch our screen while we were implementing it. When we got stuck somewhere, he would help us. Because this was a DR site and it was a little far off, we wanted to make sure that everything went smoothly.

In terms of maintenance, so far, it did not require any maintenance from our side.

Having a solution like this is similar to having insurance. When you have a car accident, that is when you know the value of your insurance. Similarly, you cannot put a definite value on a solution like this till something happens, but there is peace of mind in knowing that the software is there, the VMs are there, and we can test it anytime. That is the true value.

It is economical as compared to other brands. 

We are an HPE shop. Zerto was procured by HPE, and we were looking for a DR solution. We went for Zerto because of its simplicity and ease of installation. We did an on-site proof of concept of Zerto for a year. We liked it and purchased it.

The only other product that we looked at was the VMware one because of the orchestrator. We did not look at any other products. I know that Veeam also has the same features that Zerto has. We had some discussions, but we never looked into it. Once we had a product that was easy to install, we did not feel the need to compare. It was doing what we wanted it to do.

Another factor for going for Zerto was that its price was economical. My boss, who is the CTO, liked its licensing scheme. It was much more economical as compared to VMware, and that is why we went ahead with Zerto.

Before implementing this solution, in terms of preparation for disaster recovery, you have to identify the business applications that are critical to your environment. You have to scope that out and make sure you have your VMs accounted for because licensing depends on the number of VMs. With a product like Zerto, you have to know the number of VMs and the size of data you are going to sync. These are the two factors that you have to look into for disaster recovery. 

Zerto is way better than other products. Installation is done with the click of a button. Everything happens in the background. You do not have to worry about it. As a product, we have not had any issues so far. However, we have not yet done a full-fledged disaster recovery. We have done minor testing, and we want to do major testing. As of now, I am very happy with the product. It does not need any further modifications. It is simple. It is nice. It is easy to execute, so I would keep it that way.

We have not yet used Zerto for immutable data copies. I have been playing around to migrate a VM and see how it works. So far, we have only used it to sync up the SAP side. Our SAP stuff is already synced up, and we have done some testing of it, but we have not done any disaster recovery.  

I have not had a chance to assess Zerto for blocking unknown threats and attacks. We are mainly interested in using it for disaster recovery.

Overall, I would rate Zerto a ten out of ten.

We have approximately 1500 to 2000 Hyper-V machines. Those Hyper-V machines are being used and converted to VMware. We use Zerto for our conversion from Hyper-V to VMware. We are also considering using it for DR purposes. 

Our prod environment runs on-premises and we have a DR copy of everything that we run in production. Our development runs on machines and hardware. In the event of a DR event, we would shut down dev and bring up our secondary copy of production. We hope that Zerto is going to be the tool to help us do that.

Zerto offered us massive time saving and consistency. We have a consistent outcome every time we complete conversions. We move from one platform to another with different loads being moved each time and Zerto's results are consistent each time.

We convert 30 to 50 VMs from Hyper-V to VMware on a nightly basis which has resulted in saving time as this is good throughput. Zerto also helped to reduce downtime. If we were to do this manually, we would have a lot of downtime to shut down those VMs on Hyper-V to be able to do the conversions.

The ease of the conversion moving from Hyper-V over to VMware is the primary reason why we chose Zerto and is its most valuable feature.

There has been one pain point that we have run into. We wanted to shut down the dev environment to focus on the prod environment. We couldn't find any option in Zerto to do that.

We have been using this solution since the start of 2022. 

This is a stable solution that offers consistent results. 

From a DR perspective, we use a few solutions. We have multi-site data centers in our environment along with Cohesity. We use Cohesity from a backup and DR perspective.

If you're in the middle of conversion between different platforms, regardless of if you're moving from on-premises to host it or from one environment to another, Zerto is agile and able to move your workloads into different environments pretty easily.

I would rate this solution a nine out of ten. 

Our primary use cases were designed around backing up and being able to restore our management plan. This isn't something used for our department users. It is specifically for our infrastructure, things like vCenter, vRealize Operations—all those things that we still have to maintain. We wanted something a little more granular than just a standard backup. We needed to be able to say, "Rollback half an hour or an hour," as opposed to following the backup schedule that the larger backup system provided.

We're using it for migration. Zerto plays a large role in helping us move away from Hyper-V into VMware. We're talking about multiple departments that had to transition their applications and Zerto gave us an opportunity to do it in a much less painful way.

Another key benefit is that our response time has significantly decreased. We're no longer having to rely on the traditional process where you manually execute a backup and hope to God it works okay. And then, you have to run through whatever changes are necessary and cross your fingers that, if you have to restore, it will come back. We don't have that problem with Zerto.

The solution has also helped to reduce downtime for us, absolutely. In most cases, we are able to use Zerto as a momentary backup, run an upgrade or installation, and see whether or not we're going to succeed. We can potentially back it out without anybody knowing about it because it's still within our maintenance window. We never exceed that rather limited time period. That's very helpful. With our existing backup, more likely than not we're rolling into days at a time if something fails. So if our maintenance window was on the weekend, it would roll into the production week and cut into the week by a few days. That would be very problematic.

And the recovery speed is basically as fast as the speed of our pipe, and that's what makes it great. As long as our pipes are fast, we don't have to worry. We can roll in, roll out, or potentially roll back if we have to, within a really small window of time.

In addition, it has definitely reduced the number of operational groups involved in backups. Zerto is not managed by our storage team. It is managed by the team I'm on, which is infrastructure. Because of that, it's all internal to us on the infrastructure team. We don't have to go outside of our team to coordinate with others.

There are several valuable features because of the way we use it. The backup and restore features are definitely indispensable.

There are certain things about the user interface that could be a little bit more user-friendly. But it really depends on the audience. If we are using it as a technical tool, our team is the audience and we are able to utilize it. But if we were to pass this on to, let's say, the department users, that would become a little problematic. I'm wondering whether or not we can actually expand our offering to those department users. That may be a question.

I have been using Zerto for three years.

As long as our infrastructure is stable, it's stable.

All I have to do is add managers out there and it expands. What it boils down to is that my infrastructure has to be able to support it. I have to have space where I can send the backups to. As long as that exists, we're fine.

The customer support is pretty good. The bottom line is that the customer service is responsive, whether we're talking about technical challenges or even licensing challenges. They've been very helpful in both ways.

Positive

We played a little bit with Veeam, but for the most part, we relied on our storage team to provide us with backups. We switched to Zerto because that team wasn't able to deliver in a timely fashion and they weren't able to guarantee restorability.

I wasn't involved in the initial setup. We have an individual who is our infrastructure expert. He took it upon himself to try it out. He told us what he found out when he did that trial and we started playing with it a little bit more and saw how easy it was to use.

I don't want to create upward pressure on their pricing plan, but the pricing is good. It's affordable.

The amount we had to set aside for our existing backup solution, compared to Zerto, was astronomical. The way Zerto works, it is so easy to scale up and out. It's not going to end up creating undue pushback as far as the cost goes.

We evaluated other solutions, with Veeam being one of them.

There's a lot about Veeam that we only just touched the tip of. I can't say with a lot of certainty what specific features Veeam may have. But there's a reason that we only touched the tip of Veeam and jumped over to Zerto.

One of the things that brought us to Zerto was talking to some of the folks that were here, at VMware Explore, years back, about what Zerto did, how it did it, and where it got its origins. That told us it was something that was definitely pretty solid and worth trying. I have to admit that, after trying it, it hasn't disappointed.

Leaving Veeam aside and comparing Zerto with our existing backup functionality, forget it. The two solutions are night and day. There is no comparison whatsoever. There is a lot of overhead with our existing backup feature that we just don't have with Zerto. We definitely have an easier time managing and controlling it. Zerto is definitely easier to use than our existing backup function.

One of the things that I'm finding with Zerto is that we're discovering new uses every day. As we continue to explore what Zerto can do, we haven't even gotten to the point where we say, "We wish it could do X." I'm not quite sure how Zerto interacts with cloud as a target, right now. That's something I need to learn. That's not necessarily a fault of Zerto, it's just me not knowing it yet.

We've been using it to consolidate data centers. We have 13 hospitals and two main data centers and a cloud presence. We're trying to collapse everything. We've been using Zerto to move the workloads over to our primaries.

It's allowed us to save a lot of money by collapsing a few data centers. We have been able to evacuate the hardware in the one data center in our virtual environment, and then shut down and get rid of all those hosts. And it has saved us time in our failovers, from collapsing data centers to our primaries. It enabled us to do that on the fly.

One of the valuable features is the ability to re-IP on the fly, because it makes the migration a lot smoother on the system end.

The syncing of the replication needs improvement. My experience has been that, every once in a while, when you go to do a failover, it tells you it's not syncing. Then you have to troubleshoot and figure out why it's not fully synced up.

I have been using Zerto for three years.

It's pretty stable.

I've never had to use the technical support.

We use VMware SRM pretty exclusively for our disaster recovery stuff. SRM and Zerto are very similar in the way they work. Zerto enables features that SRM doesn't give us and that's why we purchased it.

Also, it takes half as much time to failover with Zerto as it does with SRM. Every six months we do a failover of our Epic environment from one data center to another, and we use SRM for that. We've been using Zerto for failovers from one data center to another for data center consolidation, and those seem to happen a lot faster than SRM.

We've definitely gotten our money's worth out of it for what we've been doing. We have been able to close three data centers so far.

We looked at Veeam, but that was a long time ago.