Chief Technology Officer at a insurance company with 51-200 employees
Real User
Top 10
Apr 24, 2025
Our organization used Azure Site Recovery ( /products/azure-site-recovery-reviews ) because we could not afford for our site to be down for a long time. We hosted our core client-facing and advisor-facing engine on it. It was crucial for us to maintain uptime, so we conducted regular drills to ensure we could recover the site if it failed.
I work as a System Integrator ( /products/axway-amplify-application-integration-reviews ) and Microsoft partner. I use Azure Site Recovery ( /products/azure-site-recovery-reviews ) as part of our organization's disaster recovery plan to manage customers' data backup and recovery.
We migrated around seventy on-prem servers to Azure via Site Recovery for one of our projects. We use it in our disaster recovery site, and we perform this process every three months.
When you have a large environment with applications and site databases structured in layers such as program, business layer, and database layer, it is crucial to have a secondary strategy in place. This involves running a secondary site in a different location, possibly in another country within the same region, ensuring continuity and enabling a robust disaster recovery plan to address any issues that may arise.
In my company, I use the solution as a simple tool for backup and not for restoration purposes. My company is in the phase of conducting some simple and quick testing.
We use Azure Site Recovery to duplicate our on-premises virtual machines to Azure. This ensures a backup in case of a disaster. If something goes wrong, we can quickly switch to the replicated VMs in Azure, ensuring business continuity and minimizing downtime.
Customers are interested in utilizing a BI engine for data recovery. While they initially provided their entire recovery, there have been instances where they considered switching to another solution. For certain customers, they opt not to cover the entire hardware or use Cisco cybersecurity, which might not be the case.
Sr. Sales Solutions Architect at a tech services company with 10,001+ employees
Real User
Mar 16, 2020
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.
Azure Site Recovery ensures seamless disaster recovery with features like scalability, automated file synchronization, real-time dashboards, and secure processes. It achieves a 99.99% uptime SLA and is recognized for its cost-effectiveness and user-friendly interface. Azure Site Recovery is a comprehensive disaster recovery service featuring load-balancing, fast snapshots, and native Azure integration for reliable performance. It manages virtual machine synchronization with seamless failover...
My main use case for Azure Site Recovery is that we are doing cross-region disaster recovery and processing.
Our organization used Azure Site Recovery ( /products/azure-site-recovery-reviews ) because we could not afford for our site to be down for a long time. We hosted our core client-facing and advisor-facing engine on it. It was crucial for us to maintain uptime, so we conducted regular drills to ensure we could recover the site if it failed.
I work as a System Integrator ( /products/axway-amplify-application-integration-reviews ) and Microsoft partner. I use Azure Site Recovery ( /products/azure-site-recovery-reviews ) as part of our organization's disaster recovery plan to manage customers' data backup and recovery.
We migrated around seventy on-prem servers to Azure via Site Recovery for one of our projects. We use it in our disaster recovery site, and we perform this process every three months.
We use Azure Site Recovery primarily for disaster recovery to Azure or from Azure, while Veeam is used for data center recovery.
When you have a large environment with applications and site databases structured in layers such as program, business layer, and database layer, it is crucial to have a secondary strategy in place. This involves running a secondary site in a different location, possibly in another country within the same region, ensuring continuity and enabling a robust disaster recovery plan to address any issues that may arise.
We use the tool for business continuity purposes.
In my company, I use the solution as a simple tool for backup and not for restoration purposes. My company is in the phase of conducting some simple and quick testing.
We use Azure Site Recovery to duplicate our on-premises virtual machines to Azure. This ensures a backup in case of a disaster. If something goes wrong, we can quickly switch to the replicated VMs in Azure, ensuring business continuity and minimizing downtime.
Customers are interested in utilizing a BI engine for data recovery. While they initially provided their entire recovery, there have been instances where they considered switching to another solution. For certain customers, they opt not to cover the entire hardware or use Cisco cybersecurity, which might not be the case.
We use Azure Site Recovery for our disaster recovery and business continuity purposes.
We use the tool as a backup for our environment.
The primary use case of this solution is for disaster recovery. I'm an enterprise architect.
I primarily use Site Recovery to back up our site server.
Our data was on VMware VM, and we used Azure Site Recovery to replicate all data into Azure.
We use the solution primarily for migrations, backup and BCP.
We use this solution mainly for compliance and to a DR and a commitment in RTO and RPO.
We back up our site to it and use it for a VR. We are using the most up to date version of this solution.
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.
We primarily use the solution for disaster recovery for our organization.