VMware SRM Reviews

• Fast recovery time
• Ease of use

• Easy to use
• Easy to document
• Easy to report
• Easy access to history

I can’t think of any right now, honestly.

I would give it a 7/10 for stability. It can be really bad, but generally fine, and we look at the availability when choosing new products.

It does have some limitations, but I would give it a 6/10.

Sometimes it’s good, sometimes it’s bad. It’s just luck of the draw.

We previously used Zerto. We switched because VMware only has a single point of support, as we needed to move forward with better products.

It was fairly straightforward, I would give it a 7/10.

Cisco – I’m not sure, it was there before I was there.

You have to pick whatever it best for their environment and their applications. That solution has to be able to fit, and VMware fit into ours.

Test run in protected environment

More confidence over DR services

vSphere Replication feature

Four years.

We had an issue with the Array SRA.

We had a problem connecting to the SRM plug-in.

No issues encountered.

Good.

Average.

No previous solution used.

Initial set-up was straightforward.

We used a vendor that was good.

Do a POC whilst keeping the environmental constraints in mind.

Disaster recovery of a failed site.

None, I implement this product for customers.

Storage integration.

5 years.

The integration (SRA’s) with storage and it’s versions.

None encountered.

None encountered.

9 out of 10.

9 out of 10.

Just a regular backup product. But this wasn't a disaster recovery solution.

A SRM implementation is not difficult. Getting the business requirements is more of a challenge.

I was the implementor.

For most customers about 2 years.

I don’t know as it depends on the customer.

Nope, I was asked to implement this solution.

Know your business requirements.

Instant VMware integration and a wide integration with storage vendors.

The company was able to provide customers with the required RPO that was not possible with traditional backup solutions.

Stability, speed.

4 years.

Bugs bugs bugs...

Sometimes the vm would not failover.

No backwards compatibility of different versions, this made scaling a bit difficult as we needed to upgrade existing infrastructure all the time.

3/10, VMware support was not really proficient in the product, as most of the time we would give them the solution.

3/10, VMware support was not really proficient in the product, as most of the time we would give them the solutio

No.

The integration with EMC recoverpoint was problematic in the beginning, with vm's not failing over all the time and slow recover times.

Yes, Zerto, Veeam.

POC and test.

Key feature for me is the ability to test recovery plans with zero impact to the production running environment, this is key for 'what-if’ type analysis and to provide confidence that the platform can be recovered with minimal intervention.

Organisations that have implemented SRM in my experience have confidence that their mission critical systems will be recovered within the given SLA in the event of a planned or unplanned availability event. This avoids costly and time consuming DR recovery tests which are also often unrepresentative of the real scenario.

Smaller sites or sites with mixed storage platforms rely on vSphere replication for DR purposes so additional scalability in this tool would benefit from this.

I have designed and implemented 3 solutions with this product over the last 3 years.

No issues

More around vSphere replication than SRM

No issues encountered.

VMware Tech Support is excellent.

For VMware environments there is no other option for integrated/automated DR other than 'roll your own.'

SRM setup is straight forward, SRA (storage integration) can be more complex depending on the array in question.

I was working for the vendor.

Consider your storage design and replication policy first and as always make sure you review VMware documentation and HCL for compatibility.

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.

The most valuable feature is disaster recovery testing.

The reports are very good.

The configuration process could be improved.

I have been using VMware SRM for about five years.

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.

It is easy to scale VMware SRM.

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

We did not use another solution prior to this one.

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.

We had an integrator assist us with the implementation.

We went straight to this product without evaluating other options.

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

I would rate this solution a ten out of ten.

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. 

it is a complementary solution to EMC's data recovery solutions, or RecoverPoint. Combined with VMware SRM it offers zero RPO and zero RTO, so it's a good solution for both EMC's Toolkit, and for the customer.

There is zero RPO and zero RTO when combined with the EMC solution called RecoverPoint.

I would like to see better integration with other storage solutions. I would hope to see that within the next two or three years.

I've never had any problem with downtime or the solution not working. The only issues were human errors in configuring it.

Scalability is bigger and better than the competitors.

We have always used VMware solutions because VMware is owned by EMC. So we've only used VMware SRM.

The most important criteria when selecting a vendor are stability, scalability, things that Microsoft had issues with.

It's not entirely straightforward. You have to know what you're doing in order to make it work properly.

Before choosing a cheaper solution, I would advise checking the limitations or boundaries of each solution. Compare VMware to Microsoft Hyper-V and other solutions - maybe open-source - and then see which fits your needs best.