Zerto 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 are an electric utility and we have some pretty critical workloads. We have identified the most critical workloads in our environment and have implemented Zerto as a protective measure for them.

We try to keep our critical workloads protected, which are a subset of our systems. For example, we're not going to protect a print server with Zerto.

The fact that Zerto provides continuous data protection is key for us. We have tested on a regular basis, and in one case, we tested our entire ERP system. It is a pretty big workload that includes Linux servers, databases, and other components. It's about a 45-minute window to get it back up and running. For our test, we moved the entire system to our DR facility on a weekend, ran it for an entire week from the DR site, and then brought it back the following Sunday. It worked flawlessly.

I really like the 24-hour DVR-like rollback. For example, we had an issue a few years ago, when we still had an Exchange server on-premises. One of my staff came in for the morning to do vulnerability management, saw that some updates needed to be applied, applied the updates to the Exchange server, and it totally broke it. Everybody's email was down. To resolve things, we went to Zerto, rolled back to before the updates, and it was all done in less than five or 10 minutes. It was really quick. All of the email functionality was restored and it popped up and said, "Hey, you need an update." I said, "Please do not do that update." It was pretty good.

Zerto is easy to use and the interface is very intuitive. We have never had an issue with using it. We just have a one-man team to perform failbacks or workloads. It is very simple to do and during our test with the Exchange server, it was only a matter of a few clicks. It's always been an excellent product and they've only improved it over time. We're really pleased with it.

The integration with VMware is really good.

It would be nice if we were able to purchase single licenses for Zerto. As it is now, scaling requires that we purchase a multi-pack. It hasn't been a big deal for us but it would still be helpful to have a little bit more granularity on the license count.

The only timeline or limiting factor, in my opinion, is how long it takes to replicate. That all depends on your infrastructure, and we happen to be pretty fortunate that we have a nice pipe in between the two locations, between here and our DR site. If you don't have that limiting factor, it's just a matter of time. You just wait long enough for it to replicate over and then you're covered.

I have been using Zerto for approximately seven years.

We do the updates regularly and Zerto has never given us problems. We work with a lot of different technologies and we have a lot of problems, but Zerto has not been one of them.

We haven't had much opportunity to explore scalability at this point. We're responsible for another organization's IT, as well. They're a sister company of ours and they're smaller than us, so we do all of their IT and we have them on Zerto. They're using us as a DR point.

From an expansion perspective, we scaled up from our initial install to include theirs as well, which I think we got pretty close to doubling our license count.

We are 100% deployed at this point. If we were ever to add another sister company, which is possible because we have other sister companies where opportunities may arise. A lot of the time, they're so small that they can't afford IT, so it's easier to have us manage it. In cases like this, we may have an opportunity to deploy Zerto.

We have a very small team of three people, so Zerto does not affect our headcount. There is me, who is the manager of IT or manager of information services. Then, we have our desktop technician, and then we have our network administrator.

We have never had to use Zerto's technical support for anything major. Any time that we have had to contact them, it has been for minor stuff and it's worked out fine.

A long time ago, when we had an EMC SAN, there was a VMware plugin that served as a replication solution. However, it was terrible and it never worked.

Zerto is a major upgrade that is easier to use and switching was excellent.

Replacing our legacy solution with Zerto has definitely saved us time and improved the quality of our process. I never felt like I could trust our previous solution, which was a big deal because when you're talking about backups, trust is a major factor. You have to be able to trust your solution and feel like it's going to work in a bad situation.

Zerto is one of those things that you love to have but you hate to have to use because it means that something bad is going on. That said, if there are serious problems then you want to have something that's rock solid. For us, that's Zerto, and we feel strongly about that.

The initial setup was very straightforward. We had some training with some Zerto engineers on how to set up the recovery groups and other things, but once that was set up, we made several changes later on as we played with it. Overall, it was very straightforward to configure and I think that we only had an hour of training.

The deployment took us a couple of weeks to get everything figured out, although it wasn't necessarily Zerto that was the hold-up. We only had a certain number of licenses, perhaps 15 in total. We spent time trying to determine which were our critical workloads, and there was some internal debate about it. From the Zerto perspective, there weren't a lot of issues.

