We primarily use Zerto for our DR requirements.

Near-synchronous replication is pretty much a major benefit from our perspective. We are mainly using it for DR.

We use Zerto to help protect VMs in our environment. With the use of Zerto, we now have defined RPOs, which is good.

Zerto has helped to reduce our organization's DR testing. It has also enabled us to do DR testing more thoroughly, so it has reduced the time, but it has also enabled us to do more of it.

In terms of its effect on our IT resiliency strategy, from our on-prem environment, it has been the cornerstone. We are now building a new DR strategy around Zerto because of the value that it has.

We were able to realize the benefits of Zerto pretty much immediately. At the end of the day, we had a gap. It had an immediate impact on our ability to recover.

What I like most about Zerto is that it just works at the end of the day. It is almost a set-it-and-forget-it solution in relation to its capability of keeping the DR environment in sync.

Testing is also a good feature. Bubble tests ensure the integrity of those images, and the replication process is also a major benefit.

Its capability to detect anomalies also within the transport layer is valuable. While moving and replicating the traffic, we have a little bit of comfort because of its ability to detect ransomware or anomalies within the transfer.

They should not make it so expensive so that I can buy more of it. Other than that, I do not have anything. We have not come across any issue. We are still fairly new to the product.

Zerto has been in our environment for 12 months.

It has been rock solid.

Scalability for us is based on the licensing count. I would scale it across the organization if possible, but I cannot. At the moment, it is meeting our current requirements based on our licensing constraints.

The only disaster recovery product we used was centered around recovery or restoration from backup. We never really had a disaster recovery product per se. It was managed by other backup mechanisms and replication forms.

Zerto was put in because we knew we had a gap within our DR strategy based on RPO extensions. It was deployed to bridge gaps within our DR strategy at that moment.

The initial setup was done by HPE. We went with a turnkey solution with HPE Professional Services and our incumbent tender previously used. They handled the installation and setup. We handle the management of it now, but I cannot comment much on the installation because they did it for us. It worked, and we went through training and have been using the product since.

Its learning has been fine. It has been like any other product. HPE has supported us. They have provided professional training for the team. I have not heard from the team about any issues or gaps. HPE has been very supportive of the implementation of Zerto.

It does not require any maintenance at our end. The installation is still fairly new. Nothing has come to a low yet. Over a period of time, we would probably have to spend more time on the maintenance aspect of it, but at the moment, it is pretty much a set-and-forget.

From a pricing standpoint, there is value in it without question. However, it can become quite expensive when you start looking at the number of workloads you have in the environment and what you would like to do.

We assessed other products in the market but found Zerto to be the best within this particular space. Additionally, Zerto was installed as part of a data center refresh program with HPE. We replaced compute and storage within our on-premise data centers. Considering Zerto is part of HPE, it made more sense to implement an end-to-end solution with HPE.

To new users evaluating it, I would say that if they can afford it, they should buy it.

I would rate Zerto a nine out of ten, and that is because there is always room for improvement.

We are using Zerto as a DR solution. We also utilize Zerto when we have to migrate any servers from one location to another.

Previously, we were using VMware Site Recovery Manager, and we were not happy with the services we received. There were lots of issues. Since implementing Zerto, we have been happy. We are not seeing any issues with the services. Zerto's support is also excellent. If we encounter any issues, we open a ticket, and they are available all the time.

When we implemented Zerto, we were not sure how things would work. We have a DR test or maintenance window every quarter. During the first window, when we did the DR implementation through Zerto, we found it to be very helpful. Previously, we used to manually take screenshots for DR evidence, whereas now, we can generate a report from Zerto. After the DR, it tells everything in detail such as when a VM was moved, what the procedure was, and how much time it took to consolidate from the primary site to the DR site.

When we had an issue with a legacy application over the weekend and users reported it on Monday, we had to revert the VM to a snapshot from eight hours prior. We could do that easily. This is an excellent feature. Zerto allows us to select a custom recovery time. For instance, if no one checked the server yesterday because it was a holiday and we needed to restore the VM to the day before yesterday, we could do that quickly. Zerto helps address downtime situations effectively.

Zerto has reduced the DR testing time. Previously, it took three to four hours, including app testing, but now it gets completed in one hour.

Zerto is excellent. It is the primary and only solution we are using in our organization.

The constant replication between the primary and the DR site is valuable. Zerto's near-synchronous replication is excellent.

Zerto is very easy to use. A new team member can pick up the pace in one or two days. Someone who has never worked with Zerto can understand it in one week. It has a user-friendly graphical user interface. Everything is well described.

I have one recommendation, but I am not sure if it has been addressed in the current or upcoming version. The challenge we faced occurred during a DR for a database server running on SQL Always On. We experienced a database crash and logged a case with Zerto about a year ago. They said that they do not support Always On. As a result, we had to plan accordingly. We deployed another server to that location with Always On and moved all the database servers out of the Zerto application. We are uncertain if Zerto now supports Always On because we have not explored that option. We have a couple of environments on the cloud but have not tested if that feature is available or not.

I have been using Zerto for the last four to five years.

We have experienced no issues at all.

I would rate Zerto a ten out of ten for scalability.

Zerto's support is excellent. At the time of implementation, the support was slightly delayed because there was only one way to log cases, which was through the portal. They provided us with a few articles to refer to, which helped us address the solution.

We had VMware Site Recovery Manager (SRM), which was very difficult to manage. Sometimes, we faced replication issues. When performing a failover, the network was not stable. There were many issues, including dependencies on the storage area, requiring the storage team to be available during DR tests. The network team also had to be available, involving multiple teams. With Zerto, we do not need the involvement of the storage area or network teams.

It was easy. Initially, we took help from Zerto support because we were not sure about the configuration and best practices. We received help from Zerto.

The challenge was not from Zerto's perspective; deploying VMs where we were going to install Zerto took some time. We had dependencies on aspects such as VMs not being ready. The deployment of only Zerto took less than eight hours.

We reached out to Zerto for any support.

One person can handle the implementation, but if that person is not available, it creates challenges. Whenever we undertake projects, it is between team members. One person deploys, but everyone is involved so that everyone is aware of what is being done.

Currently, it is good, but the license we are using is based on VM count. We are only protecting mission-critical servers, so we are using a very low number, about 300. However, we have 3,000 or more servers. If we consider using Zerto for data protection, it would cost us more than what we have for data protection now.

For new users, Zerto used to offer free training and certification. I am not sure if it is still available, but it was available. Anyone planning to deploy Zerto can get support from Zerto and should go through the basic training, which is free on the Zerto website. They can get certification and reach out to Zerto support if needed. Having a basic understanding of how Zerto works is important.

Overall, I would rate Zerto an eight out of ten because we do not have the functionality to protect our database servers that are on Always On.

It is part of a new deployment. We have a large deployment for the public sector in the UK, and we are using Zerto to enable disaster recovery by replicating data. This allows us to have a very low recovery point objective for that data.

Zerto is easy to use and fairly straightforward to set up. It reliably keeps the data in sync which is all that we can ask of it. It does what it says on the tin, and that takes away any worries. We know that we will be able to recover as we are contracted to do.

Having Zerto in place takes a headache off my plate. I do not have to worry about it. I check it, or I have my team check that it is up to date and synchronizing. All they have to do is log on, have a look, and confirm that we are okay and have green lights across the board. It is very easy to understand the interface.

It is one of those things that sits and does its job and does it well. Therefore, we do not have to worry about it. That is the biggest thing. We have peace of mind at the end of the day.

Zerto's near-synchronous replication is very important. We run an application in the SaaS model for our customers. Our customers sign into our application. It is a purchasing application called PECOS. We do purchasing and inventory management. They sign in to our systems and do their business. We have to ensure that the systems are highly available. In the event of a disaster, we can bring them up with a minimum loss of data. That is where Zerto comes in.

We use Zerto to help protect VMs in our environment. Our recovery point objective by contract is within four hours, but practically, it is within five minutes. Zerto is very effective. If I look at it during the day, I generally see that we are within nine to ten seconds. It is a very good thing to see.

Zerto recovery is a lot faster than recovery from a tape or a digital backup. We did a test against the old RecoverPoint and found Zerto to be faster. We also do disaster recovery tests. I have a full disaster recovery test coming up at the end of the month. We expect to be able to bring up the entire environment for our customer within 45 minutes, which is very good.

Zerto has not reduced our downtime, but it has made us feel a lot better. In the event we have downtime, we have some protection there.

Zerto has not saved us time in a real-time data recovery situation. In our rehearsals, it definitely has saved time. Hopefully, our systems have been built reliably enough that we would not have to use it for one. It is just an insurance system.

We still do DR testing. We have noticed a speed improvement in our DR testing. It is slightly faster, but we still have to do DR testing. As with any system, you have to make sure it works.

Zerto has given us confidence in our IT resilience strategy. We had similar strategies in place with the previous infrastructure. We completely renewed our entire infrastructure and replaced it with HPE backend and SAN. Zerto is the recovery solution. We have a lot of confidence that it will work if called upon.

Zerto is quite straightforward to use. It is quite easy to set up. Getting it right is a bit more complex, but setting it up is quite straightforward.

It seems to be very reliable, and it consistently keeps our data synchronized within ten seconds or so, which gives our customers confidence that the data synchronization and replication will allow for a very low recovery point objective.

The onboarding was not very good. It felt like, "Now you have Zerto, good luck. Figure out how to use it." It was not terrible. Their support since having the product has been good when I have had an issue, but there was not much of an onboarding process. The setup of the system, although simple to get working, is a little more tricky to get right. This aspect could have benefitted from a bit more explanation.

It is very easy to simply say, "There are manuals." A little hand-holding upfront instead of trying to get it right by going through a big manual would have saved a lot of time. Once I reported a problem, they were very quick to jump on that and assist us with it. It is not a huge criticism, but it would have saved time. A little bit of upfront help would have stopped us from getting into that cycle. At the end of the day, I am happy with the product. It works.

I have been using Zerto for four months.

It is stable. I would rate it a nine out of ten for stability.

I do not know about scalability. We have implemented it for the size that we need. We have not tried to change licenses, add VMs, or grow it at all. From what I understand, it is very good. We will have to increase the usage but not for a good six months or so.

Our environment has about 400 virtual machines. It is not massive. We are an application provider. We provide a purchasing and inventory management application set to our customers mainly in the UK public sector. Our clients are large organizations. They are health care and local government organizations.

I have a team of eight people. They are not daily involved with Zerto. Only four people are daily involved with Zerto.

The only issues we had stemmed from a lack of familiarity. After we submitted the ticket, their technical support got back to us and helped us resolve the issues.

I would rate them an eight out of ten. It has been very good.

We used another replication system prior to this, which was the old EMC RecoverPoint. It was very good as well, but we had a change in technology. We shifted our technology to HPE for various reasons, and Zerto was the offering that came with their data synchronization.

Overall, it was straightforward. I did it myself in the afternoon by figuring it out myself. It took us a few days to get it right and then another couple of days fiddling with it, but it was under a week.

It requires very little maintenance on a day-to-day basis. It requires monitoring to ensure that you are not running out of space. Once you have got those space parameters right, it pretty much looks after itself unless there are significant changes.

We update Zerto when a new version is available. At that point, we schedule an update.

I managed the deployment initially, but it has now been handed off to a team.

It is too early to say. I think it will eventually prove beneficial by saving us time and eliminating the constant worry of checking these things.

Having seen the product and how it works and its reliability, it seems it will pay for itself.

Nothing is cheap, but Zerto represents decent value.

I would recommend Zerto. It seems to be a very good product. It appears to be stable, and it is a simple product to manage that gives us peace of mind.

I would rate Zerto a nine out of ten. The tiny amount of problems we have encountered is reasonably insignificant. It works.

