Information Technology Director at Cameron county
Real User
With a single click, we are up and running at another site
Pros and Cons
  • "For most use cases, the failover time is a handful of minutes, if that. A single user can run the system."
  • "The tech support on my latest issue wasn't so great. I had to figure a lot of stuff out myself. It could be that I had a Level 1 tech who was new or something, but it seemed like the tech was spitballing, which does not help me."

What is our primary use case?

Right now, we use it just for disaster recovery.

How has it helped my organization?

We have always had a centralized data center. Therefore, if we were to lose connectivity or power, then access to county resources would be cut off until that issue is resolved. If there is a hurricane, it would be the same thing. If we lose power, then we would be down until something comes up. With Zerto, I can quickly get us up and running at the disaster recovery site, provided it is still operational.

For most use cases, the failover time is a handful of minutes, if that. A single user can run the system.

Zerto will reduce the number of staff involved in a data recovery situation. As of now, we have been lucky. We have not had to deal with this type of issue. However, it will require less people going forward. So, I can dedicate people to other tasks in a situation like this.

Disaster recovery would initially require four or five people to handle just the server side. This has now been cut down to just one person.

What is most valuable?

It provides great continuous data protection. The RPOs on things are in seconds.

For how long have I used the solution?

We have been using it for two years.

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.
787,560 professionals have used our research since 2012.

What do I think about the stability of the solution?

We haven't had any issues. It literally just runs. Once you have it set up, you just leave it alone.

What do I think about the scalability of the solution?

As long as I have the resources and licensing, I can keep going from a scalability perspective.

How are customer service and support?

The tech support on my latest issue wasn't so great. I had to figure a lot of stuff out myself. It could be that I had a Level 1 tech who was new or something, but it seemed like the tech was spitballing, which does not help me.

In previous instances, the technical support was great. They were able to get me up and running fairly quickly.

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

We didn't have a solution like this before that allowed for disaster recovery. Everything was restored from backup, then we had to wait. So, if something went south, then we would need to restore from a backup. I saw the Zerto product was literally one button click, then I can failover to a disaster recovery site and keep going. That was amazing during the initial review of the product. It was just easy.

We started looking at how long it would take to restore from a backup. Rebuilding that infrastructure would take hours, if not days, as opposed to having the ability with Zerto to do a single click, then we are up and running at another site.

It is being used in conjunction with our legacy backup solution.

How was the initial setup?

It was actually fairly easy to set up the solution. Installing it, creating the VPGs, and adding the VMs to it was fairly straightforward.

What about the implementation team?

Working with support on the line, we deployed Zerto in a couple hours.

What was our ROI?

It is about $1,000 per VM, so it is pricey. However, the cost and time (the manpower cost) that it would take several members of IT to restore a backup and every individual piece of the virtual environment would easily exceed the pricing cost.

If we had to trigger it, downtime would go down to whatever the RPO is at that time. Right now, our RPO average is between four and 10 seconds. This is a big cost saver for us. Anytime certain systems are down within the organization, money is lost.

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

The only negative part that I have seen so far has been the cost. It is kind of pricey, but you get what you pay for. Zerto is a lot faster than other solutions and you get enhanced performance.

Which other solutions did I evaluate?

Eventually, we will expand solution use. While there are some competitors in the market, I don't think any of them get to the ease of use and speed that Zerto has. Even Veem has CDP, which is similar, but it is not as fast, user-friendly, or worry-free.

Veeam CDP was still fledgling at the time of our evaluation. It existed, but wasn't that great. It wasn't anywhere near as robust as Zerto. Commvault had something similar as well, but even their solution doesn't do disaster recovery as quickly as Zerto.

It is important that it has both backup and disaster recovery. As I am looking for a backup and recovery solution, I am looking for something that can do everything.

What other advice do I have?

The solution was bought to help with the mitigation of ransomware.

Right now, we are still in a physical data center. We haven't looked at their solution for going to the cloud. That is something which is coming up. Eventually, we will make the switch over. Right now, we are working on a new backup and DR solution. So, that will go hand in hand once we are done with the on-prem.

I would rate Zerto as 10 out of 10 based on the way that the product works.

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
Solutions Manager at a tech consulting company with 51-200 employees
Real User
Easy-to-use interface, straightforward to deploy, good compression features, and responsive support
Pros and Cons
  • "The most important feature is that the recovery point (RPO) is less than one minute. The is really good for our customers, as they can keep their data loss to a minimum."
  • "I would like to see a separate product offer for performing backups, although I think that this is something that they are expecting to release in the next version."

What is our primary use case?

I am a solution provider and Zerto is one of the products that I implement for my clients.

Most of my customers use this product for disaster recovery purposes. Some of them use it in a local, on-premises environment, whereas other customers use it in the cloud.

