Try our new research platform with insights from 80,000+ expert users
Ravi Theja Rachamadugu - PeerSpot reviewer
Infrastructure Architect at Krish Services Group, Inc
Real User
Top 20
Application-agnostic, easy to use, and helpful for improving RPO
Pros and Cons
  • "The simplicity of use is valuable. It is easy. We just click Failover and do it. It is pretty straightforward. If someone wants to do a test failover, they log in to the console and do a test failover"
  • "I would like to request better reporting in Zerto. I can see the data that I need in the console, but if I need to put the data or the history into a report, it is difficult. It is something that auditors might require, so reporting is something that needs to be improved."

What is our primary use case?

We are using it for disaster recovery. 

How has it helped my organization?

Zerto provides near-synchronous replication, but more importantly, we can see the status at seven seconds, six seconds, five seconds, and four seconds when we log in to the Zerto console. I found that amazing. There is probably no other disaster recovery solution available in the market that is providing this functionality. It is great and definitely a huge plus point for Zerto.

We do get alerts if suspicious activity is detected on a VPG, but we did not get an actual case where there was ransomware or any other kind of attack and we had to prevent that. I have not come across that with either of my clients, but we do get alerts when Zerto finds something suspicious. We go in and look at it. In some instances, because the application was writing more files, Zerto marked it as suspicious, but we never had to do recovery for security reasons.

We use Zerto with AWS as the target. We do the failover of the on-premises VMware virtual machines to the AWS cloud. I do not deal with the implementation. I only do the administration of the tool, but whatever I did as part of AWS administration in Zerto, it was pretty seamless and straightforward. I did not get any issues there. The documentation is helpful in identifying any issues.

We have about 70 virtual machines that are being protected by using Zerto. Zerto has drastically improved our RPO. It was 15 minutes previously, whereas now, it is in seconds.

Zerto has not had much impact on our RTO. RPO has changed, but RTO has been the same for us.

Zerto has not helped to reduce downtime in any situation. We have only done tests. We have not done any actual production failover because there was no need. Similarly, Zerto has not saved us any recovery time because we never had a requirement to do a recovery since we implemented the tool. It is a pretty new environment for us, so we have not had time.

Zerto has not reduced the number of staff involved in overall backup and DR management. It has remained the same for us.

What is most valuable?

The simplicity of use is valuable. It is easy. We just click Failover and do it. It is pretty straightforward. If someone wants to do a test failover, they log in to the console and do a test failover. 

What needs improvement?

As a power user, I find the customization lacking. I feel it could be customized a little bit more, but Zerto is simple to use. It is easy to use. That is my main reason for using Zerto.

I would like to request better reporting in Zerto. I can see the data that I need in the console, but if I need to put the data or the history into a report, it is difficult. It is something that auditors might require, so reporting is something that needs to be improved.

The UI does crash a lot, and that is something that can be improved.

Buyer's Guide
Zerto
March 2025
Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
844,944 professionals have used our research since 2012.

For how long have I used the solution?

It has been about a year. I support multiple clients with multiple backup and disaster recovery products. I was a Storage and Backup engineer, but now, I am covering the solutions for the entire infrastructure. I work on Zerto for multiple clients. We have two clients who are using Zerto as a disaster recovery solution.

What do I think about the stability of the solution?

The UI does crash, but it does not affect the functionality of the software.

What do I think about the scalability of the solution?

It is scalable. There could be 10 machines or 100 machines. I did not find any issues. It is pretty scalable.

How are customer service and support?

There were some issues for which we had to get responses from them. They were pretty much on the point. There were no issues. The response time was a bit slow, but their support was pretty good. I would rate them an eight out of ten.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We used to use Azure Site Recovery to protect all of the production instances, SAP databases, some file servers, and some basic application servers. We used to first replicate to Azure and then do a test failover and a production failover. It was a bit slow. The RPOs and RTOs were not that great, and the rate of change that Azure Site Recovery supported was not completely meeting the business requirements. The third part was that Azure Site Recovery was not application-agnostic. What we loved about Zerto was that it was application-agnostic. It did not matter to Zerto what was running behind the application. It will replicate everything across any cloud. That was our main point for going for Zerto.

Zerto was also much easier. Azure Site Recovery was a little bit hard to set up and maintain, but Zerto is pretty straightforward and easy.

I did not find much difference between Zerto and other solutions in terms of the speed of recovery. The RPO is great, but when we do a failover, it is basically the same as any other solution.

