VMware Live Recovery Reviews

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.

In my company, we use VMware SRM for virtual machine replication.

The most valuable feature of VMware SRM is RTO, better described as recovery time. In most places, my company uses SRM along with backup software since SRM cannot be used as a backup product as it is just a replication tool.

VMware SRM is not a popular product anymore since all the other backup products can provide the same functions as SRM. With Veritas, Arcserve, or Commvault, you can take care of the replication part. VMware SRM is not a popular choice among users anymore since it is a highly costly product while also being complex to configure. When it comes to backup products, you can use RTO and RPO, so there is no need to have a separate solution like SRM. In general, the drawbacks of VMware SRM, where improvements can be made, stem from the fact that it is an expensive and complex product.

I have been using VMware SRM for six to seven years. My company has a partnership with VMware.

It is a stable solution.

It is a scalable solution.

At the moment, just one of our company's customers uses the solution since we have replaced the native backup software used in our company. We need to take care of the renewal of SRM since, right now, we only take care of the renewal of vSphere in our company.

The solution's technical support is excellent.

The solution's initial setup was easy, but if you try to integrate it with other storage solutions, then it gets complex and difficult.

The solution is deployed on an on-premises model.

For first-time users, VMware SRM can be a very difficult tool to use, especially considering the product's configuration part. The configuration is very difficult.

With VMware SRM, you have to download the separate appliance and think about Windows to build a separate native appliance while also having knowledge about ESXi, making it a difficult process. When it comes to VMware SRM, the technical things are very difficult to start in the first place.

I rate the overall tool a five out of ten.

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. 

We use it for disaster recovery.

I like how VMware SRM is able to automate and orchestrate disaster recovery.

The price, in general, could be lower.

I've been using this solution for probably three years now.

It is a stable solution.

It is scalable.

My experience with technical support has been fine.

The installation is straightforward if you have the required skill level. It took about a week for the initial setup.

The price could be lower, in general. My clients pay for an annual license.

I recommend VMware SRM and rate it at eight on a scale from one to ten.

We primarily use the solution for disaster recovery.

The replication is the solution's most valuable feature. If we have some issues on the VM in the main site we can migrate it to another site automatically. 

The configuration assembly for the VMware is good.

If you have a failover case, you need to work on it manually. It would be helpful if this could be automated. It would simplify things.

The stability of the solution is great. We've tested the system and haven't discovered any bugs.

The solution is very scalable.

Technical support is amazing. They have a great background in VMware issues and engineering.

The initial setup is very straightforward. It's quite simple. However, those that implement it must have some experience in virtualization. In terms of deployment, you can have a demo regarding SRM and need to apply the scenario on it. Afterward, you can apply it to your environment. It's very easy.

I handled the implementation myself.

You need a license for SRM. We have a permanent license. There aren't additional fees if you need access to support. However, you can upgrade to another support tier. If you like, you can pay extra for premium support.

We're using the on-premises deployment model.

I'd recommend the solution. I'd rate it ten out of ten.

We use the solution for DR.

We use the LDM component within our government. Additionally, SRM, a leading VMware product, is user-friendly and supports all our requirements.

There could be an integration between VMware SRM and Nutanix products, which can benefit many users.

I have been using VMware SRM since last year.

There is a minimum downtime.

I rate the solution’s stability a ten out of ten.

The solution’s scalability is good.

2000 users are using this solution.

I rate the solution’s scalability a ten out of ten.

Whenever we have an issue or need help, we raise it directly to VMware.

Positive

The initial setup is simple.

I rate the product’s pricing a five out of ten, where one is cheap, and ten is expensive.

We have a cloud environment that requires disaster recovery capabilities. We utilize HZX to extend layer two connectivity and leverage Site Recovery Manager (SRM) for replication.

I recommend the solution to other users.

Overall, I rate the solution a ten out of ten.

In my company, we use VMware SRM for synchronous replication.

The most valuable feature of the solution is that vMotion is possible in VMware SRM, making it a great tool, especially when doing a DR drill. Synchronous replication and asynchronous replication are also some of the good features of the solution.

The weakness in VMware SRM is visible when, in our company, we try to do some cross-platform programming. For cross-platform programming, we might need some external tools, like Veeam or Commvault, for cross-hypervisor replication. It is not so easy to integrate it with other solutions. The aforementioned details can be considered for improvement of the solution.

The technical support is not quick enough to respond when a user tries to contact them. For improvement, the support should respond quickly to a user.

Cross-hypervisor restoration support or multi-platform support would be some of the best traditional features I would like to see in VMware SRM's future releases.

I have been using VMware SRM for two to three years. My organization functions as a cloud service provider. My company uses the product as well as recommends the product to the company's customers.

It is a very stable solution.

We haven't found any issues with VMware SRM's scalability.

In my company, most of the machines have been replicated through VMware SRM, which consists of very few and not many in numbers. We also use Veeam as a backup for external storage, making VMware SRM a handy tool for our company.

One or two administrators are enough to handle the solution.

Speaking about the product's future usage, our company doesn't have much of a requirement for VMware SRM because we majorly need it only for testing purposes. For our company, VMware SRM is not an important tool. Our company recommends VMware SRM to our customers since VMware has been putting out all these features, making its product better.

The solution's technical support is not bad since they are responsive. My company successfully resolved most issues we faced while working with the product. My company had raised only one or two issues with VMware, and they had successfully resolved our issues.

I rate the technical support a seven to eight out of ten.

Neutral

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.

I was involved in VMware SRM's deployment phase two years ago, and it was an easy process.

The solution is deployed on-premises.

The setup phase of VMware SRM can be done within a day, and then the planning and all policies that need to be set up would take four to five days or even a week.

VMware SRM is expensive when compared to Veeam and makes Veeam look cheaper. For support, some additional payments need to be made over the licensing costs of the solution. Even with Veeam, additional payments must be made over the licensing costs.

VMware SRM is a handy solution since it does what it is told to do by its user while staying stable.

I rate the overall product an eight out of ten.

We use SRM for our failover strategy. It is for disaster recovery on failover.

Our systems fail over using SRM. So, we do a big bang DR, which is biannual, and we fail over our fairly massive Epic electronic health record (EHR) and our core applications. It takes us about 30 minutes to fail over using SRM, which is pretty good. In most hospitals that have Epic installed, Epic does the audit to make sure that we can fail over if something were to happen. Normally, sites will have a DR solution specific to the EHR, but right now, our pain point is the third-party tier-one clinical applications.

We've had configuration issues on occasion. We start to fail over, and then we have to call it off because the configuration is not right, or the data stores aren't configured correctly in the secondary data center. Oftentimes, it is just the experience level of the team, and we have to bring in the vendor to help and validate our configuration.

I have been using this solution for probably five years.

Their support is excellent.

I would rate it an eight out of 10. There is some complexity there, and that's where I would bring it down from a 10.