We have assisted some of our clients with on-premises to cloud migration. These were customers that had an established local environment but wanted to explore the cloud. For these clients, it is a cloud-based DR implementation.

There are four or five customers that did not want a cloud deployment, so we have implemented the DR site on-premises for them.

If the client is given the choice, typically they prefer a cloud-based deployment. CDP technology is becoming the new norm, even for the backup industry. However, there are some instances where it is not an option. For example, in some situations, they cannot use cloud-based storage due to legal and compliance requirements.

Some of our customers that are making a digital transformation cannot afford to lose hours or even minutes of data. As such, I think that cloud-based disaster recovery is the future and the customers understand why it is much more important for them. Together with our reputation, I see this as a game-changing situation.

How has it helped my organization?

Most of my customers are interested in DR and do not know much about the long-term retention capability. Our last three deployments already had a backup implemented from the integrator and didn't need an overnight one to avoid the loss of data. We discussed this with them and explained that this product offers much more than what they are using it for. We pointed out that it was a two-in-one solution but they continue to use it primarily for DR.

Our customers find that the interface is really easy to use. It gives you a great deal of flexibility for the administrators, as well as for the end-users to a certain extent. Overall, with respect to ease of use, this product scores the highest points in this area.

What is most valuable?

The functionality available in the console is not complicated and is easy to use, especially for DR failover. It just works.

It offers a high level of compression, which is very good. My customers and I are interested in this feature primarily because it saves bandwidth.

The most important feature is that the recovery point (RPO) is less than one minute. This is really good for our customers, as they can keep their data loss to a minimum.

What needs improvement?

I would like to see a separate product offer for performing backups, although I think that this is something that they are expecting to release in the next version.

For how long have I used the solution?

We have been using Zerto for between three and four years.

What do I think about the stability of the solution?

Based on the number of support calls that I get from my customers, where we have done the deployment, issues arise very rarely. From time to time, we get calls because the allocated space is running out. Otherwise, it is pretty much stable.

Even the situation where the allocated space runs low is rare and I haven't had this type of call in a long time. The reason for this is that I take precautions during deployment. For example, I check to see whether they have too many workflows. I know what it is that we need to do including how many VRAs we need to deploy and what the configuration should be. Over the past three to four years, I have only had to deal with four or five support tickets. Apart from that, I haven't experienced any problems.

What do I think about the scalability of the solution?

I do not have a great deal of experience with scaling this product because all of my customers have only a few hundred VMs. I know that Zerto has the capability to go beyond 5,000 or 10,000, but that is something that I've never experienced. My understanding is that it is very capable at the data center management level.

How are customer service and technical support?

In the initial phase, I leveraged technical support, but then I completed the deployment.

During the PoC, there were one or two times where I had to contact them to deal with issues. I am pretty happy with how they respond and how they follow up compared with the other vendors that I work with.

I don't have much of a complaint with respect to support.

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

I have been working with Zerto since version 6 and the most recent one that we deployed was version 8.5. Approximately six months ago, our customer that was using version 6 was upgraded to version 8, because version 8.5 was not yet released.

I also have experience with Veeam but Zerto uses a very different technology to perform the backup and change tracking. Veeam leverages the VSS technology for the volume set up, which will do the job but it is not ideal. Zerto has taken one step ahead by utilizing the Journal technology, which is the main difference that I can think of between these two products.

Prior to working with Zerto, many of my clients were using the VMware Site Recovery Manager (SRM) feature, which comes built into the product, based on their licensing. I have also had a customer who was using Commvault and others that were using NetBackup. These are typically the enterprise-caliber products that I expect to find.

One of my customers is using Veeam and because of the difference in price, with Zerto being more expensive, they did not switch. My customer felt that Veeam was convenient and the price was more tolerable. This is the only instance where my customer did not transition to Zerto.

The customers who switched have done so because Zerto provides the lowest RPO and RTO. It is one of the main points that I emphasize about this product because it is very important to them. There is also a saving in bandwidth, which is something that my customers are concerned with because they typically don't have fancy high-speed connections. The compression is superb and really helps in this regard. These are the two primary selling points.

How was the initial setup?

For us, this solution is not difficult to deploy. For a complicated environment then you have to do careful planning but otherwise, it is not hard to deploy.

Typically, if everything is well in place, the deployment will take between one and three hours. In cases where the customer's environment is very complex then I might need a little bit more time. I would estimate that it would take six-plus hours, after careful planning and ensuring that all of the resources are in place.

The installation takes less than 30 minutes; however, the customer environment increases the time because we have to do things like open ports on the firewall. We tell them about these preparations in advance but we always end up doing some of the work ourselves. In situations where the firewall has already been properly configured, I can normally complete the installation and configuration in one hour.

I have two customers that use the cloud-based deployment on Azure but the majority of them use it in a local, on-premises environment.

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

