HPE Zerto Software Reviews

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 primarily use Zerto as a disaster recovery tool to handle data transfer between virtual machines. Currently, Zerto is implemented on-premises, as 90 percent of our services reside there. However, we plan to migrate some services to the cloud and utilize Zerto's migration capabilities to move VMs directly from our on-premises environment to the cloud. This is a crucial feature for us, as our virtualization technique relies heavily on VMware, and Zerto allows for straightforward migration of critical VMs to the cloud.

Our multi-campus university faced challenges delivering services hosted in a single location to geographically dispersed users. The extensive data volume and risk of outages due to disasters led us to implement a Disaster Recovery and Continuity setup. This involves hosting primary services in one data center and maintaining a disaster recovery site in another. Zerto's replication technology allows us to continuously update data at the DR site, ensuring data currency and the ability to roll back to a stable version quickly.

Zerto is straightforward to implement because it only requires the installation of an agent on the VMs designated for migration. A service, typically a VM, must also be deployed at the disaster recovery location. This entire process is simple and can be completed within three days.

Zerto's near-synchronous replication occurs every minute, allowing for highly granular recovery points. This means that even if interruptions or malware disruptions occur within that minute, Zerto can restore to the last known good state, effectively recovering the entire setup to the latest backup. This capability ensures high data security and minimizes potential data loss.

One of the main benefits of implementing Zerto is its data compression, which significantly reduces the load on our IPsec VPN. Zerto compresses data by 80 percent before transmitting it across the VPN, minimizing the data transferred between geographically dispersed locations. This compression and subsequent decompression at the destination alleviate the strain on the VPN, preventing overload and ensuring efficient data synchronization.

Zerto simplifies malware protection by integrating it into its disaster recovery and synchronization features. This comprehensive approach eliminates the need for separate antivirus setups in virtual machines and applications. It streamlines our security measures and removes the need for additional software or solutions, resulting in an excellent return on investment.

Zerto's single-click recovery solution offers exceptional recovery speed. Through the user interface, a single click allows for a complete restoration from the most recent backup within two to three minutes, enabling rapid recovery and minimal downtime.

Zerto's Recovery Time Objective is excellent. In the past, if a virtual machine crashed, we would recover it from a snapshot, which could take one to two hours. With Zerto, the recovery process takes only five minutes, and users are typically unaware of any disruption. This allows us to restore everything quickly and efficiently.

Zerto has significantly reduced our downtime. When malware affects our data, Zerto immediately notifies us and helps us protect other applications, even those not yet implemented with Zerto. By monitoring these applications, we can quickly identify and address any potential malware spread, minimizing downtime across our systems.

Zerto significantly reduces downtime and associated costs during disruptions. Our services are unified, so in the event of a disruption without Zerto, even a half-day disruption would necessitate offline procedures. This would lead to increased manpower, service delays, and substantial financial losses due to interrupted admissions and other critical processes. By unifying service processes, Zerto minimizes the impact of outages.

Zerto streamlines our disaster recovery testing across multiple locations by enabling efficient failover testing without disrupting live services. Traditionally, DR testing required downtime of critical systems, but Zerto's replication and failover capabilities allow us to test in parallel with live operations. This non-disruptive approach ensures continuous service availability while validating our DR plan, even in scenarios like malware attacks, by creating a separate testing environment that mirrors the live setup. This comprehensive testing provides confidence in our ability to handle real-world incidents effectively. This saves us over 60 percent of the time.

Zerto streamlines system administration tasks by automating many processes, thereby reducing the workload for multiple administrators. This allows them to focus on other university services that require attention and effectively reallocate support resources from automated tasks to those requiring more dedicated management.

Zerto is used exclusively for our critical services, providing up to a 70 percent improvement in our IT resilience.

One of the most valuable features of Zerto is its straightforward cost model. It's essentially a one-time purchase, meaning you pay once and can use the software indefinitely despite the three-year license. This non-licensing-based approach allows for long-term use with a single purchase. Additionally, Zerto offers excellent technical support with responsive and helpful experts.

