Aldo Centino - PeerSpot reviewer
System Administrator at Waternet
Real User
Provides near-synchronous replication, is easy to migrate data, and helps our users collaborate
Pros and Cons
  • "The communication between the VM and the secondary data center is the most valuable feature."
  • "I would like Zerto to provide more detailed information when there is an issue."

What is our primary use case?

We use Zerto to verify the information being transferred from one data center to another.

How has it helped my organization?

When a site is down, we can continue to use the other site thanks to Zerto.

The near-synchronous replication is extremely valuable because it ensures we can continue working.

The move action between the app and data center is great and we can see the benefits in minutes.

Our RPOs are performing well thanks to Zerto.

Migrating data using Zerto is easy.

Zerto helps our users collaborate during data migration.

Our RTO using Zerto is good.

What is most valuable?

The communication between the VM and the secondary data center is the most valuable feature.

What needs improvement?

I would like Zerto to provide more detailed information when there is an issue.

Buyer's Guide
Zerto
May 2024
Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: May 2024.
772,277 professionals have used our research since 2012.

For how long have I used the solution?

I have been using Zerto for five years.

What do I think about the stability of the solution?

Zerto is extremely stable. 

What do I think about the scalability of the solution?

Zerto is scalable.

How are customer service and support?

I have used the technical support of Zerto several times and they are good.

How would you rate customer service and support?

Positive

How was the initial setup?

Though I wasn't part of the initial deployment, the procedure is relatively simple. Manager rollout is the first step, followed by CPG installation on VMs by the CPG teams and subsequent network configuration verification.

Four people are required for the deployment.

What other advice do I have?

I would rate Zerto a nine out of ten.

Zerto is a good solution for transferring data between centers.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Sr Director, Private Hosting at a wholesaler/distributor with 10,001+ employees
Real User
Top 20
Does not rely on a secondary backend product and is easier and more straightforward to use
Pros and Cons
  • "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."
  • "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."

What is our primary use case?

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.

How has it helped my organization?

Zerto provided better overall DR coverage and more consistency.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

How are customer service and support?

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

Which solution did I use previously and why did I switch?

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.

What was our ROI?

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.

What's my experience with pricing, setup cost, and licensing?

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

Which other solutions did I evaluate?

We evaluated Cohesity and other solutions.

What other advice do I have?

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

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Zerto
May 2024
Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: May 2024.
772,277 professionals have used our research since 2012.
IT Infrastructure Server Manager at a logistics company with 5,001-10,000 employees
Real User
Is consistent, agile, and reduces downtime
Pros and Cons
  • "We've seen a massive benefit from using Zerto in terms of time savings and consistency. You see a consistent outcome every time you do the conversions. We're moving from one platform to another, but the payloads in what we're moving are different. We see consistent delivery."
  • "Right now, our production environment runs on-premises, and we have a DR copy of everything that we run in production. However, our development runs on that hardware. In the case of a DR event, we would need to shut down development and bring up our secondary copy of production. We're hoping that Zerto is going to be the tool to help us do that."

What is our primary use case?

We use it for our conversion from Hyper-V to VMware. The DR purposes are being looked into as well.

We've got about 1500 to 2000 Hyper-V machines. These Hyper-V machines are used and converted to VMware, and these are the two environments that we work with now, both on-premises and in a hosted environment.

What is most valuable?

The ease of the conversion, moving from Hyper-V over to VMware, has been the most valuable feature. It's the primary reason why we chose Zerto.

We've seen a massive benefit from using Zerto in terms of time savings and consistency. You see a consistent outcome every time you do the conversions. We're moving from one platform to another, but the payloads in what we're moving are different. We see consistent delivery.

Time savings-wise, I see anywhere from 30 to 50 VMs be converted from Hyper-V to VMware on a nightly basis. We've seen some pretty good throughput on the nights that we do conversions.

Zerto has absolutely helped to reduce downtime. If we were to do this manually, the amount of time that we would have to shut down the VMs on Hyper-V to be able to do the conversions and move them over to VMware would be massive.

That amount of downtime would cost our company a lot. We've got a team of three or four guys that do the labor. If you take what they're getting paid and you compound the amount of time that it would take to do the conversion, there would be a drastic cost in labor for those conversions.

What needs improvement?

Right now, our production environment runs on-premises, and we have a DR copy of everything that we run in production. However, our development runs on that hardware. In the case of a DR event, we would need to shut down development and bring up our secondary copy of production. We're hoping that Zerto is going to be the tool to help us do that.

For how long have I used the solution?

Zerto is primarily being used this year.

What do I think about the stability of the solution?

We're getting consistent results, so the product seems to be very stable.

