This article describes on-premises workloads and apps you can protect for disaster recovery with the Azure Site Recovery service.
![]() -->
Supported Oracle Linux virtual machines on Hyper-V. Are different from the version number on the Microsoft-provided LIS download package. A mismatch doesn't indicate that the built in LIS is out of date. You can disable secure boot in the Firmware section of the settings for the virtual machine in Hyper-V Manager or you can disable it. I have posted similar question on the an Oracle support forum also and have not learned anything there yet either. Maybe Hyper-V R2 is too new for anyone to experiment with the shared disk requirement (between VMs) of muiltiple VMs running Oracle RAC self-contained within physical host (for a Test environment).
Overview
Organizations need a business continuity and disaster recovery (BCDR) strategy to keep workloads and data safe and available during planned and unplanned downtime, and recover to regular working conditions as soon as possible.
Site Recovery is an Azure service that contributes to your BCDR strategy. Using Site Recovery, you can deploy application-aware replication to the cloud, or to a secondary site. Whether your apps are Windows or Linux-based, running on physical servers, VMware or Hyper-V, you can use Site Recovery to orchestrate replication, perform disaster recovery testing, and run failovers and failback.
Site Recovery integrates with Microsoft applications, including SharePoint, Exchange, Dynamics, SQL Server, and Active Directory. Microsoft also works closely with leading vendors including Oracle, SAP, and Red Hat. You can customize replication solutions on an app-by-app basis.
Why use Site Recovery for application replication?
Site Recovery contributes to application-level protection and recovery as follows:
Workload summary
Site Recovery can replicate any app running on a supported machine. In addition, we've partnered with product teams to carry out additional testing for the apps specified in the table.
Replicate Active Directory and DNS
An Active Directory and DNS infrastructure are essential to most enterprise apps. During disaster recovery, you'll need to protect and recover these infrastructure components, before recovering your workloads and apps.
You can use Site Recovery to create a complete automated disaster recovery plan for Active Directory and DNS. For example, if you want to fail over SharePoint and SAP from a primary to a secondary site, you can set up a recovery plan that fails over Active Directory first, and then an additional app-specific recovery plan to fail over the other apps that rely on Active Directory.
Learn more about protecting Active Directory and DNS.
Protect SQL Server
SQL Server provides a data services foundation for data services for many business apps in an on-premises data center. Site Recovery can be used together with SQL Server HA/DR technologies, to protect multi-tiered enterprise apps that use SQL Server. Site Recovery provides:
Learn more about protecting SQL server.
Protect SharePoint
Azure Site Recovery helps protect SharePoint deployments, as follows:
Learn more about protecting SharePoint.
Protect Dynamics AX![]()
Azure Site Recovery helps protect your Dynamics AX ERP solution, by:
Learn more about protecting Dynamic AX.
Protect RDS
Remote Desktop Services (RDS) enables virtual desktop infrastructure (VDI), session-based desktops, and applications, allowing users to work anywhere. With Azure Site Recovery you can:
Set up disaster recovery for RDS using Azure Site Recovery.
Learn more about protecting RDS.
Protect Exchange
Site Recovery helps protect Exchange, as follows:
Learn more about protecting Exchange.
Protect SAP
Use Site Recovery to protect your SAP deployment, as follows:
Learn more about protecting SAP.
Protect IIS
Use Site Recovery to protect your IIS deployment, as follows:
Azure Site Recovery provides disaster recovery by replicating the critical components in your environment to a cold remote site or a public cloud like Microsoft Azure. Since the virtual machines with the web server and the database are being replicated to the recovery site, there is no requirement to backup configuration files or certificates separately. The application mappings and bindings dependent on environment variables that are changed post failover can be updated through scripts integrated into the disaster recovery plans. Virtual machines are brought up on the recovery site only in the event of a failover. Not only this, Azure Site Recovery also helps you orchestrate the end to end failover by providing you the following capabilities:
Learn more about protecting IIS web farm.
Protect Citrix XenApp and XenDesktop
Use Site Recovery to protect your Citrix XenApp and XenDesktop deployments, as follows:
Learn more about protecting Citrix XenApp and XenDesktop deployments. Alternatively, you can refer the whitepaper from Citrix detailing the same.
Next steps
Get started with Azure VM replication.
![]() Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |