Zerto Reviews

In the past, we were predominantly using Citrix Hypervisor in the Hyper-V shop. Now that we've moved to VMware, we utilize Zerto to move those VMs from Hyper-V and Citrix Hypervisor over to VMware.

We're also looking at utilizing it for our DR site to be able to push up those VMs to the remote site in the case of a DR situation.

Zerto improved our organization by giving us flexibility back with migrating VMs, and I look forward to the future when we utilize it more for DR situations.

The feature I've found most valuable so far has been the ability to migrate the VMs from Hyper-V and Citrix Hypervisor. It's made our migration seamless. In the beginning, we were looking at freeware tools, and it was just a massive headache. Zerto solved a lot of the roadblocks that we'd run into in the past.

We've been able to set up a set schedule of moving certain VMs on certain dates, and we've been pretty confident that it's going to go smoothly without interruptions.

When you compare the ease of use of Zerto with those of other solutions, Zerto is much easier to use. It's idiot-proof. You don't have to be super technical to be able to be successful with the product. This is nice because you can delegate some of the tasks to the service desk. For example, you could have them handle the migrations, which would free up your engineering team to be able to spend time on more important projects.

Zerto helped reduce downtime every week. We have VMs that run in Hyper-V every week, and at night, we shut them down and migrate them over to VMware. The whole process takes under an hour, so these VMs are only offline for maybe an hour at the absolute most, which has been really helpful.

I believe 15 minutes of downtime is equivalent to a million in cost. So, it would probably cost our organization four to five million per hour of downtime.

I had to have my colleague contact technical support because we had an issue where VMs in VMware were getting blocked, and we weren't able to delete them.

The company as a whole has been using it for about six months now, and I've been using it for three months since I joined the company.

I've been pretty impressed with Zerto's stability. I haven't had any weird issues with the UI or with the migration aspect of it. It's been pretty rock solid.

Since I started, we've more than doubled our server capacity, and Zerto has been able to keep up just fine. So, it's definitely scalable, and we're looking to increase capacity by another 25% or 50%. I'm pretty confident that Zerto will be able to keep up with it.

I had to have my colleague contact technical support because we had an issue where VMs in VMware were getting blocked, and we weren't able to delete them. The whole issue was resolved in less than three days, which means that the technical support is probably pretty good to be able to get the issue sorted out so quickly.

I've tried to use Veeam for migration, and it's not really built for that. There was also a freeware solution. It worked okay, but we tended to run into some weird issues, specifically with EFI and regular BIOS VMs; these VMs weren't really translating properly to VMware.

I've been told that when they originally got the quote, it was a little bit of a sticker shock. However, now that we've actually been using it for six months, I've been told that the investment was well worth it.

On a scale from one to ten, I would give Zerto a ten.

Zerto runs on a Windows Virtual Server and we have it installed at two sites. There is the production site, as well as the failover DR site.

We use this product almost exclusively for disaster recovery. It is responsible for the automated recovery of what we deem to be our mission-critical servers.

In terms of its ability to provide continuous data protection, this is a product that I trust. We test it quarterly to make sure that what the dashboard is telling us is correct. But, I've used it long enough to know that when I see the dashboard telling me that the virtual protection groups (VPGs) health are all green, then things are working correctly. Our average RPO is usually somewhere between three and 10 seconds.

We used to perform a disaster recovery test once a year, and it was painful because everything was manual. Now that we do it quarterly, we're able to provide management with reports of the tests, which not only makes management happy but also makes various governing bodies happy. We're a financial advisory firm, so it's the SEC that oversees us. That said, I'm sure this holds true in many industries. It allows you to have the reports to prove that you've done the tests. We don't have to ask them to take our word for it.

When we need to failback or move workloads, Zerto has absolutely decreased the time and number of people that are required to do so. For example, if I just want to test and prove that the network is up, it's something that I can do by myself. If I want to have people log in and test applications and stuff like that, I would need additional people. However, it has a built-in test function, so it will create a complete test network that you can run workloads on to show that the tests are successful. Afterward, you can delete the network and you're back just running, waiting for the next time you want to do that. In a situation like this, using Zerto saves eight hours or more and I can set it up and test it on my own unless I want people actually testing applications.