Zerto's pricing model is cost-prohibitive for small—to medium-sized businesses. Its structure limits affordability to approximately five to ten virtual machines. To increase accessibility for small and medium businesses, Zerto should consider a competitive pricing strategy, possibly including subscription-based licensing options. This would enable more organizations to utilize Zerto's services.

I want Zerto to add support for Proxmox.

I have been working with Zerto for one year.

Zerto is stable.

Zerto is scalable; however, the primary concern remains the cost, especially if needing to scale to 300 virtual machines. It is more cost-effective to use fewer virtual machines.

Zerto's technical support is superb. Following HP's acquisition of the product, significant improvements have been made.

Positive

The initial setup was straightforward. We implemented it in two geographically separated campuses, setting up one server and adding another for disaster recovery. Zerto's demo provided a solid understanding and clear strategy for the implementation.

We did not use third parties for deployment; our on-premises engineers handled it. Only two to three staff members were needed.

The return on investment is evident, as Zerto saves more than 60 percent of time in various operations compared to the previous manual processes. The savings extend to hardware and resource allocation, which were reduced by Zerto’s efficient backup solutions.

I rate Zerto ten out of ten.

Our on-premises firewall provides a basic level of security, but it cannot guarantee complete application security. Therefore, the application, including Zerto, must have robust security measures to mitigate any vulnerabilities. Even with a firewall, loopholes can exist, potentially compromising Zerto and other services. To ensure comprehensive security, we can integrate Zerto with our security firewall, enhancing protection and minimizing the risk of software compromise. Ultimately, Zerto remains our primary solution for software recovery in case of a security breach.

Zerto requires minimal maintenance due to its operation on virtual machines. Three people are required for the maintenance.

We have Zerto on 300 virtual machines in our environment.

Zerto's capabilities would greatly benefit organizations with on-premises and on-cloud setups, as it facilitates seamless migrations. It is highly recommended for anyone prioritizing data security and disaster recovery assurance.

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.

Positive

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.

My current use cases for HPE Zerto Software include site-to-site and site-to-cloud.

HPE Zerto Software has saved me time in data recovery situations due to something like ransomware because we have protection against it. Due to the logging functions, we can go back in time and bring systems up a day before or a day after. We have been able to avoid ransomware issues with HPE Zerto Software.

HPE Zerto Software has helped to reduce our organization's DR testing.

The features of HPE Zerto Software that I have found most valuable are the copy capabilities, specifically being able to copy a VM over to another site and bring it back up if I have an outage. I used HPE Zerto Software recently to go from cluster to cluster, and I was able to move VMs seamlessly. 

I find HPE Zerto Software very easy to use. Going in and being able to copy the VM makes it very efficient.

Near-synchronous replication makes it pretty easy for me to move things on the fly, so I can be up within about 10 minutes. Being up in 10 minutes is important for me because if we're not up in that timeframe, we have users complaining and calling.

HPE Zerto Software could evolve to where, instead of me having to push a button, it can detect disasters on the fly and automate disaster detection.

I have been using HPE Zerto Software for about a year.

HPE Zerto Software is really stable. I haven't had an experience where I've had downtime.

HPE Zerto Software scales just fine with the growing needs of my organization; it's gone from a small test group to a larger test group with no problems.

I'd give their support a ten out of ten. 

Positive

The support team was really great. Everything was configured, and out-of-the-box configurations were seamless.

I have seen a return on investment from HPE Zerto Software, already just moving from data center to data center. Just moving the things over from one spot to another with no outage time, or very little outage, reflects how I've gotten the return on investment.

The licensing and setup costs have been reasonable.

I didn't consider any other solutions before selecting HPE Zerto Software. It was given to me.

I would rate HPE Zerto Software a nine out of ten.

We use Zerto for disaster recovery between our private data centers.

Near-synchronous replication is the primary reason we chose Zerto, as nobody else is able to meet the same replication times. We have some special contracts, so Zerto is the only one that can meet those contractual requirements.

Zerto has had a significant impact on our RTOs. We have probably reduced our RTOs by 70% to 80%. Previously, we relied on manually replicated backups that we had to restore from, resulting in significant RTO compared to Zerto.

We use Zerto to help protect virtual machines in our environment. When it comes to recovery, if other solutions take five minutes, with Zerto, we can usually get them up in under a minute. Our RTOs are much quicker on Zerto. It is probably 20 seconds on Zerto versus an hour with others.

We have had multiple live disaster recovery events where Zerto saved us a lot of downtime. We have not had any ransomware situations, but it has saved us time in generalized data recovery.

Zerto has helped reduce DR testing. For the customers for whom we use Zerto for disaster recovery, we usually do DR testing once a month, and it takes us probably two minutes to run those DR tests. With other solutions that we use for our wider customer base, it takes us about two days to go through all of our DR testing.

Zerto has had a significant impact on our IT resiliency strategy. The tier-one customers that we use Zerto for have very strict requirements for their disaster recovery capabilities, and Zerto is able to meet those contractual obligations pretty easily.

We were able to realize its benefits immediately after the deployment.

The low SLA times are valuable. It is very easy to use with a straightforward user setup.

The biggest area for improvement is the technical support side. Although it has improved somewhat, after the HPE acquisition, it became apparent that level-one technical support was moved to groups unfamiliar with the Zerto product. As experienced users of Zerto, when we need to open a ticket, dealing with level-one technical support can be tough. We often need to escalate immediately due to our internal skill set surpassing level-one support capabilities. That is the biggest complaint we have with Zerto.

We have used it for roughly five years, possibly six years.

The solution is very stable, especially in the newest version. There were some challenging times shortly after the HPE acquisition, likely due to engineering changes. However, the newest version is incredibly stable, and we have no complaints.

We have not had to worry too much about scalability because we have a fairly limited implementation.

Once past level-one support, the experience improves because we then interact with people familiar with the product. I am assuming that the level-one support is generalized HPE technical support, and they are relying on Zerto Runbooks to be able to help us. They do not have a lot of familiarity with the product.

For the quality of support, I would rate it a seven out of ten.

Neutral

Before Zerto, we primarily used Veeam, but we needed faster RTOs for tier-one customers, who had contractual obligations for RPO and RTO. At that time, Zerto was the only solution that provided the necessary speed. The rest of the industry had not caught up. Currently, we use Cohesity for everything else, but for customers with stringent standards, we rely on Zerto.

Zerto is definitely easier to use from a GUI standpoint and is very straightforward for automation. It is a one-click solution for us to do our disaster recovery events.

Its initial deployment is very easy. We recently did a deployment of version 10 for our VMware 8 deployment. We completed it in a single day, taking approximately three or four hours.

It requires maintenance but it is very infrequent. We need to make manual changes to our Zerto environment maybe once a quarter.

Just one person handled the implementation.

I am not very involved with the pricing, but from my understanding, it is fairly expensive for us. This is why we limit its use to our tier-one customers. We have other disaster recovery solutions for our other customers due to the cost.

It is pretty straightforward. I would rate Zerto a nine out of ten.

We have two data centers, so we use HPE Zerto Software for site recovery. We fail over, run out of one data center, then we fail back and run out of the other, and we do failover testing. 

We were using VMC on AWS with VMware replication. The challenge was it had a five-minute RTO and we wanted something faster. At the time, HPE Zerto Software didn't support VMC on AWS, which was actually our first choice. Then we had a mandate to build a new data center.

We wanted both physical locations, so we went that direction and decided to go with HPE Zerto Software. We wanted something that we could fail over quickly, have minimal recovery times, and make sure that we could come up quickly. We use the move feature in HPE Zerto Software probably the most, moving from data center to data center. It allows us to meet with our compliance regulations to test our DR site and run in our DR site with seamless operation.

We've proven a few times that we can fail over within a very short window, and it works very well. Our RTO with HPE Zerto Software is less than five seconds. It is extremely important. We work in the financial industry, and being able to fail over and know that we can bring that server up within a very short window and that the data is going to be accurate means we're not having to go back and rework a day's worth of data. That's what we wanted and that's what we got.

The failover test option in HPE Zerto Software is the most valuable at this point since we can validate that things are going to come up, that the data is valid, and then tear it back down without having to interrupt the users. 

