HPE Zerto Software Reviews

Our primary use case is for our Tier 1 application environment, we're an SQL environment. We have around 25 VMs that are replicated to a hot site or warm site. And we're a VMware shop and we use Pure Storage as our SAN, but that doesn't matter because Zerto's agnostic. 

We're a small shop. I am the only Zerto user and my official title is Senior Systems Engineer. I handle anything data center-related as far as information stack, the blades, networking, VMware Hypervisor, and Pure Storage. We also have a Citrix environment as well we have to support. I do all of the data center work.

Zerto is a set it and forget it kind of thing. At least it's more of an insurance policy for us. We don't have a good DR plan, but the peace of mind knowing that the data is replicated off-site, like a repository or offsite environment, there is value to that. We just haven't been able to fully embrace the actual testing of the failover and failback process. The testing has worked, but we haven't done a full production failover yet. We've been planning for around a year to do one but it keeps getting pushed back.

Being hardware agnostic is nice in that we don't really need a 15 second recovery time. It's easy to use. It's always doing updates behind the scenes. These are the positive things. The setup is pretty easy. Building out the VPGs is pretty easy. And it works like it's supposed to.

Zerto does what it says it will do when it comes to providing continuous data protection. It gives me all my recovery points up to 15 seconds or less. So if need be, we could recover to that point in time that it says it can do.

Zerto is easy to use for the most part. It's pretty simplistic. The UI is pretty simplistic. There are some things that I'm waiting for newer releases to address some functionality that I'm curious to see has been fixed or not in the new version.

There are still some pieces in testing that aren't automated. There are still some built-in scripts or workflows I wish Zerto would do out-of-the-box, versus having to PowerShell or have a vendor create it, or create it myself. We haven't done a full failback yet of production so I couldn't really say. The failover process is a lot of manual steps, but Zerto is a mechanism that gets the data there. In that aspect, it does what it's supposed to do. But I wish they would expand on their out-of-the-box functionality for the VM. When you fail it over, there are DNS and SQL changes and there are reboots. There are some things I wish that Zerto would facilitate with a checkbox that would do some of these things for me versus having to PowerShell it and put the scripts in a certain place and have support run it. I want it more automated if possible.

The issue I have with ransomware is if I don't know I have ransomware in all my recovery points, and if it goes three months, I wish Zerto somehow either bought a company or could tell me that we're infected with ransomware. If I don't know how ransomware and everything gets encrypted, there's nothing to restore back to if all my recovery points have been corrupted. So I wish Zerto somehow had a mechanism to alert me of suspicious activity.

We have a Trend product that does that for us. We can get alerts of things that Trend finds, but it's always nice to have layers for your security. We have alternatives, but it would be nice if Zerto had a mechanism to alert me as well.

Alerting has also been a pain but it was supposed to be fixed in the newer version and that's. I would like to have more granular alerts.

I have been using Zerto for about four years now. 

When it comes to stability, it does what it says it's going to do. 

I do some babysitting because the alerts are relentless. My biggest pain point is the endless amount of alerts that are just noise. I have to log in and see what actually is an issue because the alerts are just endless. There's not much maintenance I have to do besides logging in and babysitting from time to time.

We keep wanting to test it. It's our main DR strategy, but we just haven't had a window to vet full failover and failback. As far as increasing, I think we're pretty stagnant at the point with what we're backing up with it.

I would rate Zerto support a seven out of ten. 

The initial setup was straightforward. You could deploy the VRAs pretty simplistically as long as you set an IP via the UI, so that was pretty easy. We were up and running in a day.

Our implementation strategy was rushed. We were doing a data center move and we just wanted an extra copy of the data. So this was a stop-gap solution that we stuck with.

We used a reseller for the deployment. They met our expectations. They provide the product, but outside the product, we have to get a stronger resource. If it goes above and beyond like if it's broken, they call Zerto support. If I want some PowerShell scripts and some cool stuff to be done, they need to find a resource. They provide the basic service, which is great. Above and beyond that, they're average or below average.

