HPE Zerto Software Reviews

We are failing over approximately 250 systems. In many ways, this could impact 3,800 insurance agents across 11 states. 

There are two sites: the source site and the production site. Those are failing over to another data center about 150 miles north of my location.

When we went from the original DR plan that we had with Double-Take to SRM, we were able to fail over in an hour and a half. We did all the storage groups in bundles, and we are like, "Wow, this is unbelievable. This is awesome." Then, we went to Zerto, and it was like, "Oh wow, we can pick and choose how we want to do this." So, Zerto provided us with a lot of value. 

We went from testing in a week, e.g., we would say, "Alright, we are going to set aside Monday through Thursday to test all the apps which have been deemed 'need to be tested', and make sure for DR purposes that they are working correctly." We went from that to a day. We can do it whenever we want much easier than before. Instead of having to do it in a group, you could have it where there is scratch space and all the things that are needed, where all the changes and deltas are being cached. Now, we can do a small group of people anytime that we want, or whenever. 

We haven't done it all in a day. Our plan is to have it fail over where we can get it done quickly enough in that morning, e.g., if we have all the testing, testers, and developers lined up, then they can test and we can have it done all in one day.

It has reduced staff stress. We are not big on cutting staff because we run pretty thin. We have even seen growth in the amount of staff involved in backup and DR management. There will be two leads going forward, sharing the primary duties.

The most valuable feature is the failover testing and being able to do that in a granular fashion. We can pick and choose what we want to fail over and at what time, then how quickly it fails over. We fail them over into a bubble, which means our developers and other testers can go in and do whatever they want. They are not impacting production outside of the bubble.

The reporting function is a big thing that we like. Our upper management and execs are always like, "Hey, we need to report about what you did." So, we can print out a report that is 200 or 300 pages long, and go, "Here you go." It was a little overwhelming the first time they got it. They were like, "What?" I am like, "You asked for a report. This is the report."

For the last three years, I was a secondary admin. We got into a situation where they were like, "Hey, you're the lead. You need to immediately be the lead." I was like, "Okay, alright." So, I was able to go in and create the protection groups and replication servers. We run VMware so we were able to push that out to the hosts, uninstall and decommission stuff. I was able to get that squared away within a day or two. It is very easy to use. If I can do it, anybody can do it.

The Zerto’s near-synchronous replication is very important. We used to say, "Hey, if we don't have this and if the building blew up from a gas leak, then what would we do?" Now, it is not just disaster recovery, but there are departments of insurance requirements for federal requirements going, "Hey, do you have a disaster plan in place that will successfully run? Can you provide me with those reports?" It also checks that box since we have requirements that need to meet for customer data. They need to be able to retrieve that data, either at the running site or production site. Or, in the case of a disaster, we will need to provide them with that information. So, it checks multiple boxes.

You can create a VPG and put anywhere from one to 17 servers in that group. We build them one by one. If something changes in VMware, it would be nice to be able to go in and change that VPG, having it update without messing up. When you change them now, it only applies to the copies from the points when you changed it. I wish it would purge that older data from the past. Right now, we have to build a new VPG, which is not a big deal as it is just a few screens. 

We have been in the Zerto world for four years, and I am the lead on Zerto now.

Stability-wise, I would probably give it 10 out of 10. It is very stable. If there is something not running correctly, then it is an outside factor. It is either the admin or a connection to the other site. With the dashboard, it will show you that you have this many protection groups built. Everything is an individual green square, but when there is a problem, then you will see red. It is very simple. If it has a problem, you will see something. I have not dealt with a problem where Zerto is just not working. It is usually user error or sort of outage. It is reliable.

As far as Zerto replication and DR purposes, it has not caused us any outages.

I have answered stuff for Zerto before, and they are like, "Why do you like it?" We say, "Because it works." For so long, we had stuff that didn't work for so long, and this solution works.

As long as you have the license to protect the VMs, then you can scale it as big as you want. 

We are currently protecting 325 VMs. We have plans to expand in the future.

My dealings with the technical support have been top-notch. They are very good. I would rate them as 10 out of 10.

Positive

We had Double-Take and were replicating to a site with SunGard, then we swapped. It was kind of a nightmare for us to get it working the way that we wanted. I am sure it is a great product, but the way that we needed it to work was just not working. Then, we went to VMware SRM, which worked great and went off without a hitch.

