No more typing reviews! Try our Samantha, our new voice AI agent.
reviewer1271010 - PeerSpot reviewer
Technical Director at a tech services company with 11-50 employees
Real User
Feb 23, 2020
Easy to use, good data recovery capabilities and very stable
Pros and Cons
  • "The solution is very easy to use."
  • "The solution is very easy to use."
  • "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."
  • "There have been issues with replication. It would be helpful if error logging was handled more effectively."

What is our primary use case?

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

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

Buyer's Guide
Azure Site Recovery
March 2026
Learn what your peers think about Azure Site Recovery. Get advice and tips from experienced pros sharing their opinions. Updated: March 2026.
885,444 professionals have used our research since 2012.

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

The solution is easily scalable.

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

How are customer service and support?

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.

How was the initial setup?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. partner
PeerSpot user
reviewer2256900 - PeerSpot reviewer
Design and Innovation Manager at a comms service provider with 501-1,000 employees
Real User
Top 20
Aug 19, 2024
Provides disaster recovery and reduces cost with easy configuration
Pros and Cons
  • "It’s native to Azure and does exactly what it’s designed to do—recover one site to another without creating all the VMs on that site. This helps reduce costs on the secondary site."

    What is our primary use case?

    We use Azure Site Recovery primarily for disaster recovery to Azure or from Azure, while Veeam is used for data center recovery.

    What is most valuable?

    It’s native to Azure and does exactly what it’s designed to do—recover one site to another without creating all the VMs on that site. This helps reduce costs on the secondary site.

    For how long have I used the solution?

    I have been using Azure Site Recovery as a partner for two years.

    What do I think about the stability of the solution?

    There is no issues with stability.

    What do I think about the scalability of the solution?

    It is suitable for large enterprises. It is scalable. These businesses have around 500 users. 

    How are customer service and support?

    Support is wonderful.

    How was the initial setup?

    It is easy to configure.

    What's my experience with pricing, setup cost, and licensing?

    It is cost-effective.

    Which other solutions did I evaluate?

    The team conducted a thorough analysis before choosing Azure Site Recovery. They likely considered integration costs and various other factors.

    What other advice do I have?

    It seems to be seamless and is working perfectly. They’re integrating it with Azure Stack Hub, which we’ve also deployed as an on-premises solution.

    Overall, I rate the solution an eight out of ten.

    Disclosure: My company has a business relationship with this vendor other than being a customer. partner
    PeerSpot user
    Buyer's Guide
    Download our free Azure Site Recovery Report and get advice and tips from experienced pros sharing their opinions.
    Updated: March 2026
    Buyer's Guide
    Download our free Azure Site Recovery Report and get advice and tips from experienced pros sharing their opinions.