We pay monthly for the CPU, memory, disk space, the Zerto replication, and then there's a Microsoft charge as well on top of that for the operating system. We pay month to month and we go year to year.

There are additional VM resource costs.

My advice would be to think about the large VMs that you're backing up. Think about the wasted disk space and wasted resources on your production environment, and if you replicate that to a hot or warm site, you have to pay for those resources. The Zerto price is what it is, so you need to work with the business and ensure your Tier 1 or most critical VMs are what you're backing up or want to back up, not just everything. Then scale that to something manageable for replication and find out if you can have minimum resources while replicating and then scale up in a true DR scenario and only pay for the resources as you need them.

It's not really Zerto's fault, but you don't have full visibility on the protected site so you have to rely on your vendor for visibility if an issue arises.

I would advise asking a lot of questions. If you're an SQL environment, make sure you failover all the key components in the correct way. If you want it fully automated, make sure you buy some extra hours to get professional support.

I would rate Zerto an eight out of ten. 

We use Zerto to replicate data between our on-premises data centers, as well as for replicating data to the cloud. It is used primarily for disaster recovery, and we're not using it very much for backups.

Continuous data replication is the most important feature to us, and we use it for disaster recovery. We have very short RPOs in the event of a data center outage.

With respect to ease of use, I would rate Zerto an eight out of ten. It is very easy to set up and utilize. The only reason I wouldn't give it a ten is that I would like to see more export capability. Right now, you can export your VPG to a spreadsheet, but you don't have a lot of control over what data goes there. You just get everything and the formatting isn't the best.

When we need to failover or move workloads, Zerto significantly decreases both the time it takes and the number of people involved. It only takes a single person to activate a failover and we can pretty much automate everything else. Instead of a week to recover a major application, we can do it in a day.

Mostly, this solution protects us from data center outages. With ransomware, it gets a little more complicated because depending on what they're doing, you could be replicating the encryption that they placed on you. Then, depending on how large your journal is, how far back you can go and how long the malware has been sitting in your network, it might not save you from a ransomware attack.

That said, it's still a major plus because if you have enough tools in your environment where you can catch the fact that they've been there, then if you've got 14 days, just as an example, in your journal, then you can go back far enough before they place any kind of encryption on your file. But, if you don't have other tools to also help protect you from ransomware, Zerto by itself may not be sufficient.

It's very rare that you have a true disaster where you have to failover a data center. I see Zerto more often being utilized to deal with some sort of database corruption. You can restore your primary site back from before the corruption. We need this Zerto protection, but it happens so rarely that you would actually have a full data center failure that, I can't say that we have had any staff reductions because of it. We have no staff specifically set aside for data recovery.

Beyond your normal path for backup and recovery, and those daily backups and managing that stuff, whether you're using Zerto for your backups or another backup utility in addition to Zerto, it hasn't really changed our staff.

The most valuable feature is the quick RPO for replication, which is our primary use case.

Zerto should add the capability to replicate the same VM to multiple sites.

The export capability should be improved so that it is more customizable in terms of what fields are exported and what the formatting is.

I would like to see the ability for Zerto to handle physical servers, although that is becoming less important to us.

I have been using Zerto with my parent company for the past several months and had been using it at a previous company for two years before that.

Zerto is very stable.

The scalability is generally good.

We're on an older version so this may have changed, but when it comes to cloud DR, they haven't kept us with the Azure capability. For example, Azure used to have an eight terabyte limit on disk drives. Azure now has a 32 terabyte limit, but Zerto still has a limit of eight. 

That said, when it comes to the number of VPGs and the number of instances, that has been sufficient for us. We have 646 VMs and 60 VPGs that are protecting 650 terabytes of data.

We have about four people who are managing it day-to-day. It is a shared role; our server engineering team is responsible for Zerto, and that team has approximately twelve people. They are all capable of utilizing Zerto, depending on their individual responsibilities, but there are probably no more than four people who currently use it on a daily basis.

We don't have one specific person to manage it but instead, we rely on the team. We're in the process of getting them all trained adequately. 

