We just raised a $30M Series A: Read our story

VMware SRM OverviewUNIXBusinessApplication

VMware SRM is #8 ranked solution in top Disaster Recovery Software. IT Central Station users give VMware SRM an average rating of 8 out of 10. VMware SRM is most commonly compared to Veeam Backup & Replication:VMware SRM vs Veeam Backup & Replication. The top industry researching this solution are professionals from a computer software company, accounting for 30% of all views.
What is VMware SRM?
VMware Site Recovery Manager is the industry-leading solution to enable application availability and mobility across sites in private cloud environments. Site Recovery Manager allows: Fast and reliable IT disaster recovery, simple and policy-based management, zero-downtime application mobility, and up to 50% lower TCO.

VMware SRM was previously known as VMware vCenter Site Recovery Manager.

VMware SRM Buyer's Guide

Download the VMware SRM Buyer's Guide including reviews and more. Updated: November 2021

VMware SRM Customers
Acorda Therapeutics, Columbia Sportswear, Mainfreight, Nippon Express, Sin Chew Media, Fisher & Paykel, Siam City Bank
VMware SRM Video

Pricing Advice

What users are saying about VMware SRM pricing:
  • "It is about $3,000 a year for the 25 pack. The package gives you the ability to protect up to 25 virtual machines."
  • "The cost of SRM is on par with market rates."
  • "The licensing costs are increasing."
  • "The price of this solution is on the expensive side."

VMware SRM Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
MB
Enterprise Architect at a consumer goods company with 11-50 employees
Real User
Top 20
Enables us to get a lot of server images successfully but it has connectivity issues with auto-recovery

Pros and Cons

  • "The product is evolving and the vendor is committed to change."
  • "There are many functionality problems with the product currently. It is also slow and unstable."

What is our primary use case?

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.  

What is most valuable?

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.  

What needs improvement?

I would say a lot could be changed to improve the product in terms of troubleshooting and supportability. I think about every two weeks, we had an incident somewhere in the software stack. There were problems that we faced with the vRA (vRealize Automation) multiple times. We had to fix the problem and redeploy it more than once to get it to work properly. Then we had to completely redo our replication. That is a big drawback because it means we had to cancel other plans that had already been scheduled.  

To summarize it briefly: users need a lot of enhancement to the quality and functionality of the software for it to be very useful.  

For support of VMware version 3, a more recent patch needs to be released. There were a few times that fixes were released but we have already upgraded to those latest levels and the known compatibility problems are not fixed.  

The replication advantage the product has does not work for all VMs. For example, if you have a large difference in change frequency within a VM and the VM is big — in one case our VM was 42 terabytes — the data just does not get across in the migration. So the product is really not able to handle either very big VMs or a very large change frequency. I remember we tried it with one Data Mart SQL database where we do continuous ETLs (Extract, Transform and Load). The data reloads on a daily basis. The replication takes too long to complete. The next afternoon after the migration started, we were more or less at 50%. By the evening, we were at 70%. We scratched the data reloaded and started all over again. We found no means to accelerate that. By the time you appear to be progressing, you have to redo the migration. So that is another disadvantage when trying to use SRM.  

There are a lot of minor things that need to be in place on both sides of the migration to make it work. If something goes wrong in the middle of the migration, you will have a tough time trying to troubleshoot it. The product has an insufficient method of logging, an insufficient level of operability, and an insufficient level of detailed technical tracing. This lack of information makes it so you can not immediately pinpoint the issues to troubleshoot them. It cost us multiple weekends of lost time while trying to troubleshoot because we do not get this information from the product.  

But the things I would like to see for sure in a new release are:  

  • Fix all minor connectivity issues with auto-recovery.  
  • Auto-diagnose, auto-identify, and auto-correct issues as they occur and at least try to fix the issues a few times before allowing it to fail. If the fix is not successful then at least inform users that the fix attempt was made and the particular area where the issue is suspected so that users do not lose hours to troubleshooting.  
  • Open up the solution to be more environmentally agnostic. It should not be so strongly integrated with vCenter. It should be loosely coupled with vCenter and allow other solutions.  
  • Make the product more robust and much faster. Many replications we have initiated took two weeks before going to the switchover. A lot happens in two weeks. It seems like an eternity when you have no idea why replications stalled over that long of a period of time.  

