I rate VMware SRM an eight out of ten for the ease of its initial setup.

More or less, due to the product itself, it's relatively easy to set up. However, in our environment, we have a VM, and that VM application is very complicated. Sometimes we have some issues in running this application on the backup site. This is not due to this SRM. Rather, it is due to our environment.

The deployment took about two years. 

We have a team of four people that can handle deployment and maintenance duties. They are all specialists. 

I would rate my experience with the initial setup a nine out of ten, with ten being easy. 

The complexity of the initial setup depends on the deployment model and current infrastructure. 

On the new base, it will be difficult because we need to install it with existing replication in place. That requires knowing how to integrate the tool. On-premise or cloud integration is a bit easier. 

Deployment itself is minimal. Configuration takes longer, usually a day or two.  It may take more or less time, depending on the size of the environment. 

I would rate the easiness of the initial setup as a seven out of ten. In our company, VMware SRM is deployed both on-premises and on the cloud. It took about two months to deploy it and it was done in-house. The number of staff required for deployment typically ranges from two to six people, depending on the size of the project. Maintenance for this solution is typically provided by the developers or vendors. We have maintenance agreements with various providers like VMware, Rubrik, Veeam, and Commvault, and hardware maintenance is handled by the hardware provider through our maintenance contracts.

The initial is straightforward if you have prior experience working with it. I rate the process a nine or ten.

In scenarios with around ten to fifteen VMs, the configuration process can typically be completed within a day. It might take around a week or two for a critical environment with 200 VMs.

We set up the infrastructure in the production site and deployed the virtual environment. Later, we configure the virtual environment and storage. For physical servers, a physical-to-virtual conversion is executed. Post-production site deployment, attention turns to the disaster recovery site, where the Site Recovery Manager is set up on both ends. Further, we can do migration testing.

The initial setup is complex and took almost a week to deploy. I would rate the installation experience as two-and-a-half out of five.

The initial setup of VMware SRM isn't straightforward because many customizations are required since it helps in the recovery of your IT environment. It is not the tool but the process that is complex. The tasks associated with using the tool in an environment for disaster recovery are complex.

The product's deployment process takes around three to four weeks to complete.

For the deployment process, you need to assess your environment before getting into the design phase, after which you need to understand the business objectives and goals clearly to design your target environment. Once your environment is ready, then you need to understand the steps you need to follow to configure VMware SRM to achieve your target state. I would say assessment followed by defining a clear business objective, and then after design, you have to build the environment.

There is a need for an architect to take care of the design part of the solution, along with a couple of engineers and a dedicated project manager to run the product during the deployment phase. There is a need for at least two engineers to run the product.

The initial setup was easy and straightforward.

I'm an architect so I did not install SRM myself, but I think there were no issues with installing it since it's a pretty standard tool nowadays. It does not require much maintenance. We are still running some old versions of VMware as there was a challenge around Oracle licensing. We are moving the Oracle workloads off of it now and addressing the architecture to get rid of the copies of the legacy versions of VMware. 

The initial setup is straightforward and user-friendly. Depending if everything in the network layer is okay, we can configure VMware SRM for both sites in less than an hour or less. The replication process will depend on the size of the VM, so if the VM is large enough, the replication process will take some time. However, the configuration of SRM is straightforward.

We found that the initial setup for this product was quite easy.

We had a simple vertical setup. We have VMware engineers at our disposal, and their expertise made it easy.

The deployment took one to two days. It was not complicated. We only needed one or two people to handle the deployment and maintenance tasks. They are engineers and junior staff. 

The product's initial setup phase was not difficult.

The solution is deployed on an on-premises model.

The solution can be deployed in a couple of hours.

VMware SRM's initial setup is easy.

The initial setup is not that difficult. I would not say it's difficult because you just experience it when deploying some VMware solutions, especially a replication plan. The first time it's not always easy. But once you get the hang of it and get it right the first time, then you don't really have issues. Such as, do you need to go there and provide a key? I wouldn't say it's that difficult - it's not so straightforward but it's not that difficult. It's not complex for me.

I've done the deployment for different clients. So I would say the first time was not easy. But, for me to do it right now wouldn't take time.

My impression is that the initial setup process is relatively straightforward.

The deployment model of this solution that we are using is on-premises.

We used the documentation for our initial setup and had some difficulties. The deployment was carried out in-house and took a day or two. We had some help from colleagues in other companies and had a couple of people from our company involved in the deployment. 

The solution's initial setup was easy, but if you try to integrate it with other storage solutions, then it gets complex and difficult.

The solution is deployed on an on-premises model.

The initial setup is straightforward.

The deployment takes about three hours.

It was pretty straightforward. We kept the DC and DR servers together in the same datacentre during initial setup and VM syncing. After setup and syncing completion, we moved the DR server to the DR site.

I rate the ease of setup a seven out of ten. The deployment takes a few months.

The initial setup is simple.

