VMware Live Recovery Reviews

We typically use it for disaster recovery testing. It automates the process of failing over from a protected site to a recovery site, helping us achieve our RTO (Recovery Time Objective).

It has simplified data center application and failover processes, but the underlying technologies can be challenging. 

If we're using replication appliances, configuring them to work with SRM can be complex. Additionally, bandwidth and VM size can impact performance.

I would rate the ease of setting up and configuring my recovery plan in VMware SRM, a ten out of ten, with ten being the easiest.

The "Test Failover" feature is valuable. It lets us run a test and see if recovery reaches the RTO. It also shows us any issues with our VMs. 

It prompts us to perform a test failover by failing over a vm or a group of vms. Once the failover is complete, it verifies if the recovery reaches its initial stage.  We can also manually trigger the failover by the click of a button.

We also used the non-disruptive testing feature but only on a few test machines to confirm functionality. It works well.

There is room for improvement in the replication interface and functionality. Every time you open a remote site, you need to sign in again.

Ideally, single sign-on after integrating with vCenter should provide secure credentials that avoid re-entering passwords for every remote site access. It takes time every single time.

It has a ton of features, but ease of use could be improved. It gets better with automatic configuration over time, adapting to access. If you bring in a storage test application, maybe an automatic plug-in to the adapter, say for HPE or other storage providers, would be helpful. We wouldn't have to go to the provider's sites to download them.

The product itself is smooth, but timing issues arise due to replication lags in multiple areas.  When this happens, we encounter errors. In our most recent environment, we left the virtual machines running at the recovery site, hoping to avoid redeployment.

In this organization, we have been using it for about five years. I've been working with it for more than that overall, maybe eight years.

I would rate the stability an eight out of ten. 

The usage is restricted to a maximum of three users. They are administrators. It does not need much scaling because one server can manage a certain number of hosts. It really depends on the underlying replication infrastructure.

Overall, I would rate the stability an eight out of ten. 

The escalation matrix seems to depend on who gets the tickets. There are many articles due to AI, so the customer service and support want you to go through those first, even when you need immediate support. It also depends on your package. Weekend support is limited (Monday-Friday), which isn't ideal for disaster recovery. For disaster recovery, we want 24/7 support.

But once we get to an actual support person, it's good.

Neutral

I would rate my experience with the initial setup a nine out of ten, with ten being easy. 

The complexity of the initial setup depends on the deployment model and current infrastructure. 

On the new base, it will be difficult because we need to install it with existing replication in place. That requires knowing how to integrate the tool. On-premise or cloud integration is a bit easier. 

Deployment itself is minimal. Configuration takes longer, usually a day or two.  It may take more or less time, depending on the size of the environment. 

I would rate the pricing a six out of ten, with ten being expensive. VMware sells in bundles of 50 VMs, so if we want to expand with a smaller number, we have to buy the whole bundle.

Overall. I would rate the solution a nine out of ten because it helps our organization. 

Our company's clients use VMware SRM for disaster recovery. 

Each OEM has varying USPs or different architectures. Some competitor solutions offer faster backup processes than VMware SRM. A native hypervisor feature is found in certain other solutions, but VMware offers it through a separate license from VMware SRM. 

The infrastructure of the solution needs to be more software-based, and less dependent on hardware. 

I have been working with VMware SRM for ten years. 

The solution is satisfyingly stable and can be easily used or administered. 

There are a few SKUs with the solution and now it has been taken over by Broadcom. The basic license of the tool can be availed for 25 VMs and can be scaled up to 75 VMs. So, based on customer requirements, our organization suggests the SKUs for licensing VMware SRM. 

The tech support offers satisfying product support. In some instances, the support team takes more time than expected to understand the issue and run diagnostics. 

OEMs are also used to share their core support or shared support. If a customer buys licenses from HP or Dell for support, they get it from the hardware OEM, and then the issues get escalated to a VMware team.