For how long have I used the solution?

I was using this between 2018 and 2019. I have been using it total for a year-and-a-half.  

What do I think about the stability of the solution?

The solution is not stable enough. If there are glitches in the process, it is not auto recovering from the issue. It is not even attempting to bring back a steady operational state. So stability is not sufficiently addressed.  

What do I think about the scalability of the solution?

The product promises to be scalable. You can add multiple vRA's — as many as you want per what you want to do. But then again, you are bound by physical constraints. For example, if you want to have multiple vRA's with multiple targets, that does not work. They have to all be directed towards one individual target. It could be multiple data stores, but it still has to be directed to the same target.  

In one case, we wanted to extend to an additional target, so we initiated two targets. Of course, the targets had two different configurations, two different data stores, and so on. That will not work. So that is where scalability ends.  

We had to do a complete reconfiguration with new targets. Then push everything over to a new target, then destroy it again, and bring it back to the first. We have done that on a few occasions, back and forth, and it is quite a cumbersome process. It should not be the case.  

Again this particular case was kind of an advanced setup. But we also have tried some multiple vRA's with just one target. But even there we have encountered synchronization issues because they need to keep in sync, and it may not happen.  

Internal software synchronization issues amongst the vRA's paralyze the replications. There are some bugs in this functionality as well. We tried to patch them up using fixes provided from the VMware lab. Eventually, we ended up on version 6.5.1. Later on, those patches disappeared, apparently because VMware understood the patches did not fix the problems — or maybe created more.  

Because of all these issues, we are no longer using the product for the moment. This is because of all the problems and the fact that there is an ongoing license cost as well. I think at the peak we had 10 users. These were admins and engineers. I was using the product as a solutions design architect. But right now I would never use it unless it is for disaster recovery or rehearsal or something like that.  

The advice that I would give to other people who are looking into implementing this solution is that every software product comes with flaws. Products can evolve very rapidly. I think in our case that it was quite a good learning experience. It was a good learning experience for VMware as well — as they acknowledged. They said they would work on improvements in the various areas I brought up to them, and I liked that they will be making the effort.  

But if considering this product, I would also look at other compelling products, like Zerto, for example, or other replication tools like the Sun virtual platform. You could look at the ease-of-use of Nutanix. Their process for replication is very different compared to what SRM offers. But the ease-of-use comes with constraints. You do not always have the choice to have equal foundations for both source and target. Then there are backup solutions like Rubrik and Veeam. There are certainly alternatives out there that are categorically different product types with other ways to accomplish similar things. But a lot of what is potentially a viable choice depends on the use case.  

My recommendation would be to prepare carefully. Mimic your own live environment in testing as close as possible to the existing architecture with the vendor. Let the vendor prove that they are value-added resellers. Make sure you have tested in a representative set up at their facilities and can achieve what you are trying to achieve before going on to attempt to deploy and use it in your own environment.  

I do not think SRM is fully ready yet for a hybrid context where the workload is working across multiple clouds and on-premises. It is an evolving product.  

How was the initial setup?

In a simple situation, the setup is a piece of cake. However, as soon as you start to work across various deployments based on various levels, the setup is much more cumbersome and much more complex. You need to deal with the interoperability issues like checking the vCenter on the left side and the vCenter on the right side, what is the ESX (Elastic Sky X) level, et cetera. You may need to downgrade your expectations accordingly, to make it still work.  