Initial setup is straight-forward but you need to really do some research on prerequisite environment config needed for this product to work as developed.

I was involved in VMware SRM's deployment phase two years ago, and it was an easy process.

The solution is deployed on-premises.

The setup phase of VMware SRM can be done within a day, and then the planning and all policies that need to be set up would take four to five days or even a week.

I rate the initial setup process of the solution a seven or eight out of ten on a scale where one is difficult, and ten is easy. The setup process was not too difficult or too easy. Essentially, we were imaging all their physical servers on the cloud.

In our company, the deployment process takes about an hour. In some cases, due to the size of the data we were dealing with, it took a couple of days, which was the maximum, but usually, it was completed within a few hours.

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.

The initial setup is very straightforward. It's not too complex. 

Deployments can typically take two months.

In the first month, I dedicate focus on learning and conducting POC sessions. For around two or three weeks, I also spend some time implementing SRM at the site.

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.  

The initial setup and configuration can be complex. It's a complicated product. I'd rate the complexity of implementation eight out of ten. 

It took us a few months to fully deploy the solution. 

The installation is logically simple and in the medium range of difficulty. However, you need to make sure you have the proper infrastructure.

The initial setup is very straightforward. It's quite simple. However, those that implement it must have some experience in virtualization. In terms of deployment, you can have a demo regarding SRM and need to apply the scenario on it. Afterward, you can apply it to your environment. It's very easy.

The initial setup is straightforward. We need to download the application file and deploy it in vCentre Server. Later, we need to register a static manager to create a bridge between two environments. After that, we check if the static environment is configured with the data centers.

The installation is straightforward if you have the required skill level. It took about a week for the initial setup.

The initial setup is definitely simple.

The last project that I worked on took two weeks to deploy. This included installing NetApp, vCenter, ESXi, and the initial application.

In a simple situation, the setup is a piece of cake. However, as soon as you start to work across various deployments based on various levels, the setup is much more cumbersome and much more complex. You need to deal with the interoperability issues like checking the vCenter on the left side and the vCenter on the right side, what is the ESX (Elastic Sky X) level, et cetera. You may need to downgrade your expectations accordingly, to make it still work.  

Also, if you have network routing in between two completely different, distinct environments, that can give you quite a lot of headaches as well. To give you an idea: in the initial setup of one migration, we could just not connect both VMs end-to-end. The site manager would not connect. The vRA's were connecting, but the site manager was not. It turned out to be a network routing issue. In actuality, the "issue" was not an issue. The routing was just was working like it should, following the default gateway. It just could never connect to the other site manager.  

At times you really need to go back down to the very basics yourself, and even then there may be no clarity about why it will not connect. It follows the route, the stage-gate goes through, and the connection does not happen.  

Then also the checkpoint restart is a problem. There is no checkpoint restart. What I mean by that is you can have eight VMs to migrate over a coming weekend and something goes wrong after the process is initiated, or somebody made a mistake in the service grouping. When you see this problem, you think you just need to remap, recalibrate, and then relaunch it. But there is no history track of what is already replicated. The service grouping does not reflect in that result. You need to start all over again. So there is no checkpoint for the restart. There is a checkpoint for an individual VM, but not for multiple VMs.  

As far as the time it takes to deploy, that will vary. We have had different levels of complexity in our deployments. We initially had a simple setup that was done in two days, but there were no different networks involved, no different vCenters, and also it was intra-cluster. When done like this it was very easy.  

It was a completely different story for the more complex setups. I think it took us about six weeks with a lot of effort. There was a lot of alignment, a lot of verification, a lot of troubleshooting, and a lot of diagnostics to get it working end-to-end on both sides. It was really too much time to take with that kind of project.  

In some basic installations, it is very straightforward, but for enterprise customers it makes sense to do some extra steps to protect applications and boot order.

The initial setup and installation were pretty straightforward. It was ten plus years ago so I do not remember the exact details, but I do not remember it being difficult at all.   

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

The complexity of the initial setup depends on the customer requirements and their environment. It can be simple, although it can be really complex when they have two or more DR sites.

The length of time for deployment can be three or four days. It depends on the sites that have to be configured.

There is not a great deal of maintenance that is required. However, it does need to be updated and the disaster recovery plan regularly tested.

The setup is relatively complex because of how we use it so the setup can take some time.

The complexity of the setup depends on the scenario, but some experience is needed for deployment and installation.

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.

Least favorite things about Site Recovery Manager. It is a little bit difficult to get it set up the first time you've ever just because it is so different.

Fairly straightforward.

It was very straightforward.

It wasn't complex.

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.

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.

It’s a little complex. Just follow the instructions, but it’s not too complicated once you get connectivity, and it requires multiple vCenters, so that can make it more costly.

It was complex as it does not include a good, extensive feasibility and compatibility guide.

Complex - settings for the sql db were not documented - had to search a lot for those.

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

Initial set-up was straightforward.

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

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

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

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.

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