Coming October 25: PeerSpot Awards will be announced! Learn more
IT Specialist at a government with 10,001+ employees
Real User
Made our migration from Hyper-V to VMware, across multiple departments, much less painful
Pros and Cons
  • "There are several valuable features because of the way we use it. The backup and restore features are definitely indispensable."
  • "There are certain things about the user interface that could be a little bit more user-friendly."

What is our primary use case?

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

How has it helped my organization?

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

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

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

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

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

What is most valuable?

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

What needs improvement?

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

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

For how long have I used the solution?

I have been using Zerto for three years.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

How are customer service and support?

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

How would you rate customer service and support?

Positive

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

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

How was the initial setup?

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

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

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

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

Which other solutions did I evaluate?

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

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

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

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

What other advice do I have?

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

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Lead Infrastructure Team at a government with 10,001+ employees
Real User
Reasonable price, great support, and helpful for keeping our website up and running without interruption
Pros and Cons
  • "The recovery was pretty seamless. It took about a minute for it to kick over when we did our testing. So, it wasn't a long downtime."
  • "When it comes to a solution, one of the things the management wants is to standardize platforms. That's why when Rubrik came out with their solution, they wanted to look at it. For instance, if you have multiple technologies, you're going to need admins to manage all those different ones. I would like Zerto to be something that fits all our needs, including the backup that Rubrik provides, but I understand that not all solutions can be that way."

What is our primary use case?

It is mainly for disaster recovery of our public-facing website.

I oversee the infrastructure team. I'm the lead for the infrastructure. It is not one of the technologies that I've primarily managed. As an infrastructure lead, I have my hands on every project, and it is hard for me to just focus on one. Especially because it is more of a disaster-recovery type solution for us, as long as replication is going fine and there are no issues, we don't really go in and play with it much.

How has it helped my organization?

It does what it claims to do. I can't say whether it improves anything. It is just the fact that we want to make sure our public-facing website is up 24/7, and Zerto gives us the capability of doing that.

It hasn't reduced downtime because we haven't experienced any downtime yet. We've done annual testing to make sure that it is working properly. So far, so good.

What is most valuable?

The replication is valuable. We have two data centers, and it is replicating from our main data center to another data center. In the event that there is an issue with the first one, it just goes over, and we have the website up and running. It does an automatic build. It keeps our website up and running without interruption. It is constantly replicating. It has the most up-to-date information, at least until the main one goes down, and then it automatically brings up the other one. It is already pre-configured with the network and everything else. So, the website is up and running in seconds.

The recovery was pretty seamless. It took about a minute for it to kick over when we did our testing. So, it wasn't a long downtime.

What needs improvement?

Zerto is more of a set-and-forget-it type of solution. As long as the replication is continuous and there are no issues, I don't touch Zerto. We don't have a lot of workload that needs to be up. We just have our web server and our applications here. Those are two main servers that we get up and running in a disaster-recovery type situation. I can't give any area of improvement from a real-world experience because we haven't had that issue, but from testing, Zerto has been working great. 

It is not something that goes beyond what our use case is for. When it comes to a solution, one of the things the management wants is to standardize platforms. That's why when Rubrik came out with their solution, they wanted to look at it. For instance, if you have multiple technologies, you're going to need admins to manage all those different ones. I would like Zerto to be something that fits all our needs, including the backup that Rubrik provides, but I understand that not all solutions can be that way. When I started working here, my predecessor who was managing Zerto had no documentation. So, I had to take over. No one else knew how to manage Zerto. So, there is just that type of learning process. That's why management wants to standardize on one solution so that it is easier to cross-train, but that's not Zerto's part. It just happens to be our environment and our management style. Zerto as a solution has been great for us.

For how long have I used the solution?

I've been using it for about three years.

What do I think about the stability of the solution?

It has been stable for us. We had networking issues that caused the replication to break, but once we had that resolved, replication was seamless again. The
networking issues were on our side.

What do I think about the scalability of the solution?

I don't have much input for its scalability because we only have a maximum of three servers that we need Zerto to bring up and get running as soon as possible, in the event that the main data center goes down.

How are customer service and support?

It has been great. I've only requested support twice. The support engineer that worked with me has been great. I believe it was for the upgrade process, and he reached out to me and informed me that there was a new version that fixed a lot of the bugs from the previous version. He worked with me to get both data centers up to the latest version. I would rate them a 10 out of 10.

How would you rate customer service and support?

Positive

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