It's extremely easy to use HPE Zerto Software. 

Our first failover test went flawlessly. We failed over our entire data center, approximately 200 VMs in half an hour - very fast. This last fast failover, we ran into a couple of hiccups. Working with support, we found we need to do more testing in between our main failovers since we've actually had an 11% failure rate of things not coming up. They advised us to test, validate, and then resync if needed, so we're learning from it.

We haven't experienced any ransomware yet with HPE Zerto Software. Regarding time savings, it has definitely been beneficial. Once we've got it set up and can manage it, it really is a time saver.

We haven't had a situation where we've had to use it to reduce downtime. Comparing it to our other failover solution, the speed is notable. We used to schedule an eight-hour day to do this, and now we're scheduling a half an hour, which saves us significant time on weekends.

Regarding RTOs and RPOs with HPE Zerto Software, we can look at it and know exactly where every VPG is regarding recovery time. The speed to move it over and bring it up is extremely efficient for us.

The solution has helped reduce our organization's DR testing. Previously, we would isolate our DR and test in a defined bubble just to validate the data was there and users could access it. Now we can fail it over to our backup data center and actively run there. We can fail it back and run both locations in an active-active mode with HPE Zerto Software, which we hadn't been able to do before.

It has allowed us to trim the team down and focus on other tasks without constantly worrying about disaster recovery. We know it's there and we can validate and test it through our monthly procedures.

When we did our test this year with HPE Zerto Software, we had some failures that we weren't expecting. The challenge was realizing there was data corruption, and fortunately we found it before we committed the failover, so we could fail back. We could resync it, and we weren't in an actual disaster. If there's any way to validate that data on the recovery site without having to manually go in and do failover testing and try to validate, that would be a feature that would be really nice. We're not sure why we had some corruption, however, we did the resync and it seemed to bring it back up and fix the problem. That's probably the biggest area I'd ask about - some way of validating the recovery sites in an automated fashion.

We started using HPE Zerto Software in April last year.

We haven't had any crashes or performance issues with HPE Zerto Software, except trying to figure out why we had some data corruption. Overall, it seems to be functioning very well. Support's biggest recommendation was that we just need to do more failover testing and validate.

We have not expanded our usage of HPE Zerto Software.

The customer support I received from HPE Zerto Software has been very good. I haven't had any complaints about the support we receive. I would rate it a nine or ten. When I ask them a question, they give me a very quick response.

We were using SRM before selecting HPE Zerto Software. From attending different conferences, HPE Zerto Software was where I wanted to get to, however, at the time, our disaster recovery site wasn't allowing for it. Comparing SRM to HPE Zerto Software, I really prefer using HPE Zerto Software. It's easier to group, set up. I can see really quickly what things are doing and I feel a lot more comfortable that things are working.

Setup was extremely fast, and we had the system up and running within a couple of days. Our biggest hold-up was getting the network configured correctly. For training, we were able to take some online courses that got us up to speed very quickly.

During the setup for HPE Zerto Software, we were working with a technician who could walk us through it and that worked really well for us.

Since we just got HPE Zerto Software, our pricing didn't seem too high. Our renewal is next year.

We used SRM before adopting HPE Zerto Software to address similar needs.

My rating for HPE Zerto Software would be ten 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.

Positive

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.

We use it for disaster recovery, replication, and backup.

We were able to see its benefits immediately after we deployed it. I used it to move sites. It is a good tool for transferring from one site to another. It does the configuration on its own and the site comes online seamlessly. You just have to commit to it, and it comes online and no one even notices it.

We create a job, which is a VPG, and we tell it to replicate it to another site. I live in Philadelphia. If Philadelphia gets attacked, we could shut it off and then go to the site that it replicated over and turn that on. It will just work as if nothing happened.

All the RPOs are less with our infrastructure because it is VM to VM in less than five seconds. We have never had a spike in our RPOs.

The recovery time of each VM is less than three to four minutes. Once we send a job over, it starts doing its thing. There is an auto-commit button, or we could time it to how much time we need before commitment. Once we bring up a VM and it reboots, we will see all the changes made, such as the IP address. If we go to DNS, we can see that the DNS entries have been updated with the new IP. We then commit to it, and it just comes back online.

