HPE Zerto Software Reviews

We use Zerto to replicate our VMware VMs. We have two data centers in our company. We use Zerto to make sure these virtual machines which are VMware are replicated in the other data centres.

We also use Zerto as a backup tool for Windows files.

Zerto is already a leader in its field. I have seen the benefit of knowing that everything is protected. We've only started a disaster recovery program in the last year after running Zerto. The business is now understanding that recovering from the traditional backup software does take a long time, and it's very complex. 

Using Zerto, I am the only department that can recover in minutes. The database team takes hours, the IBM platform takes hours as well. So time saving is what we see the most of Zerto.

Zerto's near-synchronous replication is very important. It's the reason we're still with Zerto. We collect blood in many hospitals, and some of our data centers are in hospitals with power grids that are not as good as commercial buildings. So, we do have servers that will crash. The servers are in the hospitals for latency reasons. And when a server crashes for any reason, it could be a chipmunk eating wires. We need to have another server with no data loss so that the clinics can keep going without having to do a whole bunch of data entry.

We don't use SAP HANA with Zerto, but we use SAP HANA with an Oracle database. These databases are replicated at the hardware storage level, not with Zerto.

Zerto has very little effect on our RPOs (Recovery Point Objectives). As long as we have the disk space, it works well. We currently have a one-hour to one-day RPO and are extending it to about four days based on recommendations.

The continuous replication with a low recovery point objective (RPO) is crucial for us. 

We have mission-critical applications that, if we lose data, we lose a lot of money. Zerto's low RPO ensures minimal data loss in case of a disaster.

Zerto has the ability for us to suggest features, which we do often. We do see some of these features come to life. Better alerting is something that I feel is critical. 

If you turn on the alerting of the on-prem appliances, it bombards your inbox over everything. It's too much. We had to turn that off. We use Zerto cloud analytics for alerting, and we just moved the Zerto ten about a month ago.

Some alerts, such as when one of my virtual protection groups does not have at least one day of logs configured. We find that after we do a disaster recovery failover test we recreate the virtual protection groups. Some of our junior systems admins won't specify. We need seven days of journal logs. So an alert for that would be handy.

We've been using Zerto for over eight years.

It's excellent. The product has been solid for the entire time we've used it.

We use Zerto to protect approximately 300 VMware VMs.

We have not grown Zerto in many, many years. We're likely going to double it. It should not be a problem because it's essentially almost agent-based. I feel that it can grow. We're not a very big client, so I don't know how big it can scale, but I feel that it can.

I rarely need to contact the customer service and support. The product is very good. When I have used their support, I've never had to escalate a call.

There's nothing bad about the support. They are responsive and helpful. A 10 would mean having an experience so exceptional that I would have to tell my family about it.

Positive

Zerto was deployed before my time, so I wasn't involved in the initial deployment. However, I have been involved in upgrades, which are very simple. 

I appreciate the ability to open a case with Zerto support for assistance. For our recent Zerto 10 upgrade, we also had help from Zerto Professional Services, which is a feature that management likes.

Zerto can perform disaster recovery in the cloud, but our company is not cloud-ready yet.  We do not have the governance We are still trying to figure out if we were to fail over an application, is the application team aware that they will have to pay additional funding out of their call centers. So we are at a governance stage right now of planning for recovery in the cloud.

We have two active-active data centers that replicate themselves at the VMware level. We use Microsoft Azure.

We used Zerto Professional Services to assist us with the Zerto 10 upgrade. It was a great experience. The upgrade was done in about 15 minutes for both sites. They were well-prepared and knew exactly what they were doing.

We don't see ROI in terms of direct financial ROI, as we only started our disaster recovery testing about a year ago. However, based on client satisfaction and our decision to double our Zerto licenses, we see a return on investment in terms of overall client satisfaction.

We have a licensing team that manages it, but it seems to be fairly easy to use.

We looked at Veeam and NAKIVO.

The business realized the importance of quick recovery and minimal data loss, which are the main reasons why we chose and continue to use Zerto.

From an end-user interface where you use your mouse to click, Zerto is definitely the easiest. However, for the monitoring piece, where my developers have to use the APIs, Zerto is much harder than the other tools that we've used.