Thankfully, we have not had to use this product to recover from a ransomware attack or other disaster, but it would absolutely work in that case. By replicating the data, if ransomware were to hit the production side, it most likely would not also lock the disaster recovery side. This means that we would certainly be able to bring it up from there. Alternatively, it lets us pick points in time, so we can just go back to the moment in time before the ransomware happened. In a situation like this, I can't say that it would take fewer people but it would take fewer hours.

The most valuable feature is the automated failover, as it allows us to get the essential servers up at our DR site with little intervention.

Zerto is extremely easy to use. You set it and forget it.

It has a nice graphical interface.

The reporting could be improved in terms of the reports that you can show to auditors to prove that you have done the testing. I provide the reports that it generates now but, it would be great if, at the end of a DR test, it would generate a report of everything that Zerto did.

This would include details like what systems were up. Currently, that's not how the report reads. You would have to be an IT person to read the current reports that it produces. I would like for them to be the type of reports that I can put in front of an auditor or the president of our firm that would make sense to them, without me having to interpret and explain the results.

We are in our seventh year of using Zerto.

Stability-wise, this solution is rock-solid. If it fails, it's not going to be Zerto that fails. It's going to be either that your storage has failed or the bandwidth, or connectivity, is not there. I don't see a way where Zerto would be the culprit in a failure-type instance.

Our company is fairly small and the entire firm relies on it. That said, only one person actively uses it. We have three or four IT staff but Zerto has always been my responsibility.

In terms of scalability, I bet it would be no issue whatsoever. It's licensed according to the virtual machines that you want to protect. The only limitation of the scalability would be how deep your pockets are because it's going to be license costs.

We're a registered financial advisory firm, and we are growing. In the past year to 18 months, we have grown from approximately 52 employees to 70 employees. Everybody relies on it because if we have a disaster recovery type of situation, then everybody is going to expect to be able to work.

It is still a very small number of IT staff, so I can see that as we hire more IT staff to support a larger user base, we will certainly have more users.  At least, I hope not to be the only one responsible for this solution as we grow.

I would rate the technical support a ten out of ten.

Prior to Zerto, we used VMware Site Recovery Manager (SRM). We switched because it requires a lot of manual upkeep, and there is no automation involved unless you write the scripts. There are lots of freeware sites where you can download scripts, but aside from that, we were spending a lot of time manually writing scripts and maintaining everything. This was really counterproductive for the amount of time we had available in a day.

Essentially, SRM was replaced because of better interface automation and ease of use. 

The setup is very easily done because you tie it into your VMware vCenter. When you put in your credentials, it will recognize everything on your networks. It will recognize storage, whether it be cloud-based or as in our case, at another data center. Once you have those defined, it's just a matter of creating groups that you want to recover, server-wise.

The reason that you would want to do it in groups is that you can set it up in the automation such that it will bring up groups in a certain order. That way, you have a network where the domain controllers come up in the first group, and you can automate stuff from there.

Seven years ago, when I first started to use it, I found it more difficult. I wouldn't say that it was complex but they have certainly made improvements over the years. Where it stands now, if I had to set it up from scratch, I could probably do it in about an hour. Of course, that is because of the way I know the application but in terms of how they have changed the setup, it is certainly more user-friendly than it was compared to where it started.

I remember running into a couple of issues during the deployment, and I contacted their support. They were fantastic and helped me get through it. They made sure that all of my questions were answered, and that it was up and running how we intended it to be used. A lot of it probably had to do with me being a novice at that point, in terms of using the application.

It was a multi-site deployment, with a production site and a DR site, with dedicated storage for each. We have changed the storage that it uses over the years and if I had to do it again, I would use another vendor for storage. A lot of the issues that we ran into were related to the initial storage that we used, as opposed to Zerto issues, even though it was Zerto support that helped me fix them. 

Overall, the deployment was fairly easy. Not because everything went great, but because of the combination of the application being pretty well-written and the support. I would rate the deployment an eight out of ten.

