Daniel Modrušan - PeerSpot reviewer
Assistant Vice President & Principal Systems Engineer at Bangor Savings Bank
Real User
Took our disaster recovery practice from sixteen hours down to thirty minutes
Pros and Cons
  • "I love Zerto's near-synchronous replication. I've been using Zerto for three years at my current employer and many years before that. It's been great. Anywhere I've used it, it's made the failover process a lot easier so that pretty much anybody can do it. This feature is our number one priority because we can keep our critical apps running if we have a failure, or even if we have a misconfiguration, it's very easy to recover something quickly."
  • "I would like for them to support additional hypervisor options. They support VMware but if they supported Hyper-V or Nutanix, it would be beneficial."

What is our primary use case?

Our primary use cases are for disaster recovery, data center movement, long-term recovery, and backup recovery.

How has it helped my organization?

Zerto took our disaster recovery practice from sixteen hours down to thirty minutes. 

What is most valuable?

The most valuable feature is the fully automated failover. The orchestration made the failover very easy for anyone who wasn't necessarily technically knowledgeable to be able to failover a machine.

I love Zerto's near-synchronous replication. I've been using Zerto for three years at my current employer and many years before that. It's been great. Anywhere I've used it, it's made the failover process a lot easier so that pretty much anybody can do it. This feature is our number one priority because we can keep our critical apps running if we have a failure, or even if we have a misconfiguration, it's very easy to recover something quickly.

We've moved some of our workloads to the cloud and back from the cloud using Zerto. The native tools provided by the cloud provider were not as seamless. Having DR in the cloud is very important to us because we trust that the cloud provider will provide a solution, but we also want to make sure that for our business purposes, we have a backup to disaster recoveries so that we're able to recover somewhere else if necessary.

We use Zerto to support DR on the AWS platform. We go between two different clouds. We go from VMware to Azure and also AWS.

Zerto made this quite seamless, especially going between two different clouds. It's just a matter of a couple of clicks. You don't need to understand what's happening on the back end.

We use Zerto to help protect VMs in our environment. It took our RPO from around four hours and now it could be seconds. We can recover the machine in under a minute as far as the boot time. We're between five and ten seconds RPO.

The magnitude of Zerto is much faster. We used to do a disaster recovery failover of our critical systems. It took about sixteen hours and once we had implemented Zerto, it took around thirty minutes to do for the same exact systems.

What needs improvement?

I would like for them to support additional hypervisor options. They support VMware but if they supported Hyper-V or Nutanix, it would be beneficial.

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

For how long have I used the solution?

We have been using Zerto for three years. 

What do I think about the stability of the solution?

It's been great. We've had it for three years. The only time we reboot the machines is for normal patches. We don't have to do anything else. It just works. We don't have to think about it. We've never had any issues over the three years we've been running.

What do I think about the scalability of the solution?

We started Zerto with a small footprint. We only did a few VMs as a POC with two nodes on each side. Then we've grown it to 34 nodes on each side, including the cloud. It's always the same amount of resources. We're running 150 protected VMs in there. It runs really well. 

How are customer service and support?

The few times we've had to use customer service, it's never been for anything that was really broken. It's more informational or because we didn't understand how the product works. They've been great with communication, they get back to us, and even if they don't get an answer right away in one day, they'll let us know with the ticket updates that they're still working on it. 

It's been really good as far as the little interaction we've had. The one nice thing is that we've never had to use it for anything that's been broken or that it's not working.

They have great communication. They don't just send you links to KB articles. 

How would you rate customer service and support?

Positive

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

We looked at other solutions before we purchased Zerto. We did a bake-off with a couple of other solutions. Zerto blew everything else away. The functionality is the same as everybody else, but the amount of time it takes to implement Zerto is a lot quicker. 

Making changes if you want to add another machine or another workload takes virtually seconds, whereas we found other systems took a planning time and could take hours to get implemented correctly.

How was the initial setup?

The setup was great. We had one of our newest engineers run through it because as part of the POC, the salesperson showed us how to install it. It was very straightforward. We took somebody who knew nothing about Zerto, had them install it and they had it installed and running in about fifteen minutes. It is quite easy to use. 

I can't say it's the same for SRM. There's a lot of documentation, whereas, with Zerto you point to the button, you push, and it works. 