I haven't used any other one. Rubrik just happens to be coming out with a similar solution, and because we use Rubrik, management wants us to take a look at it and do a comparison between the two.

How was the initial setup?

Aside from working with the network team to get all the networking pieces configured, it was pretty straightforward. Installing the agents on the servers and doing the initial replication took the longest time because we have close to a terabyte of data that has to be replicated from one data center to another, but other than that, it was pretty seamless.

What was our ROI?

It gives us peace of mind. It hasn't happened yet, but it does happen. Based on our annual testing, we are pretty much happy with what Zerto has done or can do.

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

Zerto is pretty reasonable. I haven't checked to see how much Rubrik is going to quote us for their solution. At least for us, the price doesn't play a big factor in the decision-making because it is a pretty small deployment for our use case.

Which other solutions did I evaluate?

We're currently evaluating Rubrik because we use that as our primary backup solution, and they just came out with a technology that's similar to Zerto. My managers, the executives, and I are in discussion on possibly looking at their solution and comparing it to Zerto to see which is the right fit for us.

In terms of ease of use, I haven't played with the Rubrik one yet just because they just announced it, but Zerto is pretty straightforward. I went in, and I did all the configuration myself within about 30, 40 minutes.

What other advice do I have?

It is a great solution for what it does, but every company and every department has its own use cases. It is just a matter of evaluating different solutions that are available and picking the right one for your environment. For us, Zerto happens to be the right one.

I would rate it a 9 out of 10 just because it fits our needs for the solution and the environment we're in.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Buyer's Guide
Zerto
September 2022
Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: September 2022.
634,775 professionals have used our research since 2012.
Solutions Architect / Building Supervisor at a university with 5,001-10,000 employees
Real User
Continuous and reliable data protection, saves us time, and the support is helpful
Pros and Cons
  • "It is convenient to use because the API allows for seamless integration when performing our day-to-day operations."
  • "Some of the integrations with our internal tools, in particular, company-specific ones, do not work. In cases like this, we have to ask for additional support."

What is our primary use case?

We primarily use Zerto for backing up our databases.

We are heavily invested in database technology. We use SQL databases such as PostgreSQL and MS SQL, and we are also functional with NoSQL databases. Our use cases are majorly relying on databases for financial vendors and most of the time, we have to perform day-to-day operations with respect to finance and accounting.

We have been using the data retention functionality for a long time and whenever there is a failure and the system goes down, we recover the data from that particular snapshot in time.

We also require security, as it is one of the major concerns. Ultimately, we align these two things together.

We are deployed in AWS, although we are also deploying in GCP and plan to do so with Azure as well.

How has it helped my organization?

Zerto provides us with continuous data protection that is reliable. It is convenient to use because the API allows for seamless integration when performing our day-to-day operations.

Currently, we do not have any long-term data retention activities, and it is not one of our core operations. However, in the past, we did have several such use cases.

Using this solution saves us time because we have been capturing the volumes and snapshots, are we able to perform operations on the Delta. This is an important benefit to us because we are able to deploy everything into production, then continue to get the backups and snapshots from there. 

Another time-effective benefit is that once we are fully backed up, we are able to perform Lambda functions on our use cases. This saves us a lot of time.

In some instances, Zerto has saved us time and on the number of people involved during failback. The number of people that are involved depends upon how critical the failure is. Any time there is a failure, we have to work from the most recent backups. For example, if the incident happens at 9:00 PM and there is a snapshot that was taken at 8:00 PM, there is one hour of work to make up for. This is much easier and quicker than having to look back at the logs for the entire day.

On a day-to-day basis, using Zerto saves us approximately 20% to 30% in terms of time. Overall, considering both our test and production environments, using Zerto benefits us with an approximate time savings of 60%.

We are using Zerto for DR in the cloud, and it has saved us money over using a physical data center. In a cloud-based deployment, the cost is quite a bit less compared to a physical environment. Also, because the cloud is a pay-as-you-go model, and you don't need the service all of the time, the paid resources are not wasted. I estimate that we save thousands of dollars per year in operations costs.

With our backups fully in place, in the cloud, Zerto has helped us reduce downtime. 

What is most valuable?

The most valuable features for me are the fast performance and seamless integration. The performance is one of the main features and the integration has helped me a lot.

When we have a system that is being fully replicated, we also get snapshots. Then, we perform our activities on the snapshots only, which reside on the cloud-based volumes. This means that our production environment is not affected.

We have low latency in production because most of the things we do are on the cloud.  When we have the backup, we just start to perform the data operations and with the help of Zerto, we can do this quite efficiently.