It didn't take a lot of time, just a couple of weeks to get us up and going. We were actually up and technically running within that same day, but to truly boot it and get it where it needed to be, it took a couple of weeks. It was a new technology to us at the time, so it took a while to get up to speed with it.

In terms of our implementation strategy, we just tried to identify the critical workloads, find the ones that really needed to be protected and start to make those recovery groups. Then, we organized them in such a way that things worked properly. For example, the components of our ERP system do have to come up in a certain order. Finding all of that stuff out and fine-tuning the process was part of our strategy. Then, we slowly started moving those workloads across. We broke it down into groups and we did those groups one at a time until the implementation was complete.

Our in-house team was responsible for implementation.

Maintenance-wise, we just keep it updated. Our network administrator applies the updates and checks the health from time to time. We have a dashboard on our big screen if we feel the need to monitor it. If we walk by and it looks like a protection group is in the red or yellow, then we look at what needs to be done to get the problem straightened out.

Price-wise, it's right in line with what we would figure. For what you get for it, it's really a good value, and we've never had any problem renewing it or anything like that.

License-wise, we budgeted $1,000 per VM. The minimum spend on it, in the beginning, can sometimes be a little bit of a headache for people, and they might have to budget creatively to get there, but once you're there, the renewals are worth it.

Licensing requires purchasing packages that consist of several licenses, and they cannot be purchased one at a time.

We paid for an hour of training that we took but otherwise, there have been no costs in addition to the standard licensing fees.

We began looking at Zerto for several reasons including the cost, ease of use, and really, the flexibility of it. When you want to switch it over and do a different workload, it's not that big of a deal.

When we first began to consider using Zerto, we had a discussion with a grocery chain that is close to us. It's a specialty grocery chain and they have exotic foods sold out of two different locations. Christmas is their busiest time of year and they have several cash registers at each location doing transactions constantly.

They had to use Zerto during the middle of that Christmastime rush and failover, from one site to the other, all of their point of sale systems. They never lost a penny in transactions. For us, that was a big testimonial. They have a similar size of environment to ours as far as server infrastructure goes, so we didn't even look at anything else.

At this time, we don't use Zerto for long-term data retention. Instead, we have some other technologies in place for that. We have Veem and we have some SAN replication and we have some network-attached storage, as well. We use Zerto as our first line of defense. For example, in response to a ransomware attack, we would use Zerto for sure to roll back before that event happened.

We have not had a ransomware attack, at least not yet. We fully expect that, if it ever does happen, we'll definitely utilize Zerto. It is essentially our insurance policy. If we ever have a ransomware incident, that would be our first line of defense to recover from it. In fact, we really haven't had many opportunities to use Zerto, thankfully. Zerto is one of those things that are great, and we're glad we have it, but you hope we never have to use it.

At this time, everything we do is on-premises but having DR in the cloud with Zerto is definitely something that we want to do in the future.

It is not important to us that Zerto offers both backup and DR functionality. For backup, we have it covered in other ways. Being in the utility business, we're very big on redundancy. In fact, we have backups to cover the backups and we have about five different levels of them that we utilize. Zerto covers the front line, and when something bad happens, we can roll back within a 24-hour period using it. Then, we have deeper levels handled by other products like Veeam. Funnily enough, Veeam kept telling us that they would add Zerto-like features, and at the same time, Zerto kept telling us that they would add Veeam-like features. We continue to use both of them.

I've recommended Zerto to several IT professionals that I've talked to because it's such a good product. I give them examples of what we have done.

Overall, it's a fantastic product.

I would rate this solution a ten out of ten.

We are using it for disaster recovery for our day-one applications that need to be up first, upon failover.

We previously had our Microsoft SQL Servers set up as clustered pairs, with the primary in one data center and the secondary in the other, and they were staying in sync via SQL Server Log shipping. That was not a very efficient way to get SQL servers failed over. There were also some things that weren't replicated through log shipping, such as the SQL Server Agent jobs that are defined on the server, or the custom permissions that are set up for the different roles. Zerto was able to replicate the entire server, including the jobs and the permissions, and eliminate the need for us to have that secondary server. We were able to break all of our SQL clusters and just have standalone SQL Servers. It helped to increase our efficiency with failover and reduced our overall compute and storage footprint around SQL by about 40 percent.