The main challenge that I face with this solution is the price. All of my customers are happy with how this product works and they like it, but unfortunately, in the market that I represent, Zerto is expensive when compared with the competition.

Another issue is that Zerto has expectations with respect to the minimum number of devices that they are protecting at a given price range. I understand that this is an enterprise product, but unfortunately, price-wise, it is really tough when it comes to the TCO for the customers in the one or two countries that I represent. Apart from that, everyone understands the value, but at the end of the day it comes down to the price being slightly higher.

Pricing is something that I have discussed with the regional head of sales in this area. I have explained that you can't have a price of 25 million per year in this region, and in turn, have requested a lower price with different models for corporations. Unfortunately, I have not received a positive response so far.

What other advice do I have?

With the separate backup product expected to be available in the next release, in a way, they have already done what I was expecting to offer to our customers. They have also announced some features that are really interesting. Right now, I'm waiting to get the new products in my hands.

My advice for anybody who is implementing Zerto is that if the system administrator has basic knowledge about networking and storage, then setting it up and deploying it will be easy, and not an issue at all. They just have to be careful and take the appropriate time to plan properly, especially in a complex environment.

In summary, this is a stable, enterprise-grade product.

I would rate this solution a nine 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. The reviewer's company has a business relationship with this vendor other than being a customer: Independent Consultant
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.
787,560 professionals have used our research since 2012.
Senior Server Storage Engineer at MAPFRE Insurance
Real User
Reduced the number of people onsite during a disaster recovery drill
Pros and Cons
  • "Most of the time, this is at least a two person job. We used to have three people doing it. Previously, when we had a disaster recovery drill, the way it worked was 12 of us would show up in the office on a Friday night and work overnight from 12:00 AM on Friday night to 8:00 AM in the morning on Saturday. Then, three of us would be working for four hours out of those eight or nine hours just getting applications up and running in Arizona. Now, for the disaster recovery drill, I just stay onsite to help and assist anybody else as they need during that time frame and my work is done in about a 30-minute time frame. This is compared to the four or five hours it used to take for the three of us to do it."
  • "The alerting doesn't quite give you the information about what exactly is going on when an issue comes up. We do get alerts inside of our vCenter, but it doesn't quite give you accurate information inside the plugin to be able to tell us what's going on without having to go into the actual Zerto application and figuring out what's causing the issue."

What is our primary use case?

We do a semiannual disaster recovery test, usually one in January and another in September, where we fail our entire company over to our Arizona DR facility. We run the business out of the Arizona location for the day. In order to be able to do that, the Zerto application allows us to migrate 58 machines over to that location and allows us to run our business from that location for the course of the day.

How has it helped my organization?

We are able to have a successful disaster recovery solution through using Zerto for our Disaster Recovery drills. We are able to fail over anytime, day or night, to run our applications out of our Arizona facility. Within a 15 or 20 minute time frame, we can have those application servers up and running in Arizona. It is just a huge help to have a successful, reliable disaster recovery solution that we know at any point in time, within 15 or 20 minutes, can be running out of a different location.

Most of the time, this is at least a two person job. Previously, when we had a disaster recovery drill it would take two of us working for three or four hours just getting applications up and running in Arizona. Now, for the disaster recovery drill, I'm able to finish my work in about 30 mins and be available onsite to help and assist anybody else as needed during the disaster recovery drill. Its ease of use and the ability to have a reliable solution for disaster recovery has become invaluable to us.

What is most valuable?

There is built-in active logging if needed for a longer retention period. If we fail a machine over and are just doing tests for it, we can fail it right back at the end of the failover without much issue. We couldn't do that with SRM. The ability to keep track within the activity log of what is going on with the VM, then fail it back prior to the one-hour time frame that we have set up without having to worry about it losing data during our tests or production failover drills.

The product is very easy to use. On a scale of one to 10, I'd say it's a nine as far as ease of use goes. In order to do an update in our old product (SRM), we basically had to take down almost our entire vCenter to be able to do the updates. Whereas, I can do updates to our Zerto product within 30 minutes to both our ZVMs in Massachusetts and Arizona. We haven't had problems troubleshooting after doing upgrades. Within five minutes, we can configure a whole new cluster solution and work on getting it synced out to Arizona.

It transfers up-to-the-minute files. Therefore, if something was to happen and the business was to go down Massachusetts due to a server failure, we could simply fire up those VMs in Arizona within approximately five minutes. The data protection level is top-notch. We haven't lost any machines, data, or VMs during the course of utilizing this product.

What needs improvement?

The alerting doesn't quite give you the information about what exactly is going on when an issue comes up. We do get alerts inside of our vCenter, but it doesn't give you accurate information on the error message to be able to tell us what's going on without having to go actually login into Zerto to determine what's causing the issue.