Also, if you have network routing in between two completely different, distinct environments, that can give you quite a lot of headaches as well. To give you an idea: in the initial setup of one migration, we could just not connect both VMs end-to-end. The site manager would not connect. The vRA's were connecting, but the site manager was not. It turned out to be a network routing issue. In actuality, the "issue" was not an issue. The routing was just was working like it should, following the default gateway. It just could never connect to the other site manager.  

At times you really need to go back down to the very basics yourself, and even then there may be no clarity about why it will not connect. It follows the route, the stage-gate goes through, and the connection does not happen.  

Then also the checkpoint restart is a problem. There is no checkpoint restart. What I mean by that is you can have eight VMs to migrate over a coming weekend and something goes wrong after the process is initiated, or somebody made a mistake in the service grouping. When you see this problem, you think you just need to remap, recalibrate, and then relaunch it. But there is no history track of what is already replicated. The service grouping does not reflect in that result. You need to start all over again. So there is no checkpoint for the restart. There is a checkpoint for an individual VM, but not for multiple VMs.  

As far as the time it takes to deploy, that will vary. We have had different levels of complexity in our deployments. We initially had a simple setup that was done in two days, but there were no different networks involved, no different vCenters, and also it was intra-cluster. When done like this it was very easy.  

It was a completely different story for the more complex setups. I think it took us about six weeks with a lot of effort. There was a lot of alignment, a lot of verification, a lot of troubleshooting, and a lot of diagnostics to get it working end-to-end on both sides. It was really too much time to take with that kind of project.  

What other advice do I have?

On a scale from one to ten where one is the worst and ten is the best, I would rate VMware SRM as about a five. I am not open to giving a positive recommendation as the product stands. It is a little generous to give it a five considering all the issues.  

This review focuses a lot on the weaknesses of the product. But we were actually able to use the solution to get quite a lot of server images successfully, especially if the servers were relatively small, like a parasitic thermal server or an ordinary file server. That type of project went fine. So, if your use case is entry-level, beginning, and maybe intermediate, I think you will be fine using the product. But even if you do not have a lot of complexity and you try to work with this in a really big enterprise and a multi-region, multi-datacenter environment, you will have a lot of challenges ahead for sure.  

We have used it as a migration tool in support of a big transformation. I would think twice before using it for continuity on a permanent basis. I might think three times before more enhancements to the product are made successfully to enhance the utility.  

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
ChukwuemekaOnyemelukwe
Infrastructure Administrator - Server, Storage & Virtualization at a tech services company with 51-200 employees
Real User
Top 20
Has the ability to schedule, write and configure the recovery and scheduled steps

Pros and Cons

  • "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."
  • "What I think can be improved is the data replication aspect."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

What I think can be improved is the data replication aspect. For example, I know of another repetition solution called RP for VM. I don't really know how to use it since I've never used it before, but I've read about it. I know its features and I've spoken to some IT practitioners who have experience with RP for VM, who work with Dell EMC, and they gave me the feeling that RP for VM is better than VMware replication technology. The argument is that RP for VM has the ability to get your application going even when there is a loss of connectivity. Whereas in VMware you have to have something like 50% connectivity for the configuration. So in that respect, RP for VM has that feature which makes it better than VMware solutions. I guess VMware should make sure they are on top of their virtualization and data replication solution, more than every other company.

Overall, I can't point to any other thing, apart from whatever feature makes some people think artificial DNE is better than the replication application and SRM. If they can just take care of that then I don't think there's anything else.

For how long have I used the solution?

I have been using VMware SRM for close to 6 years now.

What do I think about the stability of the solution?

I would say that it's stable. I think everything depends on how you design and manage your environment. For example, when it comes to data replication on the disaster recovery side, part of the challenge that most of our clients have is the link between the production site and the APR site. Sometimes the link will be having challenges and data replication won't work for a few minutes, or something like that. But I don't really think it's an issue with the VMware solution. So, I don't really have challenges with it. If you properly take care of your environment the virtual machines will not have issues. In your scenario, maybe you didn't configure your cluster very well, or your GRS is not working properly, or some virtual machines are not giving results - then most likely you are going to have challenges.