Which solution did I use previously and why did I switch?

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

How was the initial setup?

I was not involved in the initial setup but have heard feedback that those involved loved the simplicity of it.

What was our ROI?

We've absolutely seen an ROI in terms of time savings with respect to downtime. When you convert a couple of thousand machines from one platform to another, the amount of downtime that it would take itself would have paid for Zerto many times over.

What's my experience with pricing, setup cost, and licensing?

We get our money's worth with Zerto.

What other advice do I have?

If you're in the middle of a conversion between different platforms, regardless of whether you're moving from on-premises to hosted or from one environment to another, it seems to be very agile and able to move your workloads into different environments pretty easily. I would give Zerto a rating of nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Network Administrator at a financial services firm with 51-200 employees
Real User
Easy to set up and use with a nice GUI, good support, and the automated failover works well
Pros and Cons
  • "Zerto is extremely easy to use. You set it and forget it."
  • "The reporting could be improved in terms of the reports that you can show to auditors to prove that you have done the testing. I provide the reports that it generates now but, it would be great if, at the end of a DR test, it would generate a report of everything that Zerto did."

What is our primary use case?

Zerto runs on a Windows Virtual Server and we have it installed at two sites. There is the production site, as well as the failover DR site.

We use this product almost exclusively for disaster recovery. It is responsible for the automated recovery of what we deem to be our mission-critical servers.

How has it helped my organization?

In terms of its ability to provide continuous data protection, this is a product that I trust. We test it quarterly to make sure that what the dashboard is telling us is correct. But, I've used it long enough to know that when I see the dashboard telling me that the virtual protection groups (VPGs) health are all green, then things are working correctly. Our average RPO is usually somewhere between three and 10 seconds.

We used to perform a disaster recovery test once a year, and it was painful because everything was manual. Now that we do it quarterly, we're able to provide management with reports of the tests, which not only makes management happy but also makes various governing bodies happy. We're a financial advisory firm, so it's the SEC that oversees us. That said, I'm sure this holds true in many industries. It allows you to have the reports to prove that you've done the tests. We don't have to ask them to take our word for it.

When we need to failback or move workloads, Zerto has absolutely decreased the time and number of people that are required to do so. For example, if I just want to test and prove that the network is up, it's something that I can do by myself. If I want to have people log in and test applications and stuff like that, I would need additional people. However, it has a built-in test function, so it will create a complete test network that you can run workloads on to show that the tests are successful. Afterward, you can delete the network and you're back just running, waiting for the next time you want to do that. In a situation like this, using Zerto saves eight hours or more and I can set it up and test it on my own unless I want people actually testing applications.

Thankfully, we have not had to use this product to recover from a ransomware attack or other disaster, but it would absolutely work in that case. By replicating the data, if ransomware were to hit the production side, it most likely would not also lock the disaster recovery side. This means that we would certainly be able to bring it up from there. Alternatively, it lets us pick points in time, so we can just go back to the moment in time before the ransomware happened. In a situation like this, I can't say that it would take fewer people but it would take fewer hours.

What is most valuable?

The most valuable feature is the automated failover, as it allows us to get the essential servers up at our DR site with little intervention.

Zerto is extremely easy to use. You set it and forget it.

It has a nice graphical interface.

What needs improvement?

The reporting could be improved in terms of the reports that you can show to auditors to prove that you have done the testing. I provide the reports that it generates now but, it would be great if, at the end of a DR test, it would generate a report of everything that Zerto did.

This would include details like what systems were up. Currently, that's not how the report reads. You would have to be an IT person to read the current reports that it produces. I would like for them to be the type of reports that I can put in front of an auditor or the president of our firm that would make sense to them, without me having to interpret and explain the results.

For how long have I used the solution?

We are in our seventh year of using Zerto.

What do I think about the stability of the solution?

Stability-wise, this solution is rock-solid. If it fails, it's not going to be Zerto that fails. It's going to be either that your storage has failed or the bandwidth, or connectivity, is not there. I don't see a way where Zerto would be the culprit in a failure-type instance.

What do I think about the scalability of the solution?

Our company is fairly small and the entire firm relies on it. That said, only one person actively uses it. We have three or four IT staff but Zerto has always been my responsibility.

In terms of scalability, I bet it would be no issue whatsoever. It's licensed according to the virtual machines that you want to protect. The only limitation of the scalability would be how deep your pockets are because it's going to be license costs.

We're a registered financial advisory firm, and we are growing. In the past year to 18 months, we have grown from approximately 52 employees to 70 employees. Everybody relies on it because if we have a disaster recovery type of situation, then everybody is going to expect to be able to work.