I deployed Zerto with the help of a consultant, contacting support as we needed to. The consultant was NetGain Technologies and they're based out of Lexington, Kentucky. Their service was phenomenal and I would use them again in a heartbeat for this type of deployment. Ultimately, any issues that we ran into boiled down to some issues with the storage we chose to run it on.

I am responsible for the maintenance. 

We have absolutely seen a return on investment in terms of the manhours that have to be put into maintaining and testing this type of product. Thankfully, we have never had to use it in a true DR situation. However, I can guarantee that if something were to happen, even beyond the manhours and ease of automation, that it would pay for itself.

Our network infrastructure runs pretty smoothly most of the time. That said, Zerto has helped us to reduce downtime by approximately 20%. It is difficult to equate this with a monetary value because we have to consider what happens when a client misses a trade or cannot get a hold of their portfolio manager.

If it were an outage of a couple of hours then the person might pay a little more or a little less for a stock that they were trying to purchase. Overall, however, it is difficult to estimate. We aren't a day trading-type firm, so ultimately, I'm not sure that a short outage has any effect on our revenue stream whatsoever.

As a small company, we own the smallest license that Zerto offers, which is 15 VMs. I've not had to contact them or my reseller about purchasing additional licenses or to find out how much they cost.

We spoke with VMware to see what their pipeline was for upgrades or changes to Site Recovery Manager and we also looked at both Cohesity and Rubrik.

I like the separation of the software and the storage, whereas some of those other products are all-in-one. You're buying the software and storage together on the same platform. This means that the scalability would be different.

Sometimes, this is a case of adding shelves for storage. In that situation, for example, you have to start taking the data center rack space into account. Whereas with Zerto, it lets us build upon hardware we already had, even though we use dedicated storage.

Version 9 of this product is out. However, we have not yet upgraded. We're not leveraging the cloud the way a lot of companies do these days, and I know from the release notes that I've read that most of the new features are related to the cloud. There's not a lot of research and development being done on physical data centers anymore.

At this point, I'm very happy with where the product sits for my network. We are now just starting to move things to the cloud, which will take place over the next couple of years, so my assessment in this regard may change in perhaps a few years.

At the moment, we don't have plans to use it for long-term retention. We keep about three days' worth of data in Zerto and then it rolls off. We have other systems in place for long-term retention.

My advice for anybody who is looking into implementing Zerto is to do your homework. In the end, this product checks all of the boxes and it's the one that I would go with.

In the way that we use this solution, which I know is not how everybody uses it, we have storage that is specifically used for Zerto and two data centers. The way it works in that scenario, as long the bandwidth is there, meaning some sort of dedicated circuit between the two sites, it's flawless in my opinion.

The biggest lesson that I have learned from using Zerto is that disaster recovery doesn't have to be a giant pain. I certainly used to look at it that way in the past.

I would rate this solution a ten out of ten.

We've used Zerto for file recovery and entire VM recovery.

Having a fast recovery time for both of our use cases is invaluable to the business. 

The ability to form our backups automatically during the day has saved us, more than a few times. 

My impression of Zerto’s near-synchronous replication is very positive. It gets the job done. 

Near-synchronous replication is very important for our organization who use a lot of different versions of files across environments and database changes. It's what we do every day and having the functionality of near-instant recovery on entire virtual machines and files is a blessing. 

We use Zerto to protect our VMs in our environment. We do daily backups with a different backup management software and having the ability to recover data in under ten seconds has been helpful.

Speed of recovery has been very effective in getting our information back as fast as we're able to get it. The daily backup solution that we use alternatively only allows a single backup versus having continuous backup replication with Zerto, it's a no-brainer.

I would like to have more granular notifications for jobs and workloads within the applying case application.

We have been using Zerto for around sixteen months. 

It's pretty stable. The company itself has been around long enough to know they're not going anywhere. The number of clients that use them on a day-to-day basis speaks for itself. 

For our environment, scalability does a great job with how it is. It can handle scaling. 