What about the implementation team?

We did the full installation ourselves.

What was our ROI?

We got the recovery time from sixteen hours to thirty minutes. Prior, when it took sixteen hours, there would be about ten or more people who were waiting for systems to come online to be able to test. 

With Zerto, within an hour, we get the systems up, and then it's thirty minutes to test. Everybody can go home. There's a lot less time for people to be available. Zerto makes it much easier and quicker to get completed.

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

The licensing model per VM is great. It's a good way to license it because you want to protect only the devices that you're looking to protect. As far as getting the licensing and working with the sales team, they're very responsive. There's a lot of great communication, it's good all around.

Which other solutions did I evaluate?

We looked at VMware SRM. We also looked at a manual process. We chose Zerto for the simplicity and the cost ratio was phenomenal. It's easy enough that we've had nontechnical people able to failover just by clicking a button. 

For Zerto, you add the VM in the VPG or workload, point it to the target, pick where you want it to land, hit go, and it's done. With SRM, in comparison, you'd have to make sure it's being replicated between the two SANs. You have to go to a different UI, configure all of it, make sure that's working, then go into SRM and configure all the orchestration parts. It takes a lot more planning. You really have to make sure that all the different systems work together, whereas Zerto takes care of all that for you.

What other advice do I have?

I would rate Zerto a nine out of ten, there is some room for improvement. The drawback for me is that it's not compatible with every single hypervisor. If we wanted to go with another vendor for a hypervisor locally, then we'd have to look for a different solution, and there's nothing really out there that is comparable to what Zerto can do.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Real User
Top 10
Enhances resilience and data protection capabilities with real-time replication
Pros and Cons
  • "The live failover tests and point-in-time recovery options have been exceptionally valuable features of Zerto for our organization."
  • "The product could benefit from improvements in automation, specifically in the area of failovers."

What is our primary use case?

Implementing failover to a secondary data center is crucial for ensuring business continuity in the event of primary data center loss. This strategy involves automatically redirecting operations and services to the secondary data center when the primary one becomes unavailable. This not only minimizes downtime but also enhances overall system reliability. 

The failover process requires robust synchronization mechanisms to ensure data consistency between the primary and secondary data centers. Regular testing and monitoring are essential to validate the effectiveness of the failover mechanism and identify and address any potential issues proactively. 

In summary, failover to a secondary data center is a strategic measure to safeguard against disruptions, offering a resilient solution for maintaining seamless operations in dynamic and challenging environments.

How has it helped my organization?

Zerto has significantly enhanced our organization's resilience and data protection capabilities. Its real-time replication and failover features have played a pivotal role in minimizing downtime during unexpected events, ensuring business continuity. 

The platform's automation and orchestration capabilities have streamlined our disaster recovery processes, reducing manual intervention and accelerating recovery times. 

The point-in-time recovery options provided by Zerto have proven invaluable in mitigating the impact of data corruption or accidental deletions. This has bolstered our data integrity and provided a safety net against unforeseen data-related issues.

What is most valuable?

The live failover tests and point-in-time recovery options have been exceptionally valuable features of Zerto for our organization. Conducting live failover tests allows us to validate the effectiveness of our disaster recovery setup in a controlled environment. This feature ensures that all components are in place and functioning as expected, providing confidence in our ability to respond to real-world disruptions. 

Additionally, the ability to choose a specific point in time for recovery down to the seconds is crucial for data integrity. This granular control allows us to roll back to a precise moment, mitigating the impact of data corruption, accidental deletions, or other unforeseen issues. It adds a layer of precision to our recovery process, minimizing potential data loss and enhancing overall resilience.

What needs improvement?

The product could benefit from improvements in automation, specifically in the area of failovers. Currently, the process is largely manual, and introducing automated failovers after a certain time threshold would enhance efficiency and responsiveness. Automated failovers can reduce the dependency on manual intervention, allowing for quicker and more proactive responses to disruptions. In the next release, the inclusion of scheduled or automated failovers would be a valuable addition. This feature would empower organizations to set predefined parameters and triggers for failovers, ensuring a timely and automated response to potential issues. It not only streamlines operations but also adds an extra layer of reliability to the overall disaster recovery strategy.

For how long have I used the solution?

I've been using the solution for six months.

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

We did not have a solution before.