Zerto has not replaced our legacy backup solutions. Our legacy backup solution is in the same place. We are only using Zerto for DR.

How was the initial setup?

Our environment is hybrid. We are using Zerto to protect our on-prem as well as the cloud environment, but I was not involved in its deployment. 

In terms of maintenance, I never had any requirements to maintain it.

Which other solutions did I evaluate?

Evaluation was done by someone else in the organization.

What other advice do I have?

I would rate Zerto an eight out of ten. Simplicity is an advantage, but customization and reporting can be better.

Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
reviewer2266920 - PeerSpot reviewer
Sr Systems Engineer at a insurance company with 501-1,000 employees
Real User
Top 20
Great interface, easy to use, and simple to update
Pros and Cons
  • "The biggest benefit is the application-consistent disaster recovery functionality."
  • "Zerto could improve its reporting capabilities."

What is our primary use case?

The primary use case is disaster recovery. 

How has it helped my organization?

The biggest benefit is the application-consistent disaster recovery functionality. 

What is most valuable?

The most valuable features include the ease of use and the usability of the user interface. Long-term, the solution has proven to be very resilient and stable. It meets our DR needs for VM environments. 

The near-synchronous replication is a great feature. You have near real-time DR capabilities. In the years I've used it, we've had application-consistent profiles. To meet the recovery point and recovery time objectives, it helps to have that on hand. 

It's affected our RPOs positively. It totally meets them via near-synchronous replication. That means the VM stays in a consistent state and is always available. 

What needs improvement?

Zerto could improve its reporting capabilities. That's lacking. The alerting capabilities are lacking as well, partly due to the fact that there's no way to trim down the alert fatigue if there are failures within the application. It will send out alerts consistently instead of spreading the alert times every 30 minutes, hour, et cetera. 

For how long have I used the solution?

We've been using Zerto at our organization over the past eight years. 

What do I think about the stability of the solution?

The solution is very stable. 

What do I think about the scalability of the solution?

I cannot comment on scalability. We only have two Zerto instances installed, one in production and one in DR. We haven't had to scale out or to the cloud. 

We are protecting upwards of 100 virtual machines. 

How are customer service and support?

Zerto's support is good. They are responsive from an email perspective. I've never had to pick up the phone to call them for anything beyond our DR testing every year. In those cases, we do open a proactive ticket in the case that we run into issues with recovering virtual machines. 

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We did not use any other solution previously. We chose Zerto since it was an application we inherited. It wasn't something I specifically chose, however, understanding the industry, we know that it is the top player in terms of software recoverability for virtual machines. 

How was the initial setup?

I did not initially set up the solution; I inherited it. However, over the past eight years, we have gone through a number of upgrades, which for the most part have gone seamlessly. We did have a few issues in the past that support was able to fix in a timely fashion. 

What was our ROI?

I'm unsure if the company has witnessed any ROI. We have not gone through any TCO analysis. 

What's my experience with pricing, setup cost, and licensing?

The licensing is outside of my purview. 

What other advice do I have?

I'd rate the solution nine out of ten. If the reporting and alerting functionality were better, I'd rate it ten out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Zerto
March 2025
Learn what your peers think about Zerto. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
844,944 professionals have used our research since 2012.
reviewer2264499 - PeerSpot reviewer
Engineer at a financial services firm with 1,001-5,000 employees
Real User
Automatic, replicates in seconds, and has responsive support
Pros and Cons
  • "Its automation and the ability to replicate and keep an RTO of just seconds is valuable. It is all automatic. Everything is pretty transparent on the backend. It is just point-and-go."
  • "From the technical side, there can be a little bit more PowerShell integration. I know it leverages APIs, but people still use PowerShell. Some people would rather use PowerShell if that is an option."

What is our primary use case?

We are using Zerto as a DR solution for our environment as well as for migrations. When we do data center migrations, we use it to move our servers over.

We are only on-prem at the moment. We do not do disaster recovery in the cloud.

How has it helped my organization?

In the old days, during data center swaps, it used to take days to move our workload environments over, whereas now, it literally takes an hour for hundreds of servers to migrate. Literally, in under a minute, an app stack can move down and up in a new data center. It is reflected in the uptime support to our customers. Our company is very happy with the product.

Essentially, you just tell it to go and pull the trigger. It is all automatic, so you can sit there and watch the shutdown within vCenter, and then on the remote side, you can see it coming up. You can literally have your environment up and running in under a minute. You just have to prioritize what goes first, and that is a business decision.

