Overall, I rate VMware SRM a seven out of ten.

We are just a customer. 

I'm not sure which version of the product we're using. However, we are updating right now, in the next month. 

Right now, our environment is on-prem. We want to install the hyper-converged to start moving to the cloud.

I'd advise others to maintain the solution and keep it up to date. 

I'd rate the solution nine out of ten. 

Overall. I would rate the solution a nine out of ten because it helps our organization. 

Overall, I would rate VMware SRM as a seven out of ten.

I rate VMware SRM an eight out of ten.

Most of the customers are running production environments on-premises. They have their own DR environment in a different location or cloud. Business continuity planning helps us with maintenance, unexpected downtimes, or disaster recovery drills. We can seamlessly integrate it and migrate it to the DR site.

Orchestration and automation features play a significant role in disaster recovery, particularly when interfacing with the VMware vCenter. It provides seamless integration.

Incorporating non-disruptive testing capability in disaster recovery procedures has significantly benefited the overall recovery testing processes. For instance, during the production application to the disaster recovery (DR) site, customers can now check the capability and compliance of the replication process without causing disruptions to the live production environment. SRM administration has consistently proven effective in reducing recovery time objectives (RTOs) during real recovery events.

I rate it a nine out of ten.

If you're able to overcome the initial hump of setting up VMware SRM, it works very well. I'd give VMware SRM a rating of seven out of ten.

I recommend those wanting to use the solution completely understand their own environment since VMware SRM is meant for VMware environment only. You cannot integrate VMware SRM with other non-VMware products. If your requirements are very much restricted to VMware alone, then VMware SRM can be a good choice for managing activities related to disaster recovery. If you have a mixed environment, you need to think and look for other products in the market other than VMware SRM.

I rate the overall solution an eight out of ten.

If you're dealing with a more stable and homogeneous storage environment and have technical reasons to favor SAN, then SRM, which is tightly integrated with the storage vendor, may have some advantages. Veeam is a better solution when you have a mix of heterogeneous storage types, multiple sites, and diverse data replication requirements, as it operates independently of the storage application. For larger customers, such as those in the banking sector with diverse storage systems and extensive data replication needs, Veeam might be preferred. While it might have a slightly higher price point compared to SRM, it offers more flexibility and scalability. SRM, on the other hand, is well-suited for smaller customers with simpler storage environments and a smaller number of servers. It's more straightforward to configure and manage in such scenarios. Overall, I would rate VMware SRM ten out of ten.

I would advise new users to start off with manual processes and document exactly what they want to come up with in the right order. Get your IT continuity plan defined very closely and with a great amount of detail. Then start to automate with your SRM tooling to make sure that things are brought up in the right order and ensure that if one service fails and you need to bring another one across for latency purposes, you really understand all of those requirements before you start to just implement SRM and marching on without really understanding how the services tie together and the dependencies between them.

Overall, I would rate SRM an eight out of ten.

I give the solution a nine out of ten.

The deployment and maintenance can be done by one engineer.

I am the consultant solution architect, and sometimes I am the deployment engineer.

I seldom ask for support from VMware because most of the problems are caused by bugs, which we can usually fix ourselves by consulting the knowledge base on the VMware website. However, there are times when the problem is at the hardware level and VMware is not at fault - for example when there is a bug in the VMware version used by the hardware vendor. In these cases, we need to ask for support from the hardware vendor.

VMware SRM is a great solution. I always recommend the solution because it is a native replication solution for VMware. Although there are other solutions such as Zerto, they may deliver a lower RPO in certain cases. I believe Zerto is a better solution than VMware SRM, but when it comes to functionality, and for regular customers, VMware SRM is enough.

I would advise organizations who wish to use this solution, to ensure that their threat protection software is in place and up to date, as there isn't any threat protection embedded in this product.

I would rate this solution an eight out of ten.

We have some nodes which are still running VMware. We currently do have some nodes still running VMware like ESXi 7.0, however, not for production. It's right for testing purposes.

I'd rate the solution nine out of ten. 

I'd recommend the solution as it is very stable and does the job. 

I can't share my experience with the orchestration capability of VMware SRM since I am currently using the tool to test it in my environment. I haven't dealt with any real disaster scenarios in my company.

There is no requirement for any maintenance of the product at the moment.

I rate the overall tool an eight out of ten.

Just one person is enough to maintain the solution.

I highly recommend VMware SRM to other users.

Overall, I rate VMware SRM a nine out of ten.

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.

Overall, I would rate this solution a seven, on a scale from one to 10, with one being the worst and 10 being the best.