Zerto's recovery is the fastest, hands down. Compared to NetBackup, which takes hours, Zerto's recovery is a matter of minutes. We also use a tool similar to Veeam called NAKIVO for non-mission-critical systems, which has a one-day RPO. Nextiva is close to Zerto in terms of recovery speed, but Zerto's interface, orchestration capabilities, and ability to run scripts make it the top choice for us.

I would rate it a ten out of ten. There's nothing that compares to Zerto, nothing that works as well as it. My only complaint about it is the alerting. There are a lot of alerts that come through, and they are legit alerts. It's excellent.

I use it for yearly disaster recovery testing.

The main benefit we see from Zerto is that it helps to meet our disaster recovery objectives.

Zerto's near-synchronous replication is important and impressive.

Zerto helps protect VMs in our environment and has improved all over RPO. 

The speed of recovery with Zerto is extremely fast. We're able to perform disaster recovery testing on dozens of VMs within an hour or even half an hour.

I like its fast recovery, fast RPO and RTO, ease of use, easy interface, ease of deployment, and that it's always available.

I would like for Zerto to improve reporting, provide more data on individual VMs and their performance, and maybe expand into backup with the ability to scan for malware or offline scanning.

I have been using Zerto for over seven years. 

I would rate the stability an eight out of ten. 

I would rate the scalability a nine out of ten. 

The customer service and support are excellent. 

Positive

We previously used Commvault. It used a lot of scripting and configuration to make disaster recovery happen, and it was slow, with a low RPO.

We haven't tried disaster recovery in the cloud rather than in a physical data center. We only use on-premises recovery.

My experience with pricing, setup costs, and licensing was straightforward. 

We previously used or evaluated other backup and disaster recovery solutions. 

We compared Veeam and Commvault against Zerto.

We chose Zerto because of its performance and ease of use.

Overall, I would rate it an eight out of ten because there's always room for improvement. 

We use it mainly for our disaster recovery, so we replicate our production VMs between our data centers.

The solution meets our high availability and disaster recovery needs.

The disaster recovery reviews itself and it has the ability to fail over within seconds and get new machines up and running on a new data center in a matter of minutes.

It's pretty easy to use. It depends on how detailed you get into the product. If you get real detailed into the product with some of its backup capabilities, it can get a little bit more detailed, for example. However, for the disaster recovery piece itself, it's it's pretty easy to use.

The near synchronous replication is effective. It works really well. The replication and the RTO, RPO times are pretty much the best in the industry.

We saw some benefits right away in that we were understanding that we were now highly available. We also started to see more and more benefits as time went on.

It helps protect virtual machines in our environment.

Our downtime and our ability to replicate happen within seconds. We've seen other products that take about five minutes. Now, we take seconds to get things back up and going. Therefore, the loss of data is virtually nothing. We've been extremely happy with that. 

It's helped reduce downtimes in pretty much any situation. We've had instances where a data center or a cluster in a data center was down or we were having problems with it and being able to have that replicated data being able to be spun up within a matter of minutes. It's significantly helped where if we didn't have that ability, we were probably looking at at least three to four hours, if not a day, of downtime. We're talking about the difference between minutes of downtime versus hours to potentially days.

With Zerto we haven't had any any actual instances where ransomware or anything like that actually comes up. We do yearly testing where we'll fail over an entire data center. While we haven't had any malicious incidents, we've had success with conceptual testing.

Zerto hasn't necessarily reduced the overall testing in our organization. We still have to do the testing. That said, it's reduced the time in which it takes to perform that testing. So, we still have our requirements to do yearly testing. However, it's at least reducing the amount of time it takes. Before, the testing would take an entire weekend and multiple departments in order to complete it. Now we're finishing our testing in a matter of hours. We're knocking off quite a bit of time with Zerto - plus hours of time in order to complete testing.

Zerto is now our resiliency strategy. We're able to replicate all of our data and be able to bring up an entire data center within a matter of minutes, which has become our go-to for our resiliency within both of our data centers.

Recently, they started forcing everybody to use a Linux-based appliance for their z/VMs. That appliance has been extremely touchy and, in some cases, problematic. However, there were Windows-based z/VMs prior, and we never really had issues with them. But now we're running into problems where certificates aren't able to be imported for things like LDPAPS and SSL. We've run into actual downtime with the z/VMs recently, which is new to the Linux app appliance. Overall, the appliances had some bugs, and they've not been as reliable as they were in the past.

