Zerto Reviews

We use Zerto for DR purposes, we replicate what's critical to continue business. We replicate it from our headquarters to another state, a DR site. If something happens to the headquarters where we are located we could run the continued business from the DR site with Zerto.

It improved the way we function because we know that in the event of a disaster, we can easily recover our state of being in a rather quick amount of time. If there's malware, for example, we can go back to a point in time, up to five seconds before the malware started, and start production from that point on, undoing all the damage that the malware did. The ability to do that is a very good feature. It has replication and DR, but at the same time, if something happens with malware and it compromised your backups and compromised your offsite remote copies, you have that third option of saying, "We'll go to Zerto and see if we can reverse back from that point." That's pretty comforting.

If we need to fail back on work we would absolutely use Zerto for that. We'd probably do that first before we tried the backups. It's easier to do that than to try to look for the backups. 

Zerto decreases the amount of time spent trying to get everything back online. That's the most important part. If something happened, I could just go back. It would take me around 15 minutes to locate something and launch it fairly quickly. If you're doing it from a backup, you're probably going to look for a good backup, launch it, then it's got to set up. So you're looking at an hour, maybe, if you're lucky. It's a big difference.

We once had a server and there was some software and one of the controllers in the software wouldn't boot up and we did not have a copy. It was a brand new server, so we didn't have a backup copy of it just yet. We used Zerto to go back. It was in Zerto, but it wasn't on backups yet. We were replicating it just in case and we used that to restore the server back. I called support who walked me through it fairly quickly. The whole thing took around 15 to 20 minutes. It was easy. If we had used a different solution, it would have taken us an hour or maybe two. We would have needed to find the backup and then mount it. We would then launch code or a bunch of series of Wizards. Zerto is always running so if we need to get something, we just highlight, and then we go to more, and whatever we want to do, it's right there. We don't have to turn it on. We don't have to get it going. It's always running. Backups are in a stopped state, so we would have to get it going first, then look for something, then mount it, and then do whatever we're going to do. There are four steps there, versus with Zerto where it's, "Oh, it's in this VPG," go to more, it gives you all the actions you could do, clone, delete, copy and you just do it.

Zerto has reduced the number of staff involved in data recovery because it's only two people who manage the Zerto platform. It's mostly me. I do about 80% to 90% and then 10% is my supervisor. He's more into the meetings anyway. We require two people.

The replication is the most valuable feature. It's almost like a tape recorder. You can rewind if you need to, if something bad happens. You can rewind the tape and your production begins where your tape left off. Where you want it can be replayed for such a purpose.

Zerto is very good at providing continuous data protection. For replication purposes, it's definitely better than Veeam. Veeam doesn't do as good a job as Zerto does when it comes to replication. The other alternative would be to just have backups somewhere. But even with backups, you lose a lot of time because you have to set it all up. With Zerto, you failover, you just click a couple of buttons and you run from the other location.

It's very easy to use. Every morning I go into the dashboard and I can tell the health of the VPG groups. If there's a problem or anything, I'll see it in the active alerts. So the dashboard is pretty simple. There's a status that tells you if the RPOs are falling behind, or from what you set it to, there's a reminder that tells you when to do the failover test. I like that. If I'm going to add a server to a VPG, I just go to the VPG section of the menu, find our group, select it, and then edit it, go to VMs, and there it is. It gives it to me side by side. It tells me what is unprotected on the left, and then this is protected on the right. I can move from unprotected state to protected state or I can remove something that's in a protected state to an unprotected state. It always tells me at the dashboard from the bottom, how many licenses I have, and how many I'm using. I don't go over my license count where I might not be protected. It's pretty easy.

We've never had a situation where we had to go to Zerto for downtime. It's just protection, but we haven't had the situation where we've had to failover. Hopefully, we never do. It's like car insurance. You want car insurance, but you don't want to get into an accident.

