Azure Site Recovery Reviews

Primary use case really depends on the client. The product can be used by insurance companies, hospitals, healthcare professionals. We mainly use the product for backup and disaster recovery and it's suitable for small and medium enterprise companies. 
It's used occasionally, not on a daily basis. We are in partnership with Microsoft and I work as a senior sales solution architect. 

One of the valuable features is failure restores. 

Improvement could be made on the pricing model. It could be brought in line with the competitive ranges in the market 

Additional features could include more of a backup and recovery. We'd like to see the AIX operating system added into it. It's more virtual right now.

I've been using the product for the last two or three years. 

Stability really depends on the situation, sometimes it's better and other times it's worse. It's generally fine. 

Scalability is good in this solution. 

The initial setup depends on the kind of control infrastructure that the clients have and that determines whether the setup is simple or complex. Azure doesn't have its own hardware for on-prem which makes it more complex for the reseller or as a solution for companies like us,  because we have to go and talk to different vendors for hardware. It means you then have to go and  buy the licenses or OS for everything and it becomes complex for someone who is selling it to the customer because there are several elements that need to be taken into consideration. We provide installation services and that can take a week or two. 

There are different components in pricing and for each and every component you have to check the box and you have to look for options - check if they have a front end or back end kind of licensing, those are different types of licensing that can possibly be made simpler and probably cheaper. 

We looked at Dell EMC but I think we went with Site Recovery because it fits better with cloud and they're moving a lot of their workload to cloud like Azure, and want something that is seamlessly integrated. It also provides one vendor whereas with Dell you then need to go to Azure and if a problem isn't resolved then who is responsible. 

I would rate this product an eight out of 10. 

We primarily use the solution for disaster recovery for our organization.

The solution is very easy to use.

The approach the solution takes to data recovery is very good. We can fail-over from production and the disaster recovery aspect of the solution is quite seamless. There are a few configurations that need to happen, however, once it's up it works quite well.

There have been issues with replication. 

It would be helpful if error logging was handled more effectively.

When it runs, it runs well but when it doesn't run, the solution needs to make it clearer as to why and what the troubleshooting process is. All this would be possible if the error logging was streamlined a bit.

I've only been using the solution for about six months. It's still quite new to me.

We haven't faced any crashes, bugs, or glitches. I would consider the solution to be quite stable.

The solution is easily scalable.

We're pushing about 40 servers into the cloud for disaster recovery using site recovery.

I can only vouch for the actual support we've gotten from Microsoft and that was very good. We have no complaints there; the support was very helpful when it came to handling the issue that we did have.

The initial setup is very straightforward. We didn't have any issues with any complexities.

We implemented in phases. In full, it took us about two or three months to deploy the solution. However, if a company is simply looking to do one or two servers, it's only going to take a couple of hours, or maybe a couple of days to go to the cloud. 

I'd estimate it would take about a month, for your average environment (a small to medium-sized environment) to deploy onto Site Recovery.

We're a partner as well as a customer.

We would definitely recommend the product. 

I would caution, or highlight rather, that if anyone is collecting resources they need to confirm that they're all configuring it correctly so that it doesn't generate unexpected costs because of a context that may be incorrect.

I'd rate the solution nine out of ten.