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

In this scenario of disaster recovery, we start simply with our VMs. We have just two packs of 25 VMs. We just protect just about 15 VMs.

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

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.

We are using this solution to serve our customers in different sectors.

We are using VMware SRM as a disaster recovery solution for our customers. We are working with vSphere, vSAN, and other infrastructure VMware solutions. VMware SRM is completing the solution.

I mainly use VMware SRM for automation, creation of VMs, and monitoring.

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.

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.

We use SRM to invoke DR and to move workloads across the DR side.

The primary use case is for disaster recovery. We use the solution for two different sites, as well as our virtual machine backup. In a situation where one of our data centers goes down, our servers can go up on the other site.

We use this solution to run our applications and our server functions.

It was working very well with VMware since it's a VMware product. We didn't have any issues. It was quite smooth when doing drills, when we were trying to recover VMs from other sites.

I use the tool in my company for business planning, not disaster recovery.

We use VMware SRM for disaster recovery.

Our primary use is for our client. It's a system integrator frame. I have clients for whom we manage their data centers. Or, we do their integration and implementation. Basically, we use it to replicate their virtual machines, their user site, and their company site, and maybe to configure it and schedule their recovery. We use it for doing recovery tests from time to time, quarterly or yearly, for some of our clients. To test for a situation whereby a danger or a disaster could be affecting their data that is being replicated. This is good to do. Periodically, we run those tests and recover those virtual machines, and they try to work from their recovery sites to ascertain that everything is okay.

Our primary use case for VMware SRM is automatization.

We use SRM to replicate our important servers to our VR site. We are customers of VMware and I'm a junior manager. 

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

I use the solution for disaster recovery.

We use the solution for DR.

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

We are consultants in disaster recovery software. We implement VMware products for our clients.

We have implemented SRM to replicate around the 800 virtual machines to the data recovery files. Due to the fact that we implemented to data centers as well as the primary and secondary data center, we use SRM to replicate around most of the virtual machines in order to be the secondary site.

VMware SRM is used for our disaster recovery site, which is an on-premises colo (Colocation) facility. The general use case is for disaster recovery for three of our applications those being imaging, payroll, and real estate.  

We primarily use the solution for migrating our DR site.

I use VMware SRM for DR testing and VR.

We primarily use the solution for disaster recovery.

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

We use the product to implement discovery for server and database solutions.

We use it for disaster recovery.

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.

We are in technology and services but we also do enterprise architecture and strategic planning. We always work on the customer side, but we work very closely together with key partners and key vendors in the industry. This includes VMware, but other vendors as well. We realize solutions on the customer's behalf and we are also always solution-oriented and committed to delivering what the client needs. That is why we work intensively and closely with vendors like VMware.  

With VMware SRM, we had a technical account manager before coming on with them and level three support all on standby just in case we were to encounter issues. We just happened to encounter a lot of issues.  

We integrated the product at the same time partly because of discovery and partly because we want to stay vendor agnostic. We work with whatever the client has if it is a viable product. One might be using Hyper-V and another one might be using KVM (Kernel-based Virtual Machine) or Xen Project or AHV (Acropolis HyperVisor). We treat them equally to do what they need and also work with other parties, like Red Hat or Nutanix or whatever other solutions are necessary. Of course, we take our experiences from every client and every project with us on to the next opportunity.  

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.  

We are a solution provider and this is one of the products that we implement for our clients.

VMware is being used for disaster recovery to protect two sites.

Trying to analyze the feature and functionality of this combined product. SRM is current been used in the production. However, with new DR requirement, we are look for other solutions.

We are a solution provider and this is one of the products that we implement for our clients.

The primary use is for disaster recovery. The customer has a principal data center where they have their production site and they use this solution to replicate it to a secondary site. In the event of a disaster, they have a full backup, which is the best use that I have seen.

Our primary use case is for the end-users. I work as a VMware software engineer and we have about 50 people using the solution. 

This disaster recovery solution helps our clients with their mission-critical projects. They are able to maintain business continuity and increase the reliability of their services.

VMware failover is our primary use case of DC DR automation. We are integrated with array-based replication.

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.

VMware SRM is used for disaster recovery automation.

Our primary use case of this solution is for testing. 

We use this product primarily for our DR drills, which you can do quietly during office hours. Sometimes we use it for site migrations or planned outages.

We use it, I and several of my colleagues, as a data recovery solution between VMware environments. It is a complementary solution to EMC solutions, for storage.