Zerto technical support is some of the best around. I know when I reach out to them over the phone or via email, they are there quickly and offer great support. 

I would rate them a ten out of ten. Every time I have to call them, they get something ready, very fast, and our issues are resolved quickly.

Positive

We still use Veeam.

We chose Zerto because when we started our path with GreenLake, we began looking into other backup utilities and Zerto was highly recommended. After we saw a product demo, we were sold. The demo sold itself very well.

Once the VPG is configured, the automation for backups happens on its own. There's nothing else to do. You can monitor but until you need to recover the files, there's nothing else to do. Zerto is very simple. We enjoy using the product. 

The main difference between Veeam and Zerto is that with Zerto, we can get our near-instant recovery window to pull entire virtual machines back from the brink of failure. We might be able to implement more recovery windows for Veeam but from a data storage perspective, Zerto does a great job with deduplication.

We had a third party enable our Zerto configurations. They did a great job. The same VPGs are still running today. 

We used an integrator for the setup. We had a good setup. They walked us through any issues we had after the setup. 

I would rate Zerto a nine out of ten. There is a network issue that my team is still trying to figure out. Once we take care of it, it'll be a perfect ten. 

Zerto should be our primary backup solution but until we can get the network issue resolved, it is relegated as a secondary source. It still does its job. We've used it multiple times for specific cases, and it's always passed with flying colors.

We are replicating all of our production VMs to a DR site. We also have another offsite vCenter that we are replicating to a DR site for protection and eventual testing.

It makes me feel more comfortable that we have something to fall back on in case of a disaster. We are a large insurance company, so we have a lot of different applications and SQL Servers. We never had a disaster recovery site before, so this will protect us in the event of a disaster.

A good, valuable feature is using the preseeded LUNs, when deleting a virtual machine. Then, I put the VPG back to keep track of where I was at, so I don't have to replicate everything. Instead, I just preseeded LUNs since it needs less replication time.

It is fairly intuitive and easy to use.

You can go back fairly quickly. You push the button and there you are.

I need to get up to the latest version so I can move my journals to a particular LUN, saving them with a particular storage altogether, rather than with the virtual machine. This is not available until I upgrade, and I need to upgrade all my hypervisors. This would be something that would be nice to have if it could be used on older versions.

I have been using Zerto for almost three years.

It has been stable. We have had glitches between our site and DR site. When the MPLS comes back up, Zerto just kicks right back off, doing what it needs to do.

As we have been growing more VMs in production, I have still been adding to Zerto. So, I haven't had any problems with the amount of VMs and everything that Zerto can handle.

I haven't really had any problems with support. Most of the time, when calling support, I find the answer before they call me back. Or, they will send me an email, and say, "Here, try this."

I would rate the technical support as nine or 10 (out of 10).

Positive

We didn't previously use another solution.

It provides us with a safety net.

We evaluated RecoverPoint, which was very difficult to set up. Even as a test, it was hard to set up. With Zerto, all you have to do is deploy the executable and start setting things up. So, it was very easy. Then, I insisted that the company buy Zerto for me.

RecoverPoint was difficult to set up and use. It wasn't as menu-driven as Zerto. 

We really haven't done any recovery or rollbacks. We are getting there. Later this year, we will be doing those types of failover tests, rollback tests, etc.

We haven't done DR testing. That will probably be done in the next three months.

I would rate Zerto as 10 out of 10.

We use it primarily for backup and recovery of individual servers and databases. We also use it for long-term retention.

It helps us

• achieve our RPOs
• conduct successful DR tests
• provide functionality for some of our key, critical customers.

Fortunately, we haven't gone through an unplanned DR situation, but if we were to go into one Zerto would be the top technology that we would use to recover. We would expect it to function as designed to get everything back to working as normal. Otherwise, obviously, it would be a big problem for our company. Zerto is a critical, core piece of infrastructure for the IT infrastructure team. I estimate it would save us hundreds of thousands of dollars in a DR situation.