Zerto is quite easy to use. With the click of a button, I have been able to use it to do what I need. Furthermore, any end-user that I have worked with has easily been able to make use of its functionality.

What needs improvement?

Some of the integrations with our internal tools, in particular, company-specific ones, do not work. In cases like this, we have to ask for additional support. This is an area that has room for improvement.

If the API integration worked more efficiently then that would be an improvement.

For how long have I used the solution?

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

What do I think about the stability of the solution?

Zerto is a stable and reliable product. We have not experienced any anomalies in the tool. For all our use cases and workloads, we rely on it and have found that everything can be done easily.

What do I think about the scalability of the solution?

We have not had problems when we want to redeploy a number of things, so scalability has not been an issue.

We have between 30 and 40 users, including engineers, architects, and management. We are a growing and expanding company, and our workload increased from day to day. I expect that our usage of Zerto and other solutions will increase.

How are customer service and technical support?

We often reach out to contact technical support and it is good. We have a lot of use cases that we need support for because we don't always have a sufficient solution.

How was the initial setup?

The initial setup was straightforward, although we did have some problems. For example, there were instances where we could not integrate with our internal tools and we were not able to solve the problem. We looked at the FAQ and reached out to customer support to ask what the ideal solution would be.

Overall, it took between six and nine months to deploy.

What about the implementation team?

We deployed Zerto using our in-house team.

What was our ROI?

We have seen ROI in terms of time savings, as well as other points.

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

We subscribe to their annual license package and we have tier one support with them. There are no costs in addition to this.

Which other solutions did I evaluate?

We have evaluated other tools including Veeam and Veritas. There were several factors, including cost, that led us to proceed with Zerto.

What other advice do I have?

My advice for anybody who is implementing this product is to have things properly architected in advance. Otherwise, the implementation will be a hassle. Once the design is complete, if they need to change it then it will be time-consuming.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud

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

Amazon Web Services (AWS)
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
Systems Engineer Virtualization at a tech vendor with 5,001-10,000 employees
Real User
Reduced our downtime on some critical applications
Pros and Cons
  • "I prefer Zerto because it's a little more automated. VMware has more requirements... It's a little more click-and-go versus click-and-monitor..."
  • "Whenever we do a failover, there's a confirmation box that shows up later. It's a little hard to see sometimes... A popup to continue would be a little bit better because then you're not sitting and waiting for something and it's already there."

What is our primary use case?

I've used it for a temporary migration. We had to shut down a data center and we moved some database servers over to a disaster recovery site. We then did the maintenance at the data center and brought them back.

We're using it only for on-prem and we use it to replicate from our onsite data center to a co-location, but there is a fiber connection between the two, so it isn't an internet-based replication.

How has it helped my organization?

In that migration instance we had six terabytes of data that we needed to protect and bring online quickly. We had a replication going and we made the protection group switch and brought the systems back within less than 30 minutes. It reduced our downtime on some critical applications.

If we hadn't used Zerto, we would have had to vMotion them to the other side and that could have taken hours. That could also potentially have been unreliable because there's a timeout period when vMotion works. We used Zerto to be safe.

What is most valuable?

It is pretty simple to use.

What needs improvement?

Whenever we do a failover, there's a confirmation box that shows up later. It's a little hard to see sometimes. We'll do the failover and some preparation activities and then there's a checkbox you need to check to continue and sometimes it's small, in the corner, depending on which screen you're using. A popup to continue would be a little bit better because then you're not sitting and waiting for something and it's already there.

We also had an issue with a misnamed network. They should make that a little more apparent when it's not available on the destination side. We were able to go all the way through with it, but when we did the recovery, it wasn't available. A pre-check to say, "Hey, it's not available. What network do you want to use?" would be helpful.

For how long have I used the solution?

I have been using Zerto for about a month because I'm new with my current company.

What do I think about the stability of the solution?

The stability has been alright. We have failed over quite a number of machines.

We did have an issue with one failover. It didn't fail over completely. You really don't want to have to contact support in those situations, but we had to. It could have been an issue on our side as opposed to something being wrong with the configuration. I don't know what happened, but they got it working.

How are customer service and support?

We had to call support during that migration because one of the settings wasn't correct. I don't know exactly what went wrong, but we had to create a ticket. Zerto got back to us within an hour, so we were really impressed with the support from them. It was really good. They got us taken care of pretty fast and we were back online during the process, within an hour. They were quick to respond after we submitted the ticket and then they got it fixed. There's not really much more they could have done in that situation.