We then wanted something with a quicker recovery point objective (RPO), and that is when Zerto came in. They allowed us to failover in a granular fashion. We could pick and choose how we wanted to fail over in DR tests. That is a big part of our DR testing. Enterprises want to be able to know that they have a successful test and can run in a failed over environment, so the test is 50% of that. The other half is, “If we had to declare a disaster, where would we be?” The RPO is two to three seconds with Zerto. I have talked to people with Unitrends and several other companies who say that you can’t get an RPO that low, but that is what we have. Today, it is very fast today.

When we need to do our DR test on a specific day, Zerto has allowed us to be able to do that in granular fashion. With SRM, you had to fail a group of servers over. While that may have changed, at the time you could only do them by storage volumes. With Zerto, it didn't really matter. It has been like, “Which ones do you want to fail over? Do you want to do just your SQL servers?” This has allowed us to have a more granular approach to testing and DR testing. It ensures that we can do it in a certain way and confirms that our actual DR plan is a good plan.

We didn't have anything that worked for so long. I think Zerto kind of showed up and was in the great spot where they couldn't be any worse than what we had.

I was not involved in the initial setup. This has been kind of thrown in my lap, and it has not been a nightmare at all.

The prior admin hired services for updates. Going forward, I will probably do them myself.

We have seen ROI. It reduced the time for failover and failback by 90%. I am not saying that the products I mentioned earlier are bad products. They just didn't work well for what we wanted.

Zerto has had a significant impact on our RPO. It is a double-edged sword where our RTO and RPO have allowed us to almost not miss a beat. In a DR test, we are more staging and moving systems over, and this is more of a tactical approach. With some of the moves that we are making with SQL and using blue-green environments, I don't think we see a problem at all. We feel very good about it. 

We bought it through a reseller.

We are very fortunate because our budget is pretty big, and I am not making that up. Staffing may be a little thin at times, but as far as budgeting what we buy, the price for this solution has not been so outrageous that we don't buy it.

I think there is a support cost.

I was a big proponent of using SRM because I manage the VMware environment. Being a VMware product, I was more in their corner. So, it was mainly between SRM and Zerto. We also might have looked at Rubrik.

With other vendors that we used, we would sometimes start on the weekend, e.g., on a Saturday morning at 6:00 AM, then we would go through at least Thursday of the next week. It would be a long, arduous process. Sometimes, we would go only two days because we could never get past a single spot, then the entire test would be a failure. With Zerto, it has reduced our DR testing time drastically. It went down to where we think we can do a test in a single day. We were able to pull it off last year in two days with failover and failback tests as well as reports.

Zerto provides ease of use when building out jobs, then having them failover as you want, one by one or selecting five or six VPGs at a time. One of the big things that we do is with SQL. We want our databases online before doing any testing. There also needs to be domain controllers turned on for people to be able to log in. It is like, "Alright, we are going to fail over the domain controller." Next, they go, "Alright, we are going to fail over our SQL stuff." Before, when we had those SRM groupings, it would be a bit harder. You had to wait for everything to finish. Now, it is granular, where you can pick and hit one by one what you want. The database administrators can go in, and say, "Alright, we are online. There are three more that just came online." They are able to test it, and it just works. Having something that works was a big thing for us.

It has not replaced any of our legacy backup solutions. We use Veeam for any backups or system restores at this point. So, Zerto's role is just for DR.

We have luckily not had to use Zerto in a data recovery situation for ransomware. We have had one instance where we were in a spot like that, which was about two years ago, and we were able to restore it back with Veeam.

Until the last few cases, VMware support is some of the sorriest support that I have had.

I would recommend Zerto because it works. You will need to do a PoC first though.

Immutable data copies are something that we are looking into. For example, if I have a recovery point of two, nine, or 10 seconds, then we get hit with some sort of ransomware attack or something like that. We would like to have immutable data that is unchanged. So, we are looking into this feature now.

I am sure it has enabled us to do DR in the cloud, but we are not a big fan of putting that stuff in the cloud. We are not a fan of putting it on somebody else's computer if we can put it on our computer. We have been very happy having a DR site approximately 150 to 200 miles north of our main site. We are kind of running it in our own hybrid cloud at the moment.

As far as testing, there are probably 70 people who test.