In this support format, a customer might receive delayed responses, and the resolution time window can be longer than in another direct or pro support format. I would rate the tech support an eight out of ten. 

Positive

The solution offers an easy deployment process. A professional with experience in virtualization technology can setup the infrastructure and deploy VMware SRM within a few days. One or two professionals are enough for the setup and maintenance of VMware SRM. The solution is adopted by businesses on small, medium, and enterprise scales, as it's a critical application for them. 

The solution can be seamlessly integrated, but for some specific non-compatible hardware storage, some customizations need to be implemented. Popular third-party platforms like HP, Dell, and NetApp support the native features of VMware SRM for storage replication purposes. 

After Broadcom acquires the solution, numerous licensing changes are being implemented. VMware and Broadcom will educate partners and customers on the new licensing policies.

For instance, if a customer purchased the product two or two years ago and now has to procure a new license of VMware SRM, it may impact VMware's present and future business. I would rate the pricing a nine out of ten. After Broadcom acquired the solution, the licensing cost increased drastically, and other similar solutions are available at a competitive market price. 

Broadcom has to brainstorm on lucrative SKUs or offerings to onboard, especially startups or small-scale businesses. 

Our company's customers use VMware SRM for disaster recovery across varying sites. VMware SRM maintains a connection between two different sites, if one site goes down there remains another site in our company as a backup to manage the load of different production applications. VMware SRM is considered an automation tool that helps customers migrate or restart the virtual machines at the recovery site. 

The tool allows our company to customize disaster recovery plans according to business requirements. As per the precedence of virtual machines, the solution is restarted at the disaster recovery site. VMware SRM is a highly comprehensive tool, which is why customers often choose it. 

The non-disruptive testing feature is a mature technology in the solution which is also found in competitor tools in the market. The replication and failover capabilities are quite easy to set up and use. This feature has a straightforward configuration that doesn't require expertise. Any professional with knowledge of virtualization and replication technology will be able to effortlessly manage the workflows that need to be configured. 

At our company, when we replicate the virtual machine on a distant site, the data is expected to be consistent. If data consistency is not maintained, then problems arise irrespective of the replication technology, whether we use SAN to SAN or other types of data applications.

The data consistency of VMware SRM depends upon the environment and connectivity between the two sites. I would overall rate VMware SRM a ten out of ten. For VMware environments, VMware SRM is considered a necessary product to deploy. 

Before purchasing VMware SRM, I would advise others to build a disaster recovery plan with RPO and RTO involvement. When we recommend VMware SRM to the clients of our organization, they seem worried at first about the LTO and percentage of data loss in case of disaster. 

VMware SRM offers five to fifteen minutes of RTO, which can be concerning for customers on some occasions, especially if the customer belongs to BFSI, e-commerce, or any digital, commercial business category. 

In my company, we use VMware SRM for its disaster recovery capabilities. It is a tool for automating and orchestrating the disaster recovery of our company's IT environment.

The most valuable feature of the solution is that you can independently run the disaster recovery without disturbing the production instances. You can demonstrate that your disaster recovery is foolproof without encountering any disaster in your IT environment. You can demonstrate to your company's leadership team that business continuity is available for all applications. Even in a disaster scenario, one would be able to recover their environment in a certain period of time.

Currently, the recovery manager is primarily for only VMware environments or virtual machines running on VMware. Suppose the recovery manager can be extended to a non-VMware environment. In that case, we can integrate all of the tools in an IT environment together and function using one single recovery manager. Allowing for integrations with non-VMware products and environments will really help.

I have been using VMware SRM for more than ten years.

It is a pretty stable solution.

Scalability will not be applicable to VMware SRM since it is a product that does disaster recovery. Its scalability can be considered because you can add additional nodes to the product if you want to scale while ensuring you have the required licenses.

We use the solution for more than 100 customers.

