VMware Live Recovery Reviews

We primarily use the solution for migrating our DR site.

We have a system that can now move us to a DR site. I have yet to experience any major crisis, however, so I haven't yet tried it. 

The solution runs well in the background, just in case we need it. 

It is stable. 

The solution has the capability to scale well. 

I don't have any notes for improvement.

I'd like the installment and configuration to be more seamless.

The user experience could be more friendly.

It's, by definition, a complicated product. 

We'd like the entire solution to be more automated. We'd like as much automation as possible. 

The solution is very expensive. 

I've been using the solution for more than five years. 

We haven't had any stability issues. There are no bugs or glitches. It doesn't crash or freeze. It is reliable.

We have not tried to scale the solution. However, we are aware that it can be quite scalable. It depends on the license. 

The initial setup and configuration can be complex. It's a complicated product. I'd rate the complexity of implementation eight out of ten. 

It took us a few months to fully deploy the solution. 

We had an in-house team and professional service to manage the setup process. We did not do it fully by ourselves.

The pricing is very high. However, you get what you pay for. You need to invest a lot of money in order to gain any functionality. In order to have a DR site and maintain it, you need the investment. 

I'd rate the solution seven out of ten. It's expensive. However, it's a good investment. 

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.

In terms of recovery, if you have a test job script, you can put it on top of it. You can create custom steps so that it will be more granular. It will be an easy, one click solution when it comes to the recovery application.

It would be good if this solution could integrate configuration management software such as Chef Infra.

I've been using VMware SRM for more than a year.

The stability is always good because we replicate daily. I have never seen any issues because the replication is always 100% successful.

You can add multiple appliances, and it supports enterprise environments.

Technical support is very good.

The initial setup is straightforward.

The deployment takes about three hours.

VMware SRM is the best sustainability solution, I would rate it at nine on a scale from one to 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 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 are not an end-user. We are a solutions provider to companies.

All of its components are very competitive compared to other solutions. The application, the DR health check, and the scale-out file system are all great. They tailored a lot of technology in the VCDR, which is good. It's a very good solution overall.

The initial setup is very straightforward. 

The solution is stable. 

Technical support is very proactive and helpful.

The solution has proven to be easily scalable. 

They need to have their own cloud, however, unfortunately, since the solution has been acquired by VMware, I doubt that will be happening.

It is impossible to acquire Datrium data nodes, unfortunately.

It would be ideal if they added advanced analytics or AI to the solution.

We've been working with the solution since before Datrium was acquired by VMware. 

In terms of stability, recently, we encountered an issue, however, it has been addressed immediately by support. It's now resolved. For the most part, the solution is stable. 

The scalability is pretty good. We just have to ask for additional space. Eventually, it will be guaranteed on demand.

There are many users on the solution. It's a big organization.

One of the good things about the solution is that it has very proactive support there. They are helpful and responsive and we are pleased with the level of assistance they offer.

We did not previously use a different solution. 

The solution is very straightforward and easy to set up. The deployment is quick and easy. In our experience, the solution only takes four hours to deploy. 

We're integrators and therefore can implement the solution for our clients. 

We looked at other solutions, however, the product is a very good technology. We have seen its many advantages as compared to other solutions. For example, the solution has been HCI disaggregated.

I'm not sure which version of the solution we're using. 

We're an integrator. Our clients use the solution. We are not end-users. 

I'd rate the solution at a ten out of ten.

We vetted out that data center a number of years ago. We were told SRM would improve our footprint within the data center and that was attractive to us at the time so we went with it.  

We are using VMware SRM but we are also currently looking into alternatives that could replicate the benefits that SRM currently provides for our on-premises installation. Once we are in the cloud, we are looking at whether or not we need dual availability zones. We also are looking at what functionality we could get from not having to change RPs (Recovery Point) as we do now with SRM.  

I would not be able to tell you the features and benefits that are best for the Engineering Teams. That would be more a question for my Engineering Manager and those guys. I am in service delivery and I am familiar with the product but not with hands-on use.  

The decision to move to another product is a matter of room for improvement around functionality and requirements that we had with AWS and moving to the cloud. We are not going to be procuring any more licensing for SRM when we make the move to the cloud. We were looking at a cloud-native solution in order to provide the same functionality as the SRM provides but in the cloud. That is just a matter of the changing environment.  

If the functionality of SRM could be replicated in the cloud, that would be the improvement we are looking for in the product.  

I have been using SRM (Site Recovery Manager) for probably six years.  

I have contacted technical support multiple times. I would not say that I am satisfied. They are not very good and need to make an effort to improve.  

The initial setup and installation were pretty straightforward. It was ten plus years ago so I do not remember the exact details, but I do not remember it being difficult at all.   

The cost of SRM is on par with market rates. So I think the costs for this product are fine.  

I personally will not continue using the VMware SRM solution. That is not a question of what is best. Our position moving forward is that we will not be having a footprint in the VMware space. If someone had the ability to focus on lots of things with using VMware in the cloud then there no issues at all with the product and this is a good solution for that purpose. The product functionality is fairly high-quality. Our decision is more based around the direction that we are taking. We will be cloud-based and we will be using AWS predominantly as our cloud-provider solution.  

On a scale from one to ten (where one is the worst and ten is the best), I would rate this solution overall as an eight-out-of-ten. It would not be closer to a ten because there is still some work that we need to carry out with regular maintenance and then there are the increasing license costs. An eight seems about right.