How would you rate customer service and support?

Positive

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

We use VMware-native as well as Zerto. It's all circumstantial, based on sites. Some sites ended up getting an SRM license, so we have kept them instead of wasting licenses. And some sites use Zerto. Maybe down the road we'll pick one of the products, but for now, we use both.

How was the initial setup?

Zerto was already there when I stepped into the picture. I helped initiate some of the disaster recovery processes. Based on what I saw from the outside, it was easy because it was ready for that situation quickly. It was ready in a business day or less, aside from the replication aspect or the data sync from when you first set up the jobs. But the basic setup to get things going was ready within less than a business day.

What was our ROI?

I would think we have seen return on the investment in Zerto because we use it a decent amount of the time. We have reduced the downtime within the last month because of it as well.

Which other solutions did I evaluate?

We've used SRM from VMware. Personally, I prefer Zerto because it's a little more automated. VMware has more requirements and VMware tools get us stuck sometimes. If the VMware tools aren't working on a virtual machine, it won't replicate over as quickly or start up as quickly because it's waiting for that service. You have to do custom settings to avoid that. Zerto doesn't have that requirement. It's a little more click-and-go versus click-and-monitor and then trace back and see what went wrong.

Zerto is also probably faster because SRM waits for VMware tools to come up and say, "Hey, we're here." That's not a requirement that I know of, with Zerto. Maybe it is. I'm a newer user of the product.

What other advice do I have?

In terms of the number of staff involved in data recovery situations, Zerto hasn't really reduced that. My team generally handles those situations and it's the same number of people, regardless of which product we're using.

Zerto worked and did its job and it was easy to use. My team liked it, and the database administrators, who were the customers in that instance where we did the temporary migration, appreciated it.

I would rate it at eight out 10. Sometimes the interface can be a little tricky. If you're using a disaster recovery application, you're in a stressful situation already. Sometimes there are a lot of confirmations you have to go through just to start the Virtual Protection Group, and then it starts and you have to confirm again a few minutes later. You're stressed out. You're talking via chats with a bunch of people and there were times where that prompt was probably sitting there for minutes, which cost money.

More confirmations upfront and removing that second one later on in the process would be good, or a popup, instead of it being a small checkbox in the corner of the screen, is my recommendation.

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
Lee_Castillo - PeerSpot reviewer
Lead Information Security Engineer at Lumen
Real User
Top 20
Customer service stellar, reduces workloads, simplistic install and extremely easy to use
Pros and Cons
  • "The most valuable feature is how simple it is to implement and how quickly you can get up and running at the second site. The solution is also extremely easy to use, for example, You just log onto the console and you can do a test failover with a few clicks."
  • "In future releases, doing backups of the environment we need to be able to do hot backups of the database."

What is our primary use case?

We use the solution for two different data center sites. Inside the data centers we use VMware virtualization, NSX stretched VLANs and Dell servers. There are many servers, storage, virtualization, and a myriad of operating systems such as Red Hat and Windows Servers. 

We use Zerto to replicate our VMs from one site to the other, where we don't want to have to pay for two licenses of the same thing. We also do this to have high availability or to have the disaster recovery version of a piece of software. It is a benefit to be able to use Zerto to replicate that VM at the second site, and not have to power it on or anything. We know that it's always replicated on the other site. We currently use the solution for disaster recovery only but we are looking at longterm backup retention in the future.

How has it helped my organization?

I think it's perfect for providing continuous data protection for us, it is excellent. 

What is most valuable?

The most valuable feature is how simple it is to implement and how quickly you can get up and running at the second site. The solution is also extremely easy to use, for example, You just log onto the console and you can do a test failover with a few clicks. You can run a failover test for your auditors or your management. Afterwards, you can get a report on how easy it was to failover a specific application and the VMs associated with that application.

What needs improvement?

In future releases, doing backups of the environment we need to be able to do hot backups of the database. Granular based backups of the OS, versus taking a backup of the entire VMDK. Currently, I don't think we are able to do all that right now. Having an agent-based backup is a benefit because you can back up the OS files, and If you have an agent for the database, you can do a hot backup of the database and restore it. You then would have the ability to do an entire VMDK backup. I don't think that they have the ability to do a hot backup of a database itself via an agent or something similar.

For how long have I used the solution?

I have been using this solution for four years.

What do I think about the stability of the solution?

