Systems Administrator at a legal firm with 10,001+ employees
Real User
Easy to use, enabling us to configure a DR solution for our customers they can use themselves
Pros and Cons
  • "It's also very much faster than any other migration or disaster recovery platform we have. I work with virtualization, mostly on VMware, and I must admit that Zerto is even better than VMware Site Recovery Manager. Zerto compresses the data and it works much faster."

    What is our primary use case?

    We use Zerto as a migration platform from a customer's data center or from their on-premises environment to our data centers. We also use it for disaster recovery.

    How has it helped my organization?

    Zerto has helped to reduce the number of people involved during a data recovery situation in our company. All we have to do is click a few times. We have even configured a DR solution for our customers so that they can do it themselves. We give them access to the Zerto platform, as well as have a small manual of instructions, and they can go do it. It's very simple to use and to deploy and to support. It does not have a very large learning curve.

    For our clients who do DR in the cloud, Zerto has definitely saved them money. We only have a few DR client accounts, but for the ones we do have, there haven't been any failures of Zerto, whenever we do failover tests. It performs well.

    What is most valuable?

    It's a great platform because it's very well built, technically. 

    It's also very much faster than any other migration or disaster recovery platform we have. I work with virtualization, mostly on VMware, and I must admit that Zerto is even better than VMware Site Recovery Manager. Zerto compresses the data and it works much faster. We use it whenever we can, and especially whenever we are on a tight time schedule for closing a project, or we need to bring information or VMs from a client or from another data center. Zerto is very valuable because of its speed.

    And in terms of ease of use, when I started with my current company I didn't even know about Zerto. My first project was a migration from a big customer and I thought, "Wow, this will be a lot of work." It was a little scary because of the pressure to get it done. But Zerto was so easy to use. I like it a lot.

    For how long have I used the solution?

    I've been using Zerto for about 12 months, but the company I work for has been using it for four or five years.

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

    What do I think about the stability of the solution?

    It's very solid, like a rock. It's very stable.

    Even with the most recent customer that we migrated to our data center, it was really impressive that Zerto kept the levels of performance very consistent. This customer's site was at another data center provider, not one of ours. It was on a very old VMware version, and we were deploying them to the latest, vCenter Server 7. At first I thought, "We will be struggling to bring this customer over," because they were two major versions behind. I didn't think Zerto would be compatible for making this migration happen. But it worked like a charm, and we had no problems regarding Zerto itself. While we had some problems with this migration, they were not related to the technology.

    What do I think about the scalability of the solution?

    It's very scalable. Most of our core usage here is for migrations from our customers' on-premises or data center instances. And about two years ago, we had a very big migration of over 3,000 virtual machines, and Zerto performed really well. That's why we have kept Zerto in our portfolio.

    How are customer service and support?

    Their support is amazing. We have had to open some support cases and they have a very good technical team. They're always referring us to their technical teams if we need to discuss something. Or if we fail to understand some of the concepts, we can reach out to them too. It's more than a commercial relationship. They support us whenever we need help.

    How would you rate customer service and support?

    Positive

    How was the initial setup?

    We do setups of Zerto every week or two weeks, because it's not a single platform. We are a multi-cloud environment and service provider. We deploy it according to project requirements. So we don't have a single Zerto platform. We are always deploying VMs and DRs.

    Zerto is very easy and straightforward to set up. Whenever we want to use Zerto for a migration from an on-premises customer to our data center, we usually create a WAN to WAN link, or a LAN to LAN, or a VPN link between the customer and us. We just deploy the VPNs from our side to the customer site and request access to their environment. We check for special VM configurations. It's pretty straightforward. We don't like telling the customer to do it, even though it's very easy to deploy and configure, because it's part of our service to do this job for them. We also have our own guidelines and policies that we use to configure Zerto for the best migration setup.

    The last deployment I did took me four hours, which included setting up both my side and the customer side, doing the pairing and, later, the VPG's. We migrated over 100 VMs and it took about two days to fully replicate their site to ours. The migration window to do the move was about six hours because they had to change applications. But the move itself took no more than two minutes for every Zerto machine. 

    When I talk to the customers, I tell them that it will be faster than the move window we request. Most of the time set aside for the window is for taking applications offline, because they will often need to reconfigure them. When client data comes from an on-premises site to our data centers, there are usually IP address changes, or we have to update VMware tools, or do something at the Zerto machine level by changing Zerto hardware, such as a network card. The moving itself is pretty straightforward.

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

    Because I'm a support engineer, I don't really work directly on the commercial side of things. Whenever I need to request a license for Zerto, someone on our dedicated licensing support team takes care of it. So I don't know if that process is easy or not.

    Zerto works very well as a backup and recovery solution, with frequent recovery points. It's very good. But it's too pricey for us to use it as a backup solution for all of our clients. Not every customer needs recovery points every five seconds.

    What other advice do I have?

    It's a great platform, if you use it as a recovery system and as a migration tool. It's really amazing. It's a very well-developed product and one of the best solutions. In the same way that what makes Microsoft big today is Active Directory, which is an amazing product and one that no other enterprise could do any better, Zerto is the same type of leader in its category and is at the very top, without a doubt.

    Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
    PeerSpot user
    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.
    PeerSpot user
    Buyer's Guide
    Zerto
    March 2024
    Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
    767,077 professionals have used our research since 2012.
    Project Manager at a computer software company with 11-50 employees
    Real User
    The journaling capability allows you to recover from a ransomware attack.

    What is our primary use case?

    In our case, we used Zerto Replicator mainly for DRP (Disaster Recovery Plan), but also for testing.

    How has it helped my organization?

    For example, journaling capability allows you to recover from a ransomware attack. Thus, it is not only used in DRP scenarios.

    In addition, there are increasingly more environments (such as IBM BlueMix) that support Zerto replication, for public cloud contention environments.

    What is most valuable?

    Zerto allows RPO of seconds, without need of snapshots. It is agnostic to storage and allows journaling of up to 30 days.

    What needs improvement?

    For me, limiting the minimum licensing package for 15 virtual machines (VMs) is a issue. Not all environments (especially in Latam) start with 15 VMs.

    For how long have I used the solution?

    One to three years.

    What do I think about the stability of the solution?

    No, not really.

    What do I think about the scalability of the solution?

    No, not really.

    How are customer service and technical support?

    The support is in English only, and I estimate it 4/5.

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

    I know Veeam B & R and VMware SRM (along with vSphere Replication) and in environments with aggressive RPO, and non-reliance on snapshots, Zerto is a superior solution.

    How was the initial setup?

    It is not really complicated, if you do a previous good design. Installation is non-invasive, does not require agents in the virtual environment.It is not really complicated, if you do a previous good design. Installation is non-invasive, does not require agents in the virtual environment.

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

    The licensing is by virtual machines, start in 15, and grow in packs of 10. There is an annual support that must be contracted.

    Which other solutions did I evaluate?

    Yes. Veeam B & R and VMware SRM (along with vSphere Replication and storage-level replication) were evaluated.

    What other advice do I have?

    It is important to have clear:

    1. Required links between sites.
    2. Available network (ideal network L2 inter sites).
    3. Capacity for journaling (+/- 7%) in contingent site.
    Disclosure: My company has a business relationship with this vendor other than being a customer:
    PeerSpot user
    PeerSpot user
    Consultant at a tech services company with 51-200 employees
    Real User
    Managing the system is easy and reliable, you can choose any VM you want to replicate to your DR Site in Combination with other VM's.
    Pros and Cons
    • "Managing the system is easy and reliable, you can choose any VM you want to replicate to your DR Site in Combination with other VM's."
    • "Migration of complex VMware and Hyper-V solution. Using Zerto to replicate to azure and S3."

    What is our primary use case?

    We use the ZERTO Implementation to pretend critical VM and Groups of VM (Application Consistency) from failing. The solution with ZERTO helpy us to TEST and Failover without pane. Installaion is based on local primary site and remote desaster site with a distance of a few 100km and a bandwith up to 30Mbit.

    What is most valuable?

    Managing the system is easy and reliable, you can choose any VM you want to replicate to your DR Site in Combination with other VM's. Testing a DR is easy and well reported.

    How has it helped my organization?

    Any business unit can define it's needs for SLA and the IT department is able to follow these needs with less management and overhead. If a problem occurs (like ransomware or db errors) IT department is able to roll Back to the right point without loosing productivity of other not effected VM. So for both business and IT it is much easier to use Zerto and profit from best function and best performance in these area of replication tools

    What needs improvement?

    Migration of complex VMware and Hyper-V solution. Using Zerto to replicate to azure and S3.

    DR Solutions with less management and less space. Licensing of DR Site is not necessary until activation of VM. That are very good news for Db users.

    For how long have I used the solution?

    Less than one year.

    What do I think about the stability of the solution?

    As described above, only the WAN traffic regulation should be monitored, if it runs it works fine and absolutely stable

    What do I think about the scalability of the solution?

    More VM more bandwidth over WAN, but this is normal. In competition with other replication tools, Zerto works well and compression is fast and stable. If you want to scale order license for it and go on.

    How are customer service and technical support?

    Customer Service:

    Really fast and helpful. The documentation is a good stuff to read before calling, most of the events are well described and could be solved easily by yourself

    Technical Support:

    very fast and very good

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

    We uses before VMware Site Recovery. It is to complex and expensive at all.

    Parallel to the primary replication tool Zerto, we are using VEEAM Always On Replication Version 9.5. It works but we can't replicate in the same manner as Zerto, because this tool works with events and they are queued so you will not be able to replicate in the same way as Zerto. Also the amount of VM's to replicate at the same time is limited to the VEEAM Environment of proxies. More Proxies more VM, but also more overhead and bandwidth usage.

    It works fine for replicate a few times a day, but not in sec.

    How was the initial setup?

    If you follow the documentation you need about 20 Minutes to first run of replication. This is fast and you can choose it if you want with the trail license from Zerto by yourself.

    What about the implementation team?

    No we did by documentation and without external team.

    What was our ROI?

    Hopefully 50% less than with teh other solutions, we will have a look to it after a year production

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

    Licensing is VM based so you can buy packages or single VM. Price is not low but the power of application is high, so you will get your money back, in case of Disaster situation. You will be so fast back in production and this is very rent-able for the business units you safe from outtakes.

    Which other solutions did I evaluate?

    Yes, Site Recovery and VEEAM Always On Solution

    What other advice do I have?

    With the next generation Zerto5.5 they allow replication and production in azure, so cloud based DR comes reality.

    Everybody who looks for alternative solutions in physical sync mirroring of data (Metro-cluster) should think about business needs and ABC (Application Business Continuity) Zerto can do it and helps you to keep business online with less cost than other solutions.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    it_user80754 - PeerSpot reviewer
    it_user80754Principal Technical Architect at a comms service provider with 10,001+ employees
    Real User

    Including application license, support and maintenance, cost reductions and project non-app development labor costs, we see Zerto reducing overall project implementation costs by 20-25% and reducing project implementation time by 2-6 weeks. Farther along, DR test planning and execution is reduced from hundreds of hours to just a few hours. These are huge numbers, but with over 100 applications using Zerto, we have the track record to prove it.

    Further savings will accrue over application lifecycles as we begin to use Zerto as an operational support tool for application and data migration, escalation of new releases into production, refreshing and cloning new dev/test environments. These are all tasks that previously took hundreds of planning and execution man-hours now can be reduced to 10 or 20 hours total. For example, one app team refreshes their dev environments 4X annually. By using Zerto, the reduced downtime, planning and manpower requirements for refreshes effectively will add another 4 to 6 weeks annually for work on new application enhancements.

    See all 2 comments
    reviewer1199877 - PeerSpot reviewer
    Works at a educational organization with 11-50 employees
    Real User
    Instant data rollback, self-healing, and good reporting
    Pros and Cons
    • "I really like how you can test the failover as often as you need."
    • "I think Zerto could do better with size planning because it would be nice to analyze a server for a week and give an estimate on sizing the Journal."

    What is our primary use case?

    We use Zerto to protect our staff information against ransomware and is outlined in our disaster recovery plan. We have a DR site that we failover to if anything happens at our primary data center. We have only our core services, that we could not live without, being protected.

    How has it helped my organization?

    It is very easy to use. Almost anyone in our IT team can manage it after not using it for months at a time. As the DR strategist here, I like that. I enjoy having a fast way to bring a server back up. It will take me longer to get to my desk and log into everything than it will to actually complete the failover. 

    What is most valuable?

    I really like how you can test the failover as often as you need.

    The reports it generates are very good at showing our protection state.

    It is self-healing in case I mess up on something and need to re-sync. When you are protecting Terabytes of data, this comes in handy.

    What needs improvement?

    I think Zerto could do better with size planning because it would be nice to analyze a server for a week and give an estimate on sizing the Journal. I find myself estimating too high.

    It would be nice if I had an option to dynamically restore to any host in a cluster. Right now, if we have multiple things happen and the main host is down it will not work. 

    For how long have I used the solution?

    I have been using this solution for three years.

    What do I think about the scalability of the solution?

    We are only using a fraction of what it can do. If you add the backup function it scales very largely. I could see a hospital really finding this product useful.

    How are customer service and technical support?

    My first experience with technical support was not good at all. In the last few years, it has improved quite a bit. 

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

    Prior to this solution, we used storage mirroring and DFS syncing. Our old way used far too much storage. Zerto compresses the data well. 

    How was the initial setup?

    The initial setup of this solution is very straightforward. We were making initial syncs in forty-five minutes. 

    What about the implementation team?

    We did both, with most over the phone. Their expertise was fine. I didn't in any way feel like I was not getting my questions answered. 

    What was our ROI?

    Our ROI happened in nine seconds.

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

    I don't remember it being cheap. We started out slow, which was a good call. We found that in an event that was massive enough to cause an entire cluster to go offline we would be happy with our core services up and running.

    Which other solutions did I evaluate?

    At the time, Zerto was the only product doing this so easily. It might still be.

    What other advice do I have?

    Don't underestimate how good it feels to rollback data instantly. It makes me look like a Wizzard at my desk. 

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    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.
    PeerSpot user
    it_user373668 - PeerSpot reviewer
    Service Manager, Cloud Recovery at a tech services company with 1,001-5,000 employees
    Real User
    Continuous VM replication and ability to choose recovery point are key
    Pros and Cons
    • "Failover using Zerto is simply a one-button click, and it does everything else in restoring the VMs at a different datacenter (recovery site)."
    • "Zerto is an excellent solution for cloud-based environments, but for DIY clients who have another site to recover their systems it also works well."
    • "Adding or changing VPGs (Virtual Protection Groups) may require restarting replication."

    How has it helped my organization?

    Virtualization, and Zerto improves business continuity and disaster recovery tremendously.

    What is most valuable?

    • Continuous replication for VMs
    • Ability to choose point in time to recover from
    • RPOs in seconds
    • RTO in minutes

    What needs improvement?

    Adding or changing VPGs (Virtual Protection Groups) may require restarting replication.

    For how long have I used the solution?

    One to three years.

    What do I think about the stability of the solution?

    The product is very stable; no issues with upgrading to new releases.

    What do I think about the scalability of the solution?

    Adding additional VMs is fairly easy. Adding or changing VPGs (Virtual Protection Groups) may require restarting replication.

    How are customer service and technical support?

    Very good.

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

    Previously we used SRM (Site Recovery Manager). Zerto is much easier to set up and configure. Failover using Zerto is simply a one-button click, and it does everything else in restoring the VMs at a different datacenter (recovery site).

    How was the initial setup?

    Initial setup is fairly easy and the environment can be protected in just a few hours.

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

    You can find providers of a DRaaS solution with Zerto license fees for each VM. Zerto only sells to partners and they have a robust partner organization.

    What other advice do I have?

    The product works and does what is says. Zerto provides enterprise-class, virtual replication and BC/DR solutions for private, hybrid, and public clouds. Future releases will provide multiple destinations/locations to store the replicated data.

    Most companies have used backup software for their protection, or disk array replication. Zerto leapfrogs those data protection methods and provides a much more affordable BC/DR solution, with improved RPO and RTO.

    Zerto is an excellent solution for cloud-based environments, but for DIY clients who have another site to recover their systems it also works well.

    Disclosure: My company has a business relationship with this vendor other than being a customer: Zerto Partner.
    PeerSpot user
    PeerSpot user
    Senior Vmware administrator at a manufacturing company with 1,001-5,000 employees
    Vendor
    The top dog of DR IMO.

    What is most valuable?

    The ease of daily operations. This program takes almost no interaction on a daily basis.

    How has it helped my organization?

    Zerto has given us a sense of security. To know that we can move our production data to our DR site in minutes lets me sleep much better at night.

    What needs improvement?

    Support for Hyper-V which is on the way.

    For how long have I used the solution?

    In production for almost 1 year now.

    What was my experience with deployment of the solution?

    Absolutely none. I was replicating my first VPG in less than an hour.

    What do I think about the stability of the solution?

    Only things that I have caused myself.

    What do I think about the scalability of the solution?

    Started with 50 vms today protecting almost 300 and I have had no issues.

    How are customer service and technical support?

    Customer Service:

    I would give it an 8/10. Alot of customer service is handled through back and forth emails but once you get someone on a phone call and screen sharing the level goes to a 10/10.

    Technical Support:

    9/10

    Alot of customer service is handled through back and forth emails but once you get someone on a phone call and screen sharing the level goes to a 10/10.

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

    We tried out SRM but chose Zerto because of the ease of use.

    How was the initial setup?

    Very straightforward and I had a tech with me the whole way.

    What about the implementation team?

    Implemented in-house and once again it was a PAINLESS process.

    Which other solutions did I evaluate?

    SRM and went with Zerto so we would not have to use SAN-to-SAN replication.

    What other advice do I have?

    The best thing is that all you need is storage and vcenter in two locations and you have met all requirements to install and protect your vm's.

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