How was the initial setup?

We had great help from the company in terms of setting up our environment.

What about the implementation team?

We implemented through a vendor; I'd rate the experience ten out of ten.

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

Anything is the worth the cost for virtually no downtime. Time is money.

Which other solutions did I evaluate?

We did not evaluate other options.

What other advice do I have?

It is a great solution overall, however, it could use some upgrades with automation.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Buyer's Guide
Zerto
June 2024
Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: June 2024.
792,905 professionals have used our research since 2012.
Senior Security Engineer at North Shore LIJ Huntington Hospital
User
Near-zero recovery time and good security features but support needs to be more flexible
Pros and Cons
  • "Zerto helped our organization meet compliance requirements by ensuring data protection and recovery strategies align with our regulatory standards."
  • "Zerto needs to improve its documentation."

What is our primary use case?

We use the solution for replicating VMs from our on-site VMWare sites to both Google Cloud and Azure clouds. This allows us to feel confident not only in our disaster recovery capabilities but also in testing applications from our on-site data center to isolated cloud instances where there won't be any IP address or domain name system conflicts.  

The continuous backup gives us a better point in time recovery. It also reduces the amount of bandwidth to move the Zerto VM data from site to site, and we like that.

How has it helped my organization?

Zerto has improved our organization in several ways, particularly in the realm of disaster recovery, data protection, and business continuity.  

With Zerto's near-zero recovery time, our critical applications and services can be quickly restored, minimizing the impact on business operations.  

The data replication ensures that there is a consistent and up-to-date copy of the information. This helps protect against data loss and ensures data integrity.  With Zerto's single pane of glass, it's easier for IT administrators to monitor and manage their disaster recovery and data protection strategies. This has led to more efficient operations and reduced administrative overhead.

What is most valuable?

Zerto supports multi-cloud environments, allowing our organization to replicate and protect our important data across different cloud providers and sites. This flexibility has benefited our businesses with our diverse cloud strategies and our on-site data centers in different locations.  

Zerto helped our organization meet compliance requirements by ensuring data protection and recovery strategies align with our regulatory standards. 

Additionally, Zerto has incorporated security features to safeguard the replicated data.

What needs improvement?

Zerto needs to improve its documentation. It seems like some documents are copied from other older documentation, with misleading screenshots or incorrect steps.  

This can be confusing when newly introduced to a product or in a crisis situation such as a disaster recovery test or a true disaster recovery. The documentation needs to be revised, reviewed, and registered to be correct. Perhaps Zerto should consider an outside consultant to review and approve any documentation that is released.

For how long have I used the solution?

I've used the solution for about a year.

What do I think about the stability of the solution?

It's very stable, and we have had no issues.

What do I think about the scalability of the solution?

it does scan well and does what it claims to do.

How are customer service and support?

Support needs to be more flexible.

How would you rate customer service and support?

Neutral

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

We have only used vRealize.

How was the initial setup?

The documentation was confusing and, at times, incorrect.

What about the implementation team?

We handled the setup in-house.

What was our ROI?

I don't any ROI information.

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

I'd advise others to start small.

Which other solutions did I evaluate?

We also evaluated Veeam.

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.
Flag as inappropriate
PeerSpot user
Global IT Operations Manager at a insurance company with 501-1,000 employees
Real User
Instead of using SQL Always On, we protect the whole VM, saving us server costs, but management overhead has increased
Pros and Cons
  • "The quickness and efficiency of creating snapshots, on a real-time basis, is one of the most valuable features. Whenever changes are made on a server, Zerto starts taking snapshots right away and replicating them to the DR site. It's very effective and very quick."
  • "In Azure... We have to make sure that every resource group is tagged correctly, with the correct team and department because we have to bill them at the end of the month. The problem is that Zerto does not have that ability. When the product fails over or migrates a VM from on-prem, or even within Azure, to another site, it does not give you the option of selecting an existing resource group."

What is our primary use case?

We use it for migrations and VM protection.

How has it helped my organization?

The near-synchronous replication is very good. It's very critical for us. For example, with SQL, we used to use Always On to protect databases at the database level, to give us high availability and DR. But now, in Azure, we don't do that. If we wanted to do that, we would have to have a SQL Server on the protected site and another up and running on the DR site and those machines would always have to be up and running. To save on costs, instead of using Always On, we're now protecting the VM as a whole, thanks to Zerto.