What do I think about the scalability of the solution?

I have not scaled it before so I am not able to give feedback on that.

The environments we have deployed it on are enterprise environments, like the fashion wear industry, dotcom companies, and some other companies also.

How are customer service and technical support?

The only time we've contacted VMware support was in a case where we had some virtual machines mistakenly deleted and they needed someone who was very experienced in VMware virtualization, someone who understood working from the command line in the process. They needed to do some troubleshooting from the command line. I was very new to VMware virtualization solutions at that point, so I had to contact support. But anyway, that was a long time ago, about 4 -5 years back, and I have not been in contact with them at support.

How was the initial setup?

The initial setup is not that difficult. I would not say it's difficult because you just experience it when deploying some VMware solutions, especially a replication plan. The first time it's not always easy. But once you get the hang of it and get it right the first time, then you don't really have issues. Such as, do you need to go there and provide a key? I wouldn't say it's that difficult - it's not so straightforward but it's not that difficult. It's not complex for me.

I've done the deployment for different clients. So I would say the first time was not easy. But, for me to do it right now wouldn't take time.

What other advice do I have?

My advice to people considering this solution is that they should just go ahead and get it. I think that is the best virtualization solution out there. Some people say Nutanix is better. I think VMware is the best. 

I would also advise making sure your virtual environment is well taken care of. I don't think there are any other challenges that you're going to have. It's necessary that when you see it side by side, to have an operations manager help you find problematic areas and possible issues you are going to encounter in the future.

On a scale of 1 - 10, I give it a 9.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Learn what your peers think about VMware SRM. Get advice and tips from experienced pros sharing their opinions. Updated: November 2021.
553,954 professionals have used our research since 2012.
OmidKoushki
Solution Architect at KIAN company
Real User
Top 5Leaderboard
Good replication and integration capabilities with a straightforward setup

Pros and Cons

  • "The solution is very flexible."
  • "The biggest issue for us is that this product does not have any demo for customers."

What is our primary use case?

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.

How has it helped my organization?

If you can plan and create a recovery plan correctly, it will do and replicate virtual machines and when a disaster occurs, you can easily replicate off the secondary site. If you create a proper primary recovery plan, you have good protection.

What is most valuable?

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. 

What needs improvement?

VMware introduced the two next versions of the solution. They are SRM 6.5 and 6.7. I don't have any experience with these two products. However, if I was to talk about version 6, which we are using, at that time we faced a problem specifically when we create recovery plans. After the creation of the recovery plan, sometimes an issue happened in the GUI, in the Center. I'm not sure if that has since been resolved.

We've faced issues with the licensing. If you don't choose a specific license, you can only cover around five or ten virtual machines.

The biggest issue for us is that this product does not have any demo for customers. They should offer demos so that clients can try it out before they commit to buying a license.

For how long have I used the solution?

At this point, I have been using the solution for about two or three years.

What do I think about the stability of the solution?

The stability of the solution is very good. There aren't bugs or glitches. It doesn't crash or freeze. It is reliable.

What do I think about the scalability of the solution?

In terms of scalability, you can integrate the POC and you can distribute SRM on three sites. At our project, we use VPLEX architecture to distribute storage between two data centers and therefore we could publish an important file related to SRM virtual machines and the active LANs, which is distributed between two data centers. In terms of scalability and holding of data storage, we can put a doc online whenever we need to.

Our team has around six members for virtual support and maintenance of the VMware infrastructure. In terms of the customers that are related to using the VMware services, there are around 800 people.

How are customer service and technical support?

Due to the sanctions in my country, in Iran, we can not use direct support from VMware and there is not a partner in my country. Therefore, we need to study, we need to design, we need to support everything directly and focus on providing maintenance service to our customers ourselves.

How was the initial setup?

The initial setup is very straightforward. It's not too complex. 

Deployments can typically take two months.

In the first month, I dedicate focus on learning and conducting POC sessions. For around two or three weeks, I also spend some time implementing SRM at the site.

