Azure Site Recovery

Akins IT • November 7, 2018
Connect with us

Azure Site Recovery (ASR) is a complete game changer when it comes to Disaster Recovery (DR). Disaster Recovery differs from backup in that backup can take an extended amount of time to restore data and most backup solutions do not help if there is an issue with the physical location or hardware. In this article I will highlight some of the main benefits of using ASR as a part of your Disaster Recovery plan.


Cost


The single most important benefit of setting up your DR infrastructure with ASR is cost. In a traditional DR environment, clients were forced to rent/buy a separate location, datacenter or otherwise, purchase all the appropriate hardware, configure it all, and maintain it in addition to their production infrastructure. For a lot of customers, especially small to medium size customers, this solution was simply too expensive. Now with ASR, you immediately save the cost associated with another location and the hardware that is required. In addition, the client only pays for compute and usage charges IF they failover over to Azure during a test or an actual DR situation.


Simplicity


Ease of use is another great reason to leverage ASR in your DR practice. In any DR implementation it is a must to have very specific goal(s) and create a detailed plan for the execution to ensure things are not overlooked. However, on a technical level, the implementation and use of ASR is very simple. Whether you have Hyper-V or a VMware environment, there are tools and step-by step guides to implement them in either situation. With an Azure subscription, a few hours, and some basic technical knowledge, you can begin replicating and protecting portions of your infrastructure over to Azure.


Migration Tool 


An often-overlooked part of ASR is its use as a migration tool. Many clients are starting to migrate their workloads over to Azure or simply wanting to test the Azure waters. A lot of times costumers don’t entirely know where to start so they reach out to us. We will typically do a Proof of Concept for them (PoC). During the PoC we will work with the client to create or identify a low priority virtual machine, configure ASR and replicate the instance to Azure. The key here is that there is no technical requirement to ever failback, hence, migration tool. Throughout the process the client can be as involved or not involved as they like depending on their needs and goals. Once we have replicated a machine or two and the client understands the process along with some training, clients can then begin to evaluate Azure for its different uses and continue to use ASR to migrate workloads as needed.


If your company is looking into implementing a DR strategy or to reduce cost, my reasons will hopefully assist you in considering ASR. Of course, if you would like more information on ASR, please don’t hesitate to reach out to our team here at Akins IT!

Read More about Migrating to Azure
By Shawn Akins October 20, 2025
October 20, 2025 — Early today, Amazon Web Services experienced a major incident centered in its US‑EAST‑1 (N. Virginia) region. AWS reports the event began around 12:11 a.m. PT and tied back to DNS resolution affecting DynamoDB , with mitigation within a couple of hours and recovery continuing thereafter. As the outage rippled, popular services like Snapchat, Venmo, Ring, Roblox, Fortnite , and even some Amazon properties saw disruptions before recovering. If your apps or data are anchored to a single cloud, a morning like this can turn into a help‑desk fire drill. A multi‑cloud or cloud‑smart approach helps you ride through these moments with minimal end‑user impact. What happened (and why it matters) Single‑region fragility: US‑EAST‑1 is massive—and when it sneezes, the internet catches a cold. Incidents here have a history of wide blast radius. Shared dependencies: DNS issues to core services (like DynamoDB endpoints) can cascade across workloads that never directly “touch” that service. Multi‑cloud: practical resilience, not buzzwords For mid‑sized orgs, schools, and local government, multi‑cloud doesn’t have to mean “every app in every cloud.” It means thoughtful redundancy where it counts : Multi‑region or multi‑provider failover for critical apps Run active/standby across AWS and Azure (or another provider), or at least across two AWS regions with automated failover. Start with citizen‑facing portals, SIS/LMS access, emergency comms, and payment gateways. Portable platforms Use Kubernetes and containers, keep state externalized, and standardize infra with Terraform/Ansible so you can redeploy fast when a region (or a provider) wobbles. (Today’s DNS hiccup is exactly the kind of scenario this protects against.) Resilient data layers Replicate data asynchronously across clouds/regions; choose databases with cross‑region failover and test RPO/RTO quarterly. If you rely on a managed database tied to one region, design an escape hatch. Traffic and identity that float Use global traffic managers/DNS to shift users automatically; keep identity (MFA/SSO) highly available and not hard‑wired to a single provider’s control plane. Run the playbook Document health checks, automated cutover, and comms templates. Then practice —tabletops and live failovers. Many services today recovered within hours, but only teams with rehearsed playbooks avoided user‑visible downtime. The bottom line Cloud concentration risk is real. Outages will happen—what matters is whether your constituents, students, and staff feel it. A pragmatic multi‑cloud stance limits the blast radius and keeps your mission‑critical services online when one provider has a bad day. Need a resilience check? Akins IT can help you prioritize which systems should be multi‑cloud, design the right level of redundancy, and validate your failover plan—without overspending. Let’s start with a quick, 30‑minute review of your most critical services and RPO/RTO targets. (No slideware, just actionable next steps.)
By Shawn Akins October 13, 2025
How a Zero-Day in GoAnywhere MFT Sparked a Ransomware Wave—and What Mid-Sized IT Leaders Must Do Now
By Shawn Akins October 13, 2025
The clock is ticking: Learn your options for Windows 11 migration, Extended Security Updates, and cost‑smart strategies before support ends.
More Posts