I have been in contact with technical support and I would rate them a seven out of ten. They are similar to a lot of companies, where they're very quick to respond to simple issues that might be in a playbook, yet slow sometimes to get a more complex problem resolved.

This was our first true DR tool. Before that, we were just using backup solutions. The one that we were using most recently was IBM Spectrum Protect.

I have a lot of past experience in my previous company with RecoverPoint, as well as with CloudEndure. CloudEndure was used specifically for cloud DR with AWS.

Zerto is much easier to use than RecoverPoint. Both Zerto and CloudEndure are very easy to use.

The initial setup is pretty easy to do. I was not with this company when they implemented it, so I don't know how long it took them to deploy. However, in my previous company, we initially installed and set it up in a day. We didn't have much trouble.

At first, we only had a couple of small test instances. We started adding things that we needed, over time.

Using Zerto has saved us money by enabling us to do DR in the cloud because we did not have to purchase the infrastructure at the alternate site. It's difficult to approximate how much money we have saved because we never built a DR site for the applications that we now have replicated in the cloud. There has never been an on-premises solution for them.

It is relevant to point out that we're not using it so much for day-to-day backups, but rather, we're using it for continuous data protection for DR and we have not had any disaster, so it's difficult to quantify our return on investment from that perspective.

However, from the perspective of being able to do cloud DR and not having to pay for that infrastructure, and even when it comes to the ease of use when we're going from data center to data center, I think we've got a definite return on our investment in comparison to not having a continuous data protection tool.

There is a difference between what we do and what we would have been doing without a tool like Zerto. In this regard, Zerto is a kind of overhead because hopefully, you're not using it day-to-day in a real disaster. It's more like insurance.

We evaluated RecoverPoint, but Zerto's better integration into vCenter was probably the reason that we chose it.

We do not currently use Zerto for long-term retention, although we are looking at the feature.

I highly recommend Zerto. My advice for anybody who is implementing it is to go through all of the best practice guides and be sure to review whatever database they have in there. This way, they keep themselves efficient.

Also, it is important to keep in mind that it's only at a VPG level that everything is consistent. So, if you have multiple servers and applications that need to be consistent with each other, then, they really should be in the same VPG.

I would rate this solution an eight out of ten.

We're using it for site plate replication and fail-over or disaster recovery. We're primarily using it to replicate between the data centers that we own and operate.

We've had a few disasters where we've had a site go out and we've had outages or hardware failures. However, with a single click, we can have all of the failover and when the other sites come back up, it can auto re-replicate in the reverse direction so there is no extra manpower required. Whereas, normally, we would be spending hours and hours cleaning up from the failover event.

We enjoy the simplicity of not only configuring replication but failing over with a single click and then having it automatically reverse replication. We've had other products such as Veeam, and their replication works, however, it's very cumbersome to configure. When you failover, there's a bunch of work you have to do after the fact to reverse the direction and to restore the VM and how it names it and which environment it shows up in.

In terms of continuous data protection, it's the best product that we've found that does this. It's not snapshot-based. It's continuous, so there are no specific points in time we have to worry about recovering to or from. It's pretty much any time, as long as it's within our replication window.

The solution is very easy to use. It's very straightforward. You don't really have to do a lot of reading through the documentation, or things like that. You can basically scroll through the menu and figure it out.

We have not had ransomware, so we haven't had to deal with that, however, we definitely had a disaster recovery issue we had where we had the fail-over site stop unexpectedly. It did save us a bit of data loss, whereas, normally, we would have lost six hours' worth of customer data. In this case, it was seamless. We lost seconds' worth.

The solution has reduced downtime. It has done so a couple of times. There could be some cost savings there. It's just not something we calculate.

The backup solution needs to be improved. From our perspective, Veeam and Zerto were competing products. They both do very unique things that they're very good at. For instance, Veeam can do replication well. However, it's really a backup product. Zerto can do backup, and yet it's really a disaster recovery product. It would be great if they could improve upon the backup functionality, or continually improve. We've seen some improvements, however, if they continue improving upon that it may eventually eliminate the need for the other product.