The improvement that I would like to see is a little bit easier product knowledge, things like that. It's getting a lot better than it was before because it's not as old of a product as Cisco, but if you look for something like Cisco routing and networking, you'll find millions of articles out there and it's everywhere. It's prolific. So with Zerto, you have to find it within the Zerto application. Hopefully, as they grow, it'll be more out there on the net. Same thing with Microsoft. If you look for a problem with Microsoft, you're going to find millions of articles on it, maybe it's just because they've just been around for so long. I'm hoping that one day Zerto is just as prolific and can be found everywhere.

I have been using Zerto for two years. 

Zerto is very stable. There are very few errors. I just don't see any errors. The only one time we had an issue with it was with journals. We were filling up too much and we called support and they walked us through it. We found out that we were replicating a temporary drive and it's not good practice to back up temporary drives because they constantly change when it's not even necessary. So we removed the temporary drives and we never had that problem again.

I'm a system administrator.

If you were doing recovery from a backup, you'd probably want at least two people looking through backups quickly to speed up locating them. You might need somebody to set up a mount server to mount the backups on. You can get away with three people but you might need three depending on how urgently you want to get going. It depends.

For DR management, if I was with another solution I would require more people. If you have a Dell EMC, they have storage administrators that that's all they do. And so that's a dedicated position. I'm a system administrator, which means that I do the storage, I deal with the servers. It allows me to do a lot of things, not just one thing.

Scalability is excellent. We have one here, we have the one there. I know we could add another ZVM, another location, or another DR site if we wanted to. That's been in the talks for a long time. It's on pause now because of COVID-19. But if at some point we decide that we want to add a secondary DR site that is geographically opposed to where we are now, then we could replicate one, two, and three at the same time. It's got good potential to be increased.

We have about 20 to 50 servers in Maryland and we replicate all the critical, essential ones that would be required to continue to run business to North Carolina. Everything is virtual, which helps us out. We have one Zerto virtual manager here, we have a Zerto virtual manager in North Carolina, and we do failover every six months just to make sure that it works. As a matter of fact, we have a failover test coming up that we have a test of failover to make sure that it's continuing to work.

The support is very good. I've used them before. When we had the journal issues, it was easy to resolve the issue.  We've done upgrades on the versions and they've always been very responsive. If I do a P1, which is critical or they do a P4, which is just information, they respond fairly quickly. 

We've used Veeam for backup. Before Veeam, we used Unitrends, which is even worse. It didn't work. 

Zerto's good for DR replication. I don't think anybody does it better. Veeam is good for short-term backups. It doesn't do well with the replication part at all - even they say it. I've spoken to reps who agree and say that Zerto's better at it than they are.

The initial setup was pretty straightforward. You set up a ZVM here and there and tell it the direction you want it to replicate in to. You can create an EPG to the journal that goes attached.

Because we were setting it up in the middle of things, it took around one month. 

We did have a strategy of how to put those servers here, build servers there, and IP addresses we were going to assign to it. We did have some sense of where we were going to put things.

We used the reseller who helped us with the deployment. They were great. It was easy. No problems with it.

We bought it through CTI.

I think we do see ROI. We need a defensive posture to protect ourselves.

Pricing is okay. You don't use Zerto to put all of your servers in Zerto. The purpose of it is you take what is absolutely critical to continue running your business, whatever servers are in your business continuity plan. Those are the ones that you put in Zerto. Then you'll be fine in the licensing because if you just buy 200 licenses or 300 licenses and you're backing up a utility server or any server that's not essential, then your bosses are going to think you're spending too much money. But if you just zero in on what's critical and back that up with licensing, you'll be fine.

There are no additional costs that I'm aware of. We have the licensing fees that come up and then that's it, as far as I know.

We had a couple of proposals. We had the one from Veeam but we realized really quickly that it doesn't work for replication. The other alternative would have been to save the backups to the offsite location, have servers there, and load backups at the server location. That takes a lot of manual labor so we decided Zerto would the best option.