Another issue with the alerting is that it will pause a job. E.g., if we have something running from Massachusetts to Arizona, but a VM has been removed, updated or moved to a new location in vCenter. It literally pauses the VPG the VM resides in but will never give us a notification that it's been paused. Therefore, if we had an issue during the course of the day such as a power event and we needed to gain access to those VMs in some sort of catastrophe, we wouldn't be able to get access to them because that job was paused and were never notified about it being paused for whatever reason. It would therefore be a big problem if the VM was needed to be recovered and we didn't have those resources available.

It would be great to get more precise alerting to be able to allow us to troubleshoot a bit better. Or have the application at least give us a heads up, "A VPG job has been paused." Right now, it's sort of a manual process that we have to monitor ourselves, which is not a great way to do things if you have a superior disaster recovery solution.

For how long have I used the solution?

Almost two years.

What do I think about the stability of the solution?

The stability is rock-solid. Nothing has gone down since we installed it; there has been no downtime.

Typically, once a quarter, we have an update. Last year we were at version 7.5, then we recently went updates to 8.0. On top of that, they release security patches and other things to improve bugs they find in the program. Right now, there is a U4 version that's out, which we will be updating to this quarter.

In the U4 version, there are security enhancements because a lot of zero-day issues that are being found in a lot of the applications. Zerto is making more security modifications and enhancements to the encryption between one location and another, so somebody can't hack your data and access it while it's in transition.

What do I think about the scalability of the solution?

Scalability is very easy. We are going through a POC right now because we want to branch out to the cloud. Just getting that set up and going through the process was about 60 minutes.

It's very scalable and extendable. We can do one to many solutions, as far as where our disaster recovery is going. This is what we wanted. We would never have been able to do that with our SRM product.

There are two engineers trained to use the product. I'm the primary contact for the application and do most of the work on the product. One of the storage guys handles a lot of the storage set up on the back-end with me. We have at least two people trained on each application that we have in-house. Both of us are in charge of making sure the application is up-to-date and doing what it's supposed to be doing. 

How are customer service and technical support?

Zerto's technical support is very good. They are very reliable and always very pleasant to deal with. We've never an issue working with them. They usually come back with the precise solution to whatever we are troubleshooting.

Our issues are usually user self-inflicted. E.g., we remove a host out of the cluster to upgrade it or do something else with it and don't follow the correct procedure that's needed in order to be able to shut down the Zerto appliance correctly. If somebody doesn't follow that procedure, because they either don't know how, weren't aware of it, or just skip that step, then it causes problems inside of Zerto. This will pause jobs and the VPG will no longer be accessible on that host. Sometimes it's easy to get it back up and running again. Usually, when you put a new piece of hardware in the cluster that has a different set of parameters with its hardware, then the appliance will be missing because it was taken out with the old hardware. Usually, you need to get their technical support involved in order to be able to troubleshoot the issue with them to be able to get the VPG back online again on the new hardware. As I said its self-inflicted most of the time because steps are missed with our processes.

The documentation that we got from them was in depth and work well when needed, if you follow them correctly you will have success. If you don't follow the steps, that's when problems develop. Therefore, it's not a fault in their documentation, it's a fault of the user who's not following the proper steps for success. It doesn't happen often but I think we have contacted technical support only three times in the two years that we've had the product.

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

For eight years prior to using Zerto we used to use a product called SRM, which is part of VMware. We finally switched over to Zerto after having them come in and do a presentation for us. This was after trying for about a year to do that and convince our vice president to allow us to migrate over to a different platform.

The reason why we used SRM was because SRM was built into our VMware vCenter licensing. We never had a successful DR test during the previous couple of years with SRM. By switching over to the Zerto product a year and a half ago, we were able to run a successful disaster recovery test within three months of switching over. We had our first successful disaster recovery tests in two and a half years because Zerto made our life so much easier and helped getting servers over to a new location almost seamlessly. 

In order to be able to have a successful disaster recovery, we need to be able to successfully migrate 58 servers from our Massachusetts location to Arizona. On previous attempts, we got about half the stuff over there, then we'd fail. In other scenarios we would get everything over there but some of the machines wouldn't come up because of the way they were configured. One time, the business was down for about half the morning because it took us that long to get the stuff back up and running using SRM. This was a real pain point for us, getting this product in place and working successfully. It took Zerto to be able to finally get us to do that. It's been a lifesaver. All we had with SRM was nothing but headaches.

How was the initial setup?

The initial setup was very straightforward. We had everything running in half an hour. It got deployed with two virtual machines (ZVMs): One got deployed in Massachusetts and another in our Arizona location. From there, we deploy appliances to each one of the hosts that's inside of the clusters that we are managing for our disaster recovery solution.