I've been using the solution for about three years.

The solution is very stable. We haven't had any issues. The only issue we had was a DHCP issue where we didn't static a couple of the DVMs, which is the agent for each ESX host, and we were having a few gaps in replication when the IPs would change, however, we've stacked those and that has resolved that issue.

We find that it's very easily scalable. The resource overhead is very minimal so it's really easy to scale up the environment and the product kind of automates the process for you. You select where you want it, hit install, and it handles it for you.

About five people use the product in our company. We have some system administrators, we have a couple of programmers and we have a DBA.

We have around a quarter of our environment replicated with Zerto. It's mostly our critical infrastructure.

We may possibly increase usage over time.

Technical support is good. I'd give it an eight out of ten. They're pretty quick to respond. They are almost always able to resolve my issue. I have no complaints. I only had a couple of support tickets, however, the experience was pretty good.

That said, their web portal is a bit clunky to navigate. For example, putting in a request, knowing where to go, or pulling up documentation or upgrading information wasn't quite as intuitive as it could be.

We are still using Veeam mostly for backup tasks. We use Zerto for site recovery.

The initial setup was very straightforward and easy.

The installation was simple. There are lots of guides and information. There are YouTube videos. They had training classes that were free that you can go to and they have a little lab environment. Even without the assistance offered, the way you install it is very straightforward and very simple. Really anybody can run the installer and have an idea of what they're doing right out of the gate without really any training.

Deployment took around a day.

We did have a specific deployment plan and we were able to execute that in about a day. Getting all the sites set up and then the VMs replicated was fast.

We have five people on staff that can handle deployment and maintenance.

We didn't use an integrator or consultant. We just did it ourselves.

There's not a direct ROI as it's being used as an insurance policy. The only time it really benefits us is when something bad happens.

It's reasonably affordable. Obviously, cheaper would always be better, however, it's not out of the expected range. We are just paying by VM. It's my understanding there are no extra fees.

I can't remember the companies off the top of my head as it's been a few years since we've done it, however, we evaluated five or ten different options that were popular at the time. Some of them were integrated with hardware. Some of them were software only.

In the end, it came down to Zerto due to simplicity. It's very simple and straightforward. It removes all the overhead of management and knowing what is active or what's the standby copy. It handles all of those pieces for you.

We're probably on the latest version or one version behind.

We very lightly use the product for very specific things. We have a couple of things that are very high data rate, very high IO, for which we cannot use traditional snapshot-based technology and we are using that to do a long-term backup.

The solution has not reduced the number of staff involved in data recovery situations. We have maintained exactly what we had. It's simplified it so it's possible to have a reduction, however, we haven't done any reduction from that.

The biggest piece of advice I could give is if you want the best-in-class for failover and replication, as well as ease of management, there is no better product that I've seen so far. Whether hardware or software combinations, this has been the simplest deployment and it just works.

I'd rate the solution at a ten out of ten.

Database replication is our primary use case. We don't use Zerto for backups. We use Zerto as DR at our sites.

It is deployed on-premises at several sites.

It is a good DR solution for a number of databases that we use. It is just a DR solution that works. It does that continuously. I like it. Once it works, it is set and forget.

We have used it as a test in a data recovery situation due to ransomware or other causes. We haven't had to use the actual recovery. We haven't actually had to use it in an actual DR scenario, but we do DR testing. The switchover is pretty good.

Recovery is the most valuable feature. It has a good DR solution.

Zerto's ability to provide continuous data protection is good. It works. It has continuous availability.

It is pretty easy to use. The interface is intuitive and easy to use. Once you set it up, it just works. So, it is great. 

I like that it's low maintenance; it's set and forget.

As far as replication technology goes, it is a pretty good product.

It has some quirks. We have quirks with appliances. Some things don't really work as expected, but it is minor. It doesn't really affect the overall functionality.

I have been using it for a couple of years.

The stability is good. There have been no major issues.

I have 12 engineers on my team. We maintain/administer Zerto to our organization.