We use it in our data center. We have two data centers, one in Baton Rouge and one in Las Vegas, and we use it for replication. It is all used in the data center.

We did not have replication previously. Once we got Zerto, we started seeing everything backed up and replicated, and we saw its benefits pretty early. Over the years, we have kept renewing Zerto because it seems to get better. There have not been any issues with it.

Near-synchronous replication works very well. We use pretty big storage with them and never had a problem. If it is close to going over, we always get an email, and it is easy to keep up with all that, which is pretty important here at Credit Union. I have nothing but positive to say about Zerto.

Zerto is easy to use. When we first started using it, we used the emails they sent at the end of the night to see everything was fine. About five years ago, they got their own portal. Since then, we have been able to see everything in real-time. It has been super easy. I automatically get notifications on my phone or email. That has been a real high point for me with them.

We have several VMs, and Zerto has been a part of the protection plan for them.

Knowing what is going on in real-time has helped with breaches and things like that. Recently, there have been no issues. Luckily, over the last year or two, we have not had any security issues. Zerto and VMware are what we count on in our data center. As long as the data center is up and running safely, we are good here at the branch.

We run reports on XDR and get an idea of anything that has been going on. Luckily, we have been safe for the last year or two, but in 2022, there was an issue. Zerto was right on it, and we were able to get it cleaned up. Zerto has definitely helped in the ransomware aspect.

The portal is a valuable feature. I am here in Baton Rouge, and I can get into the Vegas data center and see real-time replication on the portal. The portal has been upgraded over the past several years, and it is probably the most helpful part of it.

I always get some blowback about the cost. It does not seem too bad to me. We had to upgrade to a premium subscription to get some other features. Maybe a one-size-fits-all option would be better.

I have used Zerto for eight to ten years.

I have not experienced any stability issues. We are a heavy usage bank, and it has always been steady for us. I do not have anything bad to say about that.

Scalability has been good too. We started with the one in Baton Rouge and added the one in Vegas about five years ago. It was very easy to connect them and get them mirroring each other. Scalability has been good for us.

When my staff member went to Vegas, there were some issues with logging into the device. He called the tech line and was able to talk to someone. We have had luck getting in touch with those guys. Their customer service deserves a good score, at least an eight out of ten.

At the previous bank, it was a big Cisco shop, but I have been here for almost ten years, and we have had Zerto for that long. Zerto is what I am used to.

I did not personally do the initial setup. A guy who works for me went to Vegas, called it in, and got it set up pretty well. I do not go to Vegas much, but I have been to Baton Rouge. I have tested it and played with it, and every time I have done that, it seems easy to use. My network administrator has never complained about any difficulty. For the most part, it is easy. They have a good tech support line, and if we have any trouble, they are easy to get in touch with. We are happy with that.

We have a maintenance contract with them, but I did not have to use it except for one instance a few years ago when we thought that we were going to get ransomware. We had maintenance on that. The good thing is that it is a part of the renewal. It is safe to have it, but luckily, we have not had to use it over the last few years.

Price-wise, it works fine for me, but my budgetary team is always looking for ways to cut costs, and it seems like they first look at the data center and the IT side to find savings.

Take advantage of the maintenance plan; even if it is not required, it is definitely worth getting. The techs there are really good. There are local Zerto reps who come around. Use the tech support when needed because they are always very good.

I would rate Zerto a nine out of ten.

My original use case was to protect against ransomware and any critical failure in our infrastructure, and that has been carried through to the present day.

It is incredibly easy to use, which attracted me to the product. I have been doing IT for over 30 years, so it did not take me very long at all to learn it. That is a good thing because when you have a solution like this going in, you want to make sure that you are fully confident with it within a short period of time. The learning curve for this solution was very short.

Zerto’s near-synchronous replication is good. Previously, when I tried to do it at a SAN level, which was part of the SAN vendor's portfolio of solutions, I could never get it to work. It was not very user-friendly. It was complex and difficult to configure. In comparison to that, Zerto shines.