I think this is a good tool that's easy to manage and worth the cost, so I rate it nine out of 10. 

For first-time users, VMware SRM can be a very difficult tool to use, especially considering the product's configuration part. The configuration is very difficult.

With VMware SRM, you have to download the separate appliance and think about Windows to build a separate native appliance while also having knowledge about ESXi, making it a difficult process. When it comes to VMware SRM, the technical things are very difficult to start in the first place.

I rate the overall tool a five out of ten.

VMware SRM is the best sustainability solution, I would rate it at nine on a scale from one to ten.

It’s a good product from VMware. Just ensure that for each version upgrade, be patient and look for reviews or, if possible, have a test (virtualized) environment for test deployment.

I will recommend the solution to others. It is a nice product. Overall, I rate the tool an eight out of ten.

We have a cloud environment that requires disaster recovery capabilities. We utilize HZX to extend layer two connectivity and leverage Site Recovery Manager (SRM) for replication.

I recommend the solution to other users.

Overall, I rate the solution a ten out of ten.

You should aspire to be really well versed on supporting this product you need to have in-house engineers that are well rounded in the networking, storage and operational aspects of vSphere/vCenter/SRM. I would recommend getting hands-on training through a VMware a Partner before implementing this product in your environment.

VMware SRM is a handy solution since it does what it is told to do by its user while staying stable.

I rate the overall product an eight out of ten.

l always recommend others to have a POC in place. It's always about whether a solution suits your environment or not. So if it does, then go for it. If it doesn't, one should go for another solution. I rate the overall solution an eight out of ten.

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

I would rate VMware SRM an eight out of ten.

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.

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.  

I'd rate the solution seven out of ten. It's expensive. However, it's a good investment. 

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.

We're using the on-premises deployment model.

I'd recommend the solution. I'd rate it ten out of ten.

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.

I recommend VMware SRM to others and rate it a ten out of ten. I advise other users to always install the latest version.

I recommend VMware SRM and rate it at eight on a scale from one to ten.

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.

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.  

Vmware SRM can handle all of the challenge of replication and disaster recovery in a simple way.

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.  

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.

I'd rate SRM as eight out of ten.

I would rate VMware SRM an eight out of ten.

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.

I would recommend the product to anyone requiring a disaster recovery process. 

I would rate this product an eight out of 10. 

I would rate this solution an eight out of ten.

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.

I always think there's room for improvement. They would seriously need to sit down and take a machine. I want to bring this machine up over here on a different network at a different location. And write down all the steps that they would manually do if they were going to do this process by hand. And like I said the replication is free. So they could technically replicate that over there right now today, make a copy of it and go oh, okay, go bring it up over there and write down all the steps that you have to manually do and then multiply that times the number of machines that you have to do for your DR site. 

In my case it's about one hundred. I need to bring up about one hundred servers. Then you sit there and think to yourself okay, so, and you could just, you know, take your watch and say okay, I'm going to start now. I'm going to go over there and see what it takes to get this server up at the DR site. Oh, that took me about 20 minutes. Okay, well, then, you multiply that times a hundred and you're at 200- 2000 minutes, okay. So would you have 2000 minutes’ worth of time to go through and bring, you know, work on all these servers in the-in the case of a DR scenario. And if the answer's no, then you probably should look at something to help you out. Some tool to help you out with that and that's what Site Recovery Manager brings.

Everybody looks at reviews and I look at the negative reviews as well because I feel like sometimes that some of the positive reviews may not have been real but, up, people will always complain about something they don't like. They're the most vocal so for Site Recovery Manager I would probably type in Site Recovery Manager reviews into a search engine.

I would recommend it.

Take the time to understand your change rate of your servers, your bandwidth capabilities and the recovery objects for your DR plan.

Read and follow the admin guide, otherwise when you miss a step you can search long time. Also use the correct storage adapter of your storage vendor.

I would recommend this solution to others.

I rate VMware SRM an eight out of ten.

I rate this product six out of 10. 

Zerto may be more cost efficient, so I’m not 100% sold, and may not need it at all.

Choosing VMware in general, is best in terms of functionality, but it is not necessarily cost effective, as their licensing and setup costs are too hight. Maybe we will see more products for cloud and automation.

Do an analysis of what you need. Weigh the pros and cons of each solution and use what is going to work best for you.

Gather the proper setup information.

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.

Do a POC whilst keeping the environmental constraints in mind.

Know your business requirements.

POC and test.

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

I would rate this solution a ten out of ten.

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.