We changed our name from IT Central Station: Here's why
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.
Flag as inappropriate
Lee_Castillo
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.
Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
564,322 professionals have used our research since 2012.
Sr Director Security Operations at a tech services company with 10,001+ employees
Real User
We have been able to reduce our mean time to restoration quite significantly
Pros and Cons
  • "There are two things that are keeping us with the solution: 1. It does a very good job of keeping the data in sync at all times. 2. In the event of a failover or in the event of a contingency, we are able to retrieve the data very quickly without any issues."
  • "When we are trying to upgrade any virtual machines, we have to stop the virtual machines that have been replicated in Zerto and then upgrade or update to the virtual machines onsite. Instead of having to do it manually, there should be some way of automating that particular function."

What is our primary use case?

For all the most important applications, we are using Zerto as a hot site in case something were to go on with our on-prem data center-based applications. We can immediately resort to Zerto as a failover.

It's deployed for replication from our data center into the public cloud.

How has it helped my organization?

The most important thing is the mean time to restoration. When anything goes wrong, we should be able to rely on the failover data that is available, and we should be able to restore it as quickly as possible. We have been able to reduce that mean time to restore the data pretty significantly with Zerto. It's gone from a few hours to a few minutes.

What is most valuable?


There are two things that are keeping us with the solution:

  1. It does a very good job of keeping the data in sync at all times. 
  2. In the event of a failover or in the event of a contingency, we are able to retrieve the data very quickly without any issues.

Both of these points are valuable to us because we have application data and it means we keep the data in sync. It is very important for us to know exactly where we left off in the event of any disaster or contingency. We can always rely on, or resort to, the data that we have as a backup or a failover. Also, in the event of a contingency, or even for doing a mock contingency exercise, the speed of retrieval of data and the speed of getting back up and running — minimizing the downtime — is important. That's where the second feature comes into play.

What needs improvement?

There are two areas which I would recommend for improvement. One is when we are trying to upgrade any virtual machines, we have to stop the virtual machines that have been replicated in Zerto and then upgrade or update to the virtual machines onsite. Instead of having to do it manually, there should be some way of automating that particular function.

And when it comes to AWS failover, the documentation has a lot of scope for improvement. It's come a long way since we implemented it, from the scantiness of documentation that was available to do a failover into AWS or recover from AWS, but they could still do a much better job of providing more details, how-to's, tutorials, etc.

In terms of additional features that I would like to see included in the next releases, if they could provide us some kind of long-term storage option, that would be the best thing. Then it could be a storage and a failover solution combined into one.

For how long have I used the solution?

I have been using Zerto for two-and-a-half years.

What do I think about the stability of the solution?

It's a very stable solution.

What do I think about the scalability of the solution?

It scales very well, in terms of the data size and the number of sites that we want to add on. It has scaled very well, at least in the last two releases.

We have plans to increase usage, but as it is we are using it for about 75 percent of the data at this point. The balance of the data will come onboard by early next year.

We have about 25 people using Zerto, and they're mostly database and storage administrators, infrastructure people, and security people. 

How are customer service and technical support?

We have not used the technical support. One thing I can say is that they have a very friendly team of engineers. If you have a problem, they are at your beck and call. You can call them and get it resolved.

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

We were using another solution but I don't want to name it. The primary reason we switched was the ability to restore the. Our main goal was not only to have good replication of data, but to be able to restore the data as quickly as possible in the event of any contingency, whether planned or unplanned. 

From that standpoint, when we put Zerto against the existing product, what took us a few hours in that product took us a few minutes with Zerto. That was primarily the goal. Even though this product was a little more expensive than what we had prior to going with Zerto, we still went ahead with Zerto.

How was the initial setup?

The initial setup is very straightforward compared to a lot of others. The user interface is very simple and very intuitive. It goes one step at a time so you can logically follow through the steps to set it up. Whether it's a small site or a big site, it doesn't really matter.

Overall our deployment took about two weeks. We had a detailed project plan, as we always do with any new products or projects that we come up with.

It doesn't require any full-time staff to deploy and maintain the solution. Once you turn on the process, all that somebody needs to do is just monitor the schedule and see whether it's doing things the way it has been programmed.

What was our ROI?

We have absolutely seen return on our investment with Zerto. We do mock disaster recovery exercises and, in every such exercise since we've gone ahead with Zerto, we've been able to restore the data within a few minutes, very easily, without any business loss. That gives us the confidence to say that, even in the case of a real disaster, we should be able to restore the data.

Which other solutions did I evaluate?

We didn't evaluate any other options.

What other advice do I have?

Know your use case and then do a thorough proof of concept with your use case to see whether the solution works for your environment and your specific use case. Have a well-defined project plan and negotiate your way with the vendor.