It scales pretty well.

We have a large environment, but this actual deployment is pretty limited. It has a targeted use. We are protecting some production databases.

The support is good. I would rate them as eight out of 10.

We had another version of Zerto that we decommissioned, then we built a new one.

Zerto was already present in the company when I came onboard. We just renewed the support and built several new instances.

I was involved in the initial setup from the start. It is very complex as far as requirements go and what needs to be set out for Zerto. Once you set it up, it is fine. It works.

Back and forth, our deployment took a couple of weeks. It was deployed on different sites. We needed to set up, provision, have networks open, firewalls, and allocate dedicated storage. We also needed to install it, build it, deploy the agent on the host, and configure it.

I deployed the solution myself.

I am pretty sure my company has seen ROI.

It is a good solution. It doesn't work for everything, but for certain use cases. You can't restore your entire site with it. However, if you need to restore or replicate a certain number of production and mission-critical applications, it is a good solution for that.

I like Zerto. We have big databases, so it does take a lot of storage to replicate it, but I think it is a good solution. I would recommend it.

I would rate it as eight or nine out of 10.

We have Zerto as an emergency backup if we were to lose electricity or compute.

I purchased Zerto because I wanted to get a return to operations and to minimize the downtime.

The return to operations is the most valuable feature because it decreases the amount of time it takes us to recover. 

Zerto is the best of breed when it comes to providing continuous data protection.

It has a number of features rolled together. So when we need to failover, it does it successfully without a lot of stuff that we have to tune underneath the scenes. We use Zerto for the short-term retention of the data.

I would rate its ease of use as an eight out of ten. It has made it a lot easier for us to failover. Usually, in the past, we had to manually go and bring things up and this automates it.

The solution decreases the time it takes and the people we need when we need to fail back or move workloads. It saves around eight hours and one person. We had started off with two to three people.

It could save us time in a data recovery situation due to ransomware or other causes but we haven't used it for that.

We haven't had something where we had to recover data using this product, but I assume it would reduce the number of staff involved in data recovery situations.

It has helped to reduce downtime in testing but we haven't had a serious issue where we had to switch over and use it.

The documentation needs improvement in terms of the setup, getting enough detail, and getting that up to speed.

I have been using Zerto for about a year. 

We found Zerto to be pretty stable.

We haven't had problems with scalability.

We don't really have users. We just have data that we move over which is basically the size of the campus.

We need at least one full-time employee to run it.

It's used for all of our failovers so it's in 100% usage.

I have had a little bit of experience with their technical support. I don't have any issues with them.

The ease of use, compared to other products, is much better. Zerto is all-encompassing. 

We had to work on it for about a week to get it running the way we wanted. It took so long because of the fine-tuning. We could have set it up within three hours or something just as a test to see at work, but not necessarily do everything we wanted to do.

The time it took to sync the data up took a little bit longer.

We'll probably see ROI in around three years. 

The pricing is more expensive, but the functionality is what we wanted.

There are no additional costs to standard licensing.

We also looked at Druva. We liked the flexibility that we get with Zerto. 

You'll be happy with Zerto.

The biggest lesson I have learned from Zerto is to be patient. 

I would rate Zerto a nine out of ten. 

We primarily use Zerto for replication and disaster recovery.

Zerto is good in terms of providing continuous data protection. We have databases that require point in time recovery capability and Zerto is very flexible in this regard, compared with some other solutions we use, such as Sybase Replication and Oracle Replication.

We do not yet use Zerto's long-term retention feature but we are planning to do so. Currently, we are exploring AWS Glacier for long-term retention, and we will see how Zerto can help with the process.

Using Zerto has helped to simplify our process. The DBS steps are very deeply involved in the case of Sybase replication. This means that it takes a lot of technical skill, time, and effort to manage Sybase replication. Compared with that, Zerto is very user-friendly.