We don't know what we're going to do for long-term retention. We use it for DR purposes only. But we are still looking at the long-term retention and what to do with it.

I would say if you're looking for true DR protection with minimal recovery time, then Zerto is probably going to be the one. If the objective is minimum time to recover, then this is the product you need to buy. If you want to spend time trying to set up again in a disaster, then there are a lot of things out there and for ransomware too. We have about a five-minute window where once data is compromised beyond five minutes, it's useless. So we need to keep the window to about five minutes. Because of that, Zerto is really going to have to do that at this point in a cost-effective way to recover. 

I like Zerto. You learn different things as you use it more and more, so you become more competent with it as you use it. I know that if you do have an issue, as with most other vendors, the easiest solution is to provide the logs as soon as you can, and then they're better prepared to respond if you do it that way.

I would rate Zerto a nine out of ten. Nothing is perfect. 

We have servers in Houston and we have servers at a DR site, we need to be able to make sure that they're replicated in some form or fashion. That's what we use Zerto for, to replicate between our primary site and our DR site.

The biggest improvement for us was going from a possible 24-hour lag on our backups to real-time lag. With the hurricanes here in Houston, buildings losing power, and so on, it was nice having the ability to just go flip a switch and we're live with current data as opposed to we're live with what happened yesterday.

Zerto has helped to decrease the number of people involved when we need to failback workloads. It's a much smaller number. It's time-consuming because of the way it works, but it's not overly overbearing. Instead of taking a better part of the day or two to get everything up and running, it really only takes us three or four hours. It has also decreased the number of people we need. It would take three or four of us to bring up servers, make sure they're all running, test them, and all that stuff. Now, it takes one person to bring them all up and then there's a couple of us to test it, so we have half or less of what it used to take. 

We've never had a ransomware issue. The reasons for our failover has typically been natural disaster caused.

Pretty much all of the features are valuable. The biggest thing we use it for is replication, so the ability to set up our virtual server, set it to replicate, and Zerto handling everything else is the biggest feature that we like.

The continuous data protection is great. We love it because we can see exactly how many seconds behind real-time we are, which is usually under 10 seconds. It keeps things up to date. We love the product.

We currently don't use it for long-term retention. It's something we may look at in the future, but that's not the product we're using for that.

Zerto is very easy to use once everything's set up, which isn't difficult. It takes a little bit of time to make sure all the network stuff is all set up properly, but once everything's set up, using it day to day is very simple.

Zerto has saved us money by enabling us to do DR in the cloud rather than in a physical data center. Our DR is to a physical data center. We don't put our data in the cloud.

For what we got it for, it does it great. I use a different solution for my disk-to-disk local backups to where I can have a local backup of files. I don't think Zerto does that well to where it keeps a memory of the files that are there. Basically, when something is deleted on Zerto, it gets deleted on the replicated version. So, some sort of snapshotting or something where I could have backups at different points in time of files would be a really helpful tool.

We have been using Zerto for five years. 

Stability is great. The only downtime we have is during upgrades and patches. I really haven't had any problems with the platform or stability.

The time it takes to update or patch depends on the size of the patch. Major upgrades take a little bit longer, but I mean, it's typically a couple of hours at the most. It's not a huge thing.

Scalability has been great. It continues to grow as we grow. I haven't had any problems with it.

Zerto is being used 100% across our environment. 

We've got about 11 servers doing backups in the 20 to 25 terabyte range most of the time.

Only I work with Zerto in my company. 

The two times that we've contacted technical support, we didn't have any problems. They've been helpful. They made sure we got the issue resolved and did very well with it.

We previously used Veeam. We switched because of real-time backups. Veeam was a point-in-time backup. We said, "You're going to back up at this time." It took a snapshot and backed it up. Zerto just continually backs it up and makes sure that we're currently up to date and matching the server at your primary.

We use Zerto primarily for disaster recovery to the DR site. We still use Veeam for our backup disk-to-disk local for file backups.

Once Zerto is set up and running it is much more hands-off. You don't really have to do anything. You just log in to check, make sure everything's going well, and you're pretty much done. With Veeam, I feel like I have to check in a little bit more often, make sure the backups are running properly, making sure all the files are there, and everything like that. There is a little bit more checking to do on a regular basis.

I don't know if we would have failed over with Veeam because of the amount of time it took and coming back online at the primary site. I don't know that we would have failed over, which would have been probably five or six days of downtime. If we had failed over, we'd probably have lost two or three days in one direction, and probably another two or three days coming back to the primary.

The initial setup was pretty straightforward. It took a little while to make sure we had everything connected right, and that it was going to the right place, but it's no more difficult than any other setup for something like this. I didn't find it difficult at all.

If you don't include seeding and you only include the setup and deployment, it only took us a day or two of planning and then another day of actually implementing it. The seeding took a while, but that's to be expected.

In terms of our implementation strategy, we were using a different product back then, which wasn't as up to date and live. We were just backing up at night, so we had a nightly snapshot that was being transferred to our DR site. Our strategy with Zerto was to get us to more of a real-time backup solution at the DR site and make sure everything was good. That was the entire purpose of going with Zerto.

We used a third-party integrator for the deployment. We used Centre Technologies and they were great. We've used them for other stuff and we didn't have any problems with it and never have.

The one time we had the failover and run at the DR site, instead of having two or three days of downtime, we really had less than one day of downtime. If you measure that in how much money we were able to make that day, it's around $200,000 to $300,000.

We are on the lowest license because we don't exceed the number of servers for the base license, so I don't have a lot of information about licensing. The price of it was comparable, if not better than what we were paying for Veeam. I have no problem with the pricing at all.

There are no additional costs to the standard licensing. 

Make sure you know how long it's going to take to do your initial seeding. If you've got a lot of data, and you're doing it over a pretty good distance, just make sure your pipe is big enough for the initial seeding. Once the seeding's done, pipe size doesn't matter, but the initial seeding can take a good amount of time over a small-ish pipe if you're replicating a lot of data.

For our largest servers to seed can take a full week or to 10 days for one server, for our large file server to seed is about seven terabytes, but we don't have a huge pipe at our DR site. We negotiated to increase the pipe size temporarily while we were doing the seeding, and that reduced the time drastically on how long it took to seed. I can't really give a number or what to look for. I would just have that conversation with Zerto about how long a certain pipe is going to take. How long is it going to take to seed using whatever pipe size based on the amount of data that they have.

Make sure all of your notifications are set up well when it fails. It takes a little tweaking and making sure that everything is set up right, but when you want to make sure you're notified if you get outside your SLA on how long the backups are trailing, making sure all that's set up properly is key.

I would rate Zerto a nine out of ten. 

We've used it for disaster recovery. We also use it for file recovery. We extended our journal to more days, so we were able to back up a more detailed timeline. We recently did migrations. 

One of the biggest benefits is the migration. We had to move out of a data center very quickly. We were able to failover to our disaster recovery site and run our full production there for almost two months. We then fail back over to the production site using Zerto. 

The ease of use and the ability to quickly recover our workloads is very simple and easy.

The near-synchronous replication is great. It allows us to failover and run production.

Zerto helps protect VMs in our environment. Zerto's overall effect on our RPOs has been excellent. 

The speed of recovery with Zerto versus the speed of recovery with other disaster recovery solutions is night and day. We use Veeam for backups and the amount of time that it takes to recover is so much quicker mounting with Zerto. That's why we extended the journal so that we could capture a few more days and make it easier for us to recover files.

The amount of storage that it takes up for the journals could use improvement. Outside of that, it's been great.

I have been using Zerto for five years. 

They're very stable. We had been with them for a while before HPE acquired them, and they're still going strong now. We haven't seen a lot of big changes in the way they operate, so that's always a good sign.