What is most valuable?

Its automation and the ability to replicate and keep an RTO of just seconds is valuable. It is all automatic. Everything is pretty transparent on the backend. It is just point-and-go.

Its near-synchronous replication is amazing. It is a lifesaver. You can see it replicating in real-time in seconds. The overall impact on the network is negligible as well. It is a great tool.

What needs improvement?

From the technical side, there can be a little bit more PowerShell integration. I know it leverages APIs, but people still use PowerShell. Some people would rather use PowerShell if that is an option.

For how long have I used the solution?

I have used it across several employers. I probably used it for a total of four or five years before it was bought out by HPE.

What do I think about the stability of the solution?

It is amazing. You just look at the dashboard, and it is pretty much all green unless you have some replication or journaling issues, but that is not the product's fault. 

What do I think about the scalability of the solution?

Scalability has not been an issue. You deploy it, and it just ramps up and goes. It is all in the background and automatic.

We have about 700 servers and 130 VPGs.

How are customer service and support?

I would rate them a ten out of ten. They are very responsive and technical. Even when there is no issue and you are looking for a root cause or just a question, they are very responsive. They exceed their SLAs.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

My current employer already had it in place. In my previous role, it was evaluated against a few other competitors, and it ended up being a replacement for VMware's Disaster Recovery, which at that time had a lot of issues. Zerto came in and helped us out. We implemented a few new things that Zerto did not have, and I have not looked back.

Zerto is easy to use. I would rate it a ten out of ten in terms of ease of use.

How was the initial setup?

Currently, we are still on version 9. We have deployed that. Overall, it is very easy once you get the Windows Server. I am excited about the new version 10 coming out that takes away the Windows server requirement.

What about the implementation team?

We did not use an integrator or a reseller, but we are in contact with our engineer from Zerto. I personally know him from a previous job and as a friend as well. If I have questions, I am sure he will help me out.

What was our ROI?

Uptime for our customers is important. When we are able to do transitions and not impact customers or minimize that impact, that is a financial gain at the end of the day in terms of the satisfaction that customers get, as well as the overall view of the company. As a whole, the management sees that we are doing this stuff in minutes and hours versus days. So, overall, the company is not looking to move away from Zerto anytime soon.

What's my experience with pricing, setup cost, and licensing?

I know it is per server, but I am not fully aware of the price model. I know for our VDI environment, they are looking at something that is on the lower end and that they can use just for migrations and not so much a disaster recovery.

What other advice do I have?

I would rate Zerto a ten out of ten. It scales well. It just works. It is amazingly simple. Everything is pretty much automatic. I cannot remember when I had to open a case because Zerto was not working.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Analyst at COUNTY OF BUTTE
Real User
Storage software that offers consistent performance in the conversion of Hyper-V to VMware
Pros and Cons
  • "Zerto offered us massive time saving and consistency. We have a consistent outcome every time we complete conversions."
  • "We wanted to shut down the dev environment to focus on the prod environment. We couldn't find any option in Zerto to do that."

What is our primary use case?

We have approximately 1500 to 2000 Hyper-V machines. Those Hyper-V machines are being used and converted to VMware. We use Zerto for our conversion from Hyper-V to VMware. We are also considering using it for DR purposes. 

Our prod environment runs on-premises and we have a DR copy of everything that we run in production. Our development runs on machines and hardware. In the event of a DR event, we would shut down dev and bring up our secondary copy of production. We hope that Zerto is going to be the tool to help us do that.

How has it helped my organization?

Zerto offered us massive time saving and consistency. We have a consistent outcome every time we complete conversions. We move from one platform to another with different loads being moved each time and Zerto's results are consistent each time.

We convert 30 to 50 VMs from Hyper-V to VMware on a nightly basis which has resulted in saving time as this is good throughput. Zerto also helped to reduce downtime. If we were to do this manually, we would have a lot of downtime to shut down those VMs on Hyper-V to be able to do the conversions.

What is most valuable?

The ease of the conversion moving from Hyper-V over to VMware is the primary reason why we chose Zerto and is its most valuable feature.

What needs improvement?

There has been one pain point that we have run into. We wanted to shut down the dev environment to focus on the prod environment. We couldn't find any option in Zerto to do that.

For how long have I used the solution?

We have been using this solution since the start of 2022. 