When failing back or moving workloads, the solution saves time and reduces the number of people involved. The time from the initiation of a failback to the completion is about five minutes for us. We've also made some tweaks in the DNS to help that to update and replicate quickly so that we're not waiting for that, even if the resource is available. As for the number of people involved, for SQL especially, it used to require getting the SQL team involved and they would do everything manually. Now, anybody can just click through the recovery wizard and perform the failover.

Our savings from Zerto are around licensing and how we structure our current environment. We were able to save money with our on-prem deployment, but we don't use it for cloud.

And in terms of downtime, every time we test a failover it's non impactful to operations, because we're able to do testing in an isolated environment. Before, if we wanted to test our failover processes it was going to create a production outage. That is no longer the case. Before, when we were doing regular DR tests, I would estimate the cost of the downtime to have been about one weekend per quarter. That's the time we would have to take to do that. Only if we were to do a live failover as a test, which would probably not be done more than once a year, would we really have to worry about impacting any operations.

The most valuable features would be the

• granular configuration of your SLAs
• built-in WAN compression as part of the replication 
• easy wizard-based failover.

The granularity enables us to failover specific workloads instead of an all-or-nothing type of scenario, where you have to move your entire IP block and your data center, or you have to move large chunks of VMs. Those situations also make it prohibitive to test effectively.

The replication piece with the built-in WAN compression is important because the network circuit that we send our replication traffic across isn't actually behind our normal WAN accelerators. We were able to use Zerto's built-in WAN acceleration to help those workloads compress.

The failover is important because that way I can delegate initiating a failover to other people without their having to be an expert in this particular product. It's easy enough to cross-train people.

Continuous data protection is Zerto's bread and butter. They do all of their protection through your journaling and that continuous protection gives you countless restore-point opportunities. That's extremely important for me because if one restore point doesn't work, because it is a crash-consistent restore point, you have so many others to choose from so that you really don't have to worry about having an app-consistent backup to recover from.

Zerto is also extremely easy to use, extremely easy to deploy, and extremely easy to update and maintain. The everyday utilization with the interface is very easy to navigate, and the way in which you perform testing and failover is very controlled and easy to understand.

The replication appliances tend to have issues when they recover from being powered off when a host is in maintenance mode. Sometimes you have to do a manual task where you go in and detach hard disks that are no longer in use, to get the replication appliances to power back on. There are some improvements to be made around the way those recover.

My other main inconvenience is fixed in version 8.5. That issue was moving virtual protection groups to other hosts, whenever a host goes into maintenance mode. That's actually automated in the newer version and I am looking forward to not having to do that any longer.

I've been using Zerto for coming up on four years.

My impression of its stability is very positive. It doesn't seem to have any issues recovering after you shut down any of the particular components of the application. It seems everything comes back up and comes back online well. 

Sometimes the replication appliances will stop functioning, for one reason or another, and most of the time a power cycle will resolve that. But anytime that I do have a sync issue, support will generally be back in touch with me within the first half hour after opening a ticket. They're very responsive.

The scalability is able to take on any size environment. We don't have a huge environment here. We only use it across 20 hosts, 10 at each site. They're very large hosts. If you have more than a certain number of virtual disks protected on a single replication appliance, the replication appliance will automatically make a clone of itself on that host to accommodate the additional virtual disks. It seems to be built to scale in any way that you need it to.

While our hosts are very large hosts, we don't have any current plans to extend that deployment because we have capacity to grow within our current infrastructure footprint, without having to add on resources.

I rate their technical support very highly. They're very responsive. Usually within the first 30 minutes of opening the case, someone has tried to reach out to me. I will just get a screen share, or a reply to my call with an answer, or a KB article. I have a very positive impression of their support.

We were using Site Recovery Manager for several years, and I always struggled with keeping that functioning and reliable. Every time something changed within the vCenter environment, Site Recovery Manager would tend to break. I wanted to switch to a DR product that I could rely on.

In addition to Site Recovery Manager, we were also using NetApp SnapMirror. We are still using that for our flat file data which is non VM-based. We have Rubrik as our backup solution because, while we replicate our backups, there's not any automation behind bringing those online in the other sites. So it's a manual process to do disaster recovery.

We were having to utilize those solutions to do the failovers for our day-one application in SQL and they were inefficient and ineffective for that. Zerto was able to come in and target those workloads that we needed better recovery time for, or where we needed a more aggressive replication schedule. Zerto is supplementing those other solutions.