Over the years, they have brought in immutable backups. They have brought in cloud migration, though I have not used that due to the nature of the Azure tools I use, but I have used immutable backups. In the past, we replicated from our on-prem site to our data center, and then more recently, we replicated from our on-prem site to Azure. The next stage is to replicate from Azure to another part of Azure or another region.

Zerto has had a very high impact on our RPOs. The recovery is very fast. It is instantaneous. We have already got everything replicated on our remote site, so we can just fire it up. All we have to do is follow through the scripts to change it over.

Previously, our RTO was very much in the order of two days. After we implemented Zerto, it is in the order of an hour.

We put in Zerto in response to ransomware because I had to do quite a lot of manual jumping around. Hopefully, we shut the gate on that problem. We have a solution to utilize.

We are a small to medium organization. We did not do downtime testing before we had Zerto, but now we do. It gives me the ability to test. We never had that option of testing. Usually, you cannot test the system in real-time because you have to turn off the live, whereas Zerto allows you to do it with different VLANs, etc. We can spin it up and effectively test it out. If I was doing a manual test, it would have probably taken me two or three days. I can do that in maybe 15 minutes. There is a 20 to 30 times improvement.

Zerto has had an effect on our IT resiliency strategy. It has supplemented where we did not have a tool before.

The ability to test that my backup regime is actually doing and working as I want it to do is valuable. It provides visibility and comfort. I can see in real-time that things are replicating, and my SLAs for my RPO and RTO are available instantly. That gives a lot of comfort. It is the sort of thing that gives you peace of mind.

Some of the cloud instructions around VNets and peering of networks could be clearer with some best-case examples. It is more complicated once you move into the cloud than running it on-premises. Actually doing these things is quite easy in the cloud and with Azure, but understanding how it fits in my environment can be quite a head-scratcher at times.

I started using it in early 2016 and have continued until the present day.

I would rate it a ten out of ten for stability. I never had a problem with it.

It has been fine. It has grown with the business as we changed things around. It has been very flexible. I would rate it a ten out of ten for scalability.

Their support is pretty good.

I used EMC SAN. Zerto is 400 times better. The previous one just did not work. I bought the SAN with the intention of having recoverability with it, and I could never get it to work. There was relatively zero support. It does not encourage us to persevere with it. We just ended up using it as a SAN and moved over to another solution.

We currently have a hybrid setup because we cannot migrate in seconds. It takes quite a long time to pick a network and move it into the cloud. It is not as easy as you would hope when you start moving into the cloud. There is a bit of complexity. If you have a network with multi-subscription, multi-network, VNETs, and peers, it takes a little bit longer to try and figure out how to make it work.

Initially, when I first put it on-premises, it took me about a day to get it working. In the cloud, it took a few days to head-scratch through it.

It is currently running between on-premises and Azure cloud. We do not split by department. We are not big enough to do that. We run a centralized compute function for the entire business, so it is relatively straightforward and flat as a design. Everyone uses the same environment.

It is used by only IT people. There are six of us in IT, but only three people use it with me being the primary person.

It requires a relatively small amount of maintenance. They have moved over to Linux-based machines, so we no longer have to upgrade them. We can apply a very simple process to update the actual version of Zerto. It needs a little bit of maintenance, maybe for an hour or so a month. I do the maintenance. I just keep an eye on it.

It is difficult to quantify that. I have seen no return on investment because I do not calculate around that sort of thing. If we had any disaster, we would have used it for real and would have seen a massive return on investment. It gives me peace of mind. If I am happy, then the management is happy.

Zerto has not helped reduce downtime in any situation because we have not had any downtime. Most people like me hope we never have to use it. It is like insurance.

It is not the cheapest product; it is not the most expensive product, but it works. It is a mid-range product, and it is justified in terms of being pretty quick and easy.

I would definitely recommend it, especially for people who have no current method of implementing a disaster recovery solution. It is a quick and easy fix, and I would highly recommend it.

I would rate Zerto a nine out of ten because we need a few more scenario examples when moving into Azure.

