We also used to have Datto and Carbonite for DR.

We've only used SRM. We did not use anything previously.

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.

In addition to our existing setup, we use backup software, Veeam, for replication on the disaster recovery side. With Veeam, we replicate virtual machines from the primary site to the secondary site. It is particularly advantageous because it doesn't require the same storage type on both the primary and secondary sides, which gives us flexibility and allows us to mix and match storage types if needed. One of the key benefits of Veeam is its ease of management, making it a valuable resource for replication. I believe it has a promising future, especially for handling data replication in various sectors. We also employ Veeam in the banking system to replicate data from different strategies across multiple departments. Its performance in replicating virtual machines is superior to SRM. The choice between SRM and Veeam largely depends on your storage environment and replication needs.

Before VMware SRM, we were using Veritas Volume Manager and Veritas Replication Manager for stand-alone. When we went to virtualize, we moved to SRM. I did a lot of work with IBM PowerVM and it had some nice features. It had things such as better prioritization of allocation of resources and Boot profiles where you could put one VM across another so that it grabbed the resources. You could do things such as have thin DR VMs without much allocation of CPU or memory, and then as you boot them, they start to grab all of that automatically from all of the non-prod. Functions like that were quite good in Power VM, which aren't quite as present in the VMware world. PowerVM is extremely expensive to use and that's why everyone is shifting towards commodity computers.

I have previously worked with products from other vendors like Nutanix. I still use Nutanix Acropolis in my company.

We previously used Veeam Disaster Recovery Orchestrator, which is more suited for small businesses. It doesn't offer as much flexibility as VMware SRM. For namesake, it's a DR solution, but it cannot compete with VMware SRM.

Previously we were not using any DR solution, but we are using Veeam along with SRM.

SRM is being used for far-end recovery whereby the DR site is in another city.

Veeam is being used for near-end recovery, whereby the DR server is located in the same datacenter. This is useful for VM level recovery, where only a VM or handful VMs or vDisks are affected.

Previously used Netbackup and Avamar.

In our company, we use Nutanix Leap, which is similar to VMware SRM.

VMware SRM is available to users as a separate package from VMware, while Leap comes with Nutanix allowing users to use it anytime. In terms of utility, Nutanix Leap and VMware SRM are the same.

We are also using Zerto.

Disaster recovery was completely done with physical servers prior to when we started using VMware. When we went to VMware, we started using SRM. So the first time we went with the virtual environment we deployed SRM. We just went straight with SRM just because it is a VMware product. It was already well-integrated and did what we needed it to do.  

Yes, I used other products like Storage replications or some other software like "double take.” The problem with storage replication was that it was so risky and unstable to manually bring the application up on DR site, besides taking more time to restore.

Other software, like double take, we needed to do lot of effort on each application separately which makes the solution more complex.

Prior to using VMware SRM, we were doing everything manually. Failover of VMs was done manually from promoting the replicated LUNs to read write and then bringing them up in the DR VMware environment.  It was a lot of manual work when dealing with hundreds of VMs.

In terms of VMware, we use a variety of solutions, such as VMware vSAN, VxRail, Center, and SRM.

I don't think that there is another product that serves the purpose that this VMware SRM does. Integration is very important to me, to have the whole environment integrated together in one place. Because of this, I went straight to VMware.

I was responsible for designing and implementing a DR solution for my company and being that we're on a VMware environment it seemed only logical to go to VMware first because all the machines that I need to put at my, disaster recovery site are virtual servers I was like well I'm sure VMware has a solution.

Being able to test the environment, being able to make the changes to the virtual servers so they could come up on a different network. I needed to be able to go in there and change things like the IP address, the DNS settings and stuff like that to be able for them to come up at a different location.

No.

We looked at various types of solutions like Veeam, DoubleTake and Neverfail.

No previous solution used.

We use several solutions. We determine what is best for the customer and present them with the solutions we believe fit their needs best.

Did not use a previous solution.

We previously used Zerto. We switched because VMware only has a single point of support, as we needed to move forward with better products.

No previous solution used.

Just a regular backup product. But this wasn't a disaster recovery solution.

No.

For VMware environments there is no other option for integrated/automated DR other than 'roll your own.'

We did not use another solution prior to this one.

We have always used VMware solutions because VMware is owned by EMC. So we've only used VMware SRM.

The most important criteria when selecting a vendor are stability, scalability, things that Microsoft had issues with.