I've been using Zerto for a little over 4.5 years.

There are the no real lag issues, We've only had a couple of instances where the system has been down, and wasnew since our Linux appliance install. Overall, it's been pretty reliable with the caveat that the new Linux appliance has had some downtime. Prior to that, we hadn't had any. 

Scalability's been good. There's a couple of instances where they could allow for some more local replication, however, scalability has been good.

I quite frequently contact technical support. On most things, they have been pretty good. The issues that we've had with that z/VM, those tickets can take quite a while. I have one ticket that's been open for about four and a half months now. They're still trying to figure out some of the bugs within their system, which has caused some tickets to take longer than they really should.

The quality of response has been pretty good. Maybe 7  or 8 out of 10 are quality responses. They're they're pretty good, pretty knowledgeable. Again, there are some instances where they're still learning the system as well, or there's something new, and it's a little bit odd; however, other than that, their answers are typically pretty spot on and pretty well documented.

Neutral

We used to build products by Nutanix. Their RTO times were much higher. That's about the only solution that I've used at least recently.

I wasn't part of that decision making process. Zerto had been onboarded by the time I came on to to the team here.

The deployments have been pretty easy as long as you have your network topology figured out. If you're just starting up a brand new appliance, and you're running through a setup, signing IPs , et cetera, you have to make sure that the z/VMs can talk to each other. It's a pretty easy process.

Usually, for the setup, we have the SME, which is me, and then a backup to be a second pair of eyes, however, a lot of the work is been done just by myself.

In terms of maintenance, there are updates that need to be applied. The certificate imports need to happen depending on expiration dates. There also is their key cloak integration for authentication, and that requires some upkeep as well depending on how you're signing permissions and what you're signing permissions for.

I've done redeployments myself, for example, when we switched over from Windows to Linux to z/VMs. That was all in-house. At the time when they did their very first deployment, they had used a third party vendor to assist with that. We've not needed them since. 

I don't have any visibility on the pricing. 

We're a Zerto customer.

I'd rate the solution eight out of ten. 

New users need to understand the product prior to deployment and make sure that they're taking the time to whiteboard this out. Your VRAs are going to take up a good amount of space. So users need to understand that when you're replicating data over, you are making a second copy of that data, and understand what your test scenarios are going to be. You need to understand if you need things like a test environment to actually be within Zerto since that will be taking up more space. Overall, people just be aware that the Linux appliances still have to have their bugs worked out. For first-time users, especially, I would keep those deployments as simple as possible to start.

A lot of our focus area has been around capacity planning that includes virtual machine rightsizing and then construction for failover and resiliency-type models. The other area that is important to us is looking at data in motion, data at rest, and data in transit.

By implementing Zerto, we wanted to be able to go ahead and focus a lot on workload migration and disaster recovery.

I can quickly restore data by reverting anything with more or less a nightly backup. I can pretty much have the data through recovery checkpoints, and each of the checkpoints can only be around five seconds apart.

When I need to work a lot with VPGs, it has a lot of capabilities for that. Monitoring is also very important for us. We do work with Splunk, and I am looking a lot around for logs, metrics, and traces. The capabilities that I get are system throughput, and CPU and RAM input/output.

I have used Zerto for immutable data copies. I have pretty much followed a 3-2-1 strategy. We have three copies of production data and two backup copies. We have two different media and then one off-site copy. It has this offering there.

It's helping very much in terms of the malware. They have a ransomware protection capability.

I have used other solutions jointly with Zerto. What is happening is that they have a focus on isolating and locking with a cyber resiliency vault, and what I have been doing more or less around the vault is working with the Delinea Privileged Access Manager solution. So, some areas have intersections with other tools in our stack. I would love to continue seeing more use cases out of Zerto so that I do not have to defer this anywhere else.

It has enabled us to do disaster recovery (DR) in the cloud, rather than in a physical data center. I think of it as a cloud migration tool. Having DR in the cloud is very important for our organization. I use it with Microsoft Azure.