The initial setup of VMware SRM isn't straightforward because many customizations are required since it helps in the recovery of your IT environment. It is not the tool but the process that is complex. The tasks associated with using the tool in an environment for disaster recovery are complex.

The product's deployment process takes around three to four weeks to complete.

For the deployment process, you need to assess your environment before getting into the design phase, after which you need to understand the business objectives and goals clearly to design your target environment. Once your environment is ready, then you need to understand the steps you need to follow to configure VMware SRM to achieve your target state. I would say assessment followed by defining a clear business objective, and then after design, you have to build the environment.

There is a need for an architect to take care of the design part of the solution, along with a couple of engineers and a dedicated project manager to run the product during the deployment phase. There is a need for at least two engineers to run the product.

The licensing costs for the product are perpetual in nature. A person needs to buy the license only once there is a need to buy support on a yearly basis. The licensing cost for VMware SRM is expensive.

I recommend those wanting to use the solution completely understand their own environment since VMware SRM is meant for VMware environment only. You cannot integrate VMware SRM with other non-VMware products. If your requirements are very much restricted to VMware alone, then VMware SRM can be a good choice for managing activities related to disaster recovery. If you have a mixed environment, you need to think and look for other products in the market other than VMware SRM.

I rate the overall solution an eight out of ten.

VMware SRM is deployed with some clusters. However, if the customer uses a three-tier architecture or other configurations, SRM might not be applicable. The expectation is not always to achieve 100% coverage. SRM is used for virtual machines with stringent SLAs or critical business applications. SRM is often sold in packs of 25 virtual machines, and deployment and functionality testing are conducted based on customer needs.

The simplicity of VMware SRM is one of its most important features. SRM console is straightforward to manage. It offers simplicity in monitoring, managing, and deploying, making it a unique value proposition. Additionally, Nutanix solutions also provide a simple GUI, which helps in operational efficiency.

The solution's recovery processes are very simple but not intelligent because one can easily monitor the replication progress and how the application is going. There is a workflow defined for doing their testing.

I have been using VMware SRM as a partner for ten years.

VMware SRM is a scalable solution due to its ease of documenting virtual machines. The process is straightforward if a customer already utilises 25 virtual machine licenses and requires more. They can execute the addition of the following 25 licenses. Then, they can enable those licenses and add the corresponding virtual machines to their application jobs.

It depends. We have customers using both twenty-five virtual machines and those with more than one hundred virtual machines. Therefore, the usage of VMware SRM varies from customer to customer, resulting in a mix-and-match environment.

The initial setup is very straightforward, depending on the kind and number of virtual machines.

A customer is expecting 25 virtual machines to deploy from the SDR. So, it should not take more than two days of work. If fine-tuning is required, it may take additional time, depending on the bandwidth. It's dependent on the infrastructure and varies case by case based on the bandwidth capability. Data will replicate faster with higher bandwidth, whereas lower bandwidth will result in longer replication times. Depending on the scenario, with good bandwidth, it could be a matter of only 24 hours.

Furthermore, the primary site's data size and change rate also play significant roles. If there are frequent changes at the primary site, it will naturally take more time. Additionally, the size of the primary data is another crucial aspect to consider.

The challenge is the licensing has changed from physical software to core-based, from perpetual to subscription-based.

The pricing for VMware SRM can vary significantly based on factors such as the customer segment, brand, and specific requirements.

The solution is straightforward to deploy and easy since it provides all the SRM functionality, such as security manager, with a seamless experience. 

We need to simulate for DLP . We need to freeze the application and do audio testing, and if there is an update on our data site, we need to provide feedback.

Specific solutions are pure-play SRM solutions. This solution acts as a recovery manager because the providers understand the workflow, prepare it, and know the dependencies. For instance, they understand the dependencies between virtual machines and applications, databases, ADA DNS, CSV, etc., and document them in the workflow. This documentation ensures the workflow can be executed properly, leading to a minimal Recovery Time Objective. ADR minimize RTO through automation, improving the workflow within SRM and eliminating the need for third-party solutions for security and other aspects.