Zerto is easier to use than the other solutions. There's definitely more automation and there are more seamless failover activities.

When I deployed the solution, it took certainly less than a day to get it up and running. The upgrade process has been fairly seamless and painless, in the past, as we have gone from one version to the next. That includes some of the features they've enhanced, where it automatically updates the replication appliances as well as the management pieces.

We have two data centers and they're both Active-Active for one another. Our deployment strategy for Zerto was to stand up a site server at each one, pair them together, and then start identifying the first workloads to add into Zerto protection. We started with our SQL environment. 

I was the only one involved in the deployment. If I had questions I would ask my account team. My sales engineer and the account rep are both very knowledgeable. But I actually didn't need to open a support ticket as part of the deployment. It was very easy and straightforward.

About five of us utilize Zerto. I am the infrastructure engineer, focusing on the compute side of the house. We've got a storage engineer. My manager is an applications delivery manager who uses it. We've got another senior network engineer who focuses more on the runbook side of things, and he uses it. And my backup, who is our Citrix guy, is starting to use it.

Zerto doesn't really require any particular care and feeding. Whenever a new version comes out that has features sets, I'll decide when I'm going to update it and do that myself. It doesn't really even require a support call. It's pretty straightforward. For each management appliance, updates have taken 10 to 15 minutes, in the past. And it's just a couple of minutes for each replication appliance.

Our ROI is quite significant. The SQL cost savings alone would be in the hundreds of thousands of dollars per year. That's due to the fact that we don't need to have our SQL clustering set up as an always-on cluster, which would need to be a higher tier of Microsoft licensing. We're able to use SQL standard for everything, and that wouldn't be possible without a third-party like Zerto to do the replication and failover.

Get the Enterprise Cloud license because it's the most flexible, and the pricing should come in around $1,000 per VM.

Support is an additional cost. We are currently doing three years of support. There's an additional 15 or 20 percent of overhead during each year of additional support for each license.

Definitely take the free trial and put it through its paces, because you really can't break anything with it, given the way that you can do the testing. It gives you a good opportunity to play with the tools without having to worry about causing any problems in the environment.

We have plans to evaluate the solution for long-term retention. I'm going to start testing some of their features once we upgrade to version 8.5, and then we'll evaluate if it makes sense to do that or not. We do have other backup products that we're evaluating alongside of that though.

The solution has not reduced the number of staff involved in overall backup and DR management. We already run a very lean engineering team.

I got what I expected. I'd actually been trying to bring the product in since 2014 but I kept not getting budget funding for it. I feel satisfied with what I ended up with and I'm glad that we were able to move forward with the project.

We use Zerto for data migrations. We use it to move our virtual machines from one location or data center to another and eventually, we then switch that over to DR from our facility in one state to another. It's for the migration of existing VMs.

Zerto has improved my organization by allowing us to do several VM moves. It simply allows us to bring a server back up on the new side, which looks like a reboot of a server. It's a virtual move to the new stage, so it goes from existing VM host to new VM host on the other side.

It has reduced downtime for the servers that we migrate over. By how much is a hard number to put because we do a big group of them together, so we're able to group the move as opposed to doing more one-offs.

The amount the downtime would cost my company would strictly depend upon which servers we were moving because some don't really cost the business. There are others that would cost the business for having to be up as much as possible, 24/7.

The Move feature is the most valuable feature because it allows us to move the VM from our old environment to our new environment with minimal disruption.

It's extremely easy to use. It's pretty self-explanatory as you run through setting up your VPGs for your protection groups and then to do a migration or a test failover.

Some of the features need improvement. One would be, as you're creating a Move group or a VPG, as they call it, it should either autosave or have the ability so that you can save it for coming back to later because if the setup times out, you lose all your work. That would be a nice improvement to have.

We have been using Zerto for three months. 

So far, the stability has been great. We have not had any issues with that.

Only two of us work on it and we're both system engineers.

We do not need dedicated staff for deployment and maintenance of the solution.

It's being used to move a total of around a couple of thousand VMs, so I don't have any issues with scalability.

Currently, we aren't planning to expand capacity because we have a total of around 500 agents to protect, so until we get the true DR, we will have to evaluate if we need to expand that. We will primarily only be using it for DR and any server migrations we may need to do from one system to another.