I would give it a nine out of 10. It has done what we wanted. We have been very satisfied with it. We are Zerto fans.

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 use it primarily for DR situations. Whenever we lose our primary location, we switch to another location. We also backup resources and migrating VMs in and out of different environments, cloud versus on-prem.

The most valuable feature is that it provides real-time backup. We're in the financial industry and have to have 100 percent uptime. 

It helps us have a lot better uptime than what we would normally have. It's always real-time synced, with instant recovery. We can return to another location if power drops or generators don't work.

It gives us quick uptime. It also helps our customers maintain that trust, so Zerto really does help with trust. We generally use it on-premise.

The near-synchronous replication is really good. It gives us quick uptime. It helps our customers keep that trust in us.

We use Zerto to protect VMs in our environment. Until Zerto, I didn't pay much attention to RPOs. Zerto gives the ability to bring RPOs down to seconds. 

For certain use cases, Zerto has a better speed of recovery compared to other solutions but it doesn't tie into our SANs like Veeam does. 

It is a little expensive.

We could streamline the installation better. The other thing would be ransomware notifications, like IO anomaly notifications.  If they integrate with the SAN, that would be valuable to see in terms of snapshots.

I have been using Zerto for six to seven years.

We came up with the new version, and it's pretty good. If there's no reason for me to say it's unstable. It's been proven so far.

If you buy the licensing, it will scale up to size until you will spend money on it. 

Support is helpful.

Positive

If you want to pull from the snapshot instead of tools, then SRMs are better used for this case. It's fast and the first to market with continuous data protection.

Zerto is easier to use. There is some standup at the beginning, you must install the agents. It's easy to use when it's working right, but sometimes, it takes great effort to get it going if something goes down. 

We use another solution, Veeam. We keep them both because they're both beneficial for different use cases.

The initial setup is straightforward, but if you have it the first time, you are stranded in the industry. It could take a little figuring out, but Zerto is pretty helpful.  

There have been a couple of situations which they weren't able to fix an issue right away. We move everything off to a different server until we can circle around and extend that one.

We did it in-house.

Zerto has paid for itself in man-hours saved. 

Zerto gives you the ability to bring RPOs in seconds. We can have instant uptime for everything. 

It's more expensive than other solutions but it's worth it for our environment. It has made it very easy to restore files because you can restore them down to the second. It's pretty simple. We have the agent and all the hosts. 

Overall, I rate the solution an eight out of ten.

We utilized Zerto to facilitate the migration of servers within a data center from one location to another and employed it for disaster recovery purposes.

Zerto is user-friendly. The feedback I received from my team during the migration was that it was effortless to use. I wasn't directly involved in the implementation, but I participated in the decision-making process for purchasing and analyzing Zerto. However, the feedback I received from our team indicated that it was quite straightforward to use.

The benefit to our company was the ease of moving our servers using Zerto, which saved us a lot of time. I would like to emphasize that during the data center migration, it saved us a significant amount of time. Additionally, during the disaster recovery tests, when we actually used it, it worked exceptionally well. Zerto provides us with peace of mind. In the event of an incident, the ability to recover our data effectively also grants us peace of mind.

We utilized Zerto to transition from one cloud to another, ensuring that all of our operations and applications are now in the cloud. Having disaster recovery in the cloud is an important necessity for business continuity.

We use Zerto to help protect our virtual machines.

Zerto has helped reduce our disaster recovery testing.

With Zerto, we would not require additional staff or hire a third party to assist with disaster recovery.

Using Zerto for the migration was incredibly valuable, enabling us to save tremendous amounts of time. Thankfully, we have never had to utilize the disaster recovery feature. However, if the need arose, Zerto would be instrumental in preserving our business.

Not all of the knowledge required for implementing Zerto is available in their online documentation for non-partners.

I have been using Zerto for two years.

Scalability is really good. We deployed it fairly quickly across our environment.

The technical support is responsive and helpful.

Positive

The feedback I received from our team was that the majority of the deployment went smoothly, but there were some technical aspects that were not covered in the deployment documentation, which they had to figure out.

The deployment required two people at times, but the majority of it was completed by one person.

The implementation was completed in-house.

Zerto has saved time during our data center migration, and we are utilizing it for our disaster recovery. However, we have not yet calculated the return on investment for it.

Zerto previously had a perplexing licensing structure, but they have since resolved it by implementing a unified license.