It is still a very small number of IT staff, so I can see that as we hire more IT staff to support a larger user base, we will certainly have more users.  At least, I hope not to be the only one responsible for this solution as we grow.

How are customer service and support?

I would rate the technical support a ten out of ten.

Which solution did I use previously and why did I switch?

Prior to Zerto, we used VMware Site Recovery Manager (SRM). We switched because it requires a lot of manual upkeep, and there is no automation involved unless you write the scripts. There are lots of freeware sites where you can download scripts, but aside from that, we were spending a lot of time manually writing scripts and maintaining everything. This was really counterproductive for the amount of time we had available in a day.

Essentially, SRM was replaced because of better interface automation and ease of use. 

How was the initial setup?

The setup is very easily done because you tie it into your VMware vCenter. When you put in your credentials, it will recognize everything on your networks. It will recognize storage, whether it be cloud-based or as in our case, at another data center. Once you have those defined, it's just a matter of creating groups that you want to recover, server-wise.

The reason that you would want to do it in groups is that you can set it up in the automation such that it will bring up groups in a certain order. That way, you have a network where the domain controllers come up in the first group, and you can automate stuff from there.

Seven years ago, when I first started to use it, I found it more difficult. I wouldn't say that it was complex but they have certainly made improvements over the years. Where it stands now, if I had to set it up from scratch, I could probably do it in about an hour. Of course, that is because of the way I know the application but in terms of how they have changed the setup, it is certainly more user-friendly than it was compared to where it started.

I remember running into a couple of issues during the deployment, and I contacted their support. They were fantastic and helped me get through it. They made sure that all of my questions were answered, and that it was up and running how we intended it to be used. A lot of it probably had to do with me being a novice at that point, in terms of using the application.

It was a multi-site deployment, with a production site and a DR site, with dedicated storage for each. We have changed the storage that it uses over the years and if I had to do it again, I would use another vendor for storage. A lot of the issues that we ran into were related to the initial storage that we used, as opposed to Zerto issues, even though it was Zerto support that helped me fix them. 

Overall, the deployment was fairly easy. Not because everything went great, but because of the combination of the application being pretty well-written and the support. I would rate the deployment an eight out of ten.

What about the implementation team?

I deployed Zerto with the help of a consultant, contacting support as we needed to. The consultant was NetGain Technologies and they're based out of Lexington, Kentucky. Their service was phenomenal and I would use them again in a heartbeat for this type of deployment. Ultimately, any issues that we ran into boiled down to some issues with the storage we chose to run it on.

I am responsible for the maintenance. 

What was our ROI?

We have absolutely seen a return on investment in terms of the manhours that have to be put into maintaining and testing this type of product. Thankfully, we have never had to use it in a true DR situation. However, I can guarantee that if something were to happen, even beyond the manhours and ease of automation, that it would pay for itself.

Our network infrastructure runs pretty smoothly most of the time. That said, Zerto has helped us to reduce downtime by approximately 20%. It is difficult to equate this with a monetary value because we have to consider what happens when a client misses a trade or cannot get a hold of their portfolio manager.

If it were an outage of a couple of hours then the person might pay a little more or a little less for a stock that they were trying to purchase. Overall, however, it is difficult to estimate. We aren't a day trading-type firm, so ultimately, I'm not sure that a short outage has any effect on our revenue stream whatsoever.

What's my experience with pricing, setup cost, and licensing?

As a small company, we own the smallest license that Zerto offers, which is 15 VMs. I've not had to contact them or my reseller about purchasing additional licenses or to find out how much they cost.

Which other solutions did I evaluate?

We spoke with VMware to see what their pipeline was for upgrades or changes to Site Recovery Manager and we also looked at both Cohesity and Rubrik.

I like the separation of the software and the storage, whereas some of those other products are all-in-one. You're buying the software and storage together on the same platform. This means that the scalability would be different.

Sometimes, this is a case of adding shelves for storage. In that situation, for example, you have to start taking the data center rack space into account. Whereas with Zerto, it lets us build upon hardware we already had, even though we use dedicated storage.

What other advice do I have?

Version 9 of this product is out. However, we have not yet upgraded. We're not leveraging the cloud the way a lot of companies do these days, and I know from the release notes that I've read that most of the new features are related to the cloud. There's not a lot of research and development being done on physical data centers anymore.

At this point, I'm very happy with where the product sits for my network. We are now just starting to move things to the cloud, which will take place over the next couple of years, so my assessment in this regard may change in perhaps a few years.

At the moment, we don't have plans to use it for long-term retention. We keep about three days' worth of data in Zerto and then it rolls off. We have other systems in place for long-term retention.