Once we receive an order, we initiate thorough planning and documentation. We prepare a comprehensive flow-level design and engage with the customers for confirmation. With a clear understanding of the entire expectation cycle, my team can effectively deploy the solution, ensuring seamless integration.

Maintaining VMware SRM involves setting it up correctly and regularly monitoring it for infrastructure changes. Once appropriately configured and monitored, it operates smoothly unless there are changes at the customer site, such as patch deployments or alterations to authentication or access rights. These changes can potentially lead to application failures. Therefore, ongoing vigilance is necessary to ensure the seamless operation of the solution. Bandwidth issues can also affect performance, so addressing such concerns is essential.

I strongly recommend confirming with the new Broadcom team whether their VMware SRM licensing has changed since the acquisition of Broadcom. They've consolidated their SKUs from over a hundred to ten if there have been significant changes in SRM licensing, features, or functionality.

VMware SRM offers simplicity in disaster recovery solutions. However, it's primarily optimized for VMware environments. If a customer prefers a non-VMware-focused solution at their data centre, SRM may face challenges. Converting virtual machines in such cases can be complex and cumbersome. 

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

I have mostly worked with VMware SRM, which is a solution tightly integrated with the product.

The most valuable feature of VMware SRM is its integration with the VMware platform.

VMware SRM's platform agnostics should support on-cloud usage as well. VMware SRM has to add a couple of features related to the cloud.

I have been using VMware SRM for five to six years.

VMware SRM is currently a very stable solution, but we came across many issues three to four years back.

I rate VMware SRM a nine out of ten for stability.

VMware SRM is a scalable solution. Our clients are generally enterprise businesses.

I rate VMware SRM an eight out of ten for scalability.

VMware SRM's technical support is very good.

Positive

We also used to have Datto and Carbonite for DR.

I rate VMware SRM an eight out of ten for the ease of its initial setup.

The solution's deployment took a few days.

VMware SRM is a little bit pricey. On a scale of one to ten, where one is cheap, and ten is expensive, I rate VMware SRM's pricing a seven out of ten.

Overall, I rate VMware SRM a seven out of ten.

In my area of expertise, which is resiliency, I primarily use VMware SRM for disaster recovery use cases. I also use it for backup and data loss prevention use cases, making it easier to manage and safeguard critical data within virtualized environments.

VMware SRM has improved our organization's value by consistently meeting our clients' time requirements when deploying solutions. When we implement SRM for our clients, it helps ensure that their disaster recovery and data protection needs are addressed within their expected timeframes. 

In terms of resiliency, the most valuable aspect of SRM has been its effectiveness.

There is room for improvement in the automation and orchestration aspects of this solution.

I have been using VMware SRM for ten years.

I would rate the stability of the solution as a seven out of ten. Like any software, we do encounter glitches and the need for patches and fixes from time to time, which is a normal part of maintenance. However, there is room for improvement in terms of patching processes, including reducing delays and addressing issues in applying patches. Additionally, better documentation would enhance the overall experience with the solution.

I would rate the scalability of VMware SRM as a six out of ten. Scalability challenges occur occasionally, especially during migrations from on-premises to the cloud, as it is often a gradual process over several months. Creating a financial model that aligns with this scalability can be quite challenging. Within our organization, which has a worldwide presence, approximately 90,000 people use this solution. However, in specific areas like the delivery organization and operations, the user count is in the hundreds.

I would rate the technical support as an eight out of ten.

Positive

I would rate the easiness of the initial setup as a seven out of ten. In our company, VMware SRM is deployed both on-premises and on the cloud. It took about two months to deploy it and it was done in-house. The number of staff required for deployment typically ranges from two to six people, depending on the size of the project. Maintenance for this solution is typically provided by the developers or vendors. We have maintenance agreements with various providers like VMware, Rubrik, Veeam, and Commvault, and hardware maintenance is handled by the hardware provider through our maintenance contracts.