We evaluated Veeam Backup and Replication before choosing Zerto. Zerto offers live recording, allowing us to rewind to the exact moment when the incident occurred. At the time of our selection, Zerto was the only company with this capability.

I rate Zerto a nine out of ten.

For organizations planning to implement Zerto in-house, I recommend reviewing all the setup documentation beforehand.

We use the solution to protect our general workloads, migrating VMs to the cloud and protecting VMs in the cloud. Our primary use case is to protect and provide DR.

Zerto has enabled us to mature our DR stance quite a bit in how we protect functions.

The near-synchronous replication works pretty well. Going from RPOs of an hour to five seconds is pretty interesting.

Zerto enables us to do disaster recovery in the cloud rather than in a physical data center.

Having disaster recovery in the cloud is very important for our organization as we're currently moving our production workloads to the cloud.

We use Zerto to help protect VMs in our environment. Our RPOs are getting lower.

The speed of recovery in Zerto is much faster than with SRM.

The on-prem to Azure, migration, and protection aspects are good. Zerto is one of the few tools that work pretty good and at moving between regions or clouds.

The near-synchronous replication is good. 

Automated protection of workloads from one site to another could be improved. For example, with SRM, you can create a VM, and it automatically protects it based on mappings and other factors. Zerto does not do this.

I have been using Zerto for about a year.

It can throw us for a loop at times and it can be challenging to figure out.

We are pretty large-scale. It's been one of the challenges, as it seems pretty simple for smaller scales, but as you get larger, it gets more challenging, which is where the automation piece and lack of that comes in.

Level one and level two are excellent. The development team is a challenge sometimes because they work four days a week. Sometimes, when we have to have a Dev escalation or a severe issue, it takes quite a long time to get a response.

We use SRM and Commvault. Zerto is better than both of them. Commvault is not great at Orchestration DR, and SRM locks you into VMware.

We were early adopters, so the deployment has been challenging, but it's definitely getting more mature and better as we go. 

We bought it from a reseller but we used Zerto services to get it going.

It has reasonable pricing comparable to VMware and others.

Overall, I rate Zerto an eight out of ten because it makes testing easy and provides flexibility between on-premises and various clouds.

We primarily use the solution for data replication. We have it in Oracle. It helps with disaster recovery. We have a primary and secondary server and the data can move between the two thanks to Zerto.

Right now, I'm having issues with delays when archiving. We're facing issues with RPU and getting 20 or 30-minute delays. That's a bandwidth issue.

We do rely on the replication capabilities. When our one system went down, we were able to immediately replicate. 

It's a reliable solution - if we have great bandwidth. It offers near-synchronous replication. This is very important. We're a fintech company relying on Zerto for disaster recovery. We tend to only use the replication features.

We use the solution for immutable data copies. The 3-2-1 rule is very reliable. 

We can use Zerto to help protect our VMs.

It's had a positive effect on our RPOs. We have virtual protection groups and haven't had any issues. Our production server does need to be replicated in real-time, and everything else can be replicated whenever we like. 

It only takes five to ten minutes to switch over or failover.  During data migrations, our users can continue to collaborate just fine. It's fine and fast. 

The RTO is good. If a machine is storing more than two to three terabytes, it takes longer than ten minutes, but any time the storage is less than that, it takes ten minutes or less.

Our downtime is minimal.

We've saved a lot of time in a data recovery situation. 

We do switchovers from time to time to test DR. We do switchovers every three months. It only takes half an hour. It saves us about one hour at least. We can allocate the time we save to any other activity or task. 

It's reduced the number of staff needed for DR by three or four people.

The solution did replace some legacy solutions. It replaced small backup solutions. It's helped us save on the costs needed to manage them. We've saved around two resources so far. I'm not sure how much those tools cost. However, we needed four infrastructure and two or three database people looking after those. Now, we don't need to.

We don't have great bandwidth. When we don't have good bandwidth, it doesn't work so well. 

We're not fully satisfied with the support team.

The first time, it's difficult to migrate data. However, after that, it becomes easier. 

They need to give more options, such as more archiving options. 

The company has been using the solution for around one year. I've used it for three months.

The solution is stable, from what I have seen.

We have around 100 direct Zerto users. We have around 30,000 to 35,000 end-users. We have 10 production servers, Linux machines, five development servers, and five Unity servers. 