Support is great. Every time we have an issue, which isn't very often, they're very responsive. We get in touch with somebody very quickly and they help us through it.

Positive

We use Veeam and we've used Datto. We chose Zerto for its ease of use. It was simple, and then we found out once we got it in-house how valuable it was. We just extended it from there.

We used Veeam, and we switched because Zerto was a lot easier. From implementation to actually protecting our VMs, it was so much easier.

Zerto is on top. Zerto is the best out there. 

The initial setup was easy. 

We worked with Zerto on the deployment. 

We have definitely seen ROI.

We had to move out of a data center very quickly. The data center we were in filed for bankruptcy, and we had two months to move out. The ability to flip over to our recovery site in one day, and then being able to ride that until the next time we came back up, then move all of our data back to the new data center was huge for us. That would have cost us a lot.

The initial pricing seemed a little high, but once we got into it and found out what it could do and how it benefited us, it proved itself. We didn't feel that it was too far out of the ordinary. We've increased our licensing to cover our entire environment whereas before we're only covering critical servers. 

I would rate Zerto a ten out of ten. When we started using it, it was very easy to use. It was easy to implement. Throughout the years, it's continued to be that same way. They've proven themselves. We've had the data center move, we've had failures, we've had different issues that happened in our environment, and they were able to meet all of our needs. 

I have a main data center with a few virtual machines running. I am protecting my mission-critical VMs on a disaster recovery server that I have outside of the data center. This ensures that I have protection. If something happens with my main data center at any moment, I have a copy, and that copy is at a remote and physically separated site for disaster recovery.

By implementing Zerto, I wanted to lower the RTO and RPO. Previously, the time to restore those mission-critical VMs with the traditional backup application took too long which impacted my business. That is why I decided to evaluate and then keep Zerto to protect my mission-critical VMs. It helps to lower the time to recover when something happens with one of my data centers.

Zerto is very easy to use. I did not have to attend a multi-day training. Online training is available from Zerto. It is very easy to use in my opinion as compared to other solutions.

Near-synchronous replication was the reason why I evaluated Zerto. I then decided to use Zerto because it works effectively. It is different from the other solutions in the market. Because I did not know that technology, I evaluated it, and I found out that it effectively works. That is why I decided to use it. I am a fan of Zerto.

We have a faster recovery time. I am lucky that until now, I did not have to use it in production effectively. That means that I did not lose access to my first data center, but it gave me peace of mind. I know that if something happens, at that moment, I know what to do to recover and to fail over to that second data center. There is peace of mind for sure.

We use Zerto to protect virtual machines from VMware to VMware. Our RPOs went from hours to seconds. That is a huge improvement.

Before using Zerto, I had an issue, and we had almost a day of downtime. I had to put a lot of energy and time at that moment, not being able to do my regular job. Since moving to Zerto, I never had a big downtime, but when I evaluated Zerto and ran the tests, failovers always worked. I have not had to use it in production so far because everything has stayed online until now. I am keeping my fingers crossed.

Zerto has definitely helped to reduce our organization's DR testing. Previously, the procedure to do the testing took several hours, and now, it is all automated. The nice thing is that the testing is automated. It is a part of the solution itself, and it is very easy to perform.

Zerto has enhanced our IT resiliency a lot.

I do not have many regulations to follow because I am not in finance or health care, but it simplifies my work because it clearly shows me what I have, what is supported, and what is protected. Zerto definitely enhances my visibility.

There are two main things that I like. One is the fact that my recovery time is now much lower effectively. It is also very valuable that I can test it. There is a possibility to test that failover. At a regular moment in time, I can run that test and see if it effectively works when I have a major issue in the future.

