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

The disaster recovery has been good. 

In the case of a disaster, the product is very simple. We have security and lower downtime. 

It's very reliable. The solution is stable. 

Its design is good and it does what it is intended to do. 

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.

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

VMware SRM is very effective between two sites with identical twin storage, you can have synchronization between the two sites. 

As highlighted, the most valuable feature of VMware SRM is production replication. It efficiently manages notifications and ensures accessibility within the VMware environment itself. It is advantageous compared to other products, such as Veeam, Commvault, or backup solutions, which may involve additional costs.

VMware SRM's most valuable features are its convenience and its use of stretched clusters.

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.

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 thing I like the most about SMR is the reduced cost of management.

The most valuable feature of the solution is the automatic recovery of the virtual machine if it goes down. In the event the VM goes down, we can either power it up automatically or manually depending on how we have the solution configured. When configured to power up automatically, the copy in the VM will power up.

We find the back up feature of this solution to be particularly valuable.

There's an option where you can test VM, when you can test the drill. That option was very valuable.

It's easy to set up. 

The solution is scalable. 

It is stable. 

The most valuable feature of the solution is that it is a tool or software 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.

What I like about VMware is its capability to schedule, write and configure the recovery and scheduled steps, such that you don't have to come in and start manually trying to recover the entire machine. You just push a button to recover the VMware and everything is done.

The features I have found most valuable are the ability to script test failover and the ability to re-IP.

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 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.

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.

Virtual Machine Recovery during DR situation, with automation and easy to use menus and options.

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.

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

Integrated replication / recovery plan ease of use and creation.

Running Production out of DR site

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 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.

It is easy to implement for my clients. 

It's a very nice product.

The most important features that we're using are the replication of VMs as well as the integration with the EMC recovery platform. The replication solutions to replicate the LAN and data storage to the secondary external storage.

The solution is quite stable. We haven't had an issue with the performance.

The solution is very flexible. 

I would say SRM's ability to recover my virtual machines in a timely manner and to perform bi-annual testing are the two things it has provided that are really valuable.  

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

It is stable. 

The solution has the capability to scale well. 

The solution is simple to use and has effective automation.

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.

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.

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

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

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.

What I like the most about SRM is the delta sync. We typically approach a project from an architecture perspective and we do service grouping. For example, take a situation where we plan to do a migration. We decide to go with a setup where there is a front-end portal server, there are duplication servers and there is one back-end database server. This means there are four separate VMs each representing one particular service. To get the services across, we have to wait until we have the full image replication complete. By the time we kick it off, the replication has already begun to trickle in. You can parameterize a little bit. When you really want to do the migration — probably during a service outage on the weekends as it is for production — the majority of the data is already migrated to the other side. That helps a lot because you do not need to have a tremendous service outage with this model compared to doing it in a more traditional way.  

Of course, VMware SRM not the only solution that is capable of doing this anymore. But if you have a heterogeneous environment — environments are not equal on both sides — this solution can be an advantage. In our situation, we had completely different technical specs and technology foundations at the source and target. In this case, the product is really is an enabler on the condition that you have the same hypervisor on the other side.  

Centralized recovery plans for thousands of VMs, Non-disruptive recovery testing, Automated DR workflows.

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 most valuable feature is the automation, where you press a button and everything fails over seamlessly. It is quite good.

• vSphere Replication does not take snapshots, although it will keep your snapshots. Site Recovery Manager with SAN Replication does not take snapshots of the VMs, but will take snapshots on the LUNs via the SRA to the storage provider.
• When you perform a failover, the LUNs can be chosen to sync or not, so you do have that option. With vSphere replication, it is the same concept, while it is live. The standalone VR will allow you to choose either.

SRM's best feature is automation.

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.

The most valuable features are the disaster recovery and testing.

Some of its valuable features are that it's easy to use and the interface is quite simple as well. It's really a reliable and a good product.

The most valuable feature is the integration with our Nutanix environment. If it didn't have this ability then we may not be using it.

• Array-based integration is the most valuable feature.
• It has a user-friendly dashboard and will use the same vCenter console.

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

The product is stable.

The deployment process is fast.

Site Recovery Manager is valuable because it helps with the difficult problem of failing a group of virtual machines over to your DR site and bringing them up. Because there's things that must be changed in a machine in order to bring it up somewhere else like maybe its IP address or, you know, any slew of other things, the port groups or whatever it needs to be connected in, and you can either manually do all that by hand or you can program your recovery plan in Site Recovery Manager and it's pretty much, you know, menu driven because it's common things that you would have to do to a server in order to bring it up somewhere else, and you can go in there and you can actually have it prompt you to say oh, by the way, you need to turn on the database server before you turn on the next server. And it pauses and waits there so you can go over here and turn on your database server and then you click dismiss and it goes to the next step. Which you wrote all these steps into the Site Recovery Manager so that's what it does. Really helps execute a playbook for you to be able to help bring up your disaster recovery site.

• Ease of management.
• Testing failover capabilities.

The recovery plans and customization options. I also the love the re-protect feature for easier fallback.

The automatic activation of the storage volumes and bringing up all VM’s. The recovery plans and resource mapping are good features.

With the resource mapping we can use different networks to bring up our VM’s

VMware SRM is a very nice tool for disaster recovery for virtual environments.

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. 

It’s expensive, and we also use Zerto, but good for disaster recovery testing.

Cost

Ability to support DR.

• Fast recovery time
• Ease of use

Test run in protected environment

Disaster recovery of a failed site.

Instant VMware integration and a wide integration with storage vendors.

Key feature for me is the ability to test recovery plans with zero impact to the production running environment, this is key for 'what-if’ type analysis and to provide confidence that the platform can be recovered with minimal intervention.

The most valuable feature is disaster recovery testing.

The reports are very good.

There is zero RPO and zero RTO when combined with the EMC solution called RecoverPoint.

The most valuable feature of the solution is the integration part, along with the subsequent hardware.

The solution helps to improve business continuity processes. Its automatic failover and failback policies have been wonderful.