With Zerto, I have seen five-second near-synchronous replication, so there are thousands of checkpoints in one day, and then afterward, I can have a periodic backup. I can space it out between twelve-hour snapshots. We can have one to three checkpoints per day. I can recover to the state seconds before any sort of attack, and I can utilize Zerto's in-built orchestration and automation. I could easily fail over the entire site without any sort of disruption. Those are the things I see very much in terms of positives. There is a lot of information that it can gather with synchronous replication. The other thing is that I have seen other disaster and backup service offerings, and they very much focus on getting a container image installed or some sort of binary file and then deployment from there afterward.

I find it easy to migrate the data. Once somebody understands how Zerto works, particularly around areas for analytics and automation, with the reference architecture, they will be able to quickly deploy it.

I see a lot of visibility in terms of proactive management with SLA monitoring, run metrics, and other things. We are able to test infrastructure using live and personalized data. It, in turn, becomes very much of a team effort.

Zerto provides complete visibility in terms of storage and consumption data. We get to know the capacity and application volumes. I can also address compliance aspects, such as PCI DSS which is important for us as part of the RPO.

They have an intelligent, predictive infrastructure, so I can just pretty much determine the required compute storage and other server networking resources, whether it is on-premises or in the cloud.

It also saves recovery time. We pretty much monitor that information. In terms of time savings, we are able to ensure that we can set up a backup quickly, figure out the integration details with the use of APIs, and meet our requirements around client security. Afterward, there is the cost consideration. Better documentation on the restoration process would be helpful.

Ransomware is one area where we are using Zerto. If we were utilizing another solution, that might have only been AWS-specific, and we might have not gotten much assistance in proceeding with their public cloud vendor as a result. We might have to figure out what we can do around working with an XDR or another mode of ingesting that data for any vulnerabilities and how to focus on encryption thereafter. If we were to consider another vendor, some of them may not have support for Azure. They might be AWS-focused.

Zerto has helped to reduce our organization's DR testing. We can create failover tests seamlessly, and we can do this routinely. We are able to save time and look at how we can discern between RTO and RPO.

Zerto has not reduced the number of staff involved in overall backup and DR management. Our team size is still roughly the same. We have not seen our headcount change as a result, but we do not need to hire external consultants to support a project.

If I wanted to focus on operational recovery, which may be recovering instances in the database with a 15-second data loss, there are systems administrators designed to take care of that. With Zerto's offering, someone can utilize the Zerto solution as opposed to depending on any sort of manual human intervention.

The continuation to the public cloud has been especially helpful where I can pretty much work with things like hosts and clusters as part of the data center.

Zerto has near-synchronous replication. I like it very much. They had an acquisition and are now a part of HPE. I see it very much as a robust solution.

A slight disadvantage of Zerto is that it requires the Windows Server operating system as the base OS. Over time, I would like to see more offerings in that regard. There should be more deployment options other than just the Windows operating system.

The implementation is very quick and painless, but it would be good to have more information that is not case-sensitive. In the server portal, some fields are case-sensitive. It took some time for me to understand initially.

If a VPG goes down and an application host is not responding, I want to have a little bit more flexibility to automatically point the recovery to other hosts. I would like to see a little bit more flexibility to automatically sustain two applications in their most optimal state. If the VPG is going down and any of the recovery hosts are in maintenance mode, there should be a way for maximum flexibility so that it can automatically utilize Zerto to point that recovery to other hosts.

I want some more information about how to work with bare metal drives. I have been doing some work in capacity planning for using MDM and FormFactor cable and then looking at system throughput, App latency, and a lot of scripts in Linux. I would like to have a little bit more information for anybody needing to work with bare metal drives.

I have been using Zerto for several years.

I have not seen any service disruption that impacted us. If anything like that were to occur, they would communicate it ahead of time.

It is scalable. We have more than 20,000 endpoints.

I do reach out to Zerto, and if there are any questions, we have a ticket in-house, so everyone is working on reviewing it at the same time. I would rate their support a nine out of ten. There are no negatives.

Positive

We were not using a similar solution. 

By bringing in Zerto, some legacy work has been discontinued. There is operational recovery, application migration, and application cloning. These are the three areas where Zerto has helped us.

We have a cloud version. It is a public cloud.

Its initial deployment was straightforward. I have been trying to focus on capabilities and encryption and how a long-term retention repository works, at least looking at the data capture. Another thing is utilizing some information with APIs and cloud scaling. I have broken down a lot of my use cases, and we have Zerto on the public cloud. Based on that, I was able to figure out how to work with features like compute as well as storage.