Within 30 minutes, we had it deployed to our entire production cluster and the hosts in here. After that, we just started creating jobs, which took quite awhile to do because we have a lot of large servers. However, that's not the worry of the Zerto application, but the size of the VMs we have in production. 

For our implementation strategy, we just mimicked what we had in place for our SRM environment. Our 58 machines are spread across different clusters: some in our DMZ, some in our prod and some in our WebSphere clusters. After that, we ran two tests to ensure that we were able to fail over to our Arizona location then fail back without any changes or modifications to the VMs. Once we did that, we started rolling out to each of the clusters, one Virtual Protection Group (VPG) at a time. I think we now have 23 VPGs total.

What about the implementation team?

We worked with an outside vendor (Daymark) who does a lot of our work through outside vendors. They work with Zerto directly. When we set it up originally, we had a Zerto technician on the call as well as a Daymark technician on-site working with us.

Our experience with Daymark has been very good. We love working with them and try to use them for our integration and infrastructure work. They are a very good company that are easy to deal with. We try to use them as much as we can. Thanks to Rick and Matt for a great working relationship.

What was our ROI?

We have seen huge ROI.

It used to be a three-person job, and now it only takes one person to manage and run the process. The fall back is the same thing. We've never had any issues with stuff coming back out of Arizona to our Massachusetts location. Within 15 to 20 minutes, we can have our servers successfully migrated back, then up and running just as they were originally without having too many conflicts or configuration issues. 

The solution has helped us reduce downtime in any situation that we have come across, thus far, for disaster recovery at a 4:1 ratio.

We are an insurance company therefore, if we're down for an hour, it's thousands of dollars being lost. E.g., people can't pay their insurance bills, open new policies or get the support they need for an accident.

These things have been invaluable to us:

  • Not having to have so many bodies onsite during a disaster recovery drill.
  • Not having to worry about multiple people dealing with the application.
  • The product's reliability of always being up and running and not having any issues with it.

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

It's very equitable, otherwise we wouldn't do it. It's something that we utilize for the licenses per host used. Therefore, it's very cost-efficient as far as the licensing goes. For the amount of stuff that we have configured and what we're utilizing it for, the licensing is not very expensive at all.

There is a one-time cost for maintenance and support. We have a three-year contract that we will have to renew when those three years come up. There is also licensing on top of that for whatever product you are using it depending on the host configurations.

Which other solutions did I evaluate?

Right now, we use Veritas. We will be evaluating Veeam and Rubrik as a new solution for our backups in the next quarter or so, on top of the fact that we may decide to use Zerto. The three of them are in the mix right now for when we decide to switch over vendors for a better backup solution. 

Zerto gives you the ability to utilize it as a backup solution, but it's not a true backup solution because it can't do file level backups. If you want a particular file off of a server, it can't do that for you. What it can do is give you the whole server, then you need to go back and pull that file off it. Mainly for that reason, we haven't chosen to use Zerto and may never use Zerto as our backup solution. The other solutions allow us to get a file level backup.

What other advice do I have?

Don't hesitate. Go out and do it now. Don't wait two years like we did. Push harder in order to be able to get the solution in place, especially since we know it will work better for you. Don't just take, "No," for an answer from senior management.

The application is phenomenal. They continually add new things, more plugins, and modifications to the way things work. It just gets better as they go.

We don't plan to use the solution for long-term retention at this time, but we are looking at going into a hybrid cloud solution in the near future which we may be using long-term retention for to make a duplicate copy of everything we have in our Massachusetts data center into a cloud solution. Whether it be an Azure or Amazon location on the cloud.

While I can't really speak to whether it would allow us to do it, the application is set up to create a duplicate of the actual servers in Arizona. That's how it works so quickly. If we ever had a problem, I could always revert back from the duplicates that we have out in Arizona using the application, if necessary. Luckily, we haven't had a need for that, and hopefully never do.

I would rate this solution as a nine (out of 10).

Which deployment model are you using for this solution?

On-premises

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
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
Gaurav Sharma. - PeerSpot reviewer
Infrastructure Architect at a comms service provider with 1,001-5,000 employees
Reseller
Top 5
User-friendly, easy to set up, and offers good speed to recovery times
Pros and Cons
  • "The disaster recovery features are the best I've found."
  • "We'd like to be able to migrate data without its operating system or any other functionality and without having to go through a virtual machine or server."

What is our primary use case?

The solution was primarily used for disaster recovery for clients. If there was a major issue in the data center, it allowed the client to move to the second data center. It was also used for migration to virtual machines.

How has it helped my organization?

My customer recently (a few years ago), had a major issue in one of the data centers. It was a virus attack that destroyed the servers and virtual machines. We could not recover those servers or virtual machines. After that, we decided to remove the corrupted data center and get everything recovered using Zerto. We were able to do that with the agreed-upon RTO and RPO for the customer. 

What is most valuable?