It's also the main tool that we use for our annual DR tests for all of our production applications. Once a year, for one week only, we do a failover of those critical production applications from the primary site to the DR site and we let them run there for that week. Zerto does the failover and the DR site becomes the active site while everything replicates to the former primary site. Once the week is over, we do a failback and Zerto is the main tool that we use for that, and we repeat the whole process. We're then good for the whole year. Zerto is protecting those VMs.

Another advantage is that Zerto has decreased downtime for us. It could have been a situation where we were down for weeks because of something that Azure did on their end. Even though Zerto has a partnership with Microsoft Azure, sometimes Azure makes changes that are disruptive. There was one change that affected our ability to replicate our critical workloads and it was a rough one. For that week, Zerto found a workaround because they were not getting any progress on resolving the situation from the Azure team. Zerto applied the workaround in their code and we were good, but that was a rough situation. Zerto goes out of its way to help its customers. We've had issues but Zerto has been very responsive.

What is most valuable?

The quickness and efficiency of creating snapshots, on a real-time basis, is one of the most valuable features. Whenever changes are made on a server, Zerto starts taking snapshots right away and replicating them to the DR site. It's very effective and very quick. Our SLAs are 24 hours, but Zerto could do what we needed, on-prem, in seconds, and in the cloud, in minutes. Zerto is way ahead of what our SLAs are.

Sometimes we do failover tests to make sure that we will potentially have a successful failover or migration. It's very flexible and does its job very well. And one of the things I love about the product is that whenever you do a failover, it gives you the ability to either commit or roll back. Some of Zerto's competitors don't have that ability, at least in Azure. That's critical for us because after we have DR tests on a weekend, we have users sign off on their applications that everything is fine. If something isn't right, we can always roll back to how everything was right before we started the DR test. And if everything is working great, then we commit.

What needs improvement?

Since we are primarily in the cloud now, Zerto definitely needs to update its platform. When we were decommissioning one of our on-prem data centers and going to Azure, there were issues. And with Azure, it's still limited in the way we can manage our resources there. Zerto hasn't quite kept up to date with how certain elements run within Azure.

In Azure, there is something called resource groups. You cannot create a resource without a resource group. You can apply tags to resource groups and that tagging information is very critical to our company because we now have 95 percent of our production environment workloads running in the cloud. We have to make sure that every resource group is tagged correctly, with the correct team and department because we have to bill them at the end of the month. The problem is that Zerto does not have that ability. When the product fails over or migrates a VM from on-prem, or even within Azure, to another site, it does not give you the option of selecting an existing resource group.

When it fails over, it uses the name of the group that you created within Zerto. The VM is failed over with no problem in a reasonable amount of time. But the problem then becomes that the resources are part of a resource group that has no tags. It does not follow our naming commission for resource groups and then we're stuck. It's not as easy just renaming the resource groups.

These components are very critical for us but they are missing in Zerto. They're aware of it because we've had feature-request meetings with our Zerto account team. They're working on it for the next release and have mentioned that they are going to be making improvements to the product. But for now, it's lacking.

Also, a downside with Zerto is that there is a lot of management overhead when running it in the cloud. On-prem, we used to have one Zerto management appliance, but in the cloud, we have about 20 to manage to protect our VMs. Zerto has mentioned to me that, for the next release, they're building it from the ground up and it will be much better in the cloud, with more cloud focus.

Because of the experience that I had with Zerto running on-prem, where we only had one appliance in each of our data centers, I deployed one in Azure as well. Little did I know that there were limitations and that more appliances had to be deployed because of all the replication of the traffic and the number of VMs that we were trying to replicate. But Zerto stepped in and helped when it came to that.

For how long have I used the solution?

I have been using Zerto for four years.

What do I think about the stability of the solution?

The stability is an eight out of 10.

What do I think about the scalability of the solution?

The scalability is also an eight out of 10.

How are customer service and support?

They're very helpful. They always want to understand your situation and, even if they're not sure, they do their best to help and fix the problem. 

For on-prem, there were always references, but for the cloud there is a bit of a knowledge gap. I would always get workarounds, fixes, or KB articles for on-prem, but the cloud implementation is where the documentation is lacking. But the team does its best. It depends on who you get. Some know Azure, or cloud, and some still lack that knowledge. But if they don't know, they get the right person on the call.

