We changed our name from IT Central Station: Here's why
Don Hwata
Senior Systems Engineer at a marketing services firm with 1-10 employees
Real User
Top 5Leaderboard
Good automation with seamless failover saves us time, but it needs better granularity when used with array based replication software.
Pros and Cons
  • "The most valuable feature is the automation, where you press a button and everything fails over seamlessly."
  • "You cannot use VMware SRM in conjunction with storage replication software."

What is our primary use case?

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.

What is most valuable?

The most valuable feature is the automation, where you press a button and everything fails over seamlessly. It is quite good.

What needs improvement?

When used in conjunction with storage replication software it is not possible to separate and failover an individual VM. When the VMs are sitting on the same storage LUN, the granularity is not sufficient.  Ideally, we should be able to choose one virtual machine and separate it from the rest.

If the price were more competitive then it would be very good.

For how long have I used the solution?

I have been working with VMware SRM for about five years.

What do I think about the stability of the solution?

It is stable for now. I haven't had any issues.

What do I think about the scalability of the solution?

It is scalable, although the downside to scaling is the cost.

How are customer service and technical support?

When I first contacted technical support, I had some issues. However, as time went on, the support has improved and I now think that it is okay.

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

Prior to using VMware SRM, we were doing everything manually. Failover of VMs was done manually from promoting the replicated LUNs to read write and then bringing them up in the DR VMware environment.  It was a lot of manual work when dealing with hundreds of VMs.

How was the initial setup?

The initial setup is all right and we have had no issues with it.

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

The cost of SRM is a little bit high, especially for smaller companies.

Which other solutions did I evaluate?

Yes Veeam and RecoverPoint for VM

What other advice do I have?

In summary, this is a mature product that works very well. It is easy to set up. I like the fact that it has a bubble test feature that allows you to test your configurations without actually failing over. However SRM is very pricy.

I would rate this solution a seven 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
Jacob  Morake
Founder at a comms service provider with 201-500 employees
Real User
Top 5Leaderboard
Quick to deploy, stable, and works without issues
Pros and Cons
  • "If you want to do failover, it works without any problem."
  • "Sometimes it can cause a bit of downtime during switchovers."

What is our primary use case?

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.

What is most valuable?

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

The product is stable.

The deployment process is fast.

What needs improvement?

The challenge it has is with the speed of failing over. Sometimes it can cause a bit of downtime during switchovers. Sometimes you realize that when you are failing over you can have downtime due to the fact that you're stepping down on one side and powering up on another side.

For how long have I used the solution?

We've used the solution since 2012. It's been almost ten years.

What do I think about the stability of the solution?

The stability is great. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

What do I think about the scalability of the solution?

The scalability is just a function. Whether you can scale or not depends on your resources. It depends on your bandwidth. The scalability will depend on the infrastructure it is using.

We have three people who work with the solution directly.

How was the initial setup?

The deployment doesn't take long. It also takes just a couple of hours as long as you have prepared and long as you have a design.

For the implementation process, we needed three people, however, for implementation, we need a trained engineer. Just one engineer is fine.

What about the implementation team?

If you have trained people who are certified, you can do it yourself. The most important thing is to make sure that it is done by a trained engineer.

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

We do have to pay a licensing fee in order to use the solution. We have an annual subscription. 

What other advice do I have?

I don't remember the version of SRM that we're using now.

I'd recommend the solution to others.

I would rate it at an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Learn what your peers think about VMware SRM. Get advice and tips from experienced pros sharing their opinions. Updated: January 2022.
563,208 professionals have used our research since 2012.
Senior BCDR Professional at a computer software company with 1,001-5,000 employees
MSP
Top 20
Reliable, easy to implement, and has good support

What is our primary use case?

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

What is most valuable?

It is easy to implement for my clients.  It's a very nice product.

What needs improvement?

I would like to see this solution be more scalable. We currently use our security in addition to VMware SRM.

For how long have I used the solution?

I am certified in VMware and VCloud.  I have been using VMware SRM for ten years.

What do I think about the stability of the solution?

We have no issues with the stability of VMware SRM.

What do I think about the scalability of the solution?

VMware SRM is scalable, but it can be improved. We have 15 to 20 customers who are using SRM. We have customers not only in the US but in the UK…

What is our primary use case?

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

What is most valuable?

It is easy to implement for my clients. 

It's a very nice product.

What needs improvement?

I would like to see this solution be more scalable.

We currently use our security in addition to VMware SRM.

For how long have I used the solution?

I am certified in VMware and VCloud. 

I have been using VMware SRM for ten years.

What do I think about the stability of the solution?

We have no issues with the stability of VMware SRM.

What do I think about the scalability of the solution?

VMware SRM is scalable, but it can be improved.

We have 15 to 20 customers who are using SRM. We have customers not only in the US but in the UK also.

How are customer service and technical support?

They provide very good technical support that is affordable.

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

We are also using Zerto.

How was the initial setup?

It is very easy when it comes to integrating with a data center or an appliance, but it's a bit complicated.

The length of time it takes to deploy depends on the database we are accessing. It can take two hours to deploy.

We have two senior persons to deploy and maintain it.

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

I am not involved with the pricing. 

We have a procurement team and sales team that work with the vendors.

What other advice do I have?

I would definitely recommend this solution to others who are interested in using it.

I would rate VMware SRM an eight out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Flag as inappropriate
Rakesh-Patel
Consultant at Ashtech Infotech (India) Pvt.Ltd.
Consultant
Top 20
Good reporting and disaster recovery testing capability