The replication between data centers is great. It allowed us to ensure all data was replicated from one side to another.

The near-synchronous replication is great to have. It works better than other solutions. 

It's very user-friendly and straightforward. There are no bugs in the software.

The disaster recovery features are the best I've found. 

This product allows us to do disaster recovery in the cloud rather than the physical data centers. We have multiple customers who are on a hybrid cloud. Some are on a private cloud and some are on a public cloud and Zerto allows us to provide the functionality whereby we can cover both as well as across physical data centers. We use Zerto for AWS, Azure, and GCP.

It was nice to use with AWS. Everything was in place on AWS and the functionality is well documented. We've done a POC on it. We have not yet had a chance to do a real disaster recovery just yet.

Zerto has helped us protect VMs in the customer environment. The overall effect on the RPOs is good. We can do it at a maximum within 15 minutes, however, often we can do it within five minutes, or even one minute. 

The speed of recovery is very quick compared to other tools.

It's easy to migrate data with Zerto. It's simple. Even non-technical users can see what information is needed in order to enable the replication from one site to another.

Users can still collaborate during the migration process in Azure. It depends on how much data you are including from your data center. The bandwidth connectivity between two data centers is very high.

The RTO is pretty good. We typically give our customers a heads up it will be eight hours, however, it's often less.

It's helped us reduce downtime. For example, when I was using another solution, we wanted to restore a VM. It took more than eight hours to restore ten virtual machines. In contrast, Zerto only takes 45 minutes. 

We had a corruption at one point on 20 to 25 VMs, that were critical from the customer's point of view. They had already spent so much time trying to troubleshoot. We decided to use Zerto to restore the machines and give them the latest backup. We were able to give them everything in less than one minute.

For the customer to recover using a different solution, it would take much longer. Zerto takes far less time. For example, compared to VMware SRM, it takes almost double the time compared to Zerto. 

We've been able to reduce DR testing. When we used to give RPO and RTO time to our customers, two hours for RPO and eight hours for RTO, once we started using Zerto, we reduced RPO to 15 minutes.

It's reduced the staff time involved in a data recovery situation. When we initially set up Zerto, it immediately starts replicating and does incremental replication as well. Therefore, at any given point in time, the latest data is already available on the recovery side. We just have to trigger it and everything will be restored as per our configuration. We likely save three to four hours of work during the disaster recovery period. And, in the disaster recovery phase, every minute is crucial. 

It's also reduced staff involvement. It's not complex and very straightforward. Since tasks are reduced, we do not need so much staff. 

What needs improvement?

Previously, it was not compatible with the public clouds. However, now that it is, it's helped a lot. One of the most challenging aspects in migrating items from private to public.

We'd like to be able to migrate data without its operating system or any other functionality and without having to go through a virtual machine or server. 

For how long have I used the solution?

I've used the solution since 2015. I stopped using it around 2022.

What do I think about the stability of the solution?

The solution is absolutely stable. We have customers that have used it since 2016 without any concerns. 

What do I think about the scalability of the solution?

The product can scale. 

How are customer service and support?

We haven't had to engage with technical support. 

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

I'm familiar with VMware SRM.

Not a lot of people in the market are aware of Zerto. They need to market it better.

However, Zerto is pretty simple and straightforward, compared to other options on the market.

Replacing the legacy solution has helped customers remove compatibility issues and reduce costs. 

How was the initial setup?

The deployment of the product is straightforward. We have, for example, more than 100 VMware ESX-site servers and there are two agents in terms of virtual machines that get deployed on all of them.

To deploy the solution, it only takes 30 minutes. You only need one or two resources to manage the implementation. The maintenance is minimal. Once it's set up, it's fine. 

What was our ROI?

Our customers have witnessed an ROI. 

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

The product is cost-competitive and less than other options. I do not have too much data on the exact costs, however. However, we are definitely saving costs when we compare Zerto to VMware. 

What other advice do I have?

My understanding is we have a partnership with Zerto. It provided free training to our employees and we have done multiple certifications. 

We did not use it for immutable data copies.

We don't use it for blocking unknown threats and attacks. We don't use it for security purposes. We have other security protection services for our customers, including firewalls and antivirus. We use Zerto only for disaster recovery.

I'd advise potential users to pay attention during the initial setup and watch what you are replicating from one side to another. After the setup, you will not have to put a lot of time in - as long as you pay attention during the initial phase. 

I'd rate the solution nine out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud
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. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
PeerSpot user
Computer Services Division Manager at a government with 51-200 employees
Real User
Simple and easy to understand with a clean interface
Pros and Cons
  • "The pricing and licensing are excellent. It's very straightforward."
  • "Zerto requires these thick provision walls for virtual machines that are always running."

What is our primary use case?

We primarily use the solution for disaster recovery.

How has it helped my organization?

It’s improved our organization via providing better RPOs and excellent uptime. 

What is most valuable?

The best aspects of the solution are the simplicity of use and the way that it handles the RPOs and the RTOs. I like that we’re able to dial into exactly what we want. They've been able to give us better RPOs than we ever imagined.

It has a very clean interface and is easy to understand. You don't really need a lot of technical knowledge to understand what you're doing.

I don't know if it's the compression or what, however, we get really good RPOs. The system already knows what we're trying to do. It’ll estimate and give us better RPOs than what we've actually set.

We’ve improved our RPOs 100-fold.

Uptime is excellent. The last test fail-over recovery was within almost thirty seconds to a minute. It was very, very good, and I was very impressed. This is extremely vital. We have to maintain a lot of uptime. The data that we have is constantly being written and it is very vital that we stay up for public safety reasons. To be able to have something like this solution, that can fail over and fail back easily, makes us much more agile in the data center.

What needs improvement?

There are a few technical aspects that I didn't care much for. For example, we’ve made a transition to hyper-converged technology, which is moving more towards provisioning and being smaller and more agile. Zerto requires these thick provision walls for virtual machines that are always running. I know that they're temporary. However, they're constantly running and they eat up a lot more disk space than they need to. Maybe if there was a little more of a stronger relationship with VMware and how they operate, some of that could be better managed.

For how long have I used the solution?

I've been using the solution for three or four months.

What do I think about the scalability of the solution?

It's scalable. If we need more, we just ask for more. If we need less, we scale it down.

We're already looking at how we can leverage it on other sites. To do so, we simply just buy a few licenses, deploy a couple of VMs, and then it's off to the races.

The size of our current environment is about 40 terabytes of virtual machines that we are protecting.

How are customer service and support?

We've never had to contact technical support. 

How was the initial setup?

Our experience with the initial setup was easy. It took 15 minutes. 

What about the implementation team?

We leveraged a third party for deployment. The person we hired wasn't that technical, and only knew the basics. However, it was so easy we really didn't need him.

What was our ROI?

We're still waiting on the ROI. However, it will be very easy to calculate the minute we have a failover. 

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

The pricing and licensing are excellent. It's very straightforward. You license what you use. 

Which other solutions did I evaluate?

We also evaluated VMware's cyber recovery manager. We chose Zerto due to the fact VMware’s solution was very complicated, very difficult to use, and required a lot more effort to be able to set it up and make sure that it worked. There was a lot of debugging to make sure things were working properly. Whereas Zerto was almost effortless. I was able to implement Zerto within minutes. Without exaggerating, within ten minutes I already started replicating.

What other advice do I have?

The solution just works. It works in the background and it is very hands-off. Once you set it, it just goes. 

I'd rate the solution 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.
Flag as inappropriate
PeerSpot user
Sr Systems Engineer at a construction company with 5,001-10,000 employees
Real User
It provides quick insights into where your VMs are and whether they're replicating
Pros and Cons
  • "Zerto enables us to do sandboxing failovers. You can run tests on a production environment in a sandbox and spin up a copy of your actual production environment in a few hours. When you're done with it, you can click a couple of buttons, and it's all blown away. You don't need to worry about reverting changes or interfering with your on-prem production environments."
  • "I would like to see some improvements with APIs going into the cloud so that they can more natively orchestrate the migration point-to-point without special hands-on configuration. Azure does some of that natively by having an agent on the VM, but Zerto could improve on its APIs into Azure or Google so that spinning up works more natively in that environment. It would make things smoother."

What is our primary use case?

We use Zerto for disaster recovery as a service and site-to-site migrations. 

How has it helped my organization?

Zerto enables us to do sandboxing failovers. You can run tests on a production environment in a sandbox and spin up a copy of your actual production environment in a few hours. When you're done with it, you can click a couple of buttons, and it's all blown away. You don't need to worry about reverting changes or interfering with your on-prem production environments.

What is most valuable?

The most valuable feature is the overview Zerto gives you, providing quick insights into where your VMs are and whether they're replicating. It's an easy interface to work with. Configuring Zerto to failover in Azure is pretty simple. The biggest challenge is moving from on-prem to the cloud, but that's not an issue with Zerto. The problem is the difference in hypervisors.

What needs improvement?

I would like to see some improvements with APIs going into the cloud so that they can more natively orchestrate the migration point-to-point without special hands-on configuration. Azure does some of that natively by having an agent on the VM, but Zerto could improve on its APIs into Azure or Google so that spinning up works more natively in that environment. It would make things smoother. 

For how long have I used the solution?

I've been using Zerto for about a year now.

What do I think about the stability of the solution?

I haven't faced any stability issues. The only problems I've had have been self-inflicted, so it's pretty good.

What do I think about the scalability of the solution?