I use Zerto for backup and restore.

With both Veeam and vCenter, the restoration process took a considerable amount of time. Zerto bragged about how their restoration was much faster, and it was true. It seemed unrealistically faster when they described and said that they could restore a VM within minutes. With vCenter and Veeam, when we restore a VM, depending on the size of the VM, it can take hours. Zerto proved true, and we have tested it numerous times now. We have done restorations via Zerto, and it truly does a full restoration of a VM within minutes. That was the problem we needed to solve, and they provided the solution. We are very pleased.

We are able to do a restoration so quickly because it backs up in near real-time. Of course, nothing is going to be in real-time, but it is as near real-time as possible. Instead of copying a larger amount of data, it is able to copy just delta data which is in a compressed form so that replication is more frequent. If we need to do a restoration, we will be missing less data.

Its interface is like any enterprise-grade utility. It is complex and not easy to use, but it is learnable.

We were able to see its benefits after some time. That was mostly because we did not have a good opportunity to test it in production. The initial onboarding came with an opportunity for us to do a test backup and restoration, but that was test data. You find the true value of this platform when you use it in a production environment where a stakeholder is involved and there is data that if you do not restore will lead to problems.

We use Zerto to help protect VMs in our environment. The restoration time is in minutes versus hours. That goes a long way towards our RPO. With our previous platform, it took two hours, and with this platform, it takes five minutes. It has also had a positive effect on our RTOs.

Zerto has helped us to reduce downtime with a restoration time of five minutes versus two hours.

We have not had to use it for restoration because of ransomware. We were using a couple of VMs to test migration to a new database. While testing that migration, we caused damage to the VMs. We then used Zerto to restore them prior to that damage, and it was fantastic. The restoration was quick and effective, and we were back in production in minutes versus hours.

Zerto has reduced the time spent on DR testing but we still do the same number of DR tests throughout the year to make sure. It just takes a lot less time.

Zerto has improved our confidence tremendously, and it has reduced the RPO of any potential restoration needs.

I find Zerto's ability to restore a virtual VM much more quickly than Veeam or vCenter's restoration capabilities to be incredibly valuable.

I cannot think of any features that Zerto does not have. They probably have a lot of features that I do not even use. I am primarily interested in Zerto as a backup and recovery mechanism, and it does a phenomenal job of that. It is an enterprise-grade tool, and enterprise-grade tools tend to be complex. They can be a little difficult to use at first until you learn them. It is not reasonable to suggest making it easier to use because it is an enterprise-grade tool, and it is very robust. Therefore, it is not going to be easy to use. I just have to spend the time to learn it and become good at it. I am very pleased with it as is, but the ease of use of the restoration utility could be challenging initially.

I have used Zerto for just over a year.

It is 100% stable. We have had no downtime with it, and we are pleased with its uptime and stability. We have great confidence that it will be available and usable when needed.

I have not personally contacted Zerto customer service, but Todd, my sysadmin, is the primary point of contact for Zerto. He has contacted them for issues or day-to-day troubleshooting. When there is an upgrade to be done, he always reaches out to them to get guidance and ensure that he is doing the upgrades correctly. They are very good to work with.

We were using Veeam. There were no security concerns. It was more about performance. The restoration took approximately two hours with Veeam compared to five minutes with Zerto. The benefit was obvious, but there were no concerns about data security in the backups, protection mechanisms, or air gaps on either platform. It was just about the performance.

Neither one is easy to use. They are both very similar. Veeam is probably a little bit more complex than Zerto. Zerto is already doing a slightly better job than Veeam in ease of use, but they are both very complex and difficult to learn at first until you learn them.

Anything new is always going to have a level of difficulty. It was difficult, but Zerto's onboarding development team helped us every step of the way. As we crossed bridges and had problems, that team jumped right in the middle of it and helped us resolve each and every problem until we were a hundred percent satisfied.

To fully set it up, from the kickoff call until I was satisfied that it was fully functional, it took about two weeks. There was probably a month's worth of preparatory work done in advance of the actual kickoff call and deployment, including some information gathering. You could include those 30 days prior as part of that work. Technically, it was about two weeks from the kickoff call to fully deployed and fully functional.

It is a one-person job. One person primarily takes care of it, but we have three of us who are kept abreast and familiar with the process so that we do not have a single point of failure. It is definitely something that one person can handle.

In terms of maintenance, it requires periodic patching and upgrades.

It is an enterprise-grade product. When you buy enterprise-grade tools, you have to expect to pay a higher price. It goes back to the idea of you get what you pay for. If you want an old cheap tool, you pay cheap prices to get it. If you want a good-quality tool that is robust and does a good job for you, you have to pay a higher price to get that, and Zerto is no different. We pay a little bit higher than the cheap tool price, but we get our money's worth. I am not dissatisfied with the price.

I would rate Zerto a nine out of ten. There is nothing that is absolutely perfect, but Zerto does a pretty good job of getting as close to perfect as they can.

While we primarily function as a service provider rather than serving a direct use case, our core focus lies in disaster recovery. We employ a rigorous testing process akin to gear testing and actively engage in recovery operations using Zerto for a diverse clientele, including numerous entities in the financial and government sectors.

Zerto is straightforward to use.

We started to see the full benefits of Zerto one month after the implementation.

The effort on the RPOs has been excellent, greatly enhancing our operations. We have a diverse range of customers who are quite satisfied and express confidence in the timeline for recovery.

Even Zerto's RTO is low.

Zerto has helped significantly reduce downtime and helped reduce DR testing by over 45 percent.

The most valuable aspect of Zerto is synchronized replication, which is very useful. Additionally, the availability of the virtual machines is quite good. Regarding the recovery point, we achieved at least ten recovery points, and the availability of the virtual machines is particularly notable.

The main issue with Zerto is its user interface, which lacks flexibility and presents a steep learning curve. To improve usability, the UI should be simplified and streamlined, making it more accessible to technical and non-technical users. Additionally, the UI should be better aligned with the platform's various options and features, ensuring a more intuitive and efficient user experience.

I have been using Zerto consistently for almost four and a half years.

Zerto continues to be a stable solution.

Zerto is scalable.

We interacted with technical support many times. They were totally fine and very polite. We receive support around the clock, which is excellent.

The initial setup of Zerto was straightforward, and their customer service was instrumental in helping us achieve a stable implementation within one month.

A team of five implemented Zerto in-house.

One of Zerto's main disadvantages is its pricing structure, which involves significant upfront costs and limited options for startups with minimal initial funding. Although Zerto offers a comprehensive suite of features, the high cost and lack of flexible payment options, such as pay-as-you-go subscriptions, present a barrier to entry for many businesses. To increase accessibility, Zerto should consider offering lower pricing tiers or more flexible subscription models tailored to startups' needs.

We evaluated a lot of different solutions.

There are some disadvantages; therefore, I rate Zerto eight out of ten.

We are not a partner, just a customer, but we are trying to collaborate with them as a reseller within one year.

No maintenance has been required as of yet.

Our primary use case is for seamless migration to our client's cloud environment, ensuring a non-destructive migration with minimal downtime. We focus on cloud adoption and migration, and Zerto assists with the smooth migration of client workloads to the cloud environment.

Additionally, Zerto provides disaster recovery solutions, data protection, and ensures minimal disruption during migration.

Zerto has significantly improved our organization's IT resilience by ensuring security, protecting against ransomware, and enabling seamless cloud migrations.

It has enhanced our flexibility, ensured reliable recovery, and minimized downtime.

Overall, it has increased our ROI by helping secure our digital ecosystem and improving client satisfaction.

The most valuable features of Zerto include its simplicity, ease of use, and automated features like failover and failback. It facilitates hybrid cloud and multi-cloud strategies, providing seamless migration with reduced risks. Zerto automates the complexity of manual tasks, which is beneficial for streamlined operations.