What do I think about the stability of the solution?

This is a stable solution that offers consistent results. 

Which solution did I use previously and why did I switch?

From a DR perspective, we use a few solutions. We have multi-site data centers in our environment along with Cohesity. We use Cohesity from a backup and DR perspective.

What other advice do I have?

If you're in the middle of conversion between different platforms, regardless of if you're moving from on-premises to host it or from one environment to another, Zerto is agile and able to move your workloads into different environments pretty easily.

I would rate this solution a nine out of ten. 

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
VMware Engineer at Thomas Jefferson University Hospital
Real User
Is user friendly, has great recovery speed, and has good technical support
Pros and Cons
  • "I found the very easy VPG setup, the easy recovery, and failover testing to be the most valuable features."
  • "Even though Zerto is for disaster recovery, it would be nice if it can also make backups."

What is our primary use case?

The primary use case is to migrate VMs. It's easier to use than HCX and SRM.

How has it helped my organization?

Zerto made our migration from different data centers very easy and very smooth. Zerto support and our account manager have always been there to help us out.

What is most valuable?

I found the very easy VPG setup, the easy recovery, and failover testing to be the most valuable features.

It's very user-friendly. You only need a couple of clicks, and it gets the job done. We also have SRM, but Zerto just requires a couple of clicks. You can test with Zerto, and you don't have to commit. So in terms of ease of use, Zerto is better. That's why we use it for migration.

In terms of reducing downtime, we don't actually have any because of seeding and mirroring. However, on the failover, it only takes two seconds of a blip.

Zerto's speed of recovery compared to that of others is great. It's incomparable, and the ease of use is always there.

What needs improvement?

Even though Zerto is for disaster recovery, it would be nice if it can also make backups.

For how long have I used the solution?

I've been working with Zerto for three to four years.

What do I think about the stability of the solution?

It's very stable. They have bug fixes. If there's a problem, you can report it, and they immediately provide a solution.

What do I think about the scalability of the solution?

Zerto's scalability is amazing. If they could do backups in the future, it would be better.

We're in a healthcare environment, so we have probably 30,000 VMs. We only have a couple of licenses, but that's probably going to grow in the near future. We're going to be using it in the cloud as well.

How are customer service and support?

I would give technical support a nine out of ten. I'm taking away a point because, at times, they send emails for me to read when I need something done immediately.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We previously used SRM. We use Zerto because it is just easy to use. You don't need to set up a lot of stuff. You only need to set up one appliance on each site, and you're good to go.

How was the initial setup?

The initial deployment is very straightforward. You just install the appliance, make sure that all the ports are working fine, test the connection, and you're done. If you have any problems, technical support is always there to help.

What about the implementation team?

We had help from CDI for the initial deployment, and they were not bad. It was easy enough, but we had to use our credits. If it were not for the credits, we could have done it ourselves.

After the initial deployment, my team has been doing all the upgrades and any other setups.

What was our ROI?

We're down to a couple of data centers now, and our data center cost is going down. That is the ROI we have seen with Zerto.

What's my experience with pricing, setup cost, and licensing?

The pricing is fair.

Which other solutions did I evaluate?

We evaluated SRM.

What other advice do I have?

You don't have to evaluate Zerto; it just works. I would give it a ten out of ten;
I have no complaints.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer1561206 - PeerSpot reviewer
Cloud Specialist at a tech services company with 51-200 employees
Real User
Easy to set up, good disaster recovery capabilities, helpful and responsive support
Pros and Cons
  • "Zerto provides our customers with the ability to continue work, even if something happens to their office or data center."
  • "The monitoring and alerting functionality need to be improved."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

I have been using Zerto for almost three years.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

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.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

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

Which other solutions did I evaluate?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
reviewer1371612 - PeerSpot reviewer
Network Administrator at a consultancy with 51-200 employees
Real User
Enables us to bring up a virtual machine almost immediately
Pros and Cons
  • "We selected Zerto because the RPO is extremely low, so you can get that server back up almost immediately. That was a huge thing. Also, the ability to do failover tests, where you can test your environment, but not have it impact your production environment, was huge."
  • "If I have to reboot a virtual machine host, I have issues with Zerto catching up afterward. That's about the only thing I would say needs improvement. Sometimes, when I have to do maintenance, Zerto takes a little bit to catch up. That's understandable."

What is our primary use case?