In addition, when we need to fail back or move workloads, Zerto decreases the time involved. It's hard to quantify how much time it would save us because we haven't compared it to other DR products. But if we were to use our in-house data protection backup solution or our storage solution, Zerto would save weeks of man-hours when it comes to setup, compared to those other solutions. And it could save minutes in terms of the recovery point objectives.

The instant recovery at DR locations is the most valuable feature. We're required to do periodic DR tests of critical databases, including Oracle and Microsoft SQL. We have recovery point objectives set for specific databases and we need to be able to achieve them. Zerto helps solve that business problem.

Zerto is also pretty simple and straightforward when it comes to ease of use. There were no big surprises.

I would like the ability to monitor the performance of some specific components. Right now we're having an issue with local and remote replications with some of the VPGs. Being able to look at individual VPG performance would be helpful. 

Another thing that would help would be a recommender, or some type of tool that says, "Hey, you're not conforming to best practices." It would do a conformance or compliance check to tell you if your VPGs are set up according to best practices and whether your Zerto clusters are set up optimally. It would see if you have HA enabled and whether your alerting is turned on.

Another area for improvement is alerts. We're getting so much noise right now in the 8.5 version. The problem is that we don't know which are the ones we need to act on. We don't know which ones are severe versus those that are informational or notice or debug. They have told us that when we upgrade to version 9 we'll be able to tune some of the alerts. That type of alert tuning, where we can get just the emergency and error alerts, would be helpful, while not necessarily tuning out the informational or notice or debug alerts. If alerts could be channeled to a syslog server where we could filter and see which alerts are the priority that would be an improvement.

We have a network operation center and for us to operationalize this tool with them, we have to be able to deliver each alert along with an action plan for it. That way they can take the appropriate action if Zerto has some type of error. It would help if the alerts didn't just fall on our storage and data protection team. If we could transfer some knowledge and have other level-one teams look at some of the more basic Zerto alerts and try to resolve them, that would help.

I've known about Zerto for several years but I've been actively using it for the last two months.

The stability is pretty good. I haven't seen the software itself break, or the services stop for unknown reasons. 

We did have an issue with a VPG the other day, where it went belly-up, and we had to rethink and do a bunch of baselines. So some type of health monitor that shows both the servers and the VPGs would be helpful.

I haven't worked with the scaling functionality because we only have it in our two major data centers. But I think it would be pretty straightforward and simple to set up scaling.

Currently we're protecting about one petabyte with Zerto. We have some room to grow still with Zerto.

Much like with any technical support—and this is true whether you're talking about IBM, Microsoft, Dell EMC, or any of the big tech players—their level-two guys are definitely good, if you can get one of them. But the level-one guys seem not to be as good. Zerto was acquired by Hewlett Packard Enterprise and it shows with their level-one guys. They're not as vested in the product. All the level-one people who were vested in the product probably left. So a lot of the level-one guys aren't very technical. 

We oftentimes have to work with our technical account manager to get cases moved up to level two. Once they're there, they seem to get some movement, which is good. And, obviously, their level-two support team in Israel is very good.

Positive

I was not part of the initial installation, but I've heard that some of the initial pieces are straightforward. Where it gets complex is that I don't know if it was set up according to their best practices.

The pricing follows normal industry standards.

In a previous company, I was involved in the evaluation process that ended with choosing to go with Zerto.

Zerto sits on top of a lot of other technologies. It's like a "Layer 3" for lack of a better term. Some of the other solutions that are "Layer 2" can be more attractive, solutions like Commvault, Rubrik, and Cohesity. They're able to do more native operations at the OS level, like replication. They have more hooks into the operating system to enable you to do that.

However, Zerto's user interface is good. It's simple, it's straightforward, and it gives you the RPOs and RTOs right then and there. It requires some administration from the VPG perspective, but it's able to bridge a lot of gaps.

My advice would be to work with your Zerto technical account manager for the setup and best practices.

Zerto is good when it comes to continuous data protection. We're currently in the middle of some technical support cases with them, cases that I'm watching, regarding some of our larger databases. But so far, there have been no issues with the smaller databases. It's doing its job.

We haven't yet enabled Zerto to do DR in the cloud, but that's something we are pursuing currently. We have had a demo of it but we haven't done a PoC.