I am switching to another HPE offering called HPE GreenLake for Disaster Recovery which is using Zerto technology in the backend but has a lower entry point. The native Zerto implementation is optimal for larger environments. My environment is rather small since I do not have hundreds of virtual machines. The initial Zerto offering was for a larger environment with more than 100 VMs. At that moment, it was not that easy to talk to HPE to get a good price. HPE GreenLake for Disaster Recovery uses the same technology, so it is a really good technology, but the entry point is much more interesting for me. They have lowered the number of protected VMs. That is why I am now evaluating HPE GreenLake for Disaster Recovery.

I have been using Zerto for two years.

It is always available. So far, I never had any issues. It is very good. I would rate it a nine out of ten for stability.

It is definitely scalable, at least in my environment. I do not have the biggest environment, but based on what I saw when HPE initially presented the solution and all the new things that I see in it now, it is a very scalable solution. Why I prefer this solution compared to Veeam, for instance, is its scalability. I am convinced that the way it works with journaling makes it much more scalable than other solutions.

So far, I never had to call support because I never had issues with the platform at all. Until now, everything worked fine, and I never had to contact support. This is through HPE, and I expect the HPE support to work like before and provide the same experience for Zerto.

Positive

I am still using Veeam, but with Veeam, I was never able to go up to a few seconds of RPO. Zerto is much more scalable and flexible as compared to the Veeam solution, so I am using Zerto for the short-term retention and protection of my data, and I am still using Veeam for the mid- and long-term retention of my data.

It is for on-prem to on-prem DR. I am not using the public cloud for DR.

It took less than a day to set it up. It was very easy to deploy. In less than a day, everything was set up in two data centers.

In terms of maintenance, it is self-maintaining, so I do not have to put a lot of time into it. It is part of my testing. Every two or three months, I do a failover test, and at that time, I also check if everything is working fine and if any new updates need to be applied. When there are new updates, which do not happen that often, it is very easy to deploy the updates.

Only one person was involved in its deployment. It was just me. To set up and maintain it, there is just me. I do not need several people because it integrates with my compute and my storage. I can see my hypervisor. Technically, there is one storage person who is responsible for all this.

We are a small company. Zerto is being used by one team, but there are two physical buildings. Here on-site, we have our main data center, which is highly available with multiple servers, and on our DR site, there is just one server. It is one big server where we have copies of the mission-critical VMs that we are protecting.

It is hard to measure because I have not had a real disaster since I have been using Zerto. If I consider the time while testing the procedure, it went down from hours and days to less than an hour. I see large gains, but it is hard to say in the percentage. It is effectively much better.

I think the price is fair for what it is offering. It gives me the peace of mind that my data is protected. It is worth the cost.
It is like insurance for a car. You do not get the value until you have an accident.

I am now evaluating HPE GreenLake for Disaster Recovery, which is using Zerto in the backend.

I would definitely recommend Zerto. I have really low RPOs of seconds since I started using Zerto, and it works effectively. That is why I love Zerto. It does what it should be doing.

I like the tool because you can go from anywhere to anywhere. I am currently using it for on-prem to on-prem DR, but it can go from anywhere to anywhere. It shows the flexibility and the scalability of the tool. It is a no-brainer to evaluate Zerto because you can also go perfectly to the public cloud from your on-premises so that the public cloud is your DR site. I did not use it myself, but you can even use it as a migration tool for migration from an old environment to a new environment. It is a very flexible tool. That is why I was impressed with it and how HPE integrated Zerto into its portfolio. It was a smart move to do the acquisition of Zerto.

I recently started looking into the AI insights that was added in the latest version. Need to evaluate further but it looks very promising from what I can see now already.

I would rate Zerto a nine out of ten.

I use Zerto to store and protect my files. Whether I'm working on a project or just need to access old files, Zerto ensures everything is safe. This makes it very convenient, as I can easily access any information I need with just a single click.

Zerto is effective at blocking unknown threats and attacks. We might consider using it on the business website as well, but it's important to understand how it might impact our operations. It helps with blocking threats, which is certainly valuable. So, in terms of its effectiveness, I'd say it's close to 99% guaranteed.

Zerto has helped our organization block threats, is user-friendly, is effective in storage, and inspires users.