We protect about 15 virtual machines. We use Zerto to replicate them from our home office in Pennsylvania to our co-lo facility in Arizona. Our main data center is in our Pennsylvania office, but if that office were to go down, we would use this as a DR solution so we could run our company out of Arizona.

How has it helped my organization?

When I started with the company, we didn't have a disaster recovery option. If our office were to have gone down, our company would pretty much have ceased to work. Having implemented Zerto, now we know that if there's a power issue or some kind of facility issue at our home office data center, we can run everything that's protected by Zerto out of Arizona.

What is most valuable?

The most valuable feature is the ability to spin up a copy of a virtual machine which is a complete copy, within minutes.

I also enjoy the Analytics, which is something they added recently. They tell me all about my virtual machines and what kind of data we're pushing back and forth. I've been very impressed with Zerto Analytics.

What needs improvement?

The only time I ever have an issue is because there's a virtual server on each host in our environment. If I have to reboot a virtual machine host, I have issues with Zerto catching up afterward. That's about the only thing I would say needs improvement. Sometimes, when I have to do maintenance, Zerto takes a little bit to catch up. That's understandable.

For how long have I used the solution?

I've been using Zerto for between a year-and-a-half and two years.

What do I think about the stability of the solution?

It's extremely stable. I've never had any real issues with it. When there are issues, it seems to recover eventually, so I don't really have any problems with it.

What do I think about the scalability of the solution?

It's very scalable. As long as you have the licensing, you can add more virtual machines or more VPGs, which are virtual protection groups, to the license. As long as you have the licenses, you can protect the whole environment and add and remove virtual machines from Zerto as you want.

We have 15 virtual protection groups which protect 15 virtual machines at this time. Because of the licensing costs we couldn't go crazy. We have a total of about 60 or 70 virtual machines, but we only needed to protect the critical ones. We're using 12 of those 15 licenses.

We don't have plans to increase usage of Zerto at this point because these are the critical servers. If we add more critical servers that need to be up in case of an outage at our home office, we may add more. But this 15 has covered us.

How are customer service and technical support?

Their technical support is good. Just like any technical support, it's all based on the severity of the case. I've never had any outage cases, so I have never had to sit on the phone or wait for them to get back to me. 

I opened two cases with them and they got back within a reasonable amount of time. Both times, they knew exactly what the problem was and how to fix it, just from the details I left them in the case notes.

They also have a nice option where you can submit a case, or enable remote support, right from the interface. The support's pretty nice because they can actually look at logs, once you give them remote access right into your environment. That's very useful. And they're very knowledgeable.

Which solution did I use previously and why did I switch?

We didn't have a previous solution. We selected Zerto because the RPO is extremely low, so you can get that server back up almost immediately. That was a huge thing.

Also, the ability to do failover tests, where you can test your environment, but not have it impact your production environment, was huge. 

Those two features were the main selling points for us to pick up Zerto.

How was the initial setup?

The initial setup was very straightforward, very easy. We set up a virtual machine at both locations, which are both Windows, and then installed the Zerto software and gave it credentials to connect into our environments. It did the rest for us. Once it was initially set up, we just had to figure out which virtual machines we wanted to protect and which way: did we want it to copy from our data center over to the co-lo, or back to our data center from the co-lo. They walk you through step-by-step with wizards. It's incredibly easy to set up.

Because there's a lot of data initially to sync over, the deployment took about a week in total. The initial setup only took a couple of hours, but then you have to wait for all that replication to sync.

We didn't have an implementation strategy for Zerto. Because we didn't have a previous solution, we didn't have any migration to do. We just paid for the license, got it installed, and rolled with it.

What about the implementation team?

I did it myself.

Technically there are four users who have access to it in our company. I'm the main administrator. The other ones are guest administrators and they have a little less access than I do. But nobody else really logs into it except me, unless there's an issue and I'm not there. But as the main administrator it's really all on me.

What was our ROI?

We have seen return on our investment with Zerto, absolutely. Just to have an option for disaster recovery in case our main data center goes down — which can happen, because we don't have a generator or anything in our home office — is a type of return. Not just IT, but everybody in the company from the C-suite, was happy that we have a disaster recovery option now.

What's my experience with pricing, setup cost, and licensing?

First of all, you should figure out which virtual machines are critical and how many licenses you may need before you start getting prices. You don't need to go crazy if you only have a handful of servers that need licensing. 