We have a couple hundred people using the solution within the organization. The solution is very stable, you set it up and you can forget it. When we have had issues where we lost the connectivity to a data center, we were easily able to bring up the VMs of a data center that was available using Zerto.

What do I think about the scalability of the solution?

It's very easy to add new hosts and the VRAs get to pull it out automatically. It's very easy to scale, at more sites. We are already increasing and adding more data centers that Zerto can protect for us. We are very pleased with it.

How are customer service and technical support?

The customer service is stellar. They always answer and they are very helpful. I have had very good relationships with the sales executives and sales engineers. If the team at the technical support cannot get an issue solved, then our pre-sales engineers will get on calls with us and help us sort through problems. They have been great.

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

We were using SRM, VMware's Site Recovery Manager before we switched to Zerto. We did the switch because we were impressed with the demo that was given to us. Additionally, SRM was very complicated and cumbersome.

How was the initial setup?

The setup was easy and demo replication was simple too. The initial process started by us building out the VMs of the virtual machines, as per their requirements. We deployed the manager, based on all the log information of the vCenter. You then select the data storage and it installs the VRA out on your environment. Once that is done, you put together the virtual protection groups and you build out your replication site, it is very easy.

What about the implementation team?

Our deployment took about a month to go through everything with three different staff members and for the maintenance, we have one technician. Make sure that we grouped everything properly together, based on the network and its functions, and how it should be brought back up etc.

What was our ROI?

I have saved days and even weeks of working time from using the solution. We are in the process right now of designing a new cloud infrastructure for one of our environments to utilize Zerto to replicate our VMs to our cloud. It is going to be a huge time saver, probably saving us a couple hundred thousand dollars. We've definitely seen some good return on investment with it. Our auditors are impressed by it. 

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

This solution is far less expensive than SRM and NetBackup. After the standard licencing cost there is an annual support contract, nothing that we were shocked about.

Which other solutions did I evaluate?

We have also used NetBackup but Zerto was much easier to set up.

What other advice do I have?

When trying to think of improvements I cannot think of anything to critiques at this time because it does behave so amazingly well. I've been involved with other SRM implementations and SRM is very complicated to put together and to configure, whereas Zerto is just so easy out of the box. Overall, the solution probably has saved us hundreds of thousands of dollars or maybe millions.

Some of the important lessons we have learned are you need to plan your DR carefully. That is the most important. Also, make sure that your applications are grouped together, be cognizant of the different virtual networks they go into. For example, If you have a web frontend DMZ that goes into one component, where the application and the database are in another place. You need to be careful on what networks you are sending them to at the replication site, be aware of that.

I highly recommend Zerto. I speak about the product all the time. I think that it is priceless what it does for us. 

I rate Zerto 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
Wendy B - PeerSpot reviewer
Wintel Administrator at a financial services firm with 5,001-10,000 employees
Real User
Cuts down the recovery time tremendously and improved the disaster recovery process
Pros and Cons
  • "We had a disaster recovery four or five years ago. I can't remember what happened, but I believe something crashed in our data center, like a power outage. We did a failover of our network using Zerto from production to disaster recovery. We successfully completed the failover process in three or four hours without issue. The data was current, and the application owners could access their data and continue working while the issue was resolved."
  • "I would like to see some graphical improvements in Zerto's interface. There's an option to export a list of all of our servers, but the information isn't presented the way we want. We want it in a specified sequence broken down by region, etc. We can't manipulate the data when we export it. Maybe they could change it to look more like an Excel sheet, and we can customize the graphics and data. We suggested these improvements to Zerto through their portal."

What is our primary use case?

We use Zerto for our disaster recovery procedure and testing to ensure our servers and virtual machines can failover from a production environment if there's a catastrophe. We have a disaster recovery test twice a year and use Zerto to recover the environment.

We have two environments for Zerto. One is for the US, and the other is for Europe. We updated one last week to version 9.0, and the other still uses version 8.5 but I will update that today or tomorrow.

How has it helped my organization?

Zerto cut down the recovery time tremendously and improved our disaster recovery process. It made it easier for us to recover if needed during a disaster. Zerto definitely reduced downtime. The other software we used had a lot of manual steps. It was efficient, but our recovery time was longer. I estimate that Zerto cut our recovery time by at least 70 percent.

We had a disaster recovery four or five years ago. I can't remember what happened, but I believe something crashed in our data center, like a power outage. We did a failover of our network using Zerto from production to disaster recovery. We successfully completed the failover process in three or four hours without issue. The data was current, and the application owners could access their data and continue working while the issue was resolved. 