My advice for anybody who is looking into implementing Zerto is to do your homework. In the end, this product checks all of the boxes and it's the one that I would go with.

In the way that we use this solution, which I know is not how everybody uses it, we have storage that is specifically used for Zerto and two data centers. The way it works in that scenario, as long the bandwidth is there, meaning some sort of dedicated circuit between the two sites, it's flawless in my opinion.

The biggest lesson that I have learned from using Zerto is that disaster recovery doesn't have to be a giant pain. I certainly used to look at it that way in the past.

I would rate this solution a ten out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Dov Goldman - PeerSpot reviewer
Systems Engineer at a financial services firm with 501-1,000 employees
Real User
Top 10
It saves a lot of time because we can hit a button and let it do its thing
Pros and Cons
  • "In our DR testing, Zerto allows us to go work on other things while it takes care of everything. That's valuable because we know that we can still hit all of our SLAs in a real disaster."
  • "The post-configuration part could be improved. For example, it would be super helpful to have the ability to modify DNS. Once the migration is done, we want to do some more modifications to the endpoint."

What is our primary use case?

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

How has it helped my organization?

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

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

What is most valuable?

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

What needs improvement?

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

For how long have I used the solution?

We have used Zerto for around 10 years.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

How are customer service and support?

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

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

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

What was our ROI?

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

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

I rate Zerto 10 out of 10.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
IT Infrastructure Manager at a tech services company with 10,001+ employees
Real User
Top 20
Ability to decouple from hardware, allowing flexibility in source and destination
Pros and Cons
  • "The most valuable for us and for my company is that we are replicating most of our production customers to the DR site, and we can do testing whenever we want."
  • "Zerto generates many false positive alerts, which is annoying. I still have thousands of alerts in my inbox, and those are false alerts. When I check there's actually no problem."

What is our primary use case?

Our primary use cases include replication and disaster recovery. 

How has it helped my organization?

We use Zerto to help protect VMs in our environment. We are really happy with RPOs (Recovery Point Objectives).

Both the Recovery Point Objective (RPO) and Recovery Time Objective (RTO) are fine. They always meet our requirements. Their significance is not driven by a single factor but rather by the customers. Some customers require an RPO of a few hours, while others require up to 24 hours. It depends on the specific needs of the customer.

What is most valuable?

The most valuable feature for us and for my company is that we are replicating most of our production customers to the DR site, and we can do testing whenever we want. The customers are very happy with the way we do the testing while the primary is still running. There's no disturbance to the primary production site. 

The most important function right now is that we have another DR site, which is in a very old environment that is non-Zerto. We were log shipping there through another method. We are migrating over to the Zerto platform so we can replicate it to the new DR site so we can shut it down. That's going to be a lot of savings for us, shutting down the old replication with the other way. That will be one of the benefits too.

Zerto offers near-synchronous replication, which is always on and constantly replicates only the changed data to the recovery sites within seconds. It doesn't really bother us because we have enough bandwidth. Since we do a 24-hour recovery, it does not take a lot of disk space. It's an issue sometimes because I have to constantly increase the space on the disks at the DR site. On the VPG (Virtual Protection Groups), I have to constantly increase the space. That's where the alerts are being generated too.  

Someone suggested to me that I should turn off this feature, but that's not the way to do it. Turning it off temporarily is similar to applying a bandage.

Moreover, we have plans for DR recovery in the cloud. That's our next step, and it's likely to be on the agenda. We probably will use the license we have for that, which we can use as of today.

What needs improvement?

Zerto generates many false positive alerts, which is annoying. I still have thousands of alerts in my inbox, and those are false alerts. When I check there's actually no problem.

For how long have I used the solution?

I have been using Zerto for four-plus years. 

What do I think about the stability of the solution?

It's very stable as far as we're running. Even though I'm running it on a very old Windows Server 2012 server, it's still running fine without any issues. 

What do I think about the scalability of the solution?

Scalability-wise, it's pretty good, too, but we're not there yet. We are using it for small 50+ VMs we are protecting right now, but we are continuously growing. We may have to expand with multiple ZVMs (Virtual Managers). We're going to install multiple. We just have one on each side, which we don't have an issue with.

How are customer service and support?

The customer service and support are really good. I wish they had phone support too right away, but we have to go through their website and open a ticket.

Moreover, there's always going to be something a person is not one hundred percent knowledgeable about. He has to escalate to the top tier. 

How would you rate customer service and support?

Positive

What about the implementation team?

Somebody else did the deployment in the company and I took it over after that. I just recently upgraded to the latest version without any issues. Zerto is very easy to upgrade.