We rely on Zerto for data recovery and cloud migration as our primary disaster recovery solution, especially since we lack a dedicated backup data center. Zerto's ability to block ransomware attacks and facilitate rapid server recovery provides us with significant peace of mind.

This comprehensive solution extends beyond processor recovery and data center capabilities. It also encompasses application testing and on-site data protection, ensuring comprehensive coverage in the event of any incident, including ransomware attacks.

We implemented Zerto to mitigate concerns about cyberattacks and data breaches. Zerto functions as a robust multi-layered defense, safeguarding our data. Even if an attack breaches the initial layers, Zerto allows for rapid recovery, ensuring minimal downtime and continuous synchronization with the production server.

In terms of data protection, Zerto enhances business continuity by promptly reporting any encountered cyberattacks. This allows for timely notifications and, critically, prevents the disruption of running production VMs. This real-time monitoring and reporting prove invaluable in the event of threats, facilitating swift recovery efforts.

Our recovery time now is less than 30 minutes.

Zerto's CDP has had a positive impact on our overall data recovery.

Zerto's near-synchronous replication operates in near real-time, enabling data replication with minimal to no data loss.

Our repeated use of Zerto's immutable data copies has significantly enhanced our trust in our backup and recovery procedures.

Zerto provides real-time notifications and reports, which help us prevent unknown threats.

While cloud platforms offer their own security and backup features, Zerto provides an additional layer of protection for our data in the cloud.

Google Cloud Platform provides primary security for our virtual machines. Additionally, Zerto provides us with granular reports that help us focus on specific areas to ensure further protection.

While I haven't had extensive experience with other DR solutions, Zerto offers impressive recovery speeds.

The migration is not complex.

Zerto has helped reduce downtime by over 50 percent.

Zerto has sped up our recovery time by over 20 percent.

We have been able to reduce the number of employees involved in data recovery situations by five.

I like the ease of recovery and backup the most.

Disaster recovery is the most valuable for ensuring minimal downtime during a disaster scenario.

The technical support response needs improvement. They need to treat us more as a partner.

I have been using Zerto for seven months.

I would rate the stability of Zerto nine out of ten.

I would rate the scalability of Zerto eight out of ten.

We contacted the support team by email and tickets during the data migration but received limited response.

Neutral

Previously, we relied on backups from GCP, AWS, and Azure. We transitioned to Zerto because it offers granular reporting capabilities, which helps us keep our managers and non-technical personnel informed.

The initial deployment took a few weeks.

The pricing is reasonable.

I would rate Zerto eight out of ten.

We have 500 people in our organization that use Zerto and it is used in multiple regions.

Zerto requires moderate maintenance, handled by a team of five.

We use our custom dashboards to manage and monitor our disaster recovery plans. These dashboards receive emails automatically, allowing us to take necessary actions as needed.

I recommend Zerto for data backup and recovery, as it also helps mitigate the impact of data corruption or deletion.

We are using it for disaster recovery. We have recovery point objectives (RPOs) for our ERP systems, financial systems, and real estate systems.

We only use it for on-prem disaster recovery. We are not using it for the cloud.

When we replicated our data, I turned up the machine, and it was up in seconds. It blew my mind. I could not believe it. We made a change to the database and tried to bring it back, but it did not work. I was floored by how quickly the system came up, but unfortunately, I need to get the rest of it working. We have not spent a tremendous amount of time on it. We are stuck, and we have not been able to play around with the full features of the system.

Unfortunately, we have not been able to get it to be fully functional. We were able to replicate and turn up a VM, but we were not able to bring the VM back because my team was spread thin. However, we worked with tech support and got the VM back.

I have been using Zerto for one year. 

We have not been running it long enough to see its stability.

I have a small group of virtual machines. If I buy more licenses, I am sure it would work just as well. We have fifteen VMs for our core production, financial systems, and real estate systems.

I did not work directly with them. My systems engineer worked with them, and he was not tremendously impressed. He had called their support, and the impression that I got from the engineer was that they had never seen that before, and they did not know.

