VMware SRM Review

Disaster recovery that works quickly, is stable, and has excellent technical support

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?


Which version of this solution are you currently using?

SRM 6.0
**Disclosure: I am a real user, and this review is based on my own experience and opinions.
More VMware SRM reviews from users
...who work at a Manufacturing Company
...who compared it with Zerto
Learn what your peers think about VMware SRM. Get advice and tips from experienced pros sharing their opinions. Updated: May 2021.
510,882 professionals have used our research since 2012.
Add a Comment
ITCS user