Zerto could improve by offering more flexible pricing models, especially for startups. In the Indian context, cost is a concern for many businesses, and a pay-as-you-go model would be beneficial. Additionally, more cloud support is needed beyond the major providers like AWS and Azure, such as support for Alibaba and Oracle Cloud.

I have been using the solution for three years.

The solution is stable, straightforward, and reliable. It consistently performs well in recovery situations.

As a large enterprise, we find the scalability of Zerto to be very good. It effectively supports our extensive use across many users.

I rate the customer service and support highly. They provide assistance with initial setup and other issues promptly.

Previously, we used different solutions like vMotion and NetBackup. We switched to Zerto as it provides faster recovery and minimizes recovery time, which was a limitation in the previous solutions.

The initial setup was smooth and straightforward, with the support team providing help, particularly in configuring work storage.

Our ROI has increased by about 15% since implementing Zerto.

I would rate the pricing, setup cost, and licensing around a seven on a scale of one to ten. The pricing model could be more flexible to accommodate startup companies with lower budgets.

Zerto is adaptable and straightforward, making it easy for new users to adopt. The solution has significant advantages in recovery and offers good scalability.

I would rate Zerto an eight out of a ten.

I use Zerto to monitor replication, configure protection, and manage disaster recovery and performance.

We implemented Zerto to manage disaster recovery and also for faster performance on backups and failovers.

Learning how to use Zerto can be easily achieved with some training and practice.

Zerto has helped us reduce downtime, retrieve backups faster, and manage our workload more efficiently.

Zerto has reduced downtime by 20 percent and helps protect the VMs in our environment.

It is 25 percent faster at recovering data compared to IBM Spectrum Protect.

Zerto has helped save four hours per week in recovery situations and has reduced our disaster recovery testing by 30 percent. We have used five percent of those savings towards other value-added tasks.

It has positively impacted our IT resiliency strategy.

Zerto enables disaster recovery in the cloud which is important.

Zerto provides real-time analytics and monitoring, enabling our organization to quickly identify and resolve issues.

Zerto makes my work easier. Replicating my settings helps me recover point objectives faster and retain policies.

The most valuable feature is the customization that allows me to set my protection group myself.

While Zerto provides good service, I find the pricing to be high and believe there is room for improvement. I would like to see Zerto implement a pay-as-you-go model.

While Zerto offers scalability, its implementation can be more challenging in larger organizations, indicating room for improvement in its scalability features.

I have been using Zerto for three years.

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

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

The technical support responds promptly to our requests.

I previously used IBM Spectrum Protect but Zerto provides a quicker recovery time. With IBM the recovery process for particular data is manual but with Zerto it is automated.

The initial deployment of Zerto was straightforward and took two hours to complete. Two people were involved in the deployment.

We have seen a 20 percent return on investment.

Zerto is priced high.

I would rate Zerto eight out of ten.

Zerto is deployed in multiple departments and we have ten users.

I recommend Zerto because it helps recover data faster and improves its overall quality.

We use Zerto to back up and recover our data servers.

Zerto is easy to use.

The near-synchronous replication is beneficial and simplifies my work.

I saw the benefits of Zerto immediately after we started using it.

Zerto does a good job of helping protect our virtual environment.

We have seen a 30 percent improvement in our RPO using Zerto.

We have seen a 40 percent improvement in our RTO using Zerto.

Zerto has helped us reduce downtime in several situations and has helped reduce the amount of our disaster recovery testing.

It helped save 20 percent of our time during data recovery situations due to ransomware.

Zerto has had a positive impact on our IT resiliency strategy.

The most valuable feature of Zerto is the quick recovery time.

The technical support response time has room for improvement.

I am currently using Zerto.

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

Zerto is highly scalable.

The technical support offers high-quality responses, but the response time is lengthy.

I previously used Azure Backup. Zerto is faster and more dependable.

The initial deployment was straightforward and took two hours to complete. A team of three people was involved in it.

The implementation was completed in-house.

Zerto is expensive but offers many features that make it competitive.

I would rate Zerto nine out of ten.