Zerto also brings down our costs. If we don't meet our SLAs, the clients are not happy and we get billed or fined. Every minute an application is down is costly for us. However, I don't think it has reduced our staff. We have a dedicated team for disaster recovery. While it doesn't cut down on the number of team members, It makes our jobs a lot easier.

What is most valuable?

Near-synchronous replication is an extremely powerful feature because it's like a mirror environment with almost real-time replication. Everything in my production environment is mirrored in the Zerto environment. I want the two to be as close as possible. 

If you have a disaster, we don't want your data to lag too far behind. You don't want to be an hour or two days behind. When you recover an environment in Zerto, the data is current.

What needs improvement?

I would like to see some graphical improvements in Zerto's interface. There's an option to export a list of all of our servers, but the information isn't presented the way we want. We want it in a specified sequence broken down by region, etc. We can't manipulate the data when we export it. Maybe they could change it to look more like an Excel sheet, and we can customize the graphics and data. We suggested these improvements to Zerto through their portal.

For how long have I used the solution?

We've been using Zerto for six or seven years.

What do I think about the stability of the solution?

It's highly stable. We've had no issues. We haven't had an incident or any problems with Zerto being unavailable or maintenance that would cause an outage on our side. If anything is happening on Zerto's side, we're not affected and that is great.

What do I think about the scalability of the solution?

We haven't seen any limitations so far. Zerto is constantly upgrading its products. There are upgrades every five months or so. They're constantly tweaking and making the product better.

How are customer service and support?

I rate Zerto support nine out of ten. It's excellent overall. We've only had one issue in the past six or seven years. I think the person was maybe new to the team.

They prioritize calls based on severity. If the issue is affecting our environment and we can't get anything done, they'll escalate the ticket and help us immediately. If we just have general questions or a concern that isn't severe, they still respond quickly.

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

We previously used a site recovery manager from vCenter. It's effective, but it requires a lot of manual steps, especially when we deal with databases and so forth. Zerto is quicker, more efficient, and easier on the eyes. I'm a huge fan. 

We started using Zerto because vCenter required more steps to failover our environment. Zerto does all the steps that we would normally need to do manually, reducing our recovery time and procedure steps. Something that previously took 45 minutes takes Zerto 10 minutes.

The other solutions are still in place. We use vCenter and NetBackup for our legacy systems.

How was the initial setup?

Zerto is user-friendly. When I set this up six or seven years ago, I knew nothing about Zerto. It was relatively straightforward to go from the vCenter SRM to the Zerto environment. It's intuitive, so I can log onto Zerto and figure it out without having to take a class or official training. I can log on and navigate through the screens. If I get stuck, Zerto support is always available.

There were two of us who set it up. I'm in the US, and the other guy is in the Philippines. He initiated it, and I finished it. We completed it in one day, but I don't remember how many hours it took. We did a quick check the following day to ensure everything was in line.

What about the implementation team?

I contacted Zerto recently when I upgraded one of my environments to version 9. I had some general questions because a few of our VMs were not syncing. I was getting an error message because the recovery didn't progress, so I had to reach out to Zerto support. We actually figured that out on our own, but they pointed us in the right direction.

Which other solutions did I evaluate?

We tested one product for two or three months, but I can't think of the name of it. Zerto was easier for us to dive into and pick it up quickly. The leadership of the disaster recovery team made the final decision along with management. I don't know if cost played a factor, but Zerto was more efficient and easier to use. It was exactly what we needed.

What other advice do I have?

I rate Zerto 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.
Flag as inappropriate
PeerSpot user
Principle Systems Engineer at a government with 10,001+ employees
Real User
Flexible and easy to use, saves us time in database replication tasks, and a knowledgeable support team
Pros and Cons
  • "The most valuable feature is the point in time recovery. This allows us to recover at any point in time, up to a minute or so."
  • "I am a little bit worried about how Zerto will work with large volumes of data, such as replication for big data and very large files."

What is our primary use case?

We primarily use Zerto for replication and disaster recovery.

How has it helped my organization?

Zerto is good in terms of providing continuous data protection. We have databases that require point in time recovery capability and Zerto is very flexible in this regard, compared with some other solutions we use, such as Sybase Replication and Oracle Replication.

We do not yet use Zerto's long-term retention feature but we are planning to do so. Currently, we are exploring AWS Glacier for long-term retention, and we will see how Zerto can help with the process.