What about the implementation team?

I am responsible directly for installations.

I work with a specific team that includes three members. I'm responsible as a team lead and VMware engineer. I have two other team members, one member has a specific focus on its storage concept and another is working on the networking.

What's my experience with pricing, setup cost, and licensing?

We are always looking for solutions that are more affordable. SRM is more expensive than, for example, VirtualBox.

Which other solutions did I evaluate?

I have looked into Zerto. I attended a seminar two years ago. If we ever moved off of this solution, we may switch to that. It is quite affordable and is very hands-on. It may even be easier in terms of deployment. They are very similar solutions overall.

What other advice do I have?

We are using two product versions. We are using product versions 6.0 and 6.5.

We need to use only on-premises deployment models. This due to the fact that there are sanctions in my country. We cannot use the cloud services directly as there is no support.

For customers who are using VMware infrastructure, I recommend using VMware SRM due to the fact that it has the ability to integrate with other products like HP, SRA, or even CSRA. It has good features that integrate well with a storage concept.

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

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
RA
Operations Engineer at a government with 5,001-10,000 employees
Real User
Top 5Leaderboard
Disaster recovery that works quickly, is stable, and has excellent technical support

Pros and Cons

  • "The installation and initial setup are straightforward."
  • "VMware's tech support gets a nine-out-of-ten. They are responsive and get you a useful reply."
  • "The stability of SRM has been excellent. It gets a nine-out-of-ten."
  • "The version we are currently using is not the latest and greatest but it has buggy behavior in some browsers."

What is our primary use case?

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.  

What is most valuable?

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.  

What needs improvement?

I would say VMware has room for improvement with this product. I am sure it is probably better in their 7.0 version, but there are still some bugs in the 6.O version that relates to using it with different browsers. I think a lot of what I run into is related to the 6.0 version. I believe a lot of those bugs have been fixed in the UI once you upgrade to 7.0.  

For how long have I used the solution?

We have been using the VMware SRM solution for about six years.  

What do I think about the stability of the solution?

The stability of SRM has been excellent. I would give it a nine-out-of-ten. It is a pretty solid solution.  

What do I think about the scalability of the solution?

I believe it would probably scale just fine. I only protect 25 VMs based on our licensing and I do it that way even though I actually have about 200 virtual servers. I can not really say I have done a lot to test scalability. In the six years that I have been dealing with SRM, I have just been protecting those 25 VMs. I do not have hands-on experience as to how well it would scale out.  

How are customer service and technical support?

I have dealt with the technical support at times in the last year. I would give VMware's tech support a nine-out-of-ten. They are responsive and get you a useful reply.  

Which solution did I use previously and why did I switch?

Disaster recovery was completely done with physical servers prior to when we started using VMware. When we went to VMware, we started using SRM. So the first time we went with the virtual environment we deployed SRM. We just went straight with SRM just because it is a VMware product. It was already well-integrated and did what we needed it to do.  

How was the initial setup?

The installation and initial setup were pretty straightforward. The deployment, overall, was pretty straightforward. There was a little implementation structure we had to factor in related to my storage array. But besides that, it was pretty straightforward and easy enough all the way around.  

What's my experience with pricing, setup cost, and licensing?

I pay for SRM per year. It is about $3,000 a year for the 25 pack. The package gives you the ability to protect up to 25 virtual machines.  

What other advice do I have?

From what I have seen, a lot of these new hyper-converged systems come with certain components that do a lot of what SRM does. My opinion and advice to people considering SRM would be to look to your hardware vendor or consultant. They may have some replication pieces in there that allow you to possibly not use SRM or go ahead and stay with what you already have. Depending on your situation, different combinations might prove more beneficial either within the architecture or by cost-benefit. There are a lot of options out there now for disc replication and bringing machines up at other locations.  

