Buyer's Guide
Disaster Recovery (DR) Software
November 2022
Get our free report covering VMware, Veeam Software, Zerto, and other competitors of Dell RecoverPoint for Virtual Machines. Updated: November 2022.
655,465 professionals have used our research since 2012.

Read reviews of Dell RecoverPoint for Virtual Machines alternatives and competitors

Resiliency Specialist at a computer software company with 5,001-10,000 employees
Real User
Easy to use, integrates well with vCenter, and it provides a short RPO in case of data center outage
Pros and Cons
  • "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."
  • "Zerto should add the capability to replicate the same VM to multiple sites."

What is our primary use case?

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.

How has it helped my organization?

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.

What is most valuable?

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

What needs improvement?

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.

For how long have I used the solution?

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.

What do I think about the stability of the solution?

Zerto is very stable.

What do I think about the scalability of the solution?

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. 

How are customer service and technical support?

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.

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

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.

How was the initial setup?

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.

What was our ROI?

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.

Which other solutions did I evaluate?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

Hybrid 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.
ESLAM ELSAYAAD - PeerSpot reviewer
Senior Solution Architect at ICT Misr
Real User
Top 10
Effective disaster recovery, two site synchronization, and cost effective
Pros and Cons
  • "VMware SRM is very effective between two sites with identical twin storage, you can have synchronization between the two sites."
  • "We have had an issue when some customers have traditional designs and sites. For example, on one another site, they are using hyper-converged, using VMware, or Nutanix. We have a problem with the synchronization between the storage for site to site. This is the main issue. We are adding some other tools to support the synchronization to allow the movement of the workload from site to site easily."

What is our primary use case?

We are using this solution to serve our customers in different sectors.

We are using VMware SRM as a disaster recovery solution for our customers. We are working with vSphere, vSAN, and other infrastructure VMware solutions. VMware SRM is completing the solution.

What is most valuable?

VMware SRM is very effective between two sites with identical twin storage, you can have synchronization between the two sites. 

What needs improvement?

We have had an issue when some customers have traditional designs and sites. For example, on one another site, they are using hyper-converged, using VMware, or Nutanix. We have a problem with the synchronization between the storage for site to site. This is the main issue. We are adding some other tools to support the synchronization to allow the movement of the workload from site to site easily.

Not all customers have VMware in all workloads. Some customers have a difference, VMware environments, such as Red Hat or Nutanix. VMware SRM is very effective for VMware customers. However, when you have other workflows with other vendors, you can not always use this solution.

For how long have I used the solution?

I have been using VMware SRM for approximately 12 years.

What do I think about the scalability of the solution?

VMware SRM we mainly use for our mid-size business customers. For small business-sized customers, we have different solutions we can deliver, such as Veeam. If they are a small customer that does not have a professional DR site we have a variety of solutions we can deliver depending on the customer's needs.

Enterprise businesses have many VM and the amount depends on the design of the data centers, which storage is being used, or is it hyper-converged or converged. We are choosing the best solution depending on the customer's need.

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

When comparing the difference between VMware SRM and Dell EMC RecoverPoint there are many differences between them both. VMware SRM is an automated tool for disaster recovery, RecoverPoint can do a similar job but it has better protection more than an automated tool for moving VMs. 

With our customers, we are delivering both solutions, Recovery Point and SRM, because they already had the Dell EMC storage and owned Dell Recovery Point, we only added the VMware SRM tool for moving the VMs and storing them from site to site, as an automated tool.

Dell RecoverPoint has the edge over VMware SRM in one area because they can work with other vendors, not only Dell EMC. Some customers have workloads on the cloud, Dell RecoverPoint is very effective for them.

I have used Veeam and other solutions.

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

The price of VMware SRM depends on how many VMs the customer has to move. There is a difference between the standard and enterprise license. I'm presenting the standard license to my customers because the total of VMs is not more than 50. The customer needs only the standard license and the cost is very effective for him.

What other advice do I have?

I rate VMware SRM an eight out of ten.

Disclosure: My company has a business relationship with this vendor other than being a customer: partner
Tommy Myo Min Aung - PeerSpot reviewer
Senior System Engineer at a energy/utilities company with 501-1,000 employees
Real User
Top 5
Beneficial pricing model, user friendly interface, and many free features
Pros and Cons
  • "The solution is a user-friendly interface."
  • "The solution could improve by having a version to be compatible with the Linux system. They have improved the storage depository using the Linux proxy and Linux storage, but it can completely run on the Linux environment it would be much better."

What is our primary use case?

We use Veeam Backup Replication for the data center, desktop recovery, daily backups, and for storage offline.

What is most valuable?

The solution is a user-friendly interface.

What needs improvement?

The solution could improve by having a version to be compatible with the Linux system. They have improved the storage depository using the Linux proxy and Linux storage, but it can completely run on the Linux environment it would be much better.

For how long have I used the solution?

I have been using Veeam Backup & Replication since version six which is approximately 10 years.

What do I think about the stability of the solution?

Veeam Backup Replication is highly reliable. One engineer can cover the entire backup solution for the whole organization.

What do I think about the scalability of the solution?

I have found Veeam Backup Replication to be scalable.

We have between 500 - 1,000 users using this solution.

How are customer service and support?

We have not needed to contact technical support.

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

We have previously used a Dell. However, Dell was difficult to restore backups and Veeam Backup Replication was a better fit for our needs.

We would like to have the Veeam Backup Replication from the VMware or Hyper-V direct to the tape library.

How was the initial setup?

The installation is straightforward, it does not take long to do approximately 45 minutes.

What about the implementation team?

We did the implementation in-house.

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

Veeam Backup Replication has a lot of free features. We have a mixture of the paid versions as well as the community version. They are really helpful to us.

We have approximately 200 instances of Veeam Backup Replication with paid licenses and we use the community edition for the small offices.

What other advice do I have?

I rate Veeam Backup Replication a 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.
Buyer's Guide
Disaster Recovery (DR) Software
November 2022
Get our free report covering VMware, Veeam Software, Zerto, and other competitors of Dell RecoverPoint for Virtual Machines. Updated: November 2022.
655,465 professionals have used our research since 2012.