Using Zerto has helped to simplify our process. The DBS steps are very deeply involved in the case of Sybase replication. This means that it takes a lot of technical skill, time, and effort to manage Sybase replication. Compared with that, Zerto is very user-friendly.

When we need to failback or move workloads, Zerto decreases both the number of highly skilled people involved and the time it takes to complete. For example, to do a command-line restore and recovery of Sybase involves pages of steps and it requires a talented DBA. However, with Zerto, we can take care of that with an intern. Only one person is involved in the process for either case, but with Zerto, fewer skills and experience in recovery are needed.

Fortunately, we have not yet been the victim of a ransomware attack. However, I am confident that Zerto can help, should that situation occur. Similarly, since implementing Zerto, we have not had any downtime. That said, we have simulated different scenarios and our results were good.

What is most valuable?

The most valuable feature is the point in time recovery. This allows us to recover at any point in time, up to a minute or so.

Zerto is pretty user-friendly. Normally, data recovery involves a lot of DBS skills but with Zerto, it is point-and-click.

It is very important to us that Zerto provides both backup and disaster recovery in a single platform. Because of problems that people are facing, we needed to have recovery time objectives (RTO) and recovery point objectives (RPO) for the major cloud providers. This is the primary reason that we were looking for an up-to-date and current solution.

What needs improvement?

I am a little bit worried about how Zerto will work with large volumes of data, such as replication for big data and very large files. I have not tested it yet, so I can't say for sure whether it will choke or not.

The two large clouds that we use are AWS and Azure, and compatibility with these is always important for us.

For how long have I used the solution?

We have been using Zerto for approximately five years. We are using one version back from the current one.

What do I think about the stability of the solution?

In terms of stability, so far it looks okay but I am not sure how Zerto will react to volume loads. We haven't had a chance to test that because we don't have such a large environment.

What do I think about the scalability of the solution?

Scalability has been good but I have yet to see how large a file it can handle.

We have two DBAs using the product, and then we have some interns to help out.

Currently, it is running in a small network where it is backing up a couple of replicated environments. We may increase our usage in the future, as we are now just beginning to back up everything to AWS.

How are customer service and technical support?

Zerto's technical support team is pretty knowledgeable.

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

Prior to Zerto, we were using Sybase replication. When Sybase was acquired by SAP, we began having trouble when we needed technical support. The reason that we started looking for a replacement product is that we used to contact technical support in California when we needed help. However, we now have to call Germany first, only to have them redirect the call to California. SAP is a mess.

How was the initial setup?

I was involved in setting up the proof of concept, and I found that the initial setup was okay.

Once the PoC was complete, we went into small volume testing and then started using it after that. The deployment only took us a couple of hours.

What about the implementation team?

A couple of people from our organization handled the deployment, and we had some Zerto technical reps available to answer questions. The Zerto staff are pretty knowledgeable and they answered the questions well.

What was our ROI?

Compared to the licensing fees with Oracle and SAP, we see a return on investment.

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

Price-wise, Zerto is fairly reasonable and I can't complain about it when we compare it against Oracle and SAP licensing.

We have not tried using any features that are outside of the standard licensing fees.

Which other solutions did I evaluate?

We looked into Oracle GoldenGate but it is pretty expensive and cumbersome. Sybase is better than Oracle in terms of pricing, but Zerto is cheaper.

What other advice do I have?

We have not yet enabled data recovery in the cloud, but we are planning to use it. As of now, we haven't tested it. We always back things up but in terms of restoring and testing, we are behind.

My advice for anybody who is considering this product is that it is pretty user-friendly compared to Oracle and SAP. This is a good solution to start with. Once it has been implemented, I suggest moving to volume testing to see how well it handles large volumes of data.

We have never had a real situation where we were under the gun for the purpose of RTO and RPO recovery times. As such, I can't say for sure how it will behave in a real situation but we are satisfied with our tests.

I would rate this solution an eight 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
Oran Turner - PeerSpot reviewer
ISD Engineer at a financial services firm with 10,001+ employees
Real User
Powerful and reliable
Pros and Cons
  • "The most valuable feature is Zerto's ability to precopy data to a remote destination prior to the actual live migration period. That saves us a lot of time and has been very helpful. For example, if we had migrations occurring in waves over a period of several weeks with a VPG or VPG setup of approximately 50 VMs, that is multiple gigabytes of data, even terabytes in many cases. Having that data already copied on the evening of the migration saves considerable hours of time. It easily saves us four to six hours a night."
  • "The VPG model causes us a bit of concern. We are considering using Zerto to replace Site Recovery Manager. Site Recovery Manager is very easy when we have entire data scores being replicated. We don't have to make any decisions when it comes to groupings. It is all covered. If we move to Zerto, which we are considering, we will have to work much closer with the applications teams to develop the VPG configuration and determine how the VMs will be grouped. It will be a lot more overhead for us to go that route."