Their technical support has been very good and prompt to get back to us with answers.

We would either use a Veeam or VMware solution, but we haven't had a real DR product outside of Veeam.

We find Zerto to be the most beneficial right now in helping us migrate from one data center to another data center for the testing environment. And for future capabilities, for a true DR scenario.

I would say it's a lot more simple to set up and maintain than VMware and Veeam.

Replacing these legacy solutions has saved us on the costs needed to manage them.

The implementation was really straightforward and easy. We worked with one of their support engineers and we got it up and running really quickly. The deployment took around one hour. 

We didn't really have an implementation strategy. It was about getting the server manager and server up and then walk through the installation steps. We followed their guidelines.

I'm not sure if I can put a dollar amount on ROI but the biggest return is time to actually get things set up and then begin to migrate virtual machines over to the new environment.

I'm not 100% sure about the pricing because I wasn't as much part of the pricing part of it, but it fell within our budget. Its features and price are good compared to the options we were looking at.

We also evaluated Rubrik and a solution from Dell. The main advantage that we found was that Zerto fit our current need for migrating from one environment to another better than others, and its good standing in the community where there are a few products.

My advice would be to plan out your Move groups and work with your business to get everything validated so you can back up on the other side.

I would rate Zerto a nine out of ten. 

We use Zerto for backups and DR; we back up to a StoreOnce unit and then offsite. We have over 11 servers, including three Oracle servers, one Oracle database, and an Active Directory. 

Before Zerto, we used another solution that caused database crashes and did not offer certainty regarding disaster recovery. Zerto is more configurable and stable.

A DR site reduces downtime, especially with full VM backup and online synchronization. Zerto accomplishes this without affecting network efficiency, as synchronization occurs at specific intervals.

Zerto's ease of use is outstanding; it's easy to set up and has a clear interface and menus. The reporting, analytics, and online monitoring are also excellent.  

Compared to other solutions, the speed of recovery with Zerto is faster. Our last backup solution, Data Protector, was very slow, but Zerto is rapid even in file retrieval. 

The solution helped reduce our organization's DR testing; it's hard to say precisely how much, but Zerto does faster DR testing than other products.

Improvements in stability would be welcome; there are some software bugs that can affect RPOs. We want more of a guarantee that we won't lose any of our backups, even in the event of a disaster. 

The platform measures the right speed of storage devices and gives an alert on the VPG if there is latency, but the nature of the alert suggests the solution isn't meeting the SLA. However, this shouldn't affect the health status of the backup. It should provide an express report that we should enhance our hardware rather than express latency as a threat to the backup capability.

We've been using the solution for two years. 

The stability is acceptable, we experienced an issue once, but the backup time is speedy.

The solution's architecture supports business owners to expand their disaster recovery capabilities as their infrastructure grows. Additionally, Zerto's ability to integrate with various cloud platforms and on-premises environments further enhances its scalability, offering a flexible and robust solution for organizations with evolving needs.

Customer support is one of Zerto's best aspects; the support is excellent, and we can quickly get through to them. I rate them ten out of ten. The support staff are very kind and always solve a problem. I feel secure knowing I have access to such good support.

Positive

We previously used Micro Focus Data Protector and Veeam Backup & Replication. Zerto is easier to use and more straightforward to configure. 

Zerto replaced our legacy backup solution, Data Protector. This not only saved on the cost of the old product but also provided more stability and security to our company. We now have a new backup methodology, and it's a significant upgrade.  

I carried out the initial setup with support from Zerto, which was very straightforward.

The only requirement for maintenance is monitoring the solution and updating versions.

I have 20 years of experience in IT, so I was well-positioned to carry out the deployment myself, with the assistance of Zerto support.

We have seen an ROI with Zerto. 

The pricing is slightly above average, but the immediate and comprehensive support makes the price acceptable.

We evaluated many other options but found Zerto the best, especially for our HPE environment. It's the most stable and straightforward tool, and even those with limited experience can operate it.

I rate the solution eight out of ten. 

I strongly recommend Zerto; I've tried many other solutions, but it's the most stable.

We use the product to help protect VMs in our environment, and regarding RPOs, I carry out the test for them every six months, and it's working correctly.