How would you rate customer service and support?

Positive

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

We were a VMware shop on-prem and we were migrating to the cloud from on-prem VMware to Azure, so the tool that we were using to protect VMs through DR would no longer work. We used VMware SRM (Site Recovery Manager) for years when we used to be solely on-prem. 

We started looking for a product to help and, at the time, Zerto was the one that stood out among the competitors, and it was a solid product, so we started using it. Zerto is definitely a more effective product. It is a lot quicker when bringing our VMs up on the DR side, and even when we do a fallback. And Zerto is a lot easier to use than VMware.

How was the initial setup?

The initial setup was not straightforward.

And maintenance is required for upgrades when there are newer releases, especially when it comes to Azure. There are newer releases that contain fixes and improvements and we do update the version of the Zerto appliance. They are running on Windows Servers, so we also have to patch the operating system. In Azure, there are a lot of SKUs with different pricing. Depending on the utilization of a VM, we sometimes make changes to the family types to save on costs at the VM level.

What about the implementation team?

I did it with our Zerto account team, which included our sales engineer. Just the two of us were involved.

What was our ROI?

Zerto saves us a lot of time. One team member alone can handle the DR test using Zerto, whereas before, when we used SRM, at least two or three people were involved from the VM perspective and from storage. VMware was integrated with our NetApp environment and that meant at least two or three team members were involved. But with Zerto, just one person uses the product for a DR test.

Which other solutions did I evaluate?

We looked at Azure Site Recovery. We were close to going with it. It did have the ability to do resource group selection, but there were two showstoppers at the time that prevented us from going forward with it.

When we were looking at Azure Site Recovery, it seemed that it had a better cost per VM, but Zerto was not that far off. And we were more comfortable using Zerto to protect our VMs than the other products we were testing.

What other advice do I have?

My advice is that if you're in the cloud, you really should test the failover of your VMs. If tagging is not a key component, you'll be fine. But if it is, that is a huge problem. And expect a lot more management overhead when it comes to managing Zerto in the cloud.

In terms of our RPOs, Zerto is consistent. From time to time, it may run past our SLAs, but that's because there are network or VM issues. And that happens very rarely. It almost always meets our RPOs.

The ease of moving data varies on the size. A good thing about Zerto is that it does give you a little chart indicating the step that it's at in the replication process.  But even if it's a small VM, it does take some time, including setting it all up and starting the synchronization. It's not instant.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Senior Vice President and Chief Information Technology Officer at a healthcare company with 1,001-5,000 employees
Real User
Always works, is good for our business use case, and is easy to set up
Pros and Cons
  • "The customer service and support are very good. Every time we have problems, they're ready to help us."
  • "There is room for improvement in the upgrades."

What is our primary use case?

We use Zerto for data and disaster recovery replication. 

How has it helped my organization?

From time to time, we have to go look at the DR environment. Every time we go there, Zerto application always works. That's a benefit. 

Zerto's near-synchronous replication works. The value for our business case is okay. 

Zerto's near-synchronous replication is important for healthcare, but not as much because we have time to recover data.

Zerto helped protect VMs in our environment, just for the DR.

Our RPOs are not very aggressive. So, Zerto works just fine for us. 

What is most valuable?

It's very easy to set up. Up until now, even with an old version, it always worked fine.

What needs improvement?

There is room for improvement in the upgrades. We are planning an upgrade now, and it seems that it's not straightforward.

In future releases, I look forward to the security feature.

For how long have I used the solution?

We have been using Zerto for more than five years.

What do I think about the stability of the solution?

Stability is very good. We have complaints about stability.

What do I think about the scalability of the solution?

We haven't had issues with scalability. When we add VMs, we just buy additional licenses.

How are customer service and support?

The customer service and support are very good. Every time we have problems, they're ready to help us.

They're always available and very knowledgeable. 

They need to be on-site. That would make them a ten on ten. 

How would you rate customer service and support?

Positive

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

We have only used Zerto. 

How was the initial setup?

It was very easy to deploy. There wasn't a lot of configuration needed to get the syncing working.

It is an on-premises deployment.

What about the implementation team?

We used HPE Services. Our experience with them was very good. 