Zerto's scalability seems pretty robust. I've had a few larger VMs that have been a little troublesome in terms of the RTO, but they are also outside of best practices. There should be no issues with scalability if you're working within the defined parameters of what's acceptable.

How are customer service and support?

I rate Zerto support nine out of 10. I've used their support pretty extensively. I would say the majority of the experiences have been overwhelmingly positive. Their response times and issue resolutions are satisfactory.  

One thing I would change about Zerto support is the fact that you sometimes can't find the answer you need online. Sometimes, Zerto reaches out with an answer to that particular issue, and it's in a document that the customers can't access without going through support. It doesn't feel like that information should be limited to internal use. I should be able to find that online without going through a support channel. 

How would you rate customer service and support?

Positive

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

I've also used Azure's native Azure Site Recovery solution, and there are definitely some benefits to using Zerto, such as the fact that it works at a hypervisor host level over individual VMs with agents. The performance is probably a little better in most cases. 

Zerto is easier to use than ASR overall, but the setup is a little bit more involved. After the installation, the daily use is pretty simple compared to Azure. With Azure's native solution, there's a lot more that you must do repeatedly throughout the lifecycle of any virtual machine or system that you're trying to protect. Zerto is much simpler in that regard.

How was the initial setup?

The on-prem deployment is super easy and works well. Migrating from on-prem to the cloud involves a lot more steps and things you have to configure so that it can communicate into the cloud and build everything that it needs to. That takes more time. It probably requires twice as much time to deploy on the cloud. 

What was our ROI?

We see the biggest ROI from Zerto's real-time test environment. If we want to do a proof of concept on a hundred servers, we can spin them up within a few hours and have them ready to start testing stuff with real data to see how that might look if we were to deploy that into production. It's an excellent, accurate test environment that we don't need to maintain.

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

Zerto's pricing is competitive, given the benefits and ease of setting it up. It may seem more expensive upfront, but you're going to save that over the long term by spending less engineering time configuring, reconfiguring, etc.

What other advice do I have?

I rate Zerto nine 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
Systems Engineer at a manufacturing company with 1,001-5,000 employees
Real User
Top 20
Has a quick recovery time, is straightforward to use, and reduces the resources required to recover
Pros and Cons
  • "RPO time for the copied-off VMs appears to be quite short."
  • "It is crucial for Zerto to collaborate closely with VMware in order to promptly test updates."

What is our primary use case?

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

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using Zerto for six months.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

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

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.

How was the initial setup?

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.

What about the implementation team?

We implemented using a third party.

What other advice do I have?

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.

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
Architect at a comms service provider with 10,001+ employees
Real User
Top 20
Stable and scalable solution with a valuable live migration feature
Pros and Cons
  • "The most valuable feature of this solution is the live migration."
  • "This solution could be improved by being more cloud agnostic."

What is our primary use case?

Our main use case for this solution is disaster recovery, migration and app testing.

How has it helped my organization?

Zerto helped to reduce downtime. I worked a lot in a consulting capacity and experienced DR situations where XYZ was down or a data center was down. Using Zerto to get them back up and online was a lifesaver.

Zerto reduced the staff involved in data recovery. It's a tool that allows you to do a lot just with one person at the console.

What is most valuable?

The most valuable feature of this solution is the live migration. 

What needs improvement?

This solution could be improved by being more cloud agnostic. 

For how long have I used the solution?

I have been using this solution for eight years.

What do I think about the stability of the solution?

This is a very stable product. I've never heard anybody complain about its stability. I would say it's probably one of the best out there.

What do I think about the scalability of the solution?

This is a scalable solution. 

How are customer service and support?

The technical support for this solution is good and their staff are knowledgeable and able to assist quickly with resolutions. 

I would rate them a nine out of ten. 

How would you rate customer service and support?

Positive

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

I've used several other products including Site Recovery Manager. Zerto is the easiest to learn. There is much less of a learning curve. Other tools specific to VMware are now trying to emulate what Zerto has done to make processes easier. Zerto was a huge step in making things more simple to manage. The app works really well and integrates with VMware really well. 

How was the initial setup?

The initial setup is straightforward, especially if those setting it up understand the company's infrastructure. The problems are not directly related to Zerto itself. They're always related to how the infrastructure is set up or how the network itself is segmented and having certain people that have control or access and others that don't.

What was our ROI?

The return on investment is in the ease and functionality of the tool as opposed to actually a gain from using the tool.

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

There may be less expensive solutions on the market but with Zerto, you get what you pay for. A lot of people don't like to think about the price until it's already happened and then the price is too high because they would be losing either way. It's better to think about it and pay for it upfront than pay for it after the problem.

Which other solutions did I evaluate?

We previously used and considered Site Recovery Manager.

What other advice do I have?

I would rate this solution a nine out of ten. 


Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
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.