I advise those evaluating the solution to use it, especially in an HPE environment, as it's fully compatible and easy to manage. There is no requirement for special drivers or configurations.

We use it primarily for DR situations. Whenever we lose our primary location, we switch to another location. We also backup resources and migrating VMs in and out of different environments, cloud versus on-prem.

The most valuable feature is that it provides real-time backup. We're in the financial industry and have to have 100 percent uptime. 

It helps us have a lot better uptime than what we would normally have. It's always real-time synced, with instant recovery. We can return to another location if power drops or generators don't work.

It gives us quick uptime. It also helps our customers maintain that trust, so Zerto really does help with trust. We generally use it on-premise.

The near-synchronous replication is really good. It gives us quick uptime. It helps our customers keep that trust in us.

We use Zerto to protect VMs in our environment. Until Zerto, I didn't pay much attention to RPOs. Zerto gives the ability to bring RPOs down to seconds. 

For certain use cases, Zerto has a better speed of recovery compared to other solutions but it doesn't tie into our SANs like Veeam does. 

It is a little expensive.

We could streamline the installation better. The other thing would be ransomware notifications, like IO anomaly notifications.  If they integrate with the SAN, that would be valuable to see in terms of snapshots.

I have been using Zerto for six to seven years.

We came up with the new version, and it's pretty good. If there's no reason for me to say it's unstable. It's been proven so far.

If you buy the licensing, it will scale up to size until you will spend money on it. 

Support is helpful.

Positive

If you want to pull from the snapshot instead of tools, then SRMs are better used for this case. It's fast and the first to market with continuous data protection.

Zerto is easier to use. There is some standup at the beginning, you must install the agents. It's easy to use when it's working right, but sometimes, it takes great effort to get it going if something goes down. 

We use another solution, Veeam. We keep them both because they're both beneficial for different use cases.

The initial setup is straightforward, but if you have it the first time, you are stranded in the industry. It could take a little figuring out, but Zerto is pretty helpful.  

There have been a couple of situations which they weren't able to fix an issue right away. We move everything off to a different server until we can circle around and extend that one.

We did it in-house.

Zerto has paid for itself in man-hours saved. 

Zerto gives you the ability to bring RPOs in seconds. We can have instant uptime for everything. 

It's more expensive than other solutions but it's worth it for our environment. It has made it very easy to restore files because you can restore them down to the second. It's pretty simple. We have the agent and all the hosts. 

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

We are using it for disaster recovery. 

Zerto provides near-synchronous replication, but more importantly, we can see the status at seven seconds, six seconds, five seconds, and four seconds when we log in to the Zerto console. I found that amazing. There is probably no other disaster recovery solution available in the market that is providing this functionality. It is great and definitely a huge plus point for Zerto.

We do get alerts if suspicious activity is detected on a VPG, but we did not get an actual case where there was ransomware or any other kind of attack and we had to prevent that. I have not come across that with either of my clients, but we do get alerts when Zerto finds something suspicious. We go in and look at it. In some instances, because the application was writing more files, Zerto marked it as suspicious, but we never had to do recovery for security reasons.

We use Zerto with AWS as the target. We do the failover of the on-premises VMware virtual machines to the AWS cloud. I do not deal with the implementation. I only do the administration of the tool, but whatever I did as part of AWS administration in Zerto, it was pretty seamless and straightforward. I did not get any issues there. The documentation is helpful in identifying any issues.

We have about 70 virtual machines that are being protected by using Zerto. Zerto has drastically improved our RPO. It was 15 minutes previously, whereas now, it is in seconds.

Zerto has not had much impact on our RTO. RPO has changed, but RTO has been the same for us.

Zerto has not helped to reduce downtime in any situation. We have only done tests. We have not done any actual production failover because there was no need. Similarly, Zerto has not saved us any recovery time because we never had a requirement to do a recovery since we implemented the tool. It is a pretty new environment for us, so we have not had time.

Zerto has not reduced the number of staff involved in overall backup and DR management. It has remained the same for us.

The simplicity of use is valuable. It is easy. We just click Failover and do it. It is pretty straightforward. If someone wants to do a test failover, they log in to the console and do a test failover. 

As a power user, I find the customization lacking. I feel it could be customized a little bit more, but Zerto is simple to use. It is easy to use. That is my main reason for using Zerto.