When we need to failback or move workloads, Zerto decreases both the number of highly skilled people involved and the time it takes to complete. For example, to do a command-line restore and recovery of Sybase involves pages of steps and it requires a talented DBA. However, with Zerto, we can take care of that with an intern. Only one person is involved in the process for either case, but with Zerto, fewer skills and experience in recovery are needed.

Fortunately, we have not yet been the victim of a ransomware attack. However, I am confident that Zerto can help, should that situation occur. Similarly, since implementing Zerto, we have not had any downtime. That said, we have simulated different scenarios and our results were good.

The most valuable feature is the point in time recovery. This allows us to recover at any point in time, up to a minute or so.

Zerto is pretty user-friendly. Normally, data recovery involves a lot of DBS skills but with Zerto, it is point-and-click.

It is very important to us that Zerto provides both backup and disaster recovery in a single platform. Because of problems that people are facing, we needed to have recovery time objectives (RTO) and recovery point objectives (RPO) for the major cloud providers. This is the primary reason that we were looking for an up-to-date and current solution.

I am a little bit worried about how Zerto will work with large volumes of data, such as replication for big data and very large files. I have not tested it yet, so I can't say for sure whether it will choke or not.

The two large clouds that we use are AWS and Azure, and compatibility with these is always important for us.

We have been using Zerto for approximately five years. We are using one version back from the current one.

In terms of stability, so far it looks okay but I am not sure how Zerto will react to volume loads. We haven't had a chance to test that because we don't have such a large environment.

Scalability has been good but I have yet to see how large a file it can handle.

We have two DBAs using the product, and then we have some interns to help out.

Currently, it is running in a small network where it is backing up a couple of replicated environments. We may increase our usage in the future, as we are now just beginning to back up everything to AWS.

Zerto's technical support team is pretty knowledgeable.

Prior to Zerto, we were using Sybase replication. When Sybase was acquired by SAP, we began having trouble when we needed technical support. The reason that we started looking for a replacement product is that we used to contact technical support in California when we needed help. However, we now have to call Germany first, only to have them redirect the call to California. SAP is a mess.

I was involved in setting up the proof of concept, and I found that the initial setup was okay.

Once the PoC was complete, we went into small volume testing and then started using it after that. The deployment only took us a couple of hours.

A couple of people from our organization handled the deployment, and we had some Zerto technical reps available to answer questions. The Zerto staff are pretty knowledgeable and they answered the questions well.

Compared to the licensing fees with Oracle and SAP, we see a return on investment.

Price-wise, Zerto is fairly reasonable and I can't complain about it when we compare it against Oracle and SAP licensing.

We have not tried using any features that are outside of the standard licensing fees.

We looked into Oracle GoldenGate but it is pretty expensive and cumbersome. Sybase is better than Oracle in terms of pricing, but Zerto is cheaper.

We have not yet enabled data recovery in the cloud, but we are planning to use it. As of now, we haven't tested it. We always back things up but in terms of restoring and testing, we are behind.

My advice for anybody who is considering this product is that it is pretty user-friendly compared to Oracle and SAP. This is a good solution to start with. Once it has been implemented, I suggest moving to volume testing to see how well it handles large volumes of data.

We have never had a real situation where we were under the gun for the purpose of RTO and RPO recovery times. As such, I can't say for sure how it will behave in a real situation but we are satisfied with our tests.

I would rate this solution an eight out of ten.

We are using Zerto to facilitate cloud adoption in the organization. Our product teams are migrating their VMware workloads to the cloud, and Zerto is helping with that task.

Zerto provides us with continuous data protection and it is working well for us so far. It has matched our requirements, especially in terms of compliance and security considerations. The solutions in our environment are working together to make everything achievable in terms of different certifications.

We have only been using Zerto for less than a year, and have not had much time to consider long-term data retention. However, it is our intention to use this capability in the future.

Using this product has enabled our leaders to guide the business through our transition to the cloud. It has allowed us to implement a cloud-based disaster recovery solution.

Having a cloud-based disaster recovery solution, rather than a physical one, saves us in terms of resources. I don't have exact numbers in terms of money, but I can say that in the short time that we have been using Zerto, it has saved us between 10% and 20% resource-wise, including time.

