VMware Live Recovery Reviews

We have three different VMs. During long business hours, we can shift from PR to DR. It has high availability.

Setting up VMs can be done quickly. It is easy to use. 

The improvements should be as per customer requirements. 

I have experience with VMware Cloud Disaster Recovery.

The stability of the solution is a nine out of ten, as it is highly stable. 

Two hundred users are using the solution at present. 

I would rate the initial setup an eight out of ten. 

Overall, I rate the solution an eight out of ten. 

The interface of VMware SRM is quite basic and doesn't offer much in terms of features. The solution is strong when it comes to protection and analytics, with the latter being added later on. Protection has been the major feature that we have been using, and it has been quite effective for our needs.

The two main areas for improvement in VMware SRM are pricing and administration guides. Pricing is always a consideration, and it could be improved. The administration guides can be complicated and difficult to use, so it would be helpful if it was made easier. Administrators don't want to find themselves in a situation where they can't find what they need, so it's important to make sure that the tools are easy to use.

I have been using VMware SRM for six to seven years, which is also the longest experience I have had with any VMware product. Our company recommended it to one of our customers initially, and after that, we had complete freedom to implement it for them. It was a good experience overall. Additionally, my company has a partnership with VMware.

Stability-wise, I rate the solution a seven out of ten.

The scalability of VMware SRM is good. Scalability for Azure and AWS is also good. Scalability-wise, I rate the solution an eight out of ten.

My company deals with enterprise-sized customers.

VMware's vendor support was good. I rate VMware's technical support an eight or nine out of ten. To be more specific, I rate it an eight out of ten.

Positive

I rate the initial setup process of the solution a seven or eight out of ten on a scale where one is difficult, and ten is easy. The setup process was not too difficult or too easy. Essentially, we were imaging all their physical servers on the cloud.

In our company, the deployment process takes about an hour. In some cases, due to the size of the data we were dealing with, it took a couple of days, which was the maximum, but usually, it was completed within a few hours.

I rate the solution's pricing a six on a scale of one to ten, where one is the lowest and ten is the most expensive.

l always recommend others to have a POC in place. It's always about whether a solution suits your environment or not. So if it does, then go for it. If it doesn't, one should go for another solution. I rate the overall solution an eight out of ten.

SRM's best feature is automation.

An improvement for SRM would be better interface compatibility with other products.

I've been using VMware SRM for ten years.

I've never faced any issues with SRM's stability.

SRM is reasonably priced for the functionality it provides.

I'd rate SRM as eight out of ten.

It's user-friendly, for those who have learned and experienced the technology.

VMware is one of the best products in the industry when it comes to virtualization.

Technical support needs improvement, they are not very responsive.

You should be technically skilled enough so that you don't have to rely on its support. It's not easy when you don't get the support that you would expect to receive from VMware.

I have been working with this solution for more than five years.

VMware SRM is a stable solution. It's very reliable.

VMware SRM is a scalable solution.

We have always had trouble reaching out to support and connecting with their support engineers.

I would rate the technical support a three out of five.

Neutral

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

I would rate VMware SRM an eight out of ten.

SRM is implemented as part of VMware.

We use it for failover between geographical locations from one location to another location. Sometimes for maintenance purposes, we can failover services to another location so that we can maintain the technology at another location.

The solution works well. If you want to do failover, it works without any problem.

The product is stable.

The deployment process is fast.

The challenge it has is with the speed of failing over. Sometimes it can cause a bit of downtime during switchovers. Sometimes you realize that when you are failing over you can have downtime due to the fact that you're stepping down on one side and powering up on another side.

We've used the solution since 2012. It's been almost ten years.

The stability is great. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

The scalability is just a function. Whether you can scale or not depends on your resources. It depends on your bandwidth. The scalability will depend on the infrastructure it is using.

We have three people who work with the solution directly.

The deployment doesn't take long. It also takes just a couple of hours as long as you have prepared and long as you have a design.

For the implementation process, we needed three people, however, for implementation, we need a trained engineer. Just one engineer is fine.

If you have trained people who are certified, you can do it yourself. The most important thing is to make sure that it is done by a trained engineer.

We do have to pay a licensing fee in order to use the solution. We have an annual subscription. 

I don't remember the version of SRM that we're using now.

I'd recommend the solution to others.

I would rate it at an eight out of ten.

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 are a system integrator in Morocco and this is one of the products that we implement for our clients. Our customers use VMware SRM to replicate sites for the purpose of disaster recovery. SRM is a recovery manager and we combine it with NetApp to provide recovery solutions.

The most valuable feature is the simplicity of operations. You have two main buttons, where one is red and one is green. The red button is used for real disaster recovery and the green button is used if you want to simulate it.

The interface is user-friendly.

The storage replication adapter (SRA) is quite good because it allows SRM to work with storage arrays from any vendor.

I would like to see a detailed history of the events for each site because I have found difficulty with that. The two vCenters have to be synchronized, which sometimes gives us problems because Keberos does not tolerate more than five minutes in time difference.

I have been dealing with VMware SRM since 2009.

The recovery point (RPO) is set to 24 hours, which means that this is being used daily. Our backup happens at 8:00 pm every night.

VMware SRM is scalable.

Most of our clients are in Morocco, and 80% of them are bigger companies with a lot of users.

Technical support from VMware is good and I would rate them an eight out of ten.

The initial setup is definitely simple.

The last project that I worked on took two weeks to deploy. This included installing NetApp, vCenter, ESXi, and the initial application.

We have an in-house team that includes me and two other people. We also do maintenance for some of our clients.

In the past, with version 6.0, there were two versions of SRM. There was a version for Windows as well as an appliance. However, all of our customers are now moving to the appliance.

I recommend using this product because it integrates well with replication technology from any vendor using the SRA.

I would rate this solution a nine out of ten.