VMware Live Recovery Reviews

We use the solution primarily for off-site disaster recovery. A site act as the headquarters, and there is also DR site. This means that we move application data from primary to secondary sites for storage level replication purposes. We also back up our virtual machines and their applications to the DR site. Essentially, we do disaster recovery from the primary site to the DR sites.

Before using VMware Cloud Disaster Recovery, we were running on a batch storage solution backup, which was conducted by one of my team members. However, prior to carrying out the copying, he backed up the application to local storage before copying it to the tape drive. This means that the storage controller must be up before copying was made to the tape drive, which clearly precluded the possibility of us restoring the backup. There was nothing we could do when this happened. Now, subsequent to the installation and implementation of the VMware Cloud Solution, there is no need for us to rely solely on a single storage controller. This makes things easy for us once the storage level application replicates our data to the DR site. This means that even if the entire primary site goes down, we can still fall back on the data and the application that is available on the DR site. This allows us to consistently maintain the state of our application and business data.

We feel the ability to move virtual machines while they are still running to be the most valuable feature. Consequently, the application can be migrated from one host to another in respects of virtual machines without the user taking notice.

The automation should be simplified or improved. Usually throughout the day, during peak periods, one or another task cannot be carried out. Moreover, if one wishes to move large data, the user's application response may be affected. So, it would be best if such tasks can be automated to allow such tasks to be undertaken not during peak periods. As a consequence, this would lessen the impact to the underlying resources. 

I would also like to see interoperability between various virtualization and cloud solutions. It would be nice to be able to move my VM from Windows or Hyper-V to VMware and from this to Citrix. The adding of these features would be awesome.

I have been using VMware Cloud Disaster Recovery since 2012. 

The solution is very stable. We have hardly had any issues with it. VMware is perfectly stable, except there is a problem with the underlying hardware infrastructure. 

The solution is very scalable. While using it we upgraded from 5.0 to 5.5, from this to 6.0, and from 6.0 to 6.7. As part of this process we also upgrade the underlying hardware. We are able to migrate our data with ease.

I found the support to be excellent. I am in Nigeria and, at the time, so we got the procurement through HPE Nigeria.
We benefit from VR support with HP, in addition to our support license which, too, is covered.

Before going with VMware Cloud Disaster Recovery we used Windows Backup, solely for backing up the page. 

I found the initial setup to be okay. It doesn't require much to accomplish, as it is not very complex. Its installation and commencement are very easy.

The solution took less than a month, perhaps no more than two weeks, for us to deploy.

Yes, the solution was implemented through a vendor. Their customer support and service were excellent.

I feel the solution has given us a very good return on investment since having implemented it in 2012. At the time, I believe we implemented the 5.0 or 5.5. The solution has supported our business over the years and generated tens of millions of dollars in revenues. 

I would say VMware Cloud Disaster Recovery is very expensive in comparison with other available virtualization solutions.

We did evaluate other solutions before settling on VMware Cloud Disaster Recovery. We are talking about a global company that has a presence in Nigeria and other countries, where the clients were already implementing such solutions in the business units of these countries. As a consequence, we simply adopted the use of VMware Cloud Disaster Recovery. At the time we did contemplate alternatives.

The solution is mostly on-premises and private cloud.

There are as many as 100 users in our organization that are using the applications running on VMware.

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

The advice I would give to others who are considering implementing the solution is that they should do proper planning and make sure their needs are met. Someone who does not have the benefit of experts or support personnel may consider engaging an experienced consultant. This would minimize mistakes. 

I use the solution for disaster recovery.

The solution is consistent. It is an automated DR solution. It has test features. We can test DR in advance. We are using the tool for disaster recovery. The product has improved automation. The automation of failover and failback has improved our operational efficiency significantly. It is quite easy to integrate the solution with other VMware products.

The solution must provide better integration with third-party vendors.

I have been using the solution for two years.

I rate the tool’s stability an eight out of ten.

I rate the tool’s scalability a seven out of ten. We have 10 to 20 users in our organization. We use the solution twice a month.

I rate the ease of setup a seven out of ten. The deployment takes a few months.

We deployed the product with a few in-house team members. The tool requires continuous maintenance. We need two or three people to maintain it.

I will recommend the solution to others. It is a nice product. Overall, I rate the tool an eight out of ten.

We use VMware SRM for disaster recovery.

VMware SRM replicates the VM from one site to another, and it helps us orchestrate the powering of VMs and DR when the DC goes down.

Currently, there is a limitation of consolidating only 15 sites per SRM.

Ransomware recovery or early detection could be incorporated into VMware SRM.

I have been using VMware SRM for three years.

VMware SRM is a stable solution.

VMware SRM is a scalable solution. I work with mostly small and medium businesses.

VMware SRM’s technical support is good.

Positive

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.

VMware SRM's initial setup is easy.

Two people can install VMware SRM in two to three hours.

We pay a yearly licensing fee for VMware SRM, which is not very expensive.

The fee is for the solution's license plus support. There are two options. One is subscription-based, which would be for a one or two years term base, and the other one is perpetual with support.

Just one person is enough to maintain the solution.

I highly recommend VMware SRM to other users.

Overall, I rate VMware SRM 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 use the product to implement discovery for server and database solutions.

The software is user-friendly. It has a good and effective user interface.

The product's stability could be better.

We have been using VMware SRM for eight years.

I rate the product's stability an eight out of ten. Sometimes, we need to restart the system as it stops working. It needs improvement.

We have 400 VMware SRM users in our organization. I rate its scalability a ten out of ten.

The technical support services are good.

The initial setup is straightforward. We need to download the application file and deploy it in vCentre Server. Later, we need to register a static manager to create a bridge between two environments. After that, we check if the static environment is configured with the data centers.

The software is expensive. There is a one-time cost involved in purchasing the license.

I recommend VMware SRM to others and rate it a ten out of ten. I advise other users to always install the latest version.

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 SRM to replicate our important servers to our VR site. We are customers of VMware and I'm a junior manager. 

The replication part of SRM is really good. We once had our production site collapse completely and we were able to recover all the data. The restore level of the application is very good. 

The solution is on the expensive side. 

I've been using this solution for four years. 

We've found the solution to be stable. 

The solution is scalable. 

We used the documentation for our initial setup and had some difficulties. The deployment was carried out in-house and took a day or two. We had some help from colleagues in other companies and had a couple of people from our company involved in the deployment. 

We initially took out a five-year contract and recently extended it for another 12 months. It's quite an expensive solution. 

I think this is a good tool that's easy to manage and worth the cost, so I rate it nine out of 10. 

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.