On a scale from one to ten (where one is the worst and ten is the best), I would rate the SRM as about an eight-out-of-ten.  

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Toby Sloan
Director Of Service Delivery at Kinetic IT
Real User
Top 20
A good solution for those with a VMware footprint

Pros and Cons

  • "This SRM solution can improve your footprint within a data center."
  • "The product functionality is fairly high-quality."
  • "This product is not appropriate for those moving to a broader cloud footprint."
  • "The technical support is not very good and needs to make an effort to improve."

What is our primary use case?

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.  

What is most valuable?

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.  

What needs improvement?

The decision to move to another product is a matter of room for improvement around functionality and requirements that we had with AWS and moving to the cloud. We are not going to be procuring any more licensing for SRM when we make the move to the cloud. We were looking at a cloud-native solution in order to provide the same functionality as the SRM provides but in the cloud. That is just a matter of the changing environment.  

If the functionality of SRM could be replicated in the cloud, that would be the improvement we are looking for in the product.  

For how long have I used the solution?

I have been using SRM (Site Recovery Manager) for probably six years.  

How are customer service and technical support?

I have contacted technical support multiple times. I would not say that I am satisfied. They are not very good and need to make an effort to improve.  

How was the initial setup?

The initial setup and installation were pretty straightforward. It was ten plus years ago so I do not remember the exact details, but I do not remember it being difficult at all.   

What's my experience with pricing, setup cost, and licensing?

The cost of SRM is on par with market rates. So I think the costs for this product are fine.  

What other advice do I have?

I personally will not continue using the VMware SRM solution. That is not a question of what is best. Our position moving forward is that we will not be having a footprint in the VMware space. If someone had the ability to focus on lots of things with using VMware in the cloud then there no issues at all with the product and this is a good solution for that purpose. The product functionality is fairly high-quality. Our decision is more based around the direction that we are taking. We will be cloud-based and we will be using AWS predominantly as our cloud-provider solution.  

On a scale from one to ten (where one is the worst and ten is the best), I would rate this solution overall as an eight-out-of-ten. It would not be closer to a ten because there is still some work that we need to carry out with regular maintenance and then there are the increasing license costs. An eight seems about right.  

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
DC
Senior System Engineer at a tech services company with 11-50 employees
Real User
Top 20
Good disaster recovery and testing capabilities

What is our primary use case?

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.

What is most valuable?

The most valuable features are the disaster recovery and testing.

What needs improvement?

The interface is not easy to use and can be made more user-friendly.

For how long have I used the solution?

I have been using VMware SRM for two years.

What do I think about the stability of the solution?

This is a stable solution. However, we have used older…

What is our primary use case?

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.

What is most valuable?

The most valuable features are the disaster recovery and testing.

What needs improvement?

The interface is not easy to use and can be made more user-friendly.

For how long have I used the solution?

I have been using VMware SRM for two years.

What do I think about the stability of the solution?

This is a stable solution. However, we have used older versions and have seen some problems. I would say that the current version is stable.

This solution is not used frequently because it is only in the event of disaster recovery or testing. The recovery portion is not intended for daily use.

What do I think about the scalability of the solution?

It is difficult to judge scalability because I would have to understand the intent. It is not a scale-out solution. It is for site recovery.

Our customers for VMware SRM are medium to large-sized companies.

How are customer service and technical support?

I have not recently been in touch with technical support. In the past, I have found that they solve problems on time, although it depends on the support contract that the customer has.

How was the initial setup?

The complexity of the initial setup depends on the customer requirements and their environment. It can be simple, although it can be really complex when they have two or more DR sites.

The length of time for deployment can be three or four days. It depends on the sites that have to be configured.

There is not a great deal of maintenance that is required. However, it does need to be updated and the disaster recovery plan regularly tested.

What about the implementation team?

Maintenance might be done by the customer, the vendor, or even a third-party partner if it calls for it.

What's my experience with pricing, setup cost, and licensing?

The price of this solution is on the expensive side. Also, not everything is included in the license.

What other advice do I have?