It is very scalable. We can scale up to 200 machines and have maybe around 80 right now. I'm not sure if we will scale more in the future. 

Support has dropped off. When I joined the organizations, they were very active. 

Positive

We also use Oracle. I used it in my previous company. In this company, we use HP, and it works well with Zerto.

Zerto is very easy to use, and the GUI is very comfortable. We can configure, replicate, and sync right from the GUI.

We have Zerto on an HP machine. 

I was not involved in the deployment of the solution. 

Maintenance is necessary, and we have two people handling maintenance tasks. 

The solution is worth the cost. Having disaster recovery is necessary. If we ever suffer from a hardware failure, we can easily replicate in one click. 

The solution is a bit expensive. 

We did not evaluate other options. 

I'd rate the solution nine out of ten. I'd recommend the solution to others. 

We use Zerto to back up our VMs to our disaster recovery site.

Zerto is essential for protecting critical workloads. We don't protect all of our VMs, but some need to be recovered in a timely manner. The recovery time is almost immediate.

The fast recovery speed is Zerto's most valuable feature. It gives us peace of mind to know that the VMs are replicated and are there if we ever have a disaster. We recently upgraded our license to include the cloud because we are considering migrating from our hosted data center to cloud-based DR. Zerto's near-synchronous replication has been excellent. We haven't had any issues during our testing. It has worked flawlessly, and we're very pleased.

It would be difficult to do, but I would love it if Zerto handled some of the scripting and things necessary to do a recovery. For example, it would be helpful if the solution could update the DNS to point to a new location. It would be nice to automate some of those tasks that you have to do to recover a VM and they were kinda out-of-the-box point-and-click things rather than things that required you to write a script.

We have used Zerto for five years.

We haven't had any issues with scalability, but we haven't done a lot of scaling. We initially purchased a number of licenses, and we've kinda stayed about that number for the whole time. We're currently protecting 175 VMs, which is a small fraction of our total environment.

I rate Zerto customer service eight out of 10. It's been good. I haven't had to open any tickets with support, but we worked with our sales engineer to configure things, and it went well.

Positive

We've used backup providers before to do replication, but we've never had a solution that offered immediate recovery. We evaluated VMware SRM and some other backup providers, but none were quite on Zerto's level. The recovery speed doesn't compare to Zerto. Zerto is easy to use aside from the scripting aspect of things, but the other solutions aren't aren't any better in that regard. 

The setup is straightforward. We deploy an appliance, and it's up very quickly. The initial installation is done in a day, but it takes time to configure things exactly the way you want them, get the VMs protected, write scripts, etc. 

It's hard to quantify the return, but we can do what we set out to. We're able to recover critical services in a DR site. We haven't had to use it, but we know it's there, and we've done testing that shows it works. Hopefully, we don't have to use it, but it's a good insurance policy. 

I rate Zerto nine out of 10.

We currently utilize Zerto as our disaster recovery solution. With Zerto, we replicate production virtual machines to our DR site. This approach enables us to recover and bring everything back online in a disaster swiftly. Our recovery point objective can be as low as five seconds, depending on the replication point.

Additionally, we employ Zerto for scaling purposes and for conducting upgrade testing. This entails spinning up VMs in an isolated environment, allowing us to perform various tests. For example, a few years ago, we tested the upgrade of our active directory domain controllers. By validating processes within this environment, we can ensure their smooth execution in production. These are the two primary use cases for Zerto in our organization.

Zerto is very user-friendly. We can select the VMs by installing a small agent specifically designed for the host. This agent identifies all the VMs. Zerto integrates smoothly with VMware, which is our primary core platform. I believe it also functions well with other hypervisors, although I am only familiar with VMware. Therefore, the integration with vSphere simplifies the process of creating groups, runbooks, and other components necessary for building our disaster recovery environment.

Zerto's near-synchronous replication performs admirably. Many times when I check, we are only about five seconds behind in terms of production time. Of course, this does depend on network performance. There have been instances where the delay exceeded five seconds due to network blips or other issues. However, for the most part, we consistently remain within a five-second range of our production environment.

As a manufacturer, a significant portion of our operations relies on timely execution in order to ensure efficient production and timely delivery of our products. We closely coordinate with external partners and customers to minimize downtime and maintain a seamless real-time production process, which is crucial for us.

The ability to conduct faster disaster recovery testing and the potential for quicker recovery in the event of a disaster have been greatly improved. Before using Zerto, our approach involved log shipping and manual recovery, which meant that the best we could do was recover the previous backup from the previous night, assuming the backup was successful. This process would take hours or even days. However, with Zerto's automation, we can now recover within seconds—five, ten, or twenty seconds from the point of the outage. We can bring systems back online automatically and at a significantly faster pace than our previous manual approach allowed.

Zerto has significantly improved our recovery time objectives compared to what they used to be. Previously, we would have to restore from backups from the previous night and manually configure systems. Therefore, the recovery time objective has likely decreased from days to approximately an hour, or perhaps even less. It's challenging to determine the precise timeframe in a real disaster scenario since we conduct disaster recovery testing. However, it is undoubtedly much better than it was before, although pinpointing the exact time of an actual disaster is somewhat different.

Zerto has helped us reduce our organization's disaster recovery testing from several days of preparation to just a single day.

Zerto is easy to configure and manage. The ability to quickly bring up VMs within a test environment allows us to test our disaster recovery functions and ensures that they would function just as well in an actual disaster scenario. This enables us to swiftly recover in the event of a disaster.

Zerto could be easier to configure when we need to perform data testing and establish network connectivity outside of the isolated environment. We encounter situations where there is a desire to test a printer during disaster recovery testing. However, due to the presence of an isolated environment, doing so can result in complex configurations. 

Zerto needs to improve its support for VMware Lifecycle Manager. This creates a problem with VMware's ability to automate the complete VMware stack upgrade.

I have been using Zerto for ten years.

Zerto is highly stable. It is rare to encounter any issues with it. Typically, any problems that arise are due to changes made on our end that may have inadvertently affected it. However, Zerto remains an exceptionally stable product.

To the best of my knowledge, Zerto can scale to the extent that we require. I am not aware of any limitations, as we have not encountered any thus far.

The technical support is generally very prompt in responding, and highly knowledgeable, and they will continue working with us until the problem is resolved.

Positive

We previously used Dell RecoverPoint for Virtual Machines and completely replaced it with Zerto.

Zerto is much easier to use compared to RecoverPoint. Previously, with RecoverPoint, we could only program-specific logs, and the VMs we wanted to replicate had to remain on those logs. If we moved the data off those logs, replication would be lost. However, Zerto keeps track of the VM regardless of its location, making it superior to RecoverPoint in terms of configuration and management.

Zerto is a more cost-effective product than Dell RecoverPoint.

The initial setup is straightforward. We need a virtual machine, install it, push it through, and configure it to communicate with the host for deployment. I mean, it's a very straightforward process. Two people were involved in the deployment.

The implementation was completed in-house.

The human resources necessary to perform a disaster recovery test are undoubtedly available. It is more economical than RecoverPoint. Now, it has been many years, and I am uncertain about the cost disparity. However, on the whole, there is a decrease in various aspects regarding the product's cost and the number of work hours needed for disaster recovery testing which is a clear return on investment.

The pricing is straightforward. We are on an enterprise licensing model, and it is based on a per-VM basis. We have the option to purchase them in blocks. This approach is quite cost-effective as we do not replicate our development and testing environments. We only replicate the production environment. Therefore, we are not paying for the entire setup, but only for what we are actually replicating.

I rate Zerto a ten out of ten.

Currently, we have a separate product that we use for backup, which has immutability features. However, we do not currently employ Zerto for immutability purposes.

We have considered using the cloud for disaster recovery, but currently, we maintain the same hardware at both locations. However, since we conduct all of our firmware testing and upgrades on our disaster recovery site first, we have decided to keep our own disaster recovery site instead of attempting to do it in the cloud.

We could easily transfer data to the disaster recovery system. One of Zerto's functions is to replicate data from virtual machines or migrate entire virtual machines, although we haven't utilized it for that purpose.

The only maintenance required is typically software updates. Whenever a new version is released, we must go through the process of upgrading Zerto. Other than that, unless there are any issues, it generally operates smoothly.

We just need to ensure that we know the number of virtual machines we would be replicating so that we can obtain the correct licensing. Otherwise, we will have to backtrack. If we underestimate, we will need to provide additional licensing. It is important to determine this information upfront, as well as the bandwidth between our site and the replication location, as it also affects our recovery objectives.