VMware SRM is currently a very stable solution, but we came across many issues three to four years back.

I rate VMware SRM a nine out of ten for stability.

The solution is stable. There are no bugs or glitches, and it doesn't crash or freeze. It's reliable.

I would rate the stability an eight out of ten. 

I would rate the stability of the solution as a seven out of ten. Like any software, we do encounter glitches and the need for patches and fixes from time to time, which is a normal part of maintenance. However, there is room for improvement in terms of patching processes, including reducing delays and addressing issues in applying patches. Additionally, better documentation would enhance the overall experience with the solution.

It provides a stable environment. I rate the stability a nine out of ten.

VMware SRM is stable.

It is a pretty stable solution.

It is a highly reliable solution.

It's a good and stable product. They do a lot of testing.

The solution is stable.

We have found this solution to be very stable so far.

The solution is stable. Its performance is reliable. There are no bugs or glitches and it doesn't crash or freeze. 

It is a stable solution. Stability-wise, I rate the solution an eight out of ten.

VMware SRM is a stable 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.

I would rate the stability of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

We've found the solution to be stable. 

It is a stable solution.

The stability is always good because we replicate daily. I have never seen any issues because the replication is always 100% successful.

Not really for use and operation, but a version upgrade is a real problem. When upgrading to the latest version, there are always problems with the upgrade, normal functioning etc. Doing an upgrade is lot of hard work. Always had to rely on next minor upgrade.

VMware needs to do better software testing before release.

I rate the tool’s stability an eight out of ten.

There is a minimum downtime.

I rate the solution’s stability a ten out of ten.

No issues. Product is fairly stable.

It is a very stable solution.

Stability-wise, I rate the solution a seven out of ten.

We have no issues with the stability of VMware SRM.

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

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

We haven't had any stability issues. There are no bugs or glitches. It doesn't crash or freeze. It is reliable.

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.

The stability of the solution is great. We've tested the system and haven't discovered any bugs.

I rate the product's stability an eight out of ten. Sometimes, we need to restart the system as it stops working. It needs improvement.

It is a stable 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.

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.  

No issues with stability.

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

I've never faced any issues with SRM's stability.

VMware SRM is a stable solution. It's very reliable.

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.

VMware SRM is very reliable and stable. 

I think that this product is very stable.

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

It's a very stable product. It is as scalable as VMware is itself.

Not yet.

No, but you need to have a good understanding of your bandwidth between sites. SRM does not have a native way to throttle bandwidth usage.

No, but the new web client is sometime ‘buggy.'

The solution is stable.

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

It works great, and does what it’s supposed to. Easy to do disaster revovery test without affecting production.

We faced issues as it is highly dependent on the platform in use.

None encountered.

No issues encountered.

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.

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

None encountered.

Sometimes the vm would not failover.

More around vSphere replication than SRM

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.

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