Zerto sells licensing in bundles or packages, so I wouldn't go crazy and buy 100 licenses when you only need 30. Figure out what you need before you get your licensing, because it can get expensive.

Which other solutions did I evaluate?

We have Veeam which we use for backup and I know they have replication, so we looked into that, but it just wasn't as feature-rich or as quick to restore or bring up a VM as this was. We hadn't heard about Zerto really until we went to a conference in Philadelphia. They told us about it so we looked into it and it seemed like the best option at the time. We did look at maybe one or two other options, but this was the one that looked like the best option for us.

What other advice do I have?

The biggest lesson from using Zerto is the failover capability and the testing capability. Those are two very useful things. If somebody calls me and they need to test something in a test environment, I can use the test failover copy of Zerto to bring up that virtual machine, or machines, and test things without affecting production. The other thing that is impressive is that you really can bring up a virtual machine almost immediately.

I would definitely give it a 10. I have no problems with it. I'm very happy with it.

Which deployment model are you using for this solution?

On-premises
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
PeerSpot user
Rodney Carlson - PeerSpot reviewer
Rodney CarlsonSystem Analyst at a financial services firm with 501-1,000 employees
Real User

I like the review. I would add an additional feature comment that it is not hardware dependent so you can use it on any brand or model you have.

PeerSpot user
Manager, Infrastructure at Vizient Inc
Real User
Easy to set up and configure, flexible, and gives us peace of mind for our critical applications
Pros and Cons
  • "The most valuable feature of Zerto is its overall flexibility, where it can be used for standard DR or you can also use it for server migrations, data center consolidations, etc."
  • "I wouldn't mind seeing Zerto sold at a cheaper price point, although the cost is comparable to VMware SRM."

What is our primary use case?

We use Zerto for disaster recovery of our tier 1 applications from our primary data center to our secondary data center. We have also used Zerto to successfully perform server migrations from one site to another for data center moves and company acquisitions.

Our administrators love the product and it has been proven to be easier to use than VMware SRM which we were using before going with Zerto.

How has it helped my organization?

Zerto has given us the peace of mind to know that we have full DR protection for our critical applications.

Zerto is relatively easy to set up and administer.

We were able to create runbooks within Zerto to help with DR failovers, and testing DR failovers is pretty easy as well.

We used to use VMware SRM and it was very cumbersome to add in new virtual machines or storage volumes because they would basically "break" the SRM protection groups that were already out there. With Zerto, it takes on new additions to protection groups much easier and it saves our admins a lot of time having to care and feed it.

What is most valuable?

The most valuable feature of Zerto is its overall flexibility, where it can be used for standard DR or you can also use it for server migrations, data center consolidations, etc. You can also use it for data protection and physical to virtual migrations as well.

It is kind of a swiss-army knife.

What needs improvement?

I can't think of any major areas of improvement with Zerto. Make sure that they are building in cloud-friendly features in future releases because a lot of enterprises are starting to move workloads to the cloud and are seriously considering doing DR to the cloud as well. Our company may be moving in that direction also.

I wouldn't mind seeing Zerto sold at a cheaper price point, although the cost is comparable to VMware SRM.

For how long have I used the solution?

We have been using Zerto for four Years.

What do I think about the stability of the solution?

Zerto has been rock solid for us in terms of stability.

What do I think about the scalability of the solution?

The scalability of Zerto seems to be ok. This will depend on the size of your environment and how often you need your data replicated for BCP and SLAs.

How are customer service and technical support?

Zerto customer service has been great so far. No complaints!

Which solution did I use previously and why did I switch?

We used to use VMware SRM and we switched to Zerto because it is less expensive and easier to administer.

How was the initial setup?

The initial setup of Zerto was very straight forward. The rest of the configuration will be as complex as your environment's DR needs and application stacks are.

What about the implementation team?

We had an engineer from Zerto help us with the installation and initial configuration for thirty days.

What's my experience with pricing, setup cost, and licensing?

It is good to do a full Disaster Recovery plan for your organization and doing a BCP plan as well. You need to figure out how many critical servers and applications you have in your environment so you will know how many Zerto licenses to buy, etc.

Which other solutions did I evaluate?

We only baked off VMware SRM and Zerto.

What other advice do I have?

It is good to implement a proof of concept of Zerto to test it out. I highly recommend it for data center moves.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros sharing their opinions.
Updated: March 2025
Buyer's Guide
Download our free Zerto Report and get advice and tips from experienced pros sharing their opinions.