Its implementation took about two to three months. In terms of maintenance, it requires maintenance. We focus a lot on metrics such as RTO and RPO monitoring. Somebody can also put it in maintenance mode operation.

We had Zerto representatives, and we also had work done in-house. 

I work with a team. Other colleagues are also involved in the effort. We have a team of around ten employees.

We did look at a few other vendors' offerings, but we decided on Zerto. Our organization has a partnership with them, and the other thing was that there were a few industry events, and they were able to effectively make a pitch. Their demonstration was very effective. It was also something in which the client was interested in.

To those looking to implement Zerto in their organization, I would advise creating use cases of their own and then trying to see how Zerto effectively helps them. A few areas where they can work are gathering information with the virtual machine rightsizing and being able to go ahead and create resiliency models. Afterward, they can look at compliance. For us, PCI DSS and locating the public cloud environment being used, which in our case was Microsoft Azure, were important. After they have created use cases on their own, they can come to Zerto and see how they are able to effectively handle it. If they are able to think through what they need, they can come up with specific questions and then get Zerto to effectively deliver.

I would rate Zerto a nine out of ten.

We're a managed services provider that uses Zerto primarily for disaster recovery as a service. We offer Zerto as a DR option for our clients. Our customers in the Bahamas need a DR option outside of the hurricane belt, so we have workloads throughout the world to ensure our customers have somewhere to restore from. 

Currently, we run Zerto in a vCloud environment. All of the services are brought up in a vCloud environment. It saves us from having to constantly buy equipment. The vCloud environment enables us to spin up an environment as needed instead of having unnecessary hardware sitting there using resources.

We haven't had any major disasters that required us to use Zerto, but we perform two or three live failover tests with clients. Everyone seems to be pretty happy with the product and the turnaround time.

It's all about client satisfaction. They may not understand the underlying tech architecture, but they want to know how fast we can bring the environment back up. We can achieve fast restorations and restore sections if needed instead of the entire environment. It's been a great experience for us and our customers. 

The RTO/RPO times are fast. The speed is probably the biggest selling point for us. It's not live replication, where you have two sites up at the same time, but our customers like the fact that they can restore within seconds. 

It takes them nearly to the last point of connectivity, so it's seamless and easy to operate. It's easy to operate, and customers feel that they have a level of control. With some platforms, most things need to be done by the provider, but customers have a management platform in their environment. They can run tests without our direct involvement. 

Another advantage is the ease of use. You can click through instead of typing in the code. It's all already scripted down to the network adjustments within the VMs and the timed delays for servers that need to come up in sequence. Overall, it's a good package for us to use. We started using it in about 2018 and haven't looked back.

We have an issue with the management platform because we don't always upgrade to the latest version, whereas the customers tend to constantly upgrade. Sometimes, we lose connectivity because something isn't supported. 

For example, we have VMware version 7 update 3. This morning, a customer upgraded it without informing us. It's their responsibility to notify us because our environment is large, and we don't update every time a new version comes out. It's somewhat of a pain. 

In addition to data, the other thing would be the hardware versions for VMware. I finally found a proper support matrix, but we ran into a few problems in the early stages. I don't know how to address this, but maybe when the version is going to update, the client could get a prompt saying that the cloud location is not on that same version. It would be a more efficient way to tell them instead of trying to figure it out. 

It would also be nice if you could update without having to download a new installation file for Zerto Virtual Manager. Within the app, it could prompt you to install and perform the installation from within the application. Generally, it's relatively easy to use, but it gets a little complex when customers have special network requirements and need to customize how long they want the save points to be retained. We need to work with the storage team on the backend to see what makes the most sense for the client. 

I have used Zerto for about five years.

I rate Zerto support nine out of 10. I haven't had any serious issues aside from the problem with version differences between a client's environment and ours. That is just a matter of striking a balance with the clients. An IT environment can't update too frequently because you don't want a change to break something. Unfortunately, you can't stop the customer. 

Support has been good about helping us troubleshoot those issues. It's easy to run a diagnostic tool and get the file. It's difficult to pull down a diagnostic file in some solutions because you need to do it via a command line. With this, it's just a couple of options you select. You run a diagnostic, save the file, and send it. 

Positive