We do not have any real use cases so far, but our model shows that we will need fewer people involved when we failback or move workloads. I expect that we will require 10% to 20% fewer resources in these situations.

So far, we have not had a use case where we had less downtime because of Zerto.

The most valuable feature for us is accelerating cloud adoption, as it helps provide greater speed for disaster recovery. Ultimately, this saves us time, as well as resources.

This product is easy to use. Initially, we had some issues and hiccups but we worked with the solution engineers and were able to rectify the problems and move forward.

When we initially set up the product, we didn't know about the exact features. Some of them were discussed in different wording. It took some time to get to know the solution in general, and exactly what functions each of the features is used for. They seemed more like hidden features to us.

I have been using Zerto for close to one year.

The availability of Zerto has been good for us, so far. We have not experienced any issues with it.

Being a cloud-based solution, it can be scaled as per our requirements. I don't see any issues with it. We have three people who work with it, although not on a daily basis. They are technical analysts and product engineers.

They were more hands-on during the PoC and deploying it, and they will be involved if we have any issues.

Technical support from Zerto is good and they help us all the time.

The turnaround time is good, as well as the help that they give us in understanding and resolving problems.

We are still using our previous solution for backups. We are switching away from it because we will be able to take advantage of automation and use fewer resources.

In terms of cost, using Zerto saves us approximately 15% over our previous solution.

The initial setup is straightforward. It was easy to set up the PoC and the results were good. Setting it up took a few hours and when it came time to move to production, it was in terms of days.

My team was responsible for deployment.

We have seen a return on our investment in terms of time and resources.

We evaluated several other solutions prior to selecting Zerto.

We chose Zero because it is more user-friendly, and better overall.

My advice for anybody who is considering Zerto is that it's user-friendly, easy to use, and easy to deploy. So far, Zerto has been working fine for us and my team has not had any complaints.

I would rate this solution an eight out of ten.

I am a cloud provider and I use Zerto to provide disaster recovery solutions for my clients.

Recently, we had an issue where one of our customers using Oracle Server experienced corruption in a database. The customer doesn't know when the issue started, so we used Zerto. We started to do a real-live failover for the machine, and we were able to determine the timestamp for the start of the issue. Prior to this, Oracle engineers tried for four hours to fix the database but did not have any luck in doing so. Ultimately, we were able to save the customer's data by using Zerto.

A few of my customers are using file-level restore but the majority of them are using the replication features for disaster recovery.

Zerto offers features for long-term data retention; however, we don't use them. The longest time that we back up data for is 30 days. At this time, I don't have any request for this from my customs, although in the future, if we have a customer that asks for it then we can provide it.

Zerto provides our customers with the ability to continue work, even if something happens to their office or data center.

We have a customer with an on-premises data center that replicates the environment to our cloud. One day, this customer had a water pipe burst in his data center. The entire data center was flooded and everything stopped working. We did a live failover and from that point, he could continue working but it was running from the data center in our cloud, instead. Zerto definitely saved us time in this data recovery situation.

It took the customer between four and five days to return everything back to normal onsite. During that time, he spoke with us at 9:00 AM on the first day, and after an hour, his company resumed work with our help. This reduced his downtime to one hour from approximately five days.

Performing a failback using Zerto is pretty much the same in terms of how long it takes, and how many people we require. The customer decides when to do the fallback; for example, it can be done during the night. We replicate the data at their chosen time and it avoids issues for them because they don't operate during those hours.

In a situation like a burst water pipe or a database becoming corrupt, Zerto doesn't help to reduce the number of staff involved. The reason is that when something affects the company, management, including the CEO, has to be involved. They do not deal specifically with operating Zerto but rather, they wait for things to develop. The good part is that they know that with Zerto, they have a solution, and they don't need to figure out what to do.

In terms of the number of people it takes to recover data in cases like this, there is typically one person from our company involved, and one person from our customer's company.

My customers save money using Zerto and our facilities, rather than a physical data center because they do not have to do any maintenance on the backup equipment. It is also much easier to pay one company that will do everything for them.