What was our ROI?

We have seen ROI. Several times, we needed to recover, and we were able to go to Zerto.

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

The pricing, setup, cost, and licensing are comparable to other solutions. Zerto is not more cost-effective.

Which other solutions did I evaluate?

We looked at Veeam. They're very similar. We already had the skills for Zerto, so we decided to stay with it.

We decided to stay because we have not had any problems with it, and moving to another solution doesn't make sense for us. 

What other advice do I have?

I would rate it an eight out of ten. The version we have doesn't have security yet, so maybe the next version will get a ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Jeremy Jones. - PeerSpot reviewer
Assistant It Manager at TH Plastics, Inc.
User
Protects data and servers, good replication, and offers peace of mind
Pros and Cons
  • "Zerto is fast to restore our mission-critical servers when needed."
  • "Zerto could add text alerts if there are critical problems and alerts if changes affect our replication."

What is our primary use case?

We use Zerto for offsite disaster recovery. We have over 70 VM servers, several of which are our mission-critical servers that are replicated to our VMware hosts at an offsite location. 

We also replicate our Citrix environment and Disaster Recovery Zen App servers with Zerto to our offsite location as well. Most of our servers are Windows-based operating systems. However, this doesn't matter because we are replicating the VM servers. Further down the line, we may invoke extended retention for some of our more important servers.  

How has it helped my organization?

It gives us peace of mind that our data, servers, and environment are protected. We can easily restore VMs quickly and have confidence that the replicated data will be current. 

We are able to show proof in tests, reports, and live data to our owners, showing that our most sensitive data and servers are being replicated to an offsite facility, and we can restore it in case of a natural disaster or from our system being compromised by ransomware. 

Our IT staff can easily navigate through Zerto and test failover, see if there are issues with replications, and create offline copies of the data. 

What is most valuable?

Being able to test our VPGs and prove that our disaster recovery setup is in place and functional. 

Our business owners can be assured that our data is protected, and in case a serious problem occurs, they know that we will be able to recover easily. 

Zerto is fast to restore our mission-critical servers when needed. We also use Zerto to make copies of our VM servers for our offsite Citrix Zen App Servers. Zerto has helped simplify the process of disaster recovery setup and made the tasks more efficient for our IT Staff.

What needs improvement?

Zerto could add text alerts if there are critical problems and alerts if changes affect our replication. We do receive emails, and they will alert us to issues that we are having with VPG SLAs. 

I don't have any complaints about Zerto, and I hope they continue to develop new features. If they had classes on using Zerto, that would help with onboarding new IT staff. They may already have them, and I am not aware that they do. Overall, Zerto works out great, and they do a good job. 

For how long have I used the solution?

I've used the solution for five years.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
Mike Erin - PeerSpot reviewer
VP of IT Infrastructure at Fay Financial
Real User
Top 10
The near-synchronous certification has positively impacted our operations
Pros and Cons
  • "It's very stable. It doesn't require a lot of intervention."
  • "Maybe the reporting for the failover test could be a little better."

What is our primary use case?

Our primary use case is for disaster recovery. We replicate up to Azure, and that's essentially disaster recovery as a service.

Overall, the effects of RPO have been great. They are never more than a minute or two, even throughout the production day.

What is most valuable?

If we can replicate from our native VMware environment up to native Azure, it converts the machines for us. We don't have to maintain another VMware environment somewhere. It's really given us the ability to eliminate the entire data center.

Moreover, there are cost savings tied to this. We don't pay for the rack space, power, or hardware; all of that is gone. Because the machines aren't active, all we're paying for is storage in Azure. So it has saved us quite a bit of money.

Zerto's near-synchronous certification has positively impacted our operations. Any recovery point that's too far in the past, we'll lose transactions when we fail over. We really don't want to do that. Real-time replication gives us a much better sense of security for the enterprise. It simplifies things for us and reduces costs.  It makes management feel really good, too.

Using DR in a cloud environment has been a positive experience. We're saving money. We don't have to maintain the hardware. We don't have the rack space at the other data center. It just simplifies things for us and reduces costs. It's been a positive experience overall. It's pretty easy to use. Once it's up and running, it stays running. We have had a few times when we called support and the support has been very, very good.

What needs improvement?

Maybe the reporting for the failover test could be a little better.