Zerto has helped us reduce downtime. In just about five minutes, we are up. We had one incident with a Windows patch update to a server. The server could not come back online. We went in and recovered the VM right before it rebooted and got it back online. It had the same IP and other things, and everything was fine. Even though there was a slight downtime, we were able to get it back 100% before the reboot, and then we took off the update.

Zerto has saved us time in a data recovery situation due to a vendor mistake. We use a vendor for patching. The vendor accidentally mistyped something and took down a couple of servers because of this registry. We were able to get all the VMs back online. It took about three minutes per VM. When we used Veeam, depending on how much data was there, it took us about 45 minutes to an hour.

Zerto has reduced our organization's DR testing. We send it to a DR site from prod and then back to us. It goes from prod to DR and then DR to back in less than ten minutes. We did a DR move. We had about 15 VMs. We moved all the VMs to a different site. We then moved this actual site to a different location and then moved everything back. It did not take that long compared to Veeam.

Zerto has had a positive impact on our IT resiliency strategy. I have never had a problem. The product works very well. Their support is always active. They are willing to solve any problem that you have. Each time I have spoken with them, they have helped with every question to make sure our infrastructure is running well.

The most valuable feature for me is the replication. If I need to fail over sites, it can be done quickly, in less than five minutes. Each backup is implemented in five seconds. If we were attacked, I could revert to a backup from five seconds before the attack, and no one would know we were attacked. 

Once it is implemented with the vendor, they show you everything. Everything is very simple and easy. Replication and Restore are the buttons to focus on. It is all there with just a couple of clicks. It is simple. It is laid out simply so that you can understand it quickly.

I would suggest improving automatic updates. Their software requires updating level by level to keep it current. I was unaware that I was several versions behind, so I needed assistance to guide me to the current version.

I have used the solution for about a year and a half.

It only crashes if there are insufficient resources on my ESX box, which I discovered after overloading it with too many VMs. When the Zerto job tried to run, it crashed due to a lack of resources. I consulted with tech support, and we determined the solution was to move the main workload to a resource-available ESX box. After double-checking, everything has been running smoothly. Having good equipment ensures stability.

Scalability is tied to our vSphere environment. By adding more hosts and installing VRAs on each, tasks can be efficiently managed. Increasing the number of hosts allows for more VMs, depending on licensing. The bandwidth is also strong.

I would give their support a ten out of ten. I deal with support often, and online ticket creation yields a quick response. They understand what they need, and I provide it. They analyze the logs, suggest changes, and everything works well.

Positive

We used Veeam, which is more in-depth and requires extra steps for recovery. With Zerto, I just log on to the GUI and click what I need. For a live VM backup or replication, it takes just a few clicks, which led us to choose Zerto over Veeam.

Zerto is the easiest one that I have used. In terms of pricing, it is way better than Veeam.

Our MSP used Zerto to do a project for us. I was in the meeting looking at what they were doing. It seemed so simple to use. I asked them if they could compare this to Veeam, and they said that this is way easier than Veeam. With Veeam, you have to log on to the actual backup program. You have to go to the job that you are looking for and right-click it. There are about six steps after that, whereas in Zerto, when you go down on the bottom left, with just two clicks, a menu pops up, and then you are done with another three clicks.

It is on-prem. It is VM to VM. We are also thinking about a third solution, which would be on their site. Right now, we have VM to VM, but we have two NAS for hot and cold storage, so we are using everything that they offer at the moment, but we probably might head down more in the future.

The installation process was new to us as we started from scratch. After that, it was simple. Installing the VRAs involved pointing to ESX boxes. The NAS storage connection is simple; I just enter the IP address and credentials, and it links via SMB. I just create the job, point it to its destination, and it is ready.

Deployment was handled by one representative and me. I am also responsible for managing it.

In terms of maintenance, it requires manual updates.

Its pricing is way better than Veeam.

My advice to new users is to become more familiar with it. Once you start using it, it is easy to pick up and manage.

I would rate Zerto a ten out of ten.