We purchased VMware Site Recovery Manager, but we made a lot of hardware changes. I never got it working, and I stopped paying for the licensing. I cannot compare Zerto with VMware Site Recovery Manager because I never got VMware Site Recovery Manager working, so I did not use it.

We went for Zerto because we wanted something from a reputable company that I know works and that I can get up and running with the recovery point objectives that they advertise. I was impressed when I brought it up. It met my expectations.

We paid Zerto to help us get it installed, and we paid for the quick start. However, I did not read the contract closely. The person was very helpful, but unfortunately, we did not understand that we had a limited period of time. When we went to ask for support, they said sorry and asked us to buy more hours. That was our fault. It was not explained properly, but I cannot blame Zerto because we just did not read it all. It was a line item on the contract. It was not until they said that I only had six months that I pulled up the documentation, and it was a line item off to the side that said that we had six months total for the start-up, so we did not get the environment fully set up.

When we worked with the quick start engineer, he made some recommendations about setting up a test environment. He made some recommendations here or there, but it failed to launch. When we were working with the engineer, we had some of the same problems that we had after deployment. For example, in some cases, some test machines would never boot up. We then had to redo it and do some other VM. Even at the time when we were working with the engineer, we could not bring it back, and we never resolved the issue because the time expired. Some of that is on us. We get pulled in different directions, and I did not understand the limitation. 

I have not yet seen an ROI. I will see it when I resolve my issues, and I can bring my entire environment over and get it up and running.

I do not have anything to compare it to. It is expensive, but I am not going to squabble about the price when I bring the system up in a disaster. It is what it is.

We did not evaluate other solutions.

At this time, I would rate Zerto a five out of ten. I was extremely impressed at how I was able to bring that system up, but because I have not been able to bring it back, I am in the middle. Once I can bring it back, I will be super impressed and rate it a ten, but right now, I am right in the middle. It worked great for a minute.

We utilize Zerto for our disaster recovery solution, which involves replicating our virtual machines to a remote hot site to ensure failover capabilities.

Zerto's near-synchronous replication is great. 

Our RPO is around ten seconds.

I found Zerto's dashboard and features, such as the Zerto console, easy to use. It is simple to navigate and comprehend. Additionally, it is convenient to check various RPOs and BPG groups to stay informed about the current status.

We now have a robust disaster plan in place since the implementation of Zerto, which was a significant aspect we aimed to ensure.

Syncing data over to the data center for disaster recovery is easy.

I cannot provide a specific answer regarding our RTOs, but they have definitely improved significantly compared to our previous practices.

Zerto is considerably faster than our previous disaster recovery testing, which has saved us a significant amount of time.

Zerto has reduced the number of resources required for our data recovery.

It has helped reduce the number of staff for our backup.

We are utilizing a third-party company to assist us in managing Zerto. However, the RPO time for the copied-off VMs appears to be quite short. Additionally, it is straightforward to use.

One concern we have is the speed at which Zerto maintains compatibility with VMware and different versions of VMware. We are specifically worried about potentially major security issues with our current ESXi version and whether upgrading it would cause any problems or compatibility issues with the Zerto version we are using. It is crucial for Zerto to collaborate closely with VMware in order to promptly test updates.

I have been using Zerto for six months.

Zerto is stable. We have not had any stability issues.

We have not used Zerto in the cloud, but on our ESXi host, it appears to be scalable.

We used to back up VMs to powered-off off-site storage, but Zerto provides live disaster recovery capabilities. We had been utilizing a different disaster recovery concept, but Zerto is easier to use and provides us with an improved turnaround time in the event of a disaster.

The initial setup was straightforward. I assisted in the deployment, and a total of four people were required. The deployment took one week due to the necessary networking changes that had to be made.

We implemented using a third party.

I give Zerto a ten out of ten.

We utilize Zerto for our disaster recovery, and we employ our storage appliance for local snapshots.

No maintenance is required for Zerto.

I suggest using Zerto to have the servers in different Virtual Protection Groups so that they can prioritize the most important aspects of the business.