The primary use case for Zerto in my company is to manage disaster recovery.
Infrastructure manager at a financial services firm with 201-500 employees
Ensures that we have the most up-to-date information in the case a disaster occurs
Pros and Cons
- "My organization has experienced the benefits of using the tool, which include the ability to test our disaster recovery quickly."
What is our primary use case?
How has it helped my organization?
My organization has experienced the benefits of using the tool, which include the ability to test our disaster recovery quickly.
What is most valuable?
The most valuable feature of the solution is the constant synchronization, ensuring that we have the most up-to-date information should a disaster occur and we need to handle failovers.
Zerto's near-synchronous replication is why we first acquired the product.
Zerto's overall effect on our RPOs is such that it improves them significantly, and it is the reason why we purchased the product. Rather than having to recover from backup, which is time-consuming, it is available instantly.
If I compare the speed of recovery with Zerto versus the speed of recovery with other disaster recovery solutions, Zerto is at least five times faster than other products.
What needs improvement?
It turns out that my organization has not been using all the capabilities of Zerto and we just found from the session, HPE Discover'24, that the things we were looking for already existed within Zerto. I don't have anything to ask for improvement in Zerto.
I don't want any additional features in the product as I would be busy employing the functionalities I recently found out are available in the solution.
Buyer's Guide
Zerto
November 2024
Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
824,145 professionals have used our research since 2012.
For how long have I used the solution?
I have been using Zerto for seven years.
What do I think about the stability of the solution?
The tool is very stable.
What do I think about the scalability of the solution?
The scalability is fine for our company. We are a relatively small organization, but it has done everything we needed.
How are customer service and support?
The solution's technical support has been solid and very good, and we hope it stays that way under HPE.
Which solution did I use previously and why did I switch?
In our company, we would recover from our backup software, so things depended on whatever backup tool was used at the time.
How was the initial setup?
When it comes to the product's initial setup phase, Zerto's support has been very strong and relatively straightforward.
What was our ROI?
I have experienced a return on investment from the use of Zerto. The exercises associated with disaster recovery are faster and we are able to save time now in our company.
What's my experience with pricing, setup cost, and licensing?
Fortunately, the tool's pricing and licensing are not a concern for me at the moment. Other teams handle it.
Which other solutions did I evaluate?
The evaluation of other solutions against Zerto was pretty quick. In our company, after we saw a Zerto in use, we couldn't find anything else like it in the market.
What other advice do I have?
I have used Zerto to protect VMs in our company's environment.
Considering that there is always someplace to go from where our company is currently, I rate the tool a nine out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Last updated: Jul 15, 2024
Flag as inappropriateIT System Engineer at PNFP
User-friendly, cost-effective, and saves a lot of time
Pros and Cons
- "It is very user-friendly. There is no wondering about what a feature does. It is easy to use."
- "If they already do not have it, they can have some APIs for the Horizon environment. Instead of having to use some scripts to get around, they can make it a lot more user-friendly for integration."
What is our primary use case?
We use Zerto for server migrations between data centers during the role swap that we do. We use it from a recovery standpoint as well.
We currently do not have disaster recovery to the cloud. We go between our data centers. That is what Zerto helps us accomplish.
How has it helped my organization?
Zerto works very well. We have not had any faults while using it. We are a financial institution, so we have to make sure the systems we have are available with very minimal downtime.
It has helped out a lot in man-hours. It has saved us a lot of overnight work. We can literally change our production servers in a matter of minutes to hours. Rather than having to do this gradually or a couple of weeks in advance and have several teams and business partners involved, we can literally do it live on the same day.
Zerto is probably one of the faster ones in terms of recovery. You can just go into the console, and because it is always replicating over to the other side, it takes minutes.
What is most valuable?
Being able to do our recovery and being able to migrate between data centers during the role swap is valuable just because of the amount of time it takes. It takes 55 hours or so. Right now, we are doing this in a VDI environment. We are going to experiment with it as a proof of concept because we have a thousand machines that we have to move and do all the assignments. Zerto would lessen that down by a few hours, and then we can use some scripts to do everything on the Horizon's side. We have not done it yet, but we are hoping to reduce it down to about 3 hours instead of 55 hours. We will also be able to manage our host better and be in a better recovery state. If the host happens to go down, we can quickly recover.
It is very user-friendly. There is no wondering about what a feature does. It is easy to use.
What needs improvement?
If they already do not have it, they can have some APIs for the Horizon environment. Instead of having to use some scripts to get around, they can make it a lot more user-friendly for integration.
For how long have I used the solution?
We have been using Zerto for two years.
What do I think about the stability of the solution?
It has been very stable. We have not had any issues while using it. When we need it to do its job, it is always dependable.
What do I think about the scalability of the solution?
It scales very quickly. We can set up a whole new environment in an hour. We can get the server setup and all the VMs that are required for it to function in an hour or two.
How are customer service and support?
I have not used their support. My peers had to use it. They seem very responsive and knowledgeable.
Which solution did I use previously and why did I switch?
The other DR tool that I have used is from Symantec. It was an old-school recovery tool. It was back in the day when it took a whole day to get things back up.
How was the initial setup?
It was deployed before I joined the company.
What's my experience with pricing, setup cost, and licensing?
Its price is fair. It is very cost-effective compared to the cost of the labor for your workers and associates.
Which other solutions did I evaluate?
We selected Zerto over others primarily for the ability to replicate and help with our role swap. It cuts the downtime of the production systems by a large volume. This way, we can meet the deadline and not have that much client impact. In the financial side of banking, you do not want bad performance.
What other advice do I have?
I would rate Zerto a nine out of ten. There is always room for improvement, but it definitely makes your life a lot easier.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Zerto
November 2024
Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
824,145 professionals have used our research since 2012.
Senior Manager IS Technical Services at a manufacturing company with 201-500 employees
Easy to use with great granularity and helpful support
Pros and Cons
- "I like the granularity of the checkpoints."
- "When we do failover and failback, it doesn't maintain some of the settings that it should and I don't really understand why that happens."
What is our primary use case?
We use the product solely for disaster recovery.
How has it helped my organization?
The solution has helped with zero data loss from a transactional perspective. We have about forty servers in there today and they all serve a core function for our business. With Zerto, it's a matter of just being able to achieve zero data loss in minutes in terms of recovery time. That's amazing, and it really enables our business from a disaster recovery perspective.
The key benefit for us, and why we transitioned to Zerto years ago was really the recovery time. We went from hours to days on some of these applications, to minutes.
What is most valuable?
I like the granularity of the checkpoints. That's been extremely beneficial for us in testing. The near synchronous replication of Zerto is great. Knowing that it's within seconds or minutes allows us to achieve our goals from an RPO perspective.
I like the live failovers.
It's also a very easy-to-use product and very easy to administer from just a time perspective.
We're able to stand up our DR site within an hour if we need to.
We've been able to use it to do kind VM migrations from site to site in the past. Just it doing it behind the scenes allowed us to dramatically reduce any downtime for private cloud to a private cloud or even on-premise to private cloud migrations.
When handling migrations, it's fairly intuitive. There's a progress bar with percentages. Sometimes the timing fluctuates based on bandwidth. However, it's going completely in the background. It doesn't interfere with anything. When you are live, you can cut over with minimal downtime.
It's improved our RTOs. It's dramatically improved RTOs compared to what we had before.
We've had multiple unplanned failovers and the solution worked as expected. It's probably saved us 24 hours per instance.
The product has reduced the amount of staff involved in data recovery situations. Before the solution, we had two or three different mechanisms for different types of systems in different applications. Now it's just one click, one interface, and one administrator.
What needs improvement?
When we do failover and failback, it doesn't maintain some of the settings that it should and I don't really understand why that happens. Quite regularly, anytime we do a failover or a fallback, we have to confirm all the settings for each VM. That takes a little bit of time. There is some power shell for that, so we've been able to automate that or at least optimize that. That said, that's my only complaint. Maybe that's a VMware limitation. I'm not sure.
For how long have I used the solution?
We've been a customer of Zerto for several years. We started using it around 2017 or 2018.
What do I think about the stability of the solution?
The stability is good. Of course, from a maintenance perspective, sometimes with the failover, we have to re-sync or set up the settings again for whatever reason. I'm not sure if that is a limitation of the product or a limitation of VMware.
What do I think about the scalability of the solution?
We have six or seven users that use the solution, and typically just two or three administrators.
We've scaled in that we have increased our VM count or VPG count. However, if we had thousands of VMs, I'd question the RTO or RPO capabilities at that point. However, ours is fairly small, under 40 VMs, and it has worked well for us.
How are customer service and support?
Technical support has been great. In our last DR failover, we needed to put in an urgent ticket and we got a very prompt response on that. Based on my interactions with them, by far they have the best support.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We did use other solutions before, however, they were not as comprehensive as Zerto. We moved to Zerto so we could get our RTO and RPO down to minutes. Just being able to do everything with one administrator makes it much easier than before since we were doing some things from backups.
From a desk disaster recovery perspective, Zerto has replaced all legacy backups. From an administration and time perspective, we're definitely seeing some savings there.
How was the initial setup?
The initial deployment was not very straightforward. We were able to deploy in a matter of hours. The foundational aspects of Zerto are pretty easy, however, managing VRAs and getting the replication going can be a bit more work.
For the initial deployment, we only needed a single administrator.
The solution definitely requires maintenance, just to keep everything up to date. However, it's very intuitive and everything happens very quickly, based on how many VRAs you have. We have three administrators capable of managing Zerto as needed.
We have three sites, either on private cloud or on-premises. They are all VMware-based.
What about the implementation team?
Initially, a consultant assisted us with the base installation.
What was our ROI?
We have not calculated the ROI of the solution.
What's my experience with pricing, setup cost, and licensing?
I was a little disappointed this year with the pricing, especially being a legacy customer of Zerto.
They changed the licensing structure as a result of the HP acquisition. We had a significant increase that was not very well communicated to us and wasn't planned for us and it hit us pretty hard. From a budgeting standpoint, we only got notified a couple of months before, however, we were already in our calendar year. We couldn't plan for it properly due to the timing. It was frustrating for us. The costs were up significantly for us this year. That is definitely something we will be mindful of and keep an eye on going forward. We may need to find an alternative if the costs keep increasing.
Which other solutions did I evaluate?
We did explore other solutions, such as VMware and other competitors. However, the ease of use and ease of implementation were good selling points and became a key deciding factor for us.
What other advice do I have?
We have not used the immutable data copies as of yet.
In terms of dealing with threats or attacks, I've read a lot of the white papers, however, we haven't really had to have a need or a use case for that at this point. We're aware of that functionality, however, we haven't had a need to really utilize that, thankfully.
It took us a while to realize the benefits of the product. The initial phase for us was to cover about twenty different servers, which had interdependencies within the application. It was quite difficult. It took us about a year and a half to fully utilize our application or our initial phase of productivity. That said, that wasn't a Zerto limitation. That was the fact that we were changing IP addresses between our sites, so it was more of an application configuration delay. Zerto was ready to go on day one, basically.
We don't use Zerto to support disaster recovery on AWS. We're strictly on-premises hypervisors. We use virtual machines.
We haven't used Zerto's data recovery testing functionality.
I'd advise new users to utilize the failover testing. You really have to make sure the application functions. Within our use case, for example, we have very interdependent applications. Each piece requires lots of communication, lots of databases, lots of other application transactions that are interdependent, and lots of integrations within our application. Utilizing the failover testing was critical for us.
I'd rate the solution eight out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
IT Infrastructure Specialist at a financial services firm with 501-1,000 employees
Helped our organization by merging many different technologies into one, including desktop virtualization and replication
Pros and Cons
- "The most valuable tool is the dashboard, which allows us to immediately check the DLP status, replication data, and all other data needed to have cleaner and immediate control of the situation."
- "The technical support has room for improvement."
What is our primary use case?
Currently, we use Zerto to replicate our production visual systems at our disaster recovery site in Germany. This allows us to easily meet our RTO and RPO.
How has it helped my organization?
Zerto is easy to use. Zerto is the leading disaster recovery solution.
Zerto's synchronous replication is important for our organization.
Zerto has helped our organization by merging many different technologies into one, including desktop virtualization and replication. Previously, we used to hire other providers for these services, but now we have everything in one system, saving us around 30 percent. For example, we used to have to keep a copy of our data on Veeam Backup, but now we can store it all in Zerto. This saved us time and money, and it has also made our IT infrastructure more reliable.
With Zerto, we are meeting our RPO better. Previously, it took us 20 minutes and now it is five seconds.
With Zerto, we have the best RTO.
In our simulations, we observed a reduction in downtime when using Zerto.
Our recovery time with Zerto is excellent in data recovery situations, such as those caused by ransomware. We can save around five hours compared to other solutions.
Zerto reduced the number of people involved in our data recovery by 30 percent.
What is most valuable?
The most valuable tool is the dashboard, which allows us to immediately check the DLP status, replication data, and all other data needed to have cleaner and immediate control of the situation.
What needs improvement?
File management can be improved. Zimbra is the only platform that allows for file replication.
The technical support has room for improvement.
For how long have I used the solution?
I have been using Zerto for five years.
What do I think about the stability of the solution?
Zerto is a stable solution.
What do I think about the scalability of the solution?
Zerto is scalable. We have around 200 users.
How are customer service and support?
The technical support is average. We have had some cases where we were not as comfortable with the outcomes as we were with other solutions.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
We previously used a custom solution, but we switched to Zerto to unify our systems and improve visibility.
How was the initial setup?
The initial setup was simple. We were able to deploy one FPE every two weeks. One person was involved in the deployment.
What about the implementation team?
The implementation was completed in-house.
What was our ROI?
We have seen a return on investment with Zerto, which saved us 30 percent of our costs and improved our disaster recovery time.
What's my experience with pricing, setup cost, and licensing?
The price is reasonable.
Which other solutions did I evaluate?
We did not evaluate other solutions because we were confident that Zerto was the best, as indicated by the Gartner chart.
What other advice do I have?
I give Zerto an eight out of ten.
Zerto is deployed to replicate our on-premises and virtual infrastructure data between our two offices in Germany and Italy.
Zerto requires around two hours per month of maintenance.
I recommend that new users take advantage of Zerto's flexible license program to buy one or two licenses and try them out before fully committing.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
IT Analyst at a wholesaler/distributor with 5,001-10,000 employees
We have seen significant reduction in RPOs and are now able to position our DR in the cloud
Pros and Cons
- "The near-synchronous replication is one of the primary reasons we're using Zerto because we have recovery intervals of sub-five seconds. On a scale of 10, where 10 is "very important", this feature is a 10."
- "Zerto's connectivity with automation platforms could be improved. For example, vCenter can use a VMware-developed tool called Site Recovery Manager. That can be integrated with automation platforms such as Terraform, Ansible, Chef, or Puppet, to perform automated, self-sufficient recoveries to essentially avoid any downtime. To my knowledge, Zerto does not have integration with those platforms."
What is our primary use case?
Our biggest use case is real-time replication to a secondary site in case of the need for a disaster failover. We also use it for file-level protection and restore, but the main purpose is to help add another layer of protection in the event of a disaster.
How has it helped my organization?
The biggest improvement we have seen is that Zerto has taken our anticipated recovery time from between hours and days down to seconds or a minute. Zerto has also helped us to protect VMs, and the effect on our RPOs has been incredible. Pre-Zerto, it was days if not weeks. Now it's six seconds. I don't even know if you could compare it to the RPO of our old solution. It's 100x. If we were to recover using our old system, we would lose between a day and a week's worth of data. With this, we lose virtually none.
And in terms of our RTO, recovering and validating the system has gone from between hours and days, to now happening in a matter of 30 minutes to a few hours. It has helped reduce downtime by days. Similarly, our DR testing has gone from being a multi-day process to a multi-hour process, and we use almost all of that time we save for bolstering value in other projects.
As for the number of staff involved in our backup and DR management operations, Zerto has helped us decrease it.
It has also allowed us to locate our DR in the cloud. We currently use Azure, and this ability is incredibly important as it has enabled us to reposition our resources in an environment that is separate from our main environment.
What is most valuable?
The most valuable features for us are the analytics and reporting. Being able to see a snapshot of our environment, and knowing where we stand in our recovery atmosphere using Zerto, are really valuable aspects.
The near-synchronous replication is one of the primary reasons we're using Zerto because we have recovery intervals of sub-five seconds. On a scale of 10, where 10 is "very important", this feature is a 10.
We also use Zerto for immutable data copies. We have two recovery locations and both of them are immutable, both for short-term and long-term recovery. Using this component has essentially enabled implementation of the 3-2-1 rule for us. Zerto has been pivotal in that process. Before that, the process hadn't changed in about a decade and a half. This enabled us to take a leap into the 21st century in that facet.
What needs improvement?
Zerto's connectivity with automation platforms could be improved. For example, vCenter can use a VMware-developed tool called Site Recovery Manager. That can be integrated with automation platforms such as Terraform, Ansible, Chef, or Puppet, to perform automated, self-sufficient recoveries to essentially avoid any downtime. To my knowledge, Zerto does not have integration with those platforms. Zerto does have an API, but a lot of those automation platforms have prebuilt runbooks to enable that process, whereas Zerto does not.
For how long have I used the solution?
I have been using Zerto for about five years.
What do I think about the stability of the solution?
It's incredibly stable, to the point that we don't have to second-guess whether it is functioning properly.
What do I think about the scalability of the solution?
Its scalability is infinite. We have yet to run into an issue of resource allocation or scalability.
How are customer service and support?
Their support is very good. Debatably, it's the best support we have seen out of all of our vendors.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
One of our previous solutions was VMware Site Recovery Manager. We switched because we have some servers that have a lot of transactions and we weren't able to afford to lose even an hour's worth of data. Zerto takes that potential data loss down to seconds.
And Zerto is much easier to use.
How was the initial setup?
Our deployment is both on-prem and, for replication, in Azure. The initial setup was straightforward. There was a learning curve in transitioning from our old environment, but it didn't take very long to learn.
It took us about a month to fully deploy.
Outside of updates, it doesn't require any maintenance.
What about the implementation team?
We did it in-house with support from Zerto when needed. On our side there were two or three people involved, but it was primarily done by me.
What's my experience with pricing, setup cost, and licensing?
It's expensive, for sure, but for us, it comes down to the fact that we do not replicate our entire environment using Zerto. We replicate the mission-critical servers and services, so the yearly cost of Zerto is heavily outweighed by the potential cost of an outage. It's expensive but worth it.
Which other solutions did I evaluate?
We very briefly looked at solutions such as Veeam and the option of continuing to use VMware SRM. The biggest difference was the de-snapshotting of the environment into journals with extremely low RPOs, versus scheduling a snap at a certain time.
What other advice do I have?
Overall, Zerto is pricey and it fulfills a very specific need, but it is incredibly worth the investment if uptime and recoverability are priorities.
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.
Lead Infrastructure Team at a government with 10,001+ employees
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.
SVP of Technology / Head of Information Technology at Barkley Inc.
Has significantly reduced our organization's RPO and RTO
Pros and Cons
- "Zerto has helped reduce our organization's DR testing to seconds to minutes. We have been able to save probably close to 200 hours a year."
- "If something happens, and we are out and about, I would like to be able to interface with it on our mobile phones. That would be great."
What is our primary use case?
Our use cases are disaster recovery and long-term retention against ransomware.
How has it helped my organization?
Zerto was part of our technology transformation initiative about five years ago, not only to protect our customers' intellectual property that we create for them, but also to protect our organization as a whole.
In a way, it has reduced the number of staff involved in a data recovery situation since we are contracted with insurance companies to help us recover. This solution allows us to be more self-sufficient, using our existing staff to recover.
What is most valuable?
Zerto has helped reduce our organization's DR testing to seconds to minutes. We have been able to save probably close to 200 hours a year.
What needs improvement?
If something happens, and we are out and about, I would like to be able to interface with it on our mobile phones. That would be great.
For how long have I used the solution?
I have been using it for about five years.
How are customer service and support?
Their technical support is really good. They do quarterly tests to make sure everything is working and spot on. Our Zerto engineer is local, so we work with him quite often just to make sure everything is working.
I would rate the technical support as 11 out of 10.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
It replaced Veeam. Zerto is a lot easier.
Prior to Zerto, when we were looking at our traditional disaster recovery, we were looking at 30 days plus.
What was our ROI?
We have been able to reduce our RPO and RTO to a matter of seconds to minutes versus what our technology committee established as our metrics, which was 30 minutes versus a few days.
What other advice do I have?
Knock on wood, we have never had downtime. However, it has given us better peace of mind.
I would rate Zerto as 11 out of 10.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Manager, Technical Services at a logistics company with 5,001-10,000 employees
Simple to set up and use, and offers continuous data protection with a five-second interval
Pros and Cons
- "This product is impressively easy to use. It's dummy-proof, once it's set up."
- "The long-term recovery is a little bit weak in its granularity."
What is our primary use case?
We use Zerto for real-time replication of our systems, company-wide. The main reason is disaster recovery failover.
How has it helped my organization?
We use the long-term retention functionality, although it is not deployed system-wide. We have a lot of critical systems backed up, such as our file servers. We utilize it to hold things for up to a year and we send our long-term retention to ExaGrid appliances.
When we need to failback or move workloads, this solution has decreased the time it takes and the number of people involved. The entire process is, realistically, a one-person job. We usually have an application specialist involved just to validate the health of the server. Whether it's an SQL server or application server, we have somebody that runs integrity checks on it. That said, the entire process is very painless and easily handled by one person.
I estimate that this product saves us hours in comparison to products like Veeam. Veeam would take several hours of time to fail something over.
Our company fell victim to a ransomware attack that affected between 50 and 60 servers. Until we knew for sure that the entire situation was remediated and that we weren't going to spread the infection, we restored the servers in an offline manner, which only took a matter of minutes to complete. Then, we pushed all of that data into Teams and OneDrive directly for people to start accessing it.
From the SQL server perspective, we failed those servers over, running health checks such as anti-virus scans, just to make sure that the failed over instance didn't contain the same situations. Thankfully, they did not. We probably saved ourselves several days worth of work in the grand scheme of things. In total, it potentially would have taken weeks to resolve using a different solution.
I wouldn't necessarily say that using Zerto has meant that we can reduce the number of staff in a recovery operation. However, I think it's probably mitigated the need to hire more people. Essentially, as we've continued to grow, we've avoided adding headcount to our team. Using Veeam as my problem child to compare against, if we were using it, it would have required a lot more management from us. It would have cost us more time to recover and manage those jobs, including the management of the ExaGrid appliances, as well as the VRAs, which are basically proxies.
Definitely, there is a huge saving in time using Zerto and although we didn't reduce any headcount or repurpose anything, we've definitely mitigated at least two people from the hiring perspective.
Zerto saved us considerable downtime when we experienced the ransomware attack. It may be hard to substantiate that just on the one situation but we saved at least a couple of million dollars.
What is most valuable?
The most valuable feature is the continuous recovery with the five-second checkpoint interval. Just having those checkpoints prior to when a situation arises, we're able to get the transactional data that occurred right before the server failed. That has been a blessing for us, as we are able to provide a snapshot with no more than five seconds of data loss. This means that we don't have to recreate minutes or hours worth of data for an industry that includes fulfillment, shipping, warehousing, et cetera.
Zerto is very good at providing continuous data protection. It does a very good job keeping up with the system and it creates five-second interval checkpoints. This has been helpful when it comes to needing to fail something over, getting that last moment in time that was in a usable state.
This product is impressively easy to use. It's dummy-proof, once it's set up.
What needs improvement?
The long-term recovery is a little bit weak in its granularity. Veeam is definitely superior in that aspect, as it's able to provide a granular view of files and databases, et cetera. However, it just kind of depends on what a business' recovery strategy is.
From our business perspective, it's really not impactful to us because our recovery strategy is not based on individual files. But, I could definitely see it being a challenge if there is a very large instance of individual files, as a subset, that need to be recovered. I think that if somebody has terabytes of data then Zerto will recover it faster but navigating through the file explorer to get to files is not as easy with Zerto.
One thing I don't like about the product, and I know this is where their claim to fame is, but whenever I have a VPG that has multiple virtual machines in it, and one virtual machine falls behind, it'll pause replication on everything else in that job until the one server catches up. The goal is to keep symmetric replication processing going, so the strategy makes sense, but for our business model, that doesn't really work and it has created a challenge where I have to manage each VM individually. It means that instead of having one job that would cover multiple servers, I just have one job to one server, which allows me to manage them individually.
For how long have I used the solution?
We have been using Zerto for approximately five years.
What do I think about the stability of the solution?
From a company perspective, a few years ago, I would have said that it is very stable. It is a solution that is thriving and growing. At this time, however, HP is in the process of acquiring them. While I had assumed that was their long-term plan, I didn't quite anticipate HP being the one to pick them up. As such, I am a little bit worried about what will change in the long term.
What do I think about the scalability of the solution?
Scalability-wise, it's a very painless product. As we continue to grow out our virtual environment, Zerto is able to, in a very nimble fashion, scale with us with very little effort or overhead involved.
I'm covering approximately 400 VMs currently, which is approximately 360 terabytes worth of data. That is between two separate data centers.
How are customer service and technical support?
Rating the Zerto technical support is a little bit tough because I've had some experiences that were truly 10 of 10, but then I've had one or two experiences where it was definitely a two or a three out of 10. It really depends on who I've gotten on the phone and their level of, A, comfort with their own system, and B, comfort helping the customer.
Some people have said this isn't within their scope of work, where others have said, "No, let's absolutely do this." In that regard, it's been a little hit and miss, but it's usually been a decent quality in the end.
Overall, I would rate the technical support a seven out of ten.
Which solution did I use previously and why did I switch?
I have worked with Veeam in the past and although I prefer Zerto, there are some advantages to using Veeam. For example, long-term recovery offers more features.
In-house, we had also used the Unitrends product, as well as a SAN-to-SAN replication using an old HPE LeftHand array.
The main reasons that we switched to Zerto were the management ability, as well as its ability to provide continuous replication. Veeam was a very cumbersome product to manage. There were a lot of instances to monitor and manage from a proxy perspective, whereas Zerto's VRAs are relatively transparent in their configuration and deployment. These are painless and I don't have to continually monitor them. I don't have to update them since they're not like standalone Windows instances. It's very low management for us.
Of course, continuous replication is critical because Veeam, even though when we had owned the product, it claimed 15-minute intervals were doable, it never seemed to actually keep up with those 15-minute snapshot intervals.
One final reason that we migrated from Veeam is that they were utilizing VM snapshots at the time. I know that they've moved away from that approach now, but it was very painful for our environment at the time. The VMware snapshots were causing some of our legacy and proprietary applications to fail.
How was the initial setup?
The initial setup is very simple.
Our implementation strategy involved setting it up for our two data centers. We have a primary and secondary data center, and Zerto keeps track of all of the VMs at the primary site and replicates them to the other site.
In the future, we plan on looking into the on-premises to cloud replication. On-premises to Azure direct is on our roadmap.
What about the implementation team?
I completed the setup myself without support or anybody else involved in the deployment.
It took approximately an hour to deploy.
I handle all of the administration and maintenance. As the senior manager of infrastructure, I oversee our work and server group. I have also retained private ownership over the disaster recovery plan and failover plan.
What was our ROI?
We have probably not seen a return on investment from using Zerto. We don't really have lots of situations where we have to use it and can substantiate any kind of financial claim to it.
What's my experience with pricing, setup cost, and licensing?
I do not like the current pricing model because the product has been divided into different components and they are charging for them individually. I understand why they did it, but don't like the model.
Our situation is somewhat peculiar because when we bought into it, we owned everything. Later on down the road, they split the licensing model, so you had to pay extra for the LTR and extra for the multi-site replication. However, since we were using LTR prior to that license model change, they have allowed us to retain the LTR functionality at our existing licensing level, but not have the multi-site replication.
Which other solutions did I evaluate?
We have not evaluated other options in quite a long time. We very briefly evaluated Rubrik.
What other advice do I have?
When we first decided to implement Zerto, it wasn't very important that it provides both backup and DR in one platform. In fact, realistically, even now, while we have it and we used it on a limited scope, I'm not sure that it's needed.
With respect to our legacy solutions, I'd say that the cost of replacing them with Zerto is net neutral in the end.
My advice to anybody who is considering Zerto is that it's an awesome product and it won't steer them wrong. That said, there are some issues such as the licensing model and the situations where VPGs falling behind suspends the replication. Overall, it is a good product.
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.
Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros
sharing their opinions.
Updated: November 2024
Popular Comparisons
Veeam Data Platform
Commvault Cloud
Rubrik
VMware Live Recovery
BDRSuite Backup & Replication
Nasuni
NAKIVO Backup & Replication
Arcserve UDP
Dell RecoverPoint for Virtual Machines
Hornetsecurity Altaro VM Backup
Datto Cloud Continuity
AWS Elastic Disaster Recovery
Druva Phoenix
Infrascale Backup & Disaster Recovery
Precisely Assure MIMIX
Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Software replication to remote sites during disaster recovery?
- What are the differences between Zerto, VMware SRM and Veeam Backup & Replication?
- Why is disaster recovery important?
- Can Continuous Data Protection (CDP) replace traditional backup?
- Can you recommend a disaster recovery automation tool?
- How does Datto compare to ShadowProtect?
- When evaluating Disaster Recovery Software, what aspect do you think is the most important to look for?
- What is the difference between cyber resilience and business continuity?
- Internal vs External DR Site: Pros and cons
- Disaster Recovery Software: Which is the Best Solution in the Market?