Publicité
Check these out next
![[HEWEBAR 2012] Adaptive Images in Responsive Web Design](https://cdn.slidesharecdn.com/ss_thumbnails/hewebar-2012-adaptive-images-in-rwd-120729151800-phpapp02-thumbnail.jpg?width=600&height=600&fit=bounds)
Azure BCDR in Action: From Setup to Failover and Back
23 Mar 2023•0 j'aime•209 vues
0 j'aime
Soyez le premier à aimer ceci
afficher plus
vues
Nombre de vues
0
Sur Slideshare
0
À partir des intégrations
0
Nombre d'intégrations
0
Signaler
Technologie
The slide deck includes screen captures of relevant processes and resource settings, serves as a reference for context and expected results relevant to the referenced workshop. While the deck is not intended to replace the workshop instructions and despite inconsistent resource names in some sections, the process flows with expected resource states are accurately depicted. One may find it handy for realizing the how and what for executing the workshop exercises and tasks.
ssuser6c6f84Suivre
Publicité
Publicité
Publicité
Recommandé
Provisioning, deploying and debugging node.js applications on azurePatriek van Dorp
Hdf installing-hdfnmrrsc
WSO2 Dep Sync for Artifact Synchronization of Cluster NodesWSO2
[WSO2] Deployment Synchronizer for Deployment Artifact Synchronization Betwee...Kasun Gajasinghe
整合Cloud Foundry 和 Kubernetes 技術打造企業級雲應用平台解決方案inwin stack
Windows Azure News - October 2013paulbouwer
Azure BCDR in Action: From Setup to Failover and Back
- Azure BCDR in Action From Setup to Failover and Back Yung Chou Cloud Solution Architect US West
- References • Microsoft Cloud Workshop • Building a resilient IaaS architecture • Selected Readings • Multi-tier web application built for HA/DR • Tutorial: AG in multiple subnets - SQL Server on Azure VMs • Azure Application Architecture Fundamentals • Microsoft Azure Well-Architected Framework • Security documentation • General questions about the Azure Site Recovery service 2 3/17/2023
- Agenda • The app • Architecture and Deployment • SQL AlwaysOn • DR Approach • DR Settings • SQL Back End • Automation and DR Plan • IIS Front End • Failover Test This delivery covers most of Exercise 2 and beyond of the workshop. 3/17/2023 3
- 3/17/2023 4 The following slides are: • Taken from multiple deployments of the workshop • Intended as additional information to facilitate your workshop deployment by providing a reference for the context and expected results These slides are: • NOT for replacing the workshop instructions • With most values if referenced along with the workshop instructions on relevant exercises and tasks Notice while the slides taken from deployments may show resource names inconsistent from one section to another, the process flows with expected resource states remain correctly depicted.
- 3/17/2023 5
- West US3 East US ContosoWebLBPrimary ContosoWebLBSecondary Contoso Front Door Contoso Insurance App • Front Door pointing to Contoso origin • External LB • HTTP only on port 80 • Source and DR sites • Front Door routes • Web/IIS Tier • Zone redundancy • Backup with CRR • Internal LB • Port 1443 from IIS Tier only • Source and DR sites • Data/SQL Tier • Three-node failover cluster • Cloud Witness • Zone redundancy • AlewaysOn with listener on 1443 • One vnet with a DC in each zone • Vnet peering between westus3 and eastus • RSV • Backup RSV in westus3 • Site Recovery RSV in eastus 3/17/2023 9
- Disaster Recovery Approach 10 Tier DR Strategy Web Failover using Azure Site Recovery SQL Secondary SQL AlwaysOn Availability Group replica with asynchronous replication. Failover steps are integrated into Azure Site Recovery using Azure Automation. AD Active-active domain controllers 3/17/2023
- Create a Cloud Witness for SQL Failover Cluster 11 3/17/2023
- Add SQLVMs to Load Balancer Backend Pool 12 3/17/2023
- Create a SQL Failover Cluster (in SQLVM1) New-Cluster -Name AOGCLUSTER -Node SQLVM1,SQLVM2 -StaticAddress 10.0.2.99 13 3/17/2023
- Configure Quorum 14 3/17/2023
- Verify the Quorum 15 3/17/2023
- Enable SQLVM1 AlwaysOn for High Availability 16 3/17/2023
- 17 3/17/2023
- Enable SQLVM2 AlwaysOn for High Availability 19 3/17/2023
- Configure SQL AlwaysOn (with SQLVM1) 21 3/17/2023
- 22 3/17/2023
- 23 3/17/2023
- 24 3/17/2023
- 25 3/17/2023
- 26 3/17/2023
- Add WebVMs to Load Balancer Backend Pool 27 3/17/2023
- RDP into WebVM1 28 3/17/2023
- 29 3/17/2023
- 30 3/17/2023
- RDP into WebVM2 31 3/17/2023
- Contoso Insurance App • External LB • HTTP only on port 80 only • Web/IIS Tier • Zone redundancy • Internal LB • Port 1443 from IIS Tier only • Data/SQL Tier • Two-node failover cluster • Cloud Witness • Zone redundancy • AlewaysOn with listener on 1443 • One vnet with one DC in each zone HTTP Requests 3/17/2023 34
- Contoso Insurance App Deployment Highlights • Contoso.ins • Source in westus3 • contoso-vnet-westus3 • Contoso.ins.DR-Site • DR site in eastus • contoso-vnet-eastus • Contoso.ins.RSV • Backup: contoso-RSV-westus3 • IIS1, IIS2, SQL1 and SQL2 backup • DR: contoso-RSV-eastus • Automation account • Failover runbooks 3/17/2023 35
- 3/17/2023 36
- 3/17/2023 37
- 3/17/2023 38
- 3/17/2023 39
- 3/17/2023 40
- 3/17/2023 41
- 3/17/2023 42
- 43 3/17/2023
- 44 3/17/2023
- Create An Automation (RunAs) Account for Executing DR Runbooks 45 3/17/2023
- DR Runbooks 46 MCW-Building-a-resilient-IaaS-architecture/studentfiles.zip at master · benstegink/MCW-Building-a-resilient-IaaS-architecture (github.com) 3/17/2023
- Import SQL DR Runbooks 47 3/17/2023
- 48 3/17/2023
- 3/17/2023 49
- Import Web DR Runbook 50 3/17/2023
- 51 3/17/2023
- 3/17/2023 52 Repeat the steps to import and published both runbooks.
- Add Automation Variables { "PrimarySiteRG": "contoso-insurance-w3", "PrimarySiteSQLVM1Name": "SQLVM1", "PrimarySiteSQLVM2Name": "SQLVM2", "PrimarySiteSQLPath": "SQLSERVER:SqlSQLVM1DEFAULTAvailabilityGroupssqlAO", "PrimarySiteVNetName": "contoso-insurance-hub-w3", "PrimarySiteWebSubnetName": "Apps", "PrimarySiteWebLBName": "ContosoWebLBPrimary", "SecondarySiteRG": "contoso-insurance-east", "SecondarySiteSQLVMName": "SQLVM3", "SecondarySiteSQLPath": "SQLSERVER:SqlSQLVM3DEFAULTAvailabilityGroupssqlAO", "SecondarySiteVNetName": "contoso-spoke-east", "SecondarySiteWebSubnetName": "Apps", "SecondarySiteWebLBName": "ContosoWebLBSecondary" } 53 3/17/2023
- 54 3/17/2023
- Extend the SQL AlwaysOn Created Earlier to include SQLVM3 to the Always On group as an asynchronous replica 1. In Azure portal, add SQLVM3 to the load-balancer backend pool in the DR site. 2. In SQLVM1, add SQLVM3 to the existing Windows Server Failover Cluster. 3. In SQLVM3, 3nable AlwaysOn and set the domain login credentials. 4. In SQLVM1, • update the Availability Group Listener to include the SQLVM3 IP address, • add SQLVM3 as an asynchronous replica in the existing Always On Availability Group. 5. In SQLVM1, run PowerShell script to update the failover cluster with the Listener IP addresses. 55 3/17/2023
- Add SQLVM3 to DR SQL LB Back End Pool 56 3/17/2023
- Add SQLVM3 to the Failover Cluster • Restart ADs as needed to ensure DNS entries are current • RDP into SQLVM1 and Add-ClusterNode -Name SQLVM3 58 3/17/2023
- Enable SQL AlwaysOn of SQLVM3 60 3/17/2023
- Back to SQLVM1 to Add SQLVM3 as a Replica 61 3/17/2023
- 62 3/17/2023
- 63 3/17/2023
- 64 3/17/2023
- Create Backup and DR Recovery Services Vaults 3/17/2023 68
- 69 3/17/2023
- 70 3/17/2023
- 71 3/17/2023
- 72 3/17/2023
- 73 3/17/2023
- 74 3/17/2023
- 75 3/17/2023
- 3/17/2023 76
- Verify DR Readiness 3/17/2023 77
- 3/17/2023 78
- 3/17/2023 79
- 3/17/2023 80
- 3/17/2023 81
- 3/17/2023 82
- 3/17/2023 83
- 3/17/2023 84
- 3/17/2023 85
- 3/17/2023 86
- 3/17/2023 87
- 3/17/2023 88
- 3/17/2023 89
- 3/17/2023 90
- 3/17/2023 91
- 3/17/2023 92
- 3/17/2023 93
- 3/17/2023 94
- 3/17/2023 96
- 3/17/2023 97
- 3/17/2023 98
- 3/17/2023 99
- 3/17/2023 100
- 3/17/2023 101
- 3/17/2023 102
- 3/17/2023 103
- 3/17/2023 104
- 3/17/2023 105
- 3/17/2023 106
- 3/17/2023 107
- 3/17/2023 108
- 3/17/2023 109
- 3/17/2023 110
- 3/17/2023 111
- 3/17/2023 112
- 3/17/2023 113
- 3/17/2023 114
- 3/17/2023 115
- 3/17/2023 116
- 3/17/2023 117
- 3/17/2023 118
- 3/17/2023 119
- 3/17/2023 120
- 3/17/2023 121
- 3/17/2023 122
- 3/17/2023 123
- 3/17/2023 124
- 3/17/2023 125
- 3/17/2023 126
- 3/17/2023 127
- 3/17/2023 128
- 3/17/2023 129
- 3/17/2023 130
- 3/17/2023 131
- 3/17/2023 132
- 3/17/2023 133
- 3/17/2023 134
- 3/17/2023 135
- 3/17/2023 136
- 3/17/2023 137
- 3/17/2023 138
- 3/17/2023 139
- 3/17/2023 140
- 3/17/2023 141
- 3/17/2023 142
- 3/17/2023 143
- 3/17/2023 144
- 3/17/2023 145
- 3/17/2023 146
- 3/17/2023 147
- 3/17/2023 148
- 3/17/2023 149
- 3/17/2023 150
- 3/17/2023 151
- 3/17/2023 152
- 3/17/2023 153
- 3/17/2023 154
- 3/17/2023 155
- 3/17/2023 156
- 3/17/2023 157
- 3/17/2023 158
- 3/17/2023 159
- 3/17/2023 161
- 3/17/2023 162
- 3/17/2023 163
- 3/17/2023 164
- 3/17/2023 165
- 3/17/2023 166
- 3/17/2023 167
- 3/17/2023 168
- 3/17/2023 169
- 3/17/2023 170
- 3/17/2023 171
- 3/17/2023 172
- 3/17/2023 173
- Step Description Documentation Reference Test Test the ASR configuration routinely and often for failing over from source site to DR one to ensure it works as expected Run a test failover (disaster recovery drill) to ASR Failover Initiate failover to switch over to the replicated environment for DR or planned maintenance About failover and failback in ASR - Modernized - ASR Commit Commit the changes made during the failover process to the replicated environment to ensure it's up-to-date Run a failover during disaster recovery with ASR Re-protect Re-protect the production environment to ensure it's ready for the next failover Reprotect Azure VMs to the primary region with ASR Re-test Re-test the ASR configuration to ensure it works as expected after re-protecting Fall back Fall back to the production environment if the failover was initiated for planned maintenance or testing Re-commit Re-commit the changes made during the failover process to the production environment to ensure it's up-to-date Re-protect Re-protect the replicated environment to ensure it's ready for the next failover after falling back Failover/Failback Routine 3/17/2023 174
Notes de l'éditeur
- In my experience, many companies viewed implementing Business Continuity and Disaster Recovery (BCDR) as too technically complex and financially unfeasible, resulting in it becoming more of an academic exercise than an attainable, predictable, measurable, and verifiable business process. With Azure Recovery Services, I have found this perception no longer accurate. I used the Microsoft Cloud Workshop to showcase Azure BCDR with step-by-step guidance to Configure a DR plan for a database app in Azure West US 3 region Drill/rehearse the plan to failover the app to Azure East US region is a DR scenario Execute a failover to mimic conducting a DR episode Commit the failover upon verifying the plan executed with expected results Later Follow a series of steps for reversing and falling back the app to its original region, West US 3 Reenable the protection, i.e., DR pan, and ensure readiness for future DR needs The slide deck includes screen captures of relevant processes and resource settings, serves as a reference for context and expected results. While the deck is not intended to replace the workshop instructions and despite inconsistent resource names in some sections, the process flows with expected resource states are accurately depicted. One may find it handy for realizing the how and what of executing the workshop exercises and tasks.
- Upon deployed the application, ContosoWebLBPrimaryIP has the public IP and the DNS name of the app. The landing page here is slightly different from that provided by the workshop.
- Policy page
- Customer info page
- Policy Holder page
- The presented demo infrastructure is not necessarily a recommendation. For instance, instead of internal LB, another option may be https://learn.microsoft.com/en-us/azure/architecture/example-scenario/infrastructure/multi-tier-app-disaster-recovery
- Enable Disaster Recovery for the Contoso application https://github.com/microsoft/MCW-Building-a-resilient-IaaS-architecture/blob/master/Hands-on%20lab/HOL%20step-by%20step%20-%20Building%20a%20resilient%20IaaS%20architecture.md#exercise-2-enable-disaster-recovery-for-the-contoso-application
- Configure HA for the SQL Server tier https://github.com/microsoft/MCW-Building-a-resilient-IaaS-architecture/blob/master/Hands-on%20lab/HOL%20step-by%20step%20-%20Building%20a%20resilient%20IaaS%20architecture.md#task-3-configure-ha-for-the-sql-server-tier
- https://github.com/microsoft/MCW-Building-a-resilient-IaaS-architecture/blob/master/Hands-on%20lab/HOL%20step-by%20step%20-%20Building%20a%20resilient%20IaaS%20architecture.md#task-3-configure-ha-for-the-sql-server-tier
- https://github.com/microsoft/MCW-Building-a-resilient-IaaS-architecture/blob/master/Hands-on%20lab/HOL%20step-by%20step%20-%20Building%20a%20resilient%20IaaS%20architecture.md#task-3-configure-ha-for-the-sql-server-tier BCDR DEMO GITHUB REPO https://github.com/Microsoft/MCW-Building-A-Resilient-IaaS-Architecture Suggest using: westus3 and eastus New-Cluster -Name AOGCLUSTER -Node SQLVM1,SQLVM2 -StaticAddress 10.0.2.99
- Select the Subnet of 10.0.2.0/24 and then add IPv4 10.0.2.100 and select OK. This is the IP address of the Internal Load Balancer that is in front of the SQLVM1 and SQLVM2 in the Data subnet running in the Primary Site.
- SQLAlwaysOn
- 10.0.2.100
- The automation account and associated runbooks can be placed in any region other than the source/primary region, as in DR the source/primary region is expected experiencing an outage.
- Bastion host names are difference due to an unplanned redeployment on Bastion in westus3.
- Location: Any region that support automation except for your primary region.
- Repeat the steps to import and published both runbooks.
- Configure DR for the SQL Server tier https://github.com/microsoft/MCW-Building-a-resilient-IaaS-architecture/blob/master/Hands-on%20lab/HOL%20step-by%20step%20-%20Building%20a%20resilient%20IaaS%20architecture.md#task-3-configure-dr-for-the-sql-server-tier
- Add-ClusterNode -Name SQLVM3
- Enable Disaster Recovery for the Contoso application https://github.com/microsoft/MCW-Building-a-resilient-IaaS-architecture/blob/master/Hands-on%20lab/HOL%20step-by%20step%20-%20Building%20a%20resilient%20IaaS%20architecture.md#exercise-2-enable-disaster-recovery-for-the-contoso-application
- https://github.com/microsoft/MCW-Building-a-resilient-IaaS-architecture/blob/master/Hands-on%20lab/HOL%20step-by%20step%20-%20Building%20a%20resilient%20IaaS%20architecture.md#task-4-configure-dr-for-the-web-tier
- Exercise 3: Enable Backup for the Contoso application https://github.com/microsoft/MCW-Building-a-resilient-IaaS-architecture/blob/master/Hands-on%20lab/HOL%20step-by%20step%20-%20Building%20a%20resilient%20IaaS%20architecture.md#exercise-3-enable-backup-for-the-contoso-application
- Task 3: Enable Backup for the SQL Server tier https://github.com/microsoft/MCW-Building-a-resilient-IaaS-architecture/blob/master/Hands-on%20lab/HOL%20step-by%20step%20-%20Building%20a%20resilient%20IaaS%20architecture.md#task-3-enable-backup-for-the-sql-server-tier AS NEEDED Register-AzResourceProvider -ProviderNamespace Microsoft.SqlVirtualMachine New-AzSqlVM -Name ‘ci-sql1' -ResourceGroupName ‘ci-w3' -SqlManagementType Full -Location ‘westus3' -LicenseType PAYG New-AzSqlVM -Name ‘ci-sql2' -ResourceGroupName ‘ci-w3' -SqlManagementType Full -Location ‘westus3' -LicenseType PAYG New-AzSqlVM -Name ‘ci-sql3' -ResourceGroupName ‘ci-eus' -SqlManagementType Full -Location ‘eastus' -LicenseType PAYG
- Task 5: Configure a public endpoint using Azure Front Door https://github.com/microsoft/MCW-Building-a-resilient-IaaS-architecture/blob/master/Hands-on%20lab/HOL%20step-by%20step%20-%20Building%20a%20resilient%20IaaS%20architecture.md#task-5-configure-a-public-endpoint-using-azure-front-door
- Task 2: Validate Disaster Recovery - Failover IaaS region to region https://github.com/microsoft/MCW-Building-a-resilient-IaaS-architecture/blob/master/Hands-on%20lab/HOL%20step-by%20step%20-%20Building%20a%20resilient%20IaaS%20architecture.md#task-2-validate-disaster-recovery---failover-iaas-region-to-region
- Task 2: Validate Disaster Recovery - Failover IaaS region to region https://github.com/microsoft/MCW-Building-a-resilient-IaaS-architecture/blob/master/Hands-on%20lab/HOL%20step-by%20step%20-%20Building%20a%20resilient%20IaaS%20architecture.md#task-2-validate-disaster-recovery---failover-iaas-region-to-region
Publicité