There is an area of improvement for Zerto folks. Every time we do an upgrade, if we are three or four releases behind, we have to go to the next level, then the next level, and then the latest. This is a pain. We would like the ability to skip to the newest version. 

What was our ROI?

ROI is pretty good compared to the recovery compared to the investment we have. The solution is worth it. If we go to the cloud, the ROI is definitely going to be much more.

What's my experience with pricing, setup cost, and licensing?

The pricing is pretty decent. We got a good deal. 

Which other solutions did I evaluate?

I really like Zerto. I've been using it for many years. It's a quick recovery. I failed over the complete site to the DR many times and then failed back to the production without any issues. 

We have VMware SRM but we are not using it. We have a license, we can use it, but we're not using it because Zerto is our primary right now. 

Zerto is very easy to use. It's not dependent on the hardware. It can decouple from any hardware. You can use it, even if you have different hardware at the source and the destination. That was the biggest attraction when we got into Zerto. It's pretty decent. 

What other advice do I have?

I would rate Zerto a ten out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Jose Tomala - PeerSpot reviewer
IT Linux System Engineer at a financial services firm with 5,001-10,000 employees
Real User
Enables us to recover virtual machines to a specific point in time, and test recovery for more machines with less staff
Pros and Cons
  • "The replication and recovery features are the most valuable... On two occasions, other departments in our organization reported issues with specific virtual machines. We used the checkpoint feature of the Zerto to enable the recovery of those machines to a point that was a few minutes prior to the problem."
  • "We had some issues with replication, especially on Linux, but we have already resolved them."

What is our primary use case?

We use it for storage and replication. In our organization, our team is responsible for the disaster recovery process.

How has it helped my organization?

Before, we were able to test about 16 virtual machines in production. Now, we can do the same exercise with 180 virtual machines, in less time. And previously, we needed our whole team to execute the manual process with Hitachi. Now, we use half that number of personnel in this exercise.

The speed of recovery is definitely better with Zerto versus the previous mechanisms we had. It has helped to reduce downtime without a doubt. On two occasions when we used Zerto for recovery, we reduced the downtime by about 80 percent.

We had an issue with change configurations in a database and we couldn't roll back those changes. We used Zerto to recover the state of the virtual machines to 10 minutes before the changes.

It has also exceeded our expectations when it comes to RTO.

What is most valuable?

The replication and recovery features are the most valuable. We have been able to recover files with Zerto. First, we enable the virtual machines on the recovery site and then we navigate to find the file that we need. On two occasions, other departments in our organization reported issues with specific virtual machines. We used the checkpoint feature of the Zerto to enable the recovery of those machines to a point that was a few minutes prior to the problem.

It's an excellent tool for the replication of VMs.

What needs improvement?

We had some issues with replication, especially on Linux, but we have already resolved them.

I would like them to enable more backup configuration features. I'm not sure if Zerto can give us immutable files for ransomware protection. That could improve the backup.

For how long have I used the solution?

I have been using Zerto for about two years.

What do I think about the stability of the solution?

The stability gets a high grade from me. I don't recall any issues.

What do I think about the scalability of the solution?

Our principal site is located in one city and the recovery site is in another city. They are connected by an extended LAN.

In terms of scalability, it is good because, on the two occasions that we have done the upgrade process, they were "hot," meaning we didn't need to turn off our servers and that's very important for us. We always have our tools available.

How are customer service and support?

We have opened cases on several occasions for update processes and for issues that we had at a moment when we were doing an exercise and replicating a VM to the recovery site. Their response was immediate and they were very efficient in coming up with resolutions.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We didn't have any previous backup solution.

What's my experience with pricing, setup cost, and licensing?

The pricing is a little more expensive in comparison to other tools.

Knowing the backup options that Zerto has, we could be using it to back up our entire company's virtual machines, but we are just using its replication and backup for some virtual machines, but not all of them. That's because we are limited in terms of our license. We are only replicating about 30 percent of our virtual machines, those that have been identified as the most important for the organization.

Which other solutions did I evaluate?

We checked out Veritas Risk Advisor and Veeam.

What other advice do I have?

It is meeting our RPO expectations and we are happy with the RPO.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Analyst at COUNTY OF BUTTE
Real User
Top 20
Storage software that offers consistent performance in the conversion of Hyper-V to VMware
Pros and Cons
  • "Zerto offered us massive time saving and consistency. We have a consistent outcome every time we complete conversions."
  • "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."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

This is a stable solution that offers consistent results. 

Which solution did I use previously and why did I switch?

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.

What other advice do I have?

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. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros sharing their opinions.
Updated: May 2024
Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros sharing their opinions.