I would like to request better reporting in Zerto. I can see the data that I need in the console, but if I need to put the data or the history into a report, it is difficult. It is something that auditors might require, so reporting is something that needs to be improved.

The UI does crash a lot, and that is something that can be improved.

It has been about a year. I support multiple clients with multiple backup and disaster recovery products. I was a Storage and Backup engineer, but now, I am covering the solutions for the entire infrastructure. I work on Zerto for multiple clients. We have two clients who are using Zerto as a disaster recovery solution.

The UI does crash, but it does not affect the functionality of the software.

It is scalable. There could be 10 machines or 100 machines. I did not find any issues. It is pretty scalable.

There were some issues for which we had to get responses from them. They were pretty much on the point. There were no issues. The response time was a bit slow, but their support was pretty good. I would rate them an eight out of ten.

Positive

We used to use Azure Site Recovery to protect all of the production instances, SAP databases, some file servers, and some basic application servers. We used to first replicate to Azure and then do a test failover and a production failover. It was a bit slow. The RPOs and RTOs were not that great, and the rate of change that Azure Site Recovery supported was not completely meeting the business requirements. The third part was that Azure Site Recovery was not application-agnostic. What we loved about Zerto was that it was application-agnostic. It did not matter to Zerto what was running behind the application. It will replicate everything across any cloud. That was our main point for going for Zerto.

Zerto was also much easier. Azure Site Recovery was a little bit hard to set up and maintain, but Zerto is pretty straightforward and easy.

I did not find much difference between Zerto and other solutions in terms of the speed of recovery. The RPO is great, but when we do a failover, it is basically the same as any other solution.

Zerto has not replaced our legacy backup solutions. Our legacy backup solution is in the same place. We are only using Zerto for DR.

Our environment is hybrid. We are using Zerto to protect our on-prem as well as the cloud environment, but I was not involved in its deployment. 

In terms of maintenance, I never had any requirements to maintain it.

Evaluation was done by someone else in the organization.

I would rate Zerto an eight out of ten. Simplicity is an advantage, but customization and reporting can be better.

We primarily use it for DR, that is, for VM replication between two data centers, using it not only for replication but also for orchestration.

Zerto provided better overall DR coverage and more consistency.

I found VM level replication and being able to group the VM levels to be valuable. I like not having to worry about whether a particular VM is in the right storage group; some of those sorts of things would trip us up previously. 

It's a lot easier and more straightforward for a VM administrator because he can know that this VM goes in this group or gets this tag, for example, and that it's now in a DR group and is taken care of. I don't have to worry about all the backend details. It's just simplified.

In terms of ease of use, the benefit of Zerto over SRM is the fact that it doesn't rely on a secondary backend product, with having to have the right storage groups with RecoverPoint or something else with multi-tier architecture.

It's still too early to compare the speed of recovery with Zerto versus the speed of recovery with other disaster recovery solutions. We've just started the DR tests to understand the time difference. However, from what I've seen so far, the speed of recovery is similar but more consistent with Zerto. We don't have situations where we've missed this or that.

Zerto reduced the staff involved in data recovery situations by a single person. Now, we don't have the backend storage person who has to keep an eye on it anymore. With a different solution, we would have needed two people.

There's one feature that SRM had that Zerto doesn't have, and it's one that we've been asking for. With the orchestration part of the failover, with our DR and our primary sites, the IP addresses are almost identical. The only difference is one octet. With SRM, we could say during a failover change. With Zerto, we keep hearing that it's coming, but we haven't received it yet. It's a feature that would be very beneficial. It would reduce the time a little bit more.

I've been working with Zerto for about two years.

The stability seems fine. I haven't seen any issues with it thus far.

For our organization, the scalability matched our needs. Between the data centers, we probably have somewhere in the neighborhood of 3,000 VMs.

From what I have seen, the technical support has been very good. They've been very responsive to my team.

We previously used SRM. Zerto is a little bit more mature, has a better feature set, and is more aligned with the features and functionalities that we need.

We have seen an ROI from the perspective of a reduction in hardware and a reduction in the number of people trying to focus on the tool sets.

It is less expensive than the full solution that we had previously, but at the same time, it's not an inexpensive product either.

We evaluated Cohesity and other solutions.

Overall, Zerto is a very good product for us, and I would rate it at nine on a scale from one to ten.