I work on the cloud management side, so it was already deployed. I wasn't involved in deploying the cloud portion. However, I installed all of the virtual management for customers and set up the environment for them. That part of it was easy. It was a click-through thing. Most of the time, we'll guide the customer through the process, so they can see it as well. We show them the step-by-step process of performing the updates. 

Zerto is like a Ferrari. It's very fast but not the cheapest solution. You're paying a high price for quality and the assurance that you will have the environment up and steady. 

There are tradeoffs, too. Our clients spend money on licensing but save on equipment. The customers could either buy a bunch of equipment or pay for Zerto licenses. That's where we come in. We provide you with a cloud solution that doesn't cost all this money upfront. The prices could always be better, but we don't complain so much about it because the savings come from other places.

I rate Zerto nine out of 10. A lot of people are trying to convince us to look at VMware backups instead, but I don't see the urgency because Zerto works for us. I don't see anything on the market that can restore in seconds as opposed to minutes or hours. For us to switch, we would need something that beats Zerto. Right now, nothing beats it.

We use HPE Zerto Software for disaster recovery, resiliency, and peace of mind.

It provides peace of mind, it allows us to feel confident knowing that the data protection platform is in-place and allows for rapid recovery in the event of data integrity failures, or platform disruptions.

The contextual help and simulation of HPE Zerto Software are the most valuable features. HPE Zerto Software's continuous data protection or CDP is critical for our organization because it allows us to recover within seconds to minutes, and the journal allows us to pick a point-in-time recovery. The journal allows us to recover from a point in time before an event occurred.

I cannot think of any ways HPE Zerto Software needs improvement, as I have used it at a previous company as well, and it is a reputably reliable platform.

I have been using HPE Zerto Software for over several years.

I have not experienced any downtime, crashes, or performance issues with HPE Zerto Software; it is a reliable platform and it is very well-engineered.

HPE Zerto Software scales with the growing needs of our organization.

HPE Zerto Software's customer service and technical support have been fantastic.

Positive

We used Veeam as our previous solution and we switched to HPE Zerto Software to ensure that we had a mutable backup, as well as synchronous replication.

I don't perform setup and initial configuration, another team does that.

That amount of downtime would cost our organization in the millions.

I don't operate in this vein of the business.

Veeam, Rubrik, ASR.

HPE Zerto Software's recovery speed is very fast and reliable compared to the disaster recovery solution we used before. I would rate HPE Zerto Software overall as a ten; it is a fantastic product.

We use it for disaster recovery and analytics.

We use Zerto to help protect VMs in our environment. We are also using it for our Virtual Protected Group or VPG.

By implementing Zerto, we wanted disaster management, especially for our data. We did not want to lose data unnecessarily.

Over time, I keep seeing different benefits of using Zerto.

In terms of ease of use, Zerto is easy to use.

Zerto has near synchronous replication. It is okay. It has been easy for me to use.

Zerto is faster than other recovery solutions for real-time automation.

Zerto makes it easy for me to navigate and move my data to the cloud. It has had a positive effect.

Zerto has helped reduce downtime. There is about 25% reduction.

Zerto has improved the data recovery time. It has saved me time. It is faster than what I was using before. Zerto has saved me a lot of time, but I do not have the metrics.

Zerto has helped reduce our organization's DR testing by 30%. It has had a positive effect on our IT resilience.

I like the automation of transferring data in the case of any disaster to our VMs. It is also easy to use and fast. 

Its price is a little bit on the higher side. Other than the pricing, I do not have any areas for improvement. I am enjoying Zerto. Everything is working the way I want it.

I have been using Zerto for the past two years.

Its stability is okay.

Its scalability is okay. As we keep having more customers, we might have to scale it, but for now, it is good.

I contacted them once, and I got a quick response. They are fast. I wrote to them, and I quickly got a response. The response was timely and effective.

Positive

I was using Microsoft Azure backup before. I migrated to Zerto. Zerto is faster.

It is deployed in the cloud. Its deployment was not too easy and also not difficult.

Like every other team, it took us some time to get it going. It is not as easy as one, two, and three. It took us about one hour to get it going. That is why it is not too easy, but it is also not difficult.

After installation, we took the entire day because we were trying to make sure everything worked fine.

So far, I have not done any maintenance for Zerto.

We had two people involved in its deployment.

Zerto is a little bit on the higher side in terms of pricing. It would be better if they had a pay-as-you-go package.