What is our primary use case?

We have previously used Zerto for data center migration projects. We have another data center migration coming up within the next year where we will be using Zerto as well.

How has it helped my organization?

We had pretty strict requirements when it came to cross data center migration capabilities. We wanted to ensure that no plugins or drivers were needed. We also wanted a simple deployment. Zerto very easily fit that bill.

What is most valuable?

The most valuable feature is Zerto's ability to synchronize data to the remote destination prior to the actual live migration date. This saves a massive amount of time during the actual migrations, and has been extremely beneficial. Having the data already synchronized on the evening of the migrations makes the final moves fast, easy, and seamless.

The interface is very easy to use. The product is easy to understand. We have had great success in using it for migrations. The benefit for us has primarily been the ease of use and stability of the product.

What needs improvement?

The VPG model has caused a bit of a concern. We are considering using Zerto to replace Site Recovery Manager. SRM is very easy when we have entire data stores being replicated. We don't have to make any decisions when it comes to groupings of VMs. If we move to Zerto, which we are considering, we will have to work closely with our applications teams to create VPGs and determine how the VMs will be grouped. This will probably be beneficial in the long term, but short term it will create more work for our team.

I spoke to a Zerto engineer who mentioned that we could do a VPG at the cluster level and a VPG at the datastore level. However, the one issue we've seen with VPGs is if the synchronization fails the entire VPG has to be recreated. Even though we can cover our environment at the cluster level or datastore level, that wouldn't be ideal. We really need a simpler solution for DR that will cover all of our VMs at once, instead of spending a considerable amount of time on VPG creation. 

For how long have I used the solution?

We have been using Zerto for about three years.

What do I think about the stability of the solution?

The stability is very good. All of the components that we set up for Zerto have been very stable. 

What do I think about the scalability of the solution?

Scalability has met our needs.

How are customer service and support?

Support has been excellent. We had a couple of issues initially with a VPG that wasn't functioning properly. Support was very quick to respond. They were able to assist us and resolve the issue very quickly. We have only had to call support one time.

How would you rate customer service and support?

Positive

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

We also use Site Recovery Manager. SRM does not have the same feature set for migrations that Zerto has.

How was the initial setup?

The product was easy to deploy. At the time, the only thing that we wanted to improve was to have an appliance for the ZVM, instead of a Windows server. I understand an appliance is available now. This will be very beneficial in the future.

The deployment was straightforward. We basically went through the documentation and then had a planning meeting with Zerto. Once we understood all of the requirements we were able to deploy very quickly with really no issues at all. We deployed Zerto in less than a week.

What about the implementation team?

We implemented the product ourselves. Zerto's expertise has always been very good.

What was our ROI?

Our migrations were all successful. We had no issues at any point during the project. That is what really sold us on Zerto.

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

The licensing costs are not cheap. It is an expensive product. However, you do get what you pay for.

Which other solutions did I evaluate?

There was really no other product that compared to Zerto. Zerto had exactly what we were looking for in a data center migration product. It had the ease of use and interface that we were looking for, that is, very simple and straightforward.

Zerto's ability to copy the data first, then synchronize just prior to the migrations made it much faster and easier for us to use than other solutions.

What other advice do I have?

Understand the VPG configuration. Understand that you will need to make some decisions as to how to cover your VMs. We eventually went with one VPG per VM for our migrations. This is because we discovered if the VPG has a problem, then you need start over and recreate the VPG. If you choose to cover 50 VMs on a VPG, and if that VPG fails for some reason, then you need to restart the whole process. So you need to consider your VPG design and how you are grouping your VMs.

We haven't used it yet for disaster recovery, but that is something that we will be looking at over the next year.

We have had great success with the product. It is one of the very few products that we have recently used that literally had no issues and worked exactly as designed. At every single point in our migration, it was successful. We had multiple migration waves that occurred over a period of a year and a half. We literally had no failures during that entire time, which is of rare in the industry and made us very happy. Now that we have another data center migration project coming up, we decided we were just going to go straight back to Zerto.

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
Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros sharing their opinions.
Updated: September 2022
Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros sharing their opinions.