I would give it an eight out of ten in terms of costliness.

Overall, I would rate VMware SRM as a seven 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.

Our initial deployment of VMware's Site Recovery Manager in conjunction with PostgreSQL for automotive sales, and also involved integrating SRM with HP's triple storage systems. It leverages background storage replication to ensure stable and reliable business continuity.

Stability and ease of installation, along with straightforward maintenance through the graphical user interface, make this solution a practical choice. It eliminates the need for complex compliance requirements, making it a highly effective solution.

The primary site lacks adequate equipment, such as power backup and cooling, which can lead to downtime during issues like power outages or overheating.

We have been working with it for six years now.

It is a highly reliable solution.

It's important to note that the scalability of the solution should align with the customer's needs. If they anticipate increased workloads and data, they can easily scale up their storage systems. Site Recovery Manager simplifies this process, as it doesn't necessitate extensive reconfiguration, instead, it involves adding or extending data links in the replication groups, making it a straightforward and manageable process. It is well-suited for mid-sized and small companies that don't have extensive data replication needs. It's a practical choice for businesses in need of a reliable and scalable disaster recovery solution that matches their specific requirements.

VMware offers excellent support for its products, and we haven't encountered any noteworthy issues or negative experiences in our interactions with their support team.

Positive

In addition to our existing setup, we use backup software, Veeam, for replication on the disaster recovery side. With Veeam, we replicate virtual machines from the primary site to the secondary site. It is particularly advantageous because it doesn't require the same storage type on both the primary and secondary sides, which gives us flexibility and allows us to mix and match storage types if needed. One of the key benefits of Veeam is its ease of management, making it a valuable resource for replication. I believe it has a promising future, especially for handling data replication in various sectors. We also employ Veeam in the banking system to replicate data from different strategies across multiple departments. Its performance in replicating virtual machines is superior to SRM. The choice between SRM and Veeam largely depends on your storage environment and replication needs.

The initial setup was easy and straightforward.

The implementation process typically involves setting up VMware, configuring virtual machines, creating storage blocks, and installing the necessary components. For VMware to work seamlessly with the storage, a connector from the storage vendor is installed within the VMware environment, and once this is in place, replication can begin. In cases where there's a substantial amount of data to replicate, and the customer lacks a robust network link between sites, a physical transfer of data is undertaken. This involves physically moving storage devices from the primary site to the DR site, initiating the replication process, and then returning the storage to its original location once replication is completed. The replication process usually takes around two weeks, which is considered suitable for customers with relatively uncomplicated needs. For smaller customers with ten machines or so, replication is organized into groups based on different data sources on the storage system. Implementation requires the involvement of one or two technical experts who are well-versed in the equipment and storage systems. Monitoring the system is primarily the responsibility of the customer, with one or two IT personnel overseeing the process. Email notifications are often set up to keep track of system performance and any issues that may arise.

It is reasonably priced, and its cost hasn't been a significant factor in our implementation. We utilize various licensing options, but we typically purchase licenses upfront, avoiding monthly or yearly payment structures. We often opt for multi-year agreements, and if technical support isn't required, it allows us to maintain the same number of virtual machines and central traffic capacity.

If you're dealing with a more stable and homogeneous storage environment and have technical reasons to favor SAN, then SRM, which is tightly integrated with the storage vendor, may have some advantages. Veeam is a better solution when you have a mix of heterogeneous storage types, multiple sites, and diverse data replication requirements, as it operates independently of the storage application. For larger customers, such as those in the banking sector with diverse storage systems and extensive data replication needs, Veeam might be preferred. While it might have a slightly higher price point compared to SRM, it offers more flexibility and scalability. SRM, on the other hand, is well-suited for smaller customers with simpler storage environments and a smaller number of servers. It's more straightforward to configure and manage in such scenarios. Overall, I would rate VMware SRM ten out of ten.