My advice to anybody who is implementing this solution is to know well what they want from this solution. It is a complex project, not in the installation, but in creating the disaster recovery plan. 

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
AF
Consultant at a tech services company with 51-200 employees
Real User
Top 5
Effective automation, easy to use, but stability needs improvement

Pros and Cons

  • "The solution is simple to use and has effective automation."
  • "There needs to be better stability during heavy capacity in future releases."

What is our primary use case?

I use VMware SRM for DR testing and VR.

What is most valuable?

The solution is simple to use and has effective automation.

What needs improvement?

VMware SRM does not have the capacity to do DR tests. We had issues whenever we were doing tests with the root cause analysis. We had 70 to 80 percent successful results because the vCenters were overloaded and that was the reason that we were having capacity issues.

We have been experiencing an additional problem when adding a regular VM in the replicated storage. By default, it will show an error. However, there is not any monitoring mechanism that would show you are not supposed to have a regular VM which is non-VR in the replicated SRM storage. Whenever we used to do testing we had to figure out that a regular VM is there and remove it manually.

For how long have I used the solution?

I have been using this solution for approximately seven years.

What do I think about the stability of the solution?

The stability should be smooth, and as for the capacity, we should be able to run the test successfully. However, from our research and DR test results, we came to the conclusion that we have to run the DR test during the non-production hours. Logically, they should be able to be done during the production hours, but that is not the case. We have to ensure that the vCenters are free and are not doing regular work for us not to have any issues during the DR test.

There needs to be better stability during heavy capacity in future releases.

What do I think about the scalability of the solution?

The solution is easy to scale.

The solution is used extensively in our large organization.

How are customer service and technical support?

When we first started out using this solution we encountered a few issues and used the support but we now know how to fix most of the issues and have not used them. Additionally, we have our own team for support.

How was the initial setup?

The installation is logically simple and in the medium range of difficulty. However, you need to make sure you have the proper infrastructure.

Which other solutions did I evaluate?

I have evaluated Veritas and Zerto.

What other advice do I have?

I would advise others looking into implementing VMware SRM not to totally be dependent upon it. Review other solutions, such as Veritas regulatory platform and Zerto. There are newer VM DR options coming out regularly and they should not have only one solution.

I rate VMware SRM a six out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Mourad Koudir
Consultant-Instructor at Flexdata
Consultant
Top 20
User-friendly, simple to use, and it can be used with storage arrays from any vendor

Pros and Cons

  • "The most valuable feature is the simplicity of operations."
  • "The two vCenters have to be synchronized, which sometimes gives us problems because Keberos does not tolerate more than five minutes in time difference."

What is our primary use case?

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.

What is most valuable?

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 needs improvement?

I would like to see a detailed history of the events for each site because I have found difficulty with that. The two vCenters have to be synchronized, which sometimes gives us problems because Keberos does not tolerate more than five minutes in time difference.

For how long have I used the solution?

I have been dealing with VMware SRM since 2009.

What do I think about the stability of the solution?

The recovery point (RPO) is set to 24 hours, which means that this is being used daily. Our backup happens at 8:00 pm every night.

What do I think about the scalability of the solution?

VMware SRM is scalable.

Most of our clients are in Morocco, and 80% of them are bigger companies with a lot of users.

How are customer service and technical support?

Technical support from VMware is good and I would rate them an eight out of ten.

How was the initial setup?

The initial setup is definitely simple.

The last project that I worked on took two weeks to deploy. This included installing NetApp, vCenter, ESXi, and the initial application.

What about the implementation team?

We have an in-house team that includes me and two other people. We also do maintenance for some of our clients.

What other advice do I have?

In the past, with version 6.0, there were two versions of SRM. There was a version for Windows as well as an appliance. However, all of our customers are now moving to the appliance.

I recommend using this product because it integrates well with replication technology from any vendor using the SRA.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Buyer's Guide
Download our free VMware SRM Report and get advice and tips from experienced pros sharing their opinions.