I got a review from a friend and decided to give it a try. She asked me to give it a try to see how I could recover data fast and do other things without wasting time. I was looking for these features, and I got them with Zerto.

I would advise knowing what you want in the software and why you are going for this software. If you want fast data recovery software, you should go for Zerto. I have been using Zerto for two years, and I have not had any reason for regret. New users who are going for Zerto would not regret their decision.

I would rate Zerto an eight out of ten.

We are using Zerto as a disaster recovery solution.

We utilize Zerto for three replication scenarios: on-premises to on-premises, on-premises to cloud, and planned cloud-to-cloud replication.

Zerto is easy to use and implement, especially when performing a failover.

Zerto's near synchronous replication is valuable for our SQL database.

The benefits of Zerto were immediately apparent. After implementation, we quickly realized we were protected against any disaster. Zerto also provides visibility into the health of replication, allowing us to identify and address any potential issues.

Since implementing Zerto, we have observed a positive impact on our Recovery Point Objectives, which have been reduced by half.  Zerto's ability to easily group servers by application and configure protection groups streamlined our processes. Moreover, Zerto's support for on-premises to cloud replication is invaluable. We've leveraged this capability to replicate all systems to the cloud, establishing a robust disaster recovery solution. Zerto has proven to be an effective cloud migration and disaster recovery planning tool.

Our Recovery Time Objective determines how quickly we can restore our infrastructure. Zerto has been instrumental in reducing our RTO by enabling rapid recovery in any disaster recovery scenario.

Zerto has significantly reduced our downtime. For example, some servers have a recovery point objective of just five seconds. During disaster recovery tests conducted last year, we recovered 60 servers within eight hours, including server delivery, startup, and operating system verification by our team.

Zerto is our primary tool for achieving all disaster recovery objectives.

Zerto is a flexible and resilient business continuity and disaster recovery solution. Its industry-leading replication technology enables seamless data protection across cloud, on-premise, and hybrid environments.

Another valuable feature is the failover capability. Unlike many other tools we tested, Zerto allows us to perform a disaster recovery test without risk to our production environment.

Zerto's current reporting capabilities are insufficient for our needs. We require detailed reports to analyze the performance of our environments. To achieve this, we have developed a custom reporting solution using Zerto and other tools to thoroughly assess VPG configurations and overall environment health against specified parameters. Unfortunately, Zerto does not natively provide this level of reporting functionality.

I have been using Zerto for seven years.

Zerto is highly stable, and I do not recall encountering any crashes.

Scaling Zerto is easy. We just need to add additional virtual/appliances servers.

Zerto provides excellent support, but response times to our issues can sometimes be a concern, possibly due to the size and complexity of our environment.

Positive

We currently utilize both SRM and Zerto, but SRM's replication capabilities are limited to data centers, while Zerto offers additional cloud replication options. Unlike SRM, which is exclusively designed for VMware infrastructure, Zerto is compatible with other virtual platforms, providing greater flexibility.

Zerto is easier to use than SRM.

The initial deployment is straightforward. We only need to deploy a few servers to build an environment and start to replicate.

Deploying Zerto in a single region required three months. One contributing factor to this timeline was the time-intensive process of collecting Virtual Recovery Appliances and deploying them across 500 ESXi servers. A team of ten architects and engineers was dedicated to this project.

The implementation was completed in-house by my team and me. As the architect, I oversaw the project's planning, construction, and deployment. We consulted with Zerto to identify potential areas for improvement.

Compared to other options like SRM, Zerto is a more expensive solution, making it primarily suitable for larger organizations. Smaller and medium-sized businesses might find Zerto's cost expensive. While Azure Site Recovery is free for users of Azure cloud services, Zerto offers a broader range of features.

I would rate Zerto nine out of ten.

Our organization takes a unique approach to disaster recovery testing, conducting 15 tests annually to meet policy and audit requirements. Zerto is the cornerstone of our DR testing strategy, enabling us to validate between five and seven applications in each test.

Zerto requires ongoing maintenance and a dedicated person monitors it daily. However, we must still test and deploy updates into our production environment.

Potential users should be knowledgeable of virtual environments and clearly understand their disaster recovery needs, including the required replication type, desired recovery strategy, and whether Zerto aligns with their specific requirements.