The biggest lesson our organization has learned in using Zerto is that you should understand the product very well. You should understand what the product is capable of doing and leverage the options and features that are available in the product to the optimal extent. 

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.
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.
Flag as inappropriate
Cloud Hosting Operations Manager at a energy/utilities company with 10,001+ employees
Real User
Top 20
Reduced the backup recovery time of our main backup solution by several hours
Pros and Cons
  • "It reduced the backup recovery time of our main backup solution by several hours. It's reduced our time because before we have to build a system and restore the data, we install the application and restore the data that took us at least a good 24 hours to do that. And now it's really minutes for us to recover our backup solution."
  • "I'm not sure if it has throttling, meaning, what's going over the wire and how we can throttle that to reduce the amount of data that's going across the bandwidth. I can't remember if that's something that's in this product. It might be in the more recent version."

What is our primary use case?

We're replicating mainly some of our critical applications. One is our backup solution and then also some critical applications that we don't want to have to recover from tapes. That's been working very well for us. We actually just recently went through a DR rehearsal, where we ran a quick test and that ran for about a week and then completed that test. Then we were able to report that we were able to successfully recover our critical ERP system inside of the remote location successfully.

How has it helped my organization?

I don't have to worry about Zerto so much. It definitely continues working. We definitely have monitoring and everything like this to make sure things are working just fine, but I can't complain about it in any kind of way. I know we are a little behind on the version that we're using and we need to be on the latest and greatest. Right now we're on version 7.0.

It reduced the backup recovery time of our main backup solution by several hours. It's reduced our time because before we have to build a system and restore the data, we install the application and restore the data that took us at least a good 24 hours to do that. And now it's really minutes for us to recover our backup solution.

Zerto reduced the number of staff involved in data recovery or in a data recovery situation. It's now only one person while it was four previously. 

What is most valuable?

Comparing it to VMware SRM, Zerto is by far the best that I've used before for providing continuous data protection. 

Different parts of the company use VMware, we use Zerto, and then we saw where they were taking us. Ours really takes less than an hour just to do a quick failover. So it didn't make any sense to go with VMware one, so we ended up going with Zerto.

An employee had actually introduced us to it and we looked at it and wanted to try it. He was working for a bank that does quite a bit as far as doing disaster recovery. So if a bank used it then I would definitely use it. 

It is fairly easy. It's not as technical to get around it or anything like that.

It's a fairly easy tool to use. 

What needs improvement?

I know that Zerto can definitely improve some functionalities. I know some of the cloud pieces probably enable that. At the moment, it's doing what we want for us, and what it's doing for us right now is plenty. I can't say there's any improvement that I can see that needs to be done at the moment.

I'm not sure if it has throttling, meaning, what's going over the wire and how we can throttle that to reduce the amount of data that's going across the bandwidth. I can't remember if that's something that's in this product. It might be in the more recent version. 

For how long have I used the solution?

I have been using Zerto for three to four years. 

How are customer service and support?

Their support has been very good. I can't complain about them. 

How was the initial setup?

The initial deployment was straightforward for the admin that deployed it. It was not complicated. That person left and then another person came in who didn't know anything about this product and he picked it up fairly easily and he's able to manage it with ease.

He's a VMware administrator and he also maintains Zerto.

The deployment was done within a day.  

We don't have plans to increase usage because we are at the point where we're closing out. We're migrating some of our data centers and right now I know it's going to continue utilizing what we have. We haven't even hit the capacity of what we've got right now. Because I think the license we have is around 75 servers. We haven't even hit that. The only thing that's stopping us from right now is just that we need to increase the storage at the remote location to handle additional workloads. We have around 14 servers. 

What was our ROI?

We have seen ROI from Zerto. 

It has reduced downtime. It went from 24 hours to four minutes. It could even be seconds. It's fairly quick.

The dollar amount would equate to something in the millions. For an environment to be restored it means restoring our ERP systems. Then in that ERP in that system, it also has some manufacturing as well.

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

Pricing is fair. I don't see a big issue with the pricing for what we are trying to do. The things that we're replicating, if it were to go down it pays for it in itself there.

What other advice do I have?

We don't have any plans for long-term retention. They talked to us about it. But at the moment it's not in our forecast to look at that.

We don't have to failback because we just fail to a bubble, in other words. We don't want to bring down production because we're going through migration of our ERP. So we fail it over into this bubble. And that's what we're using. It is the test failover that we're using in that environment. Then in that environment, everything is isolated. That's how we use it today. We have never had to failback back to our main site.

I would rate it 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.
Flag as inappropriate
Juan  Saldana
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.

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.
Flag as inappropriate
Cloud Systems Engineer III at a computer software company with 1,001-5,000 employees
Real User
Reduces our backup admin time and helped with migration to our cloud provider
Pros and Cons
  • "The most valuable features are the single pane of glass and the reduction in time it takes for our systems engineering team to manage the platform."
  • "If I had to pick anything, it would be the documentation for upgrades. They need to make it easier for users to do upgrades without having to contact support, by providing better documentation for that."