For how long have I used the solution?

I have been using Zerto since 2020, so it's been three years.

What do I think about the stability of the solution?

It's very good. It's very stable. It doesn't require a lot of intervention. 

What do I think about the scalability of the solution?

We haven't had any problems with scalability. We have 75 machines protected by Zerto and it does a fine job.  

How are customer service and support?

Support has been very good.

How would you rate customer service and support?

Positive

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

We used to use Site Recovery Manager when we had two data centers, and it was VMware to VMware. We were using EMC storage. Zerto is a lot easier to use than Site Recovery Manager. It requires less care and feeding. 

Site Recovery Manager occasionally would lose virtual machines, and it was kind of a pain, but Zerto just kept running. So overall, we're really happy with the switch to Zerto.

How was the initial setup?

The initial setup was easy.

Since we don't have to maintain all of the hardware and the second data center, one person can manage the entire Azure environment by themselves. As a result,  Zerto has helped us reduce staff. 

What about the implementation team?

We did an assisted setup with Zerto tech on the line, and It was really painless. It was simple and straightforward. The initial process including getting the servers and everything set up, was pretty short. The process included getting the VMs all added to the recovery groups and things like that. 

The whole process from start to finish took less than a week.

What was our ROI?

It has proven to be a cost-effective solution for us. 

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

It could always be less money. 

What other advice do I have?

Overall, I would rate the solution a ten out of ten. It requires little care and feeding. Not a lot goes wrong with it. It just works.

Which deployment model are you using for this solution?

Public Cloud

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

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Gregory L. - PeerSpot reviewer
Converged Infrastructure Engineer at a insurance company with 10,001+ employees
Real User
Is fast to set up and has valuable replication features
Pros and Cons
  • "It reduced the time for DR tests from the infrastructure side. Being able to get our work done in a matter of a couple of minutes so the app teams can get to work and can do their testing has been significant."
  • "We would love to have a native management pack for vROps and to be able to view a dashboard and metrics for BPGs within vROps. We would like to have a single view for monitoring and provide customers with dashboards so they can see their own BPGs."

What is our primary use case?

We use Zerto as a DR tool. Instead of having to have a duplicate DR server, we can add a system to BPG and point it to whatever our DR site will be and replicate it for customers.

We also use it for migration planning. If we need to move VMs from on-premise to Azure or back, or it was built in the wrong place, we can easily move it over. 

How has it helped my organization?

It reduced the time for DR tests from the infrastructure side. Being able to get our work done in a matter of a couple of minutes so the app teams can get to work and can do their testing has been significant. 

Before we would have to use a backup recovery tool to restore it to a LAN, which could take hours at times, depending on the solution that was being used. 

What is most valuable?

The replication features are most valuable. It's fast to set up a BPG and get a system added. This aspect is very important to our business. Being able to provide customers with a very fast DR experience, whether it's for a test or live case scenario, and being able to provide the ability to move systems to Azure for cost savings or migrations, saves our ops teams a lot of time.

What needs improvement?

We would love to have a native management pack for vROps and to be able to view a dashboard and metrics for BPGs within vROps. We would like to have a single view for monitoring and provide customers with dashboards so they can see their own BPGs. 

We would also like to have a native plugin for VRA built by either VMware or Zerto. That way there's actual support for it and we're not on the hook for trying to figure out what happened if it breaks.

For how long have I used the solution?

We have been using Zerto for four years.

What do I think about the stability of the solution?

The only problems we've had stability-wise come from upgrades.

What do I think about the scalability of the solution?

This is a scalable solution. The only challenge is that there's no way to manage it centrally at the moment. If you have 30 vCenters, you now have 30 appliances and you have to remember where everything is, which can become a pain point when it comes to trying to find where this VM is being replicated and what BPG it's in. 

How are customer service and support?

The support for this solution could be improved. It is challenging for staff who actually understand the product. We had issues where we ended up spending hours and sometimes days on the phone, only for us to figure it out on our own.

They're very personable and fine to work with. It seems like technical expertise is lacking. I would rate them a five out of ten.

How would you rate customer service and support?

Neutral

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

I haven't used too many other disaster recovery tools. We used standard backup solutions and Zerto is significantly faster. 

What other advice do I have?

I would rate this solution a nine out of ten. 

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