VMware Live Recovery Reviews

Instant VMware integration and a wide integration with storage vendors.

The company was able to provide customers with the required RPO that was not possible with traditional backup solutions.

Stability, speed.

4 years.

Bugs bugs bugs...

Sometimes the vm would not failover.

No backwards compatibility of different versions, this made scaling a bit difficult as we needed to upgrade existing infrastructure all the time.

3/10, VMware support was not really proficient in the product, as most of the time we would give them the solution.

3/10, VMware support was not really proficient in the product, as most of the time we would give them the solutio

No.

The integration with EMC recoverpoint was problematic in the beginning, with vm's not failing over all the time and slow recover times.

Yes, Zerto, Veeam.

POC and test.

Key feature for me is the ability to test recovery plans with zero impact to the production running environment, this is key for 'what-if’ type analysis and to provide confidence that the platform can be recovered with minimal intervention.

Organisations that have implemented SRM in my experience have confidence that their mission critical systems will be recovered within the given SLA in the event of a planned or unplanned availability event. This avoids costly and time consuming DR recovery tests which are also often unrepresentative of the real scenario.

Smaller sites or sites with mixed storage platforms rely on vSphere replication for DR purposes so additional scalability in this tool would benefit from this.

I have designed and implemented 3 solutions with this product over the last 3 years.

No issues

More around vSphere replication than SRM

No issues encountered.

VMware Tech Support is excellent.

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

SRM setup is straight forward, SRA (storage integration) can be more complex depending on the array in question.

I was working for the vendor.

Consider your storage design and replication policy first and as always make sure you review VMware documentation and HCL for compatibility.

VMware SRM is used for disaster recovery automation.

VMware SRM is a very nice tool for disaster recovery for virtual environments.

The solution could improve by removing some of the limitations we have been facing. There could be better integrated.

I have been using VMware SRM for approximately 10 years.

The solution is stable.

VMware SRM is scalable.

We have approximately 25 people using this solution in my company.

The support could be improved, they are slow.

The installation is of a moderate difficulty level. The time it takes to implement depends on what vendor you are integrating it with, such as HP. The typical duration of implementation including the configuration is approximately five days.

We have one engineer for the maintenance and support of VMware SRM.

There is an annual license to use this solution.

I would recommend this solution to others.

I rate VMware SRM an eight out of ten.

Our primary use case of this solution is for testing. 

The UI is very user-friendly and testing is easy, it doesn't require a lot of resources or a SAN team to enable testing, a single person can do it and get results. 

Unfortunately, SRM is not stable and it therefore requires continuous monitoring. If there are any issues associated with the Center, SRM doesn't work well and as a result, it generates a lot of tickets and productivity drops. 

I've been using this solution for five years.

Although this solution is a good tool, it lacks stability. We have five users in our team. 

The overall advantage of VMware is its scalability. But when it comes to SRM, scalability is not really relevant. It's only relevant in terms of the DR solution because SRM is a component of VMware, which requires vCenter. 

The technical support is quite good. 

Setup of SRM required the architectural team. The SAN team plays a very important role here because there's not enough stability. The DR test can fail because of the associated orchestration issues with regard to the SAN.

I've never used Zerto, but from my training and my personal analysis, I think it's better than SRM. 

I rate this product six out of 10. 

We use this product primarily for our DR drills, which you can do quietly during office hours. Sometimes we use it for site migrations or planned outages.

The most valuable feature is disaster recovery testing.

The reports are very good.

The configuration process could be improved.

I have been using VMware SRM for about five years.

This is the most stable solution that I have seen. It is used on a daily basis, although we are only monitoring it intermittently. It monitors our critical workloads in the background.

It is easy to scale VMware SRM.

We have been in touch with technical support once or twice and we are happy with them.

We did not use another solution prior to this one.

The initial setup is simple and it takes approximately four hours to deploy.

There is not much in terms of maintenance and we do not have that role assigned to anybody.

We had an integrator assist us with the implementation.

We went straight to this product without evaluating other options.

This is a product that I would recommend for people with a VMware stack.

I would rate this solution a ten out of ten.

We use VMware Cloud Disaster Recovery as a disaster recovery service and backup as a service.

The most valuable features are the backup and disaster recovery services.

VMware Cloud Disaster Recovery could improve by enhancing the network bandwidth from the storage.

In a future release, I would like to see new functionality or current feature enhancements.

I have been using VMware Cloud Disaster Recovery for a few years.

I have found VMware Cloud Disaster Recovery to be stable.

The scalability of VMware Cloud Disaster Recovery is very good.

We have customers in the medium to large-scale enterprise companies.

The technical support provided by VMware is one of the best I have used.

I have used many similar solutions to VMware Cloud Disaster Recovery, such as Veeam and Citrix.

The installation is normally simple for users to fully implement.

The price of VMware Cloud Disaster Recovery should be lowered in order to compete better in the market.

I rate VMware Cloud Disaster Recovery a nine out of ten.

We use it, I and several of my colleagues, as a data recovery solution between VMware environments. It is a complementary solution to EMC solutions, for storage. 

it is a complementary solution to EMC's data recovery solutions, or RecoverPoint. Combined with VMware SRM it offers zero RPO and zero RTO, so it's a good solution for both EMC's Toolkit, and for the customer.

There is zero RPO and zero RTO when combined with the EMC solution called RecoverPoint.

I would like to see better integration with other storage solutions. I would hope to see that within the next two or three years.

I've never had any problem with downtime or the solution not working. The only issues were human errors in configuring it.

Scalability is bigger and better than the competitors.

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.

It's not entirely straightforward. You have to know what you're doing in order to make it work properly.

Before choosing a cheaper solution, I would advise checking the limitations or boundaries of each solution. Compare VMware to Microsoft Hyper-V and other solutions - maybe open-source - and then see which fits your needs best.