How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
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.
Our primary use case of this solution is for testing.
We use SRM for our failover strategy. It is for disaster recovery on failover.
I use VMware SRM for DR testing and VR.
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 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.
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 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.
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 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.
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 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.
We primarily use the solution for disaster recovery.
VMware failover is our primary use case of DC DR automation. We are integrated with array-based replication.
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.
We all know it's really hard to get good pricing and cost information.
Please share what you can so you can help your peers.