Azure Site Recovery
By:Lalit Rawat
Azure Site Recovery contributes to your business continuity and disaster recovery (BCDR )strategy by orchestrating replication
of on-premises virtual machines and physical servers. You replicate servers and VMs from your primary on-premises
datacenter to the cloud (Azure), or to a secondary datacenter.
 Site Recovery can be deployed in both the classic portal and the Azure portal.
 Azure classic portal, you can support Site Recovery with the classic services management model.
 Azure portal, you can support the classic model, or Resource Manager deployments.
 Azure subscription Creation.
 Azure VPN Onprem to Azure.
 Azure storage account in vault region
 Create a Recovery Services vault.
 Failover form Azure .
 Download the necessary files.
 Install and register the Recovery Services agent.
 Test the failover on Azure.
•VMM server: An on-premises VMM server with one or more clouds.
•Hyper-V host or cluster: Hyper-V host servers or clusters managed in VMM
clouds.
•Azure Site Recovery Provider and Recovery services agent: During
deployment, you install the Azure Site Recovery Provider on the VMM server,
and the Microsoft Azure Recovery Services agent on Hyper-V host servers.
The Provider on the VMM server communicates with Site Recovery over
HTTPS 443 to replicate orchestration. The agent on the Hyper-V host server
replicates data to Azure storage over HTTPS 443 by default.
•Azure: You need an Azure subscription, an Azure storage account to store
replicated data, and an Azure virtual network so that Azure VMs are
connected to a network after failover.
• Set up an Azure storage account
• Prepare the VMM server
• Prepare for network mapping
• Create a Recovery Services vault
• Choose your protection goals.
• Set up the source environment.
• Set up the Azure Site Recovery Provider.
• Set up the target environment
• Set up replication settings
• Capacity planning
• Network bandwidth considerations
• Enable replication
• Test your deployment
• Run a test failover
• Monitor your deployment
Azure Site Recovery

Azure Site Recovery

  • 1.
  • 2.
    Azure Site Recoverycontributes to your business continuity and disaster recovery (BCDR )strategy by orchestrating replication of on-premises virtual machines and physical servers. You replicate servers and VMs from your primary on-premises datacenter to the cloud (Azure), or to a secondary datacenter.  Site Recovery can be deployed in both the classic portal and the Azure portal.  Azure classic portal, you can support Site Recovery with the classic services management model.  Azure portal, you can support the classic model, or Resource Manager deployments.
  • 3.
     Azure subscriptionCreation.  Azure VPN Onprem to Azure.  Azure storage account in vault region  Create a Recovery Services vault.  Failover form Azure .  Download the necessary files.  Install and register the Recovery Services agent.  Test the failover on Azure.
  • 5.
    •VMM server: Anon-premises VMM server with one or more clouds. •Hyper-V host or cluster: Hyper-V host servers or clusters managed in VMM clouds. •Azure Site Recovery Provider and Recovery services agent: During deployment, you install the Azure Site Recovery Provider on the VMM server, and the Microsoft Azure Recovery Services agent on Hyper-V host servers. The Provider on the VMM server communicates with Site Recovery over HTTPS 443 to replicate orchestration. The agent on the Hyper-V host server replicates data to Azure storage over HTTPS 443 by default. •Azure: You need an Azure subscription, an Azure storage account to store replicated data, and an Azure virtual network so that Azure VMs are connected to a network after failover.
  • 6.
    • Set upan Azure storage account • Prepare the VMM server • Prepare for network mapping • Create a Recovery Services vault • Choose your protection goals. • Set up the source environment. • Set up the Azure Site Recovery Provider. • Set up the target environment • Set up replication settings • Capacity planning • Network bandwidth considerations • Enable replication • Test your deployment • Run a test failover • Monitor your deployment