Zerto's Cloud disaster recovery is impressive, and recovering most of our data can be relatively straightforward. However, it requires careful planning and understanding. Navigating the recovery site is crucial, so ensure we read and comprehend the instructions thoroughly before clicking anything. This way, we'll know which box to choose and where to click to achieve our desired outcome.

It is easy to migrate data using Zerto.

It helps reduce downtime.

It has helped reduce our disaster recovery time. Before Zerto, we needed ten people for disaster recovery and now with Zerto, we are down to three. 

Zerto is truly inspiring. Sometimes, when I provide information and receive it back, it can be remarkably refreshing and motivate me to get the most out of it. There might be instances where I initially think something isn't applicable, but then I try it out and say "wow" as I realize I am getting something positive from it. it becomes quite inspiring and brings out my best creative potential. Witnessing these features makes me naturally want to explore and create more.

The performance was generally good, but occasional lag disrupted the flow, leaving room for improvement.

I have been using Zerto for four months.

While Zerto is stable, it can sometimes be slow to retrieve the data we need.

Zerto is scalable.

We used to complete tasks manually, which consumed a lot of manpower, before adopting Zerto.

Zerto is affordable.

I would rate Zerto a nine out of ten.

No matter what we choose to do, there will always be potential positives and negatives. When aiming for the best outcome, focus on visualizing success and avoid dwelling on negativity. However, even while striving for the positive, acknowledge that occasional setbacks like technology issues or unexpected problems might occur. Don't get discouraged in the present; trust that Zerto will ultimately lead to something beneficial and fulfilling.

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

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

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

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

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

We can use Zerto to help protect our VMs.

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

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

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

Our downtime is minimal.

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

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

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

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

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

We're not fully satisfied with the support team.

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

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

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

The solution is stable, from what I have seen.

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

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

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

Positive

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

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

We have Zerto on an HP machine. 

I was not involved in the deployment of the solution. 

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

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

The solution is a bit expensive. 

We did not evaluate other options. 

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

Our primary use case is for disaster recovery. We replicate up to Azure, and that's essentially disaster recovery as a service.

Overall, the effects of RPO have been great. They are never more than a minute or two, even throughout the production day.

If we can replicate from our native VMware environment up to native Azure, it converts the machines for us. We don't have to maintain another VMware environment somewhere. It's really given us the ability to eliminate the entire data center.

Moreover, there are cost savings tied to this. We don't pay for the rack space, power, or hardware; all of that is gone. Because the machines aren't active, all we're paying for is storage in Azure. So it has saved us quite a bit of money.

Zerto's near-synchronous certification has positively impacted our operations. Any recovery point that's too far in the past, we'll lose transactions when we fail over. We really don't want to do that. Real-time replication gives us a much better sense of security for the enterprise. It simplifies things for us and reduces costs.  It makes management feel really good, too.

Using DR in a cloud environment has been a positive experience. We're saving money. We don't have to maintain the hardware. We don't have the rack space at the other data center. It just simplifies things for us and reduces costs. It's been a positive experience overall. It's pretty easy to use. Once it's up and running, it stays running. We have had a few times when we called support and the support has been very, very good.

Maybe the reporting for the failover test could be a little better.

I have been using Zerto since 2020, so it's been three years.

It's very good. It's very stable. It doesn't require a lot of intervention. 

We haven't had any problems with scalability. We have 75 machines protected by Zerto and it does a fine job.  

Support has been very good.

Positive

We used to use Site Recovery Manager when we had two data centers, and it was VMware to VMware. We were using EMC storage. Zerto is a lot easier to use than Site Recovery Manager. It requires less care and feeding. 

Site Recovery Manager occasionally would lose virtual machines, and it was kind of a pain, but Zerto just kept running. So overall, we're really happy with the switch to Zerto.

The initial setup was easy.