Using Zerto makes it easier for my clients, giving them time to work on other things. The main reason is that they don't have to maintain or upgrade their environment. Not having to implement new recovery solutions as their needs change, saves them time.

The most valuable feature is the ability to do disaster recovery.

Zerto is very user-friendly and engineer-friendly, as well. When we need to create a new Virtual Protection Group (VPG) for replication, then it is done with just a few clicks of the mouse. We can see all of the environments and we don't need to install agents on the customer's VMs.

The live failover feature is very helpful.

With regards to providing continuous data protection, it's great. Most of the time, it's about five seconds for replication.

The monitoring and alerting functionality need to be improved. Ideally, the monitoring would include the option for more filters. For example, it would be helpful if we could filter by company name, as well as other attributes.

I have been using Zerto for almost three years.

Zerto is a pretty stable product. We have had issues from time to time over two years, but usually, it is stable. When we have trouble then we contact their excellent technical staff.

I have quite a lot of customers that are using Zerto for disaster recovery and it is simple to scale. Our intention is to increase our usage by bringing on more customers that will replicate from their on-premises environment to the cloud.

In my company, there are five or six people who work doing the backup and recovery operations. On the client's side, they normally have one or two people that are in charge of maintaining the data center.

The size of your environment will depend on how many VMs you need to replicate. For example, if you are replicating 100 VMS then you can use a small environment. However, if you are replicating 1,000 or more VMS then you will need a stronger and larger environment, with more storage and more memory.

The technical staff is excellent and we contact them whenever we need something.

We had a customer that replicated his VM and for some reason, when we tried to do a failover test, the VM came back with an error saying that the network card was disconnected. We spoke with the Zerto technical staff and they actually implemented an ad-hoc fix for our environment. In the next Zerto version update, they released it for all their customers.

The technical support is definitely responsive and they explain everything.

I began using Zerto version 6.5 and am now using version 8. We did not use a different solution for disaster recovery beforehand.

We use Veeam for backup tasks. We looked at Veeam CDP to compare with Zerto, and Zerto is definitely better. It is more user-friendly, agentless, and the technical support is better.

The initial setup is straightforward and pretty easy to complete. It takes about an hour to deploy. During the process, you set up the Zerto server to see the whole environment. You then install VRAs on all of the hosts. In general, the management server is pretty user-friendly.

The implementation strategy changes depending on the customer. We did have a few customers that required a more extensive setup because one had an IPsec connection, and a few of them were using point-to-point connections. That's the only strategy. But with Zerto, they need to decide which VMs they want to replicate, and then we create it based on that. First, we will want to replicate the DC, the domain controllers, and then we will want the infrastructure servers, and then the database servers, and the last one is the application.

During setup, one person from our company normally works with one person from our customer's side. Only a single person is required for maintenance.

My impression is that Zerto is more expensive than other solutions, although I don't have exact numbers.

We evaluated CloudEndure and we also had Double-Take, but neither of these solutions worked well. These solutions were based on agents, which affected the customers' server performance.

In terms of usage, Zerto is a different level of experience when compared to other products. It is easier to set up and use.

With other solutions, we need to install software on the customer's server and then reboot, whereas, with Zerto, we don't need to do these things. In fact, there is no downtime on the customer's side. Depending on the customer's environment, post-installation downtime may have been as little as one minute, or more than an hour.

In situations where downtime is expected, and there is an important application like a database running, these periods need to be scheduled. Normally, downtime will be scheduled at night, after business hours. Although there may not be a disruption in work, it is an extra effort that needs to be put into the other products.

Looking ahead, I have seen that the next version of Zerto will support Salesforce replication. This could be something that is useful for my customers.

The biggest lesson that I have learned from user Zerto is that every organization should have a disaster recovery plan. My advice for anybody who is considering this product is to calculate how much it will cost in the event of downtime or a disaster, and then compare it to the cost of Zerto. Once this is done, people will opt for a disaster recovery solution.

I would rate this solution a ten out of ten.