What is our primary use case?

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.

What is most valuable?

The most valuable feature is disaster recovery testing. The reports are very good.

What needs improvement?

The configuration process could be improved.

For how long have I used the solution?

I have been using VMware SRM for about five years.

What do I think about the stability of the solution?

This is the most stable solution that I have seen. It is used on a daily basis, although we are only monitoring it intermittently. It monitors our critical workloads in the background.

What do I think about the scalability of the solution?

It is easy to scale VMware SRM. …

What is our primary use case?

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.

What is most valuable?

The most valuable feature is disaster recovery testing.

The reports are very good.

What needs improvement?

The configuration process could be improved.

For how long have I used the solution?

I have been using VMware SRM for about five years.

What do I think about the stability of the solution?

This is the most stable solution that I have seen. It is used on a daily basis, although we are only monitoring it intermittently. It monitors our critical workloads in the background.

What do I think about the scalability of the solution?

It is easy to scale VMware SRM.

How are customer service and technical support?

We have been in touch with technical support once or twice and we are happy with them.

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

We did not use another solution prior to this one.

How was the initial setup?

The initial setup is simple and it takes approximately four hours to deploy.

There is not much in terms of maintenance and we do not have that role assigned to anybody.

What about the implementation team?

We had an integrator assist us with the implementation.

Which other solutions did I evaluate?

We went straight to this product without evaluating other options.

What other advice do I have?

This is a product that I would recommend for people with a VMware stack.

I would rate this solution a ten 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
Consultant at Daniyals Inc
Real User
Top 5
UI is very user-friendly and it doesn't require a lot of resources; lacking in stability
Pros and Cons
  • "The UI is very user-friendly and testing is easy."
  • "Lacks stability and as a result requires continuous monitoring."

What is our primary use case?

Our primary use case of this solution is for testing. 

What is most valuable?

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. 

What needs improvement?

Unfortunately, SRM is not stable and it therefore requires continuous monitoring. If there are any issues associated with the Center, SRM doesn't work well and as a result, it generates a lot of tickets and productivity drops. 

For how long have I used the solution?

I've been using this solution for five years.

What do I think about the stability of the solution?

Although this solution is a good tool, it lacks stability. We have five users in our team. 

What do I think about the scalability of the solution?

The overall advantage of VMware is its scalability. But when it comes to SRM, scalability is not really relevant. It's only relevant in terms of the DR solution because SRM is a component of VMware, which requires vCenter. 

How are customer service and support?

The technical support is quite good. 

How was the initial setup?

Setup of SRM required the architectural team. The SAN team plays a very important role here because there's not enough stability. The DR test can fail because of the associated orchestration issues with regard to the SAN.

Which other solutions did I evaluate?

I've never used Zerto, but from my training and my personal analysis, I think it's better than SRM. 

What other advice do I have?

I rate this product six out of 10. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Senior Information Technology Manager at a retailer with 5,001-10,000 employees
Real User
Good failover time and excellent support
Pros and Cons
  • "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."
  • "We've had configuration issues on occasion. We start to fail over, and then we have to call it off because the configuration is not right, or the data stores aren't configured correctly in the secondary data center. Oftentimes, it is just the experience level of the team, and we have to bring in the vendor to help and validate our configuration."

What is our primary use case?

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

What is most valuable?

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.

What needs improvement?

We've had configuration issues on occasion. We start to fail over, and then we have to call it off because the configuration is not right, or the data stores aren't configured correctly in the secondary data center. Oftentimes, it is just the experience level of the team, and we have to bring in the vendor to help and validate our configuration.

For how long have I used the solution?

I have been using this solution for probably five years.

How are customer service and technical support?

Their support is excellent.

What other advice do I have?

I would rate it an eight out of 10. There is some complexity there, and that's where I would bring it down from a 10.

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
Mohab Samy
VMware Technician Manager at VAS
Real User
Top 5Leaderboard
Effective disaster recover, stable, and scalable

What is our primary use case?

VMware SRM is used for disaster recovery automation.

What is most valuable?

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

What needs improvement?

The solution could improve by removing some of the limitations we have been facing. There could be better integrated.

For how long have I used the solution?

I have been using VMware SRM for approximately 10 years.

What do I think about the stability of the solution?

The solution is stable.

What do I think about the scalability of the solution?

VMware SRM is scalable. We have approximately 25 people using this solution in my company.

How are customer service and support?

The support could be improved, they are slow.

How was the initial setup?

The…

What is our primary use case?

VMware SRM is used for disaster recovery automation.

What is most valuable?

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

What needs improvement?

The solution could improve by removing some of the limitations we have been facing. There could be better integrated.

For how long have I used the solution?

I have been using VMware SRM for approximately 10 years.

What do I think about the stability of the solution?

The solution is stable.

What do I think about the scalability of the solution?

VMware SRM is scalable.

We have approximately 25 people using this solution in my company.

How are customer service and support?

The support could be improved, they are slow.

How was the initial setup?

The installation is of a moderate difficulty level. The time it takes to implement depends on what vendor you are integrating it with, such as HP. The typical duration of implementation including the configuration is approximately five days.

What about the implementation team?

We have one engineer for the maintenance and support of VMware SRM.

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

There is an annual license to use this solution.

What other advice do I have?

I would recommend this solution to others.

I rate VMware SRM 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
Flag as inappropriate