Since we don't have to maintain all of the hardware and the second data center, one person can manage the entire Azure environment by themselves. As a result,  Zerto has helped us reduce staff. 

We did an assisted setup with Zerto tech on the line, and It was really painless. It was simple and straightforward. The initial process including getting the servers and everything set up, was pretty short. The process included getting the VMs all added to the recovery groups and things like that. 

The whole process from start to finish took less than a week.

It has proven to be a cost-effective solution for us. 

It could always be less money. 

Overall, I would rate the solution a ten out of ten. It requires little care and feeding. Not a lot goes wrong with it. It just works.

Right now, we use it just for disaster recovery.

We have always had a centralized data center. Therefore, if we were to lose connectivity or power, then access to county resources would be cut off until that issue is resolved. If there is a hurricane, it would be the same thing. If we lose power, then we would be down until something comes up. With Zerto, I can quickly get us up and running at the disaster recovery site, provided it is still operational.

For most use cases, the failover time is a handful of minutes, if that. A single user can run the system.

Zerto will reduce the number of staff involved in a data recovery situation. As of now, we have been lucky. We have not had to deal with this type of issue. However, it will require less people going forward. So, I can dedicate people to other tasks in a situation like this.

Disaster recovery would initially require four or five people to handle just the server side. This has now been cut down to just one person.

It provides great continuous data protection. The RPOs on things are in seconds.

We have been using it for two years.

We haven't had any issues. It literally just runs. Once you have it set up, you just leave it alone.

As long as I have the resources and licensing, I can keep going from a scalability perspective.

The tech support on my latest issue wasn't so great. I had to figure a lot of stuff out myself. It could be that I had a Level 1 tech who was new or something, but it seemed like the tech was spitballing, which does not help me.

In previous instances, the technical support was great. They were able to get me up and running fairly quickly.

We didn't have a solution like this before that allowed for disaster recovery. Everything was restored from backup, then we had to wait. So, if something went south, then we would need to restore from a backup. I saw the Zerto product was literally one button click, then I can failover to a disaster recovery site and keep going. That was amazing during the initial review of the product. It was just easy.

We started looking at how long it would take to restore from a backup. Rebuilding that infrastructure would take hours, if not days, as opposed to having the ability with Zerto to do a single click, then we are up and running at another site.

It is being used in conjunction with our legacy backup solution.

It was actually fairly easy to set up the solution. Installing it, creating the VPGs, and adding the VMs to it was fairly straightforward.

Working with support on the line, we deployed Zerto in a couple hours.

It is about $1,000 per VM, so it is pricey. However, the cost and time (the manpower cost) that it would take several members of IT to restore a backup and every individual piece of the virtual environment would easily exceed the pricing cost.

If we had to trigger it, downtime would go down to whatever the RPO is at that time. Right now, our RPO average is between four and 10 seconds. This is a big cost saver for us. Anytime certain systems are down within the organization, money is lost.

The only negative part that I have seen so far has been the cost. It is kind of pricey, but you get what you pay for. Zerto is a lot faster than other solutions and you get enhanced performance.

Eventually, we will expand solution use. While there are some competitors in the market, I don't think any of them get to the ease of use and speed that Zerto has. Even Veem has CDP, which is similar, but it is not as fast, user-friendly, or worry-free.

Veeam CDP was still fledgling at the time of our evaluation. It existed, but wasn't that great. It wasn't anywhere near as robust as Zerto. Commvault had something similar as well, but even their solution doesn't do disaster recovery as quickly as Zerto.

It is important that it has both backup and disaster recovery. As I am looking for a backup and recovery solution, I am looking for something that can do everything.

The solution was bought to help with the mitigation of ransomware.

Right now, we are still in a physical data center. We haven't looked at their solution for going to the cloud. That is something which is coming up. Eventually, we will make the switch over. Right now, we are working on a new backup and DR solution. So, that will go hand in hand once we are done with the on-prem.

I would rate Zerto as 10 out of 10 based on the way that the product works.