What is our primary use case?

We utilize Zerto to backup our on-prem environment to our cloud provider. We've also used it for migrations from on-prem to our cloud provider.

Our deployment model is a hybrid. We're using on-prem and also replicating to Azure.

It is used in our production environment and also our lower environment, on-prem. It's like a DR, as we're backing it all up to our cloud provider. There are a handful of servers involved, replicating and backing up.

How has it helped my organization?

It saves us about eight to 10 hours a month in staff time.

Another benefit is just the peace of mind that everything is backed up. We rely on the backups, that they're good backups. It's not like we have to second-guess them.

It has also helped us with our migration to our cloud provider. It's made it easier, sped up the process, and taken a lot of the guesswork out of it.

The solution has reduced the number of staff involved in data recovery situations for our backup and recovery side by at least two people.

What is most valuable?

The most valuable features are 

  • the single pane of glass
  • the reduction in time it takes for our systems engineering team to manage the platform.

In addition, the RPOs and RTOs are great on it. It keeps up with things. The protection has been perfect so far when we have done our tests of spinning things up every six months or so. All our backups have come up with no issues at all. They just make great replication copies.

Zerto is also easy to use. That single pane of glass makes it very easy to check on the status of replicated items, and if there are any issues, to dig into them to fix them.

What needs improvement?

So far, it's been pretty good. I haven't had any issues. If I had to pick anything, it would be the documentation for upgrades. They need to make it easier for users to do upgrades without having to contact support, by providing better documentation for that.

For how long have I used the solution?

We have been using Zerto since 2018.

What do I think about the stability of the solution?

So far, it's been very stable. We don't have any issue with the services or the ZVAs. They just keep trucking. There have been no stability issues at.

What do I think about the scalability of the solution?

It's very easy to scale with it. As our environment has grown over the years, we've been able to add ZVAs to it, configure them, and they just fall right into the mix. Scaling is very easy.

How are customer service and technical support?

Technical support has been very helpful and quick to get back with responses. Ticket turnaround time has never taken more than an hour for me to receive a response back to a general question.

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

We used Avamar. The primary reason we switched to Zerto was the integration with cloud providers that it provides.

How was the initial setup?

I was not involved in the implementation, but I do remember that it was a pretty short implementation time. It included setting up the ZVA agents in our on-prem environment and connecting to our provider's cloud storage. The longest part of the implementation was getting the data, the initial seed or the backups, up there. But that's nothing against Zerto. Every environment will be different on that and has to get its initial copy up there. Since then, keeping copies up to date has been good. It meets up with RPOs and RTOs.

The initial implementation and getting everything set up took us about two and a half weeks. After that, to get everything that we are protecting into the cloud took us close to a month. We had to do it in stages, due to our work environment and our connections at the time. We didn't have the biggest connections, but that's more on our side, not Zerto's.

There are three people involved in maintaining Zerto for us. They're systems engineers.

Which other solutions did I evaluate?

Zerto is a lot easier to use than Avamar: easier management, easier setup, and the single pane of glass to watch over everything makes it better. I wouldn't say there's really a cost savings. They're probably comparable in price, but there were a lot more features and options with Zerto than in Avamar.

What other advice do I have?

If you want something that's easy to set up, with a single pane of glass, and that doesn't take a backup administrator to admin, Zerto is the way to go.

The only lesson we really learned, and this has been resolved now, is that when we initially started using Zerto there were some hiccups when it came to Linux servers, hiccups that we had to work through. Support was very helpful and resolved it for us, but it made it a little bit of a manual process. In the later releases of Zerto, they've resolved those issues. They just had to work out some kinks.

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.
System Engineer at American Medical Response
Real User
Top 20
Enables us to move an VM from our old environment to our new environment with minimal disruption
Pros and Cons
  • "The Move feature is the most valuable feature because it allows us to move the VM from our old environment to our new environment with minimal disruption."
  • "Some of the features need improvement. One would be, as you're creating a Move group or a VPG, as they call it, it should either autosave or have the ability so that you can save it for coming back to later because if the setup times out, you lose all your work. That would be a nice improvement to have."

What is our primary use case?

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

How has it helped my organization?

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

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

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

What is most valuable?

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

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

What needs improvement?

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

For how long have I used the solution?

We have been using Zerto for three months. 

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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

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

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

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

How are customer service and technical support?

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

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

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

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

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

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

How was the initial setup?

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

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

What was our ROI?

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

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

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

Which other solutions did I evaluate?

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

What other advice do I have?

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

I would rate Zerto a nine out of ten. 

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.