resolved the conflicts I inadvertently created
This commit is contained in:
Ben Stegink
Родитель
6784907d04
Коммит
7541fa356e
|
|
@ -19,7 +19,7 @@ Microsoft may have patents, patent applications, trademarks, copyrights, or othe
|
|||
|
||||
The names of manufacturers, products, or URLs are provided for informational purposes only and Microsoft makes no representations and warranties, either expressed, implied, or statutory, regarding these manufacturers or the use of the products with any Microsoft technologies. The inclusion of a manufacturer or product does not imply endorsement of Microsoft of the manufacturer or product. Links may be provided to third party sites. Such sites are not under the control of Microsoft and Microsoft is not responsible for the contents of any linked site or any link contained in a linked site, or any changes or updates to such sites. Microsoft is not responsible for webcasting or any other form of transmission received from any linked site. Microsoft is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement of Microsoft of the site or the products contained therein.
|
||||
|
||||
© 2021 Microsoft Corporation. All rights reserved.
|
||||
© 2022 Microsoft Corporation. All rights reserved.
|
||||
|
||||
Microsoft and the trademarks listed at https://www.microsoft.com/en-us/legal/intellectualproperty/Trademarks/Usage/General.aspx are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.
|
||||
|
||||
|
|
@ -27,9 +27,9 @@ Microsoft and the trademarks listed at https://www.microsoft.com/en-us/legal/int
|
|||
|
||||
<!-- TOC -->
|
||||
|
||||
[Building a resilient IaaS architecture hands-on lab step-by-step](#building-a-resilient-iaas-architecture-hands-on-lab-step-by-step)
|
||||
[Abstract and learning objectives](#abstract-and-learning-objectives)
|
||||
[Overview](#overview)
|
||||
- [Building a resilient IaaS architecture hands-on lab step-by-step](#building-a-resilient-iaas-architecture-hands-on-lab-step-by-step)
|
||||
- [Abstract and learning objectives](#abstract-and-learning-objectives)
|
||||
- [Overview](#overview)
|
||||
- [Solution architecture](#solution-architecture)
|
||||
- [Requirements](#requirements)
|
||||
- [Help references](#help-references)
|
||||
|
|
@ -65,7 +65,7 @@ Microsoft and the trademarks listed at https://www.microsoft.com/en-us/legal/int
|
|||
|
||||
In this hands-on lab, you will deploy a pre-configured IaaS environment and then redesign and update it to account for resiliency and high availability. Throughout the hands-on lab, you will use various configuration options and services to help build a resilient architecture.
|
||||
|
||||
At the end of the lab, you will be better able to design and use availability zones, SQL Server Always On Availability Groups, Azure Site Recovery, Azure Backup, and Azure Front Door to implement a fully resilient IaaS application. The training includes content on high availability, disaster recovery, as well as knowledge on how to back up the databases and virtual machines.
|
||||
At the end of the lab, you will be better able to design and use availability zones, SQL Server Always On Availability Groups, Azure Site Recovery, Azure Backup, and Azure Front Door to implement a fully resilient IaaS application. The training includes content on high availability, disaster recovery, as well as knowledge of how to back up the databases and virtual machines.
|
||||
|
||||
## Overview
|
||||
|
||||
|
|
@ -126,11 +126,11 @@ A template will be used to save time. You will configure each tier in subsequent
|
|||
|
||||
The template contains five child templates, containing the various resources required for:
|
||||
|
||||
- The ADVM2 virtual machine, which will be a second Domain Controller
|
||||
- The SQLVM2 virtual machine, which will be a second SQL Server
|
||||
- The WebVM2 virtual machine, which will be a second web server
|
||||
- Two load balancers, one for the web tier and one for the SQL tier
|
||||
- The virtual network with the proper DNS configuration in place
|
||||
- The ADVM2 virtual machine, which will be a second Domain Controller.
|
||||
- The SQLVM2 virtual machine, which will be a second SQL Server.
|
||||
- The WebVM2 virtual machine, which will be a second web server.
|
||||
- Two load balancers, one for the web tier and one for the SQL tier.
|
||||
- The virtual network with the proper DNS configuration in place.
|
||||
|
||||
4. You can check the HA resource deployment status by navigating to the **ContosoRG1** resource group, selecting **Deployments** in the resource group left-nav, and checking the status of the deployments. Make sure the deployment status is **Succeeded** for all templates before proceeding to the next task.
|
||||
|
||||
|
|
@ -162,8 +162,8 @@ In this task, you will build a Windows Failover Cluster and configure SQL Always
|
|||
2. Complete the **Create storage account** form using the following details:
|
||||
|
||||
- **Resource group**: Use existing / ContosoRG1
|
||||
- **Storage account name:** Unique name starting with `contososqlwitness`
|
||||
- **Location**: Any location in your area that is **NOT** your Primary or Secondary site, for example **West US 2**
|
||||
- **Storage account name**: Unique name starting with `contososqlwitness`
|
||||
- **Location**: Any location in your area that is **NOT** your Primary or Secondary site, for example **West US 3**.
|
||||
- **Performance**: Standard
|
||||
- **Replication**: Zone-redundant storage (ZRS)
|
||||
- **Access tier (default)**: Hot
|
||||
|
|
@ -172,9 +172,9 @@ In this task, you will build a Windows Failover Cluster and configure SQL Always
|
|||
|
||||
3. Switch to the **Advanced** tab. Change the **Minimum TLS version** to **Version 1.0**. Then select **Review + Create**, followed by **Create**.
|
||||
|
||||
|
||||
|
||||
|
||||
> **Note:** To promote the use of the latest and most secure standards, by default, Azure storage accounts require TLS version 1.2. This storage account will be used as a Cloud Witness for our SQL Server cluster. SQL Server requires TLS version 1.0 for the Cloud Witness.
|
||||
> **Note**: To promote the use of the latest and most secure standards, by default, Azure storage accounts require TLS version 1.2. This storage account will be used as a Cloud Witness for our SQL Server cluster. SQL Server requires TLS version 1.0 for the Cloud Witness.
|
||||
|
||||
4. Once the storage account is created, navigate to the storage account blade. Select **Access keys** under **Security + networking**. Toggle the **Show/Hide keys button** (Shown as hide keys in the screenshot), copy the **storage account name** and the **first access key**, and paste them into your text editor of choice - you will need these values later.
|
||||
|
||||
|
|
@ -188,7 +188,7 @@ In this task, you will build a Windows Failover Cluster and configure SQL Always
|
|||
|
||||
|
||||
|
||||
> **Note:** The load-balancing rule in the load balancer has been created with **Floating IP (direct server return)** enabled. This is important when using the Azure load balancer for SQL Server AlwaysOn Availability Groups.
|
||||
> **Note**: The load-balancing rule in the load balancer has been created with **Floating IP (direct server return)** enabled. This is important when using the Azure load balancer for SQL Server AlwaysOn Availability Groups.
|
||||
|
||||
7. From the Azure portal, navigate to the **SQLVM1** virtual machine. Select **Connect**, then choose **Bastion**.
|
||||
|
||||
|
|
@ -199,7 +199,7 @@ In this task, you will build a Windows Failover Cluster and configure SQL Always
|
|||
- **Username**: `demouser@contoso.com`
|
||||
- **Password**: `Demo!pass123`
|
||||
|
||||
> **Note:** When using Azure Bastion to connect to a VM using domain credentials, the username must be specified in the format `user@domain-fqdn` and **not** in the format `domain\user`.
|
||||
> **Note**: When using Azure Bastion to connect to a VM using domain credentials, the username must be specified in the format `user@domain-fqdn` and **not** in the format `domain\user`.
|
||||
|
||||
|
||||
|
||||
|
|
@ -215,7 +215,7 @@ In this task, you will build a Windows Failover Cluster and configure SQL Always
|
|||
|
||||
|
||||
|
||||
>**Note:** It is possible to use a wizard for this task, but the resulting cluster will require additional configuration to set the static IP address in Azure.
|
||||
>**Note**: It is possible to use a wizard for this task, but the resulting cluster will require additional configuration to set the static IP address in Azure.
|
||||
|
||||
11. After the cluster has been created, select **Start** and then **Windows Administrative Tools**. Locate and open the **Failover Cluster Manager**.
|
||||
|
||||
|
|
@ -317,7 +317,7 @@ In this task, you will build a Windows Failover Cluster and configure SQL Always
|
|||
|
||||
35. On the **Connect to Server** dialog box, enter the Server Name of **SQLVM2**and select **Connect**. **Note**: The username for your lab should show **CONTOSO\demouser**.
|
||||
|
||||
|
||||
|
||||
|
||||
36. For **SQLVM2**, select Automatic Failover and Availability Mode of Synchronous commit.
|
||||
|
||||
|
|
@ -413,7 +413,7 @@ In this task, you will build a Windows Failover Cluster and configure SQL Always
|
|||
|
||||
|
||||
|
||||
> **Note:** It could take a minute to connect the first time as this goes through the Azure Internal Load Balancer.
|
||||
> **Note**: It could take a minute to connect the first time as this goes through the Azure Internal Load Balancer.
|
||||
|
||||
56. Move back to Failover Cluster Manager on **SQLVM1**, and you can review the IP Addresses that were added by selecting Roles and **BCDRAOG** and viewing the Resources. Notice how the **10.0.2.100** is Online.
|
||||
|
||||
|
|
@ -456,7 +456,7 @@ In this task, you will configure a high-availability web tier. This comprises tw
|
|||
|
||||
|
||||
|
||||
> **Note:** You will test the HA capabilities later in the lab.
|
||||
> **Note**: You will test the HA capabilities later in the lab.
|
||||
|
||||
## Exercise 2: Enable Disaster Recovery for the Contoso application
|
||||
|
||||
|
|
@ -489,7 +489,7 @@ In this task, you will deploy the resources used by the DR environment. First, y
|
|||
-Location 'East US 2'
|
||||
```
|
||||
|
||||
> **Note:** If your deployment fails with an error *`"The requested size for resource '<resourceID>' is currently not available"`*, add the parameter `-skuSizeVM 'D2s_v5'` to the end of the `New-AzSubscriptionDeployment` and rerun the command:
|
||||
> **Note**: If your deployment fails with an error *`"The requested size for resource '<resourceID>' is currently not available"`*, add the parameter `-skuSizeVM 'D2s_v5'` to the end of the `New-AzSubscriptionDeployment` and rerun the command:
|
||||
|
||||
```powershell
|
||||
# Only run this command if the previous deployment failed with an error that size was not available
|
||||
|
|
@ -499,10 +499,10 @@ In this task, you will deploy the resources used by the DR environment. First, y
|
|||
```
|
||||
|
||||
3. Take a few minutes to review the template while it deploys. Navigate to the Azure portal home page, select **Subscriptions**, then **Deployments** to review the template and deployment progress. Note that the template includes:
|
||||
- A DR virtual network, which is connected using VNet peering to the existing virtual network
|
||||
- Two additional domain controller VMs, **ADVM3** and **ADVM4**
|
||||
- An additional SQL Server VM, **SQLVM3**
|
||||
- Azure Bastion, to enable VM access
|
||||
- A DR virtual network, which is connected using VNet peering to the existing virtual network.
|
||||
- Two additional domain controller VMs, **ADVM3** and **ADVM4**.
|
||||
- An additional SQL Server VM, **SQLVM3**.
|
||||
- Azure Bastion, to enable VM access.
|
||||
|
||||
|
||||
|
||||
|
|
@ -526,7 +526,7 @@ In this task, you will deploy the resources used by the DR environment. First, y
|
|||
|
||||
|
||||
|
||||
> **Important:** Next, you will set up the Azure Automation account that will be used to automate certain failover and failback tasks. This will require several PowerShell scripts to be imported as Azure Automation runbooks. **Be sure to execute the following steps from the LabVM since that is where the scripts are located.**
|
||||
> **Important**: Next, you will set up the Azure Automation account that will be used to automate certain failover and failback tasks. This will require several PowerShell scripts to be imported as Azure Automation runbooks. **Be sure to execute the following steps from the LabVM since that is where the scripts are located.**
|
||||
|
||||
8. From the Azure portal, select **+Create a resource**, followed by **IT & Management Tools**, then **Automation**.
|
||||
|
||||
|
|
@ -538,7 +538,7 @@ In this task, you will deploy the resources used by the DR environment. First, y
|
|||
|
||||
|
||||
|
||||
> **Note:** Azure Automation accounts are only allowed to be created in certain Azure regions, but they can act on any region in Azure (except Government, China, or Germany). It is not required to have your Azure Automation account in the same region as the failover resources, but it **CANNOT** be in your primary region.
|
||||
> **Note**: Azure Automation accounts are only allowed to be created in certain Azure regions, but they can act on any region in Azure (except Government, China, or Germany). It is not required to have your Azure Automation account in the same region as the failover resources, but it **CANNOT** be in your primary region.
|
||||
|
||||
10. Once the Azure automation account has been created, select **Run as accounts** under **Account Settings**. Then, select **Create** under **Azure Run as Account**.
|
||||
|
||||
|
|
@ -570,7 +570,7 @@ In this task, you will deploy the resources used by the DR environment. First, y
|
|||
|
||||
> **Note**: You must be connected to the **LABVM** to complete the next steps.
|
||||
|
||||
17. Select the **Folder** icon on the Import blade and select the file **ASRRunbookSQL.ps1** from the `C:\HOL\` directory on the **LABVM**. Update the name to be **ASRSQLFailover**. Set the Runbook type to **PowerShell Workflow**. This is the name of the Workflow inside the Runbook script. Leave everything else set to the default. Select **Import**.
|
||||
17. Select the **Folder** icon on the Import blade and select the file **ASRRunbookSQL.ps1** from the `C:\HOL\` directory on the **LABVM**. Set the Runbook type to **PowerShell Workflow**. Update the name to **ASRSQLFailover**. This is the name of the Workflow inside the Runbook script. Leave everything else set to the default. Select **Import**.
|
||||
|
||||
|
||||
|
||||
|
|
@ -584,7 +584,7 @@ In this task, you will deploy the resources used by the DR environment. First, y
|
|||
|
||||
|
||||
|
||||
> **Note:** When you configure the ASR Recovery Plan for the IaaS deployment, you will use the SQL Runbook as a Pre-Failover Action and the Web Runbook as a Post-Failover action. They will run both ways and have been written to take the "Direction" of the failover into account when running.
|
||||
> **Note**: When you configure the ASR Recovery Plan for the IaaS deployment, you will use the SQL Runbook as a Pre-Failover Action and the Web Runbook as a Post-Failover action. They will run both ways and have been written to take the "Direction" of the failover into account when running.
|
||||
|
||||
Next, you will create a variable in Azure Automation that contains settings (such as resource group names and VM names) that describe your environment. This information is required by the runbooks you imported. Using variables allows you to avoid hard-coding this information in the runbooks themselves.
|
||||
|
||||
|
|
@ -630,7 +630,7 @@ The configuration of these domain controllers is fully automatic. In this task,
|
|||
|
||||
1. From the Azure portal home page, select **Subscriptions**, choose your subscription, select **Deployments**, then open the **Contoso-IaaS-DR** deployment used for the DR site.
|
||||
|
||||
|
||||
|
||||
|
||||
2. Select **Template** and review the template contents. Note the use of `dependsOn` to carefully control the deployment sequence. The resources are deployed as follows:
|
||||
|
||||
|
|
@ -676,7 +676,7 @@ This task comprises the following steps:
|
|||
|
||||
|
||||
|
||||
> **Note:** For this lab, the DR site is configured with a single SQL Server VM. Using a load balancer is therefore not strictly required. However, it allows the DR site to be extended to include its own HA cluster if needed.
|
||||
> **Note**: For this lab, the DR site is configured with a single SQL Server VM. Using a load balancer is therefore not strictly required. However, it allows the DR site to be extended to include its own HA cluster if needed.
|
||||
|
||||
3. Return to your browser tab containing your Bastion session with **SQLVM1**. (If you have closed the tab, reconnect using Azure Bastion with username `demouser@contoso.com` and password `Demo!pass123`.)
|
||||
|
||||
|
|
@ -823,7 +823,7 @@ Custom scripts in Azure Automation are called by Azure Site recovery to add the
|
|||
|
||||
|
||||
|
||||
6. Update the blade using the following inputs:
|
||||
6. Update the blade using the following:
|
||||
|
||||
- **Target resource group**: ContosoRG2
|
||||
- **Target virtual network**: VNet2
|
||||
|
|
@ -838,7 +838,7 @@ Custom scripts in Azure Automation are called by Azure Site recovery to add the
|
|||
|
||||
|
||||
|
||||
8. Under 'Extension settings', select **\[+\] Show details**. Change the **Automation Account** to use your existing Automation Account
|
||||
8. Under 'Extension settings', select **\[+\] Show details**. Change the **Automation Account** to use your existing Automation Account.
|
||||
|
||||
|
||||
|
||||
|
|
@ -852,7 +852,7 @@ Custom scripts in Azure Automation are called by Azure Site recovery to add the
|
|||
|
||||
11. The **BCDRRSV** blade should still have the **Site Recovery** option (under 'Getting started') selected. Select **Step 2: Manage Recovery Plans**.
|
||||
|
||||
|
||||
|
||||
|
||||
12. Select **+Recovery plan**.
|
||||
|
||||
|
|
@ -861,14 +861,14 @@ Custom scripts in Azure Automation are called by Azure Site recovery to add the
|
|||
13. Fill in the **Create recovery plan** blade as follows:
|
||||
|
||||
- **Name**: BCDRIaaSPlan
|
||||
- **Source**: Central US *(This is your primary region)*
|
||||
- **Target**: East US 2 *(This is your secondary region)*
|
||||
- **Source**: Central US *(This is your primary region.)*
|
||||
- **Target**: East US 2 *(This is your secondary region.)*
|
||||
- **Allow items with deployment model**: Resource Manager
|
||||
- **Select Items**: Select **WebVM1** and **WebVM2**
|
||||
- **Select Items**: Select **WebVM1** and **WebVM2**.
|
||||
|
||||
|
||||
|
||||
> **Note:** It is **critical** to use the correct recovery plan name `BCDRIaaSPlan`. This plan name must match the name of the Azure Automation variable you created in the first task in this exercise.
|
||||
> **Note**: It is **critical** to use the correct recovery plan name `BCDRIaaSPlan`. This plan name must match the name of the Azure Automation variable you created in the first task in this exercise.
|
||||
|
||||
14. Select **Create** to create the recovery plan. After a moment, the **BCDRIaaSPlan** Recovery plan will appear. Select it to review.
|
||||
|
||||
|
|
@ -876,39 +876,41 @@ Custom scripts in Azure Automation are called by Azure Site recovery to add the
|
|||
|
||||
15. When the **BCDRIaaSPlan** loads **notice**, it shows **2 VMs in the Source**, which is your **Primary** Site.
|
||||
|
||||
You will now customize the recovery plan to trigger the SQL failover and configure the web tier load-balancer during the failover process; select **Customize**.
|
||||
16. You will now customize the recovery plan to trigger the SQL failover and configure the web tier load-balancer during the failover process; select **Customize**.
|
||||
|
||||
|
||||
|
||||
16. Once the **BCDRIaaSPlan** blade loads, select the **ellipsis** next to **All groups failover**, then select **Add pre-action** from the context menu.
|
||||
17. Once the **BCDRIaaSPlan** blade loads, select the **ellipsis** next to **All groups failover**, then select **Add pre-action** from the context menu.
|
||||
|
||||
|
||||
|
||||
17. On the **Insert action** blade, select **Script** and then provide the name `ASRSQLFailover`. Ensure that your Azure Automation account is selected, and then choose the Runbook name: **ASRSQFailover**. Select **OK**.
|
||||
> **Note:** If nothing happens, select the **X** in the upper right corner and select **OK** when asked about discarding your changes. You will notice that the script is still added to the recovery plan.
|
||||
18. On the **Insert action** blade, select **Script** and then provide the name `ASRSQLFailover`. Ensure that your Azure Automation account is selected, and then choose the Runbook name: **ASRSQFailover**. Select **OK**.
|
||||
|
||||
> **Note**: If nothing happens, select the **X** in the upper right corner and select **OK** when asked about discarding your changes. You will notice that the script is still added to the recovery plan.
|
||||
|
||||
|
||||
|
||||
> **Note:** As noted on the 'Insert action' blade, the ASRSQLFailover runbook will be executed on both failover and failback. The runbook has been written to support both scenarios.
|
||||
> **Note**: As noted on the 'Insert action' blade, the ASRSQLFailover runbook will be executed on both failover and failback. The runbook has been written to support both scenarios.
|
||||
|
||||
18. Once the **BCDRIaaSPlan** blade loads, select the **ellipsis** next to **Group 1: Start**, then select **Add post action** from the context menu.
|
||||
19. Once the **BCDRIaaSPlan** blade loads, select the **ellipsis** next to **Group 1: Start**, then select **Add post action** from the context menu.
|
||||
|
||||
|
||||
|
||||
19. On the **Insert action** blade, select **Script** and then provide the name: **ASRWEBFailover.** Ensure that your Azure Automation account is selected and then choose the Runbook name: **ASRWEBFailover**. Select **OK**.
|
||||
> **Note:** If nothing happens, select the **X** in the upper right corner and select **OK** when asked about discarding your changes. You'll notice that the script is still added to the recovery plan.
|
||||
20. On the **Insert action** blade, select **Script** and then provide the name: **ASRWEBFailover.** Ensure that your Azure Automation account is selected and then choose the Runbook name: **ASRWEBFailover**. Select **OK**.
|
||||
|
||||
> **Note**: If nothing happens, select the **X** in the upper right corner and select **OK** when asked about discarding your changes. You'll notice that the script is still added to the recovery plan.
|
||||
|
||||
|
||||
|
||||
20. Make sure that your **Pre-steps** are running under **All groups failover** and the **Post-steps** are running under **Group1: Start**. Select **Save**.
|
||||
21. Make sure that your **Pre-steps** are running under **All groups failover** and the **Post-steps** are running under **Group1: Start**. Select **Save**.
|
||||
|
||||
|
||||
|
||||
21. After a minute, the portal will provide a successful update notification. This means that your recovery plan is fully configured and ready to failover and back between the primary and secondary regions.
|
||||
22. After a minute, the portal will provide a successful update notification. This means that your recovery plan is fully configured and ready to failover and back between the primary and secondary regions.
|
||||
|
||||
|
||||
|
||||
22. Return to the Recovery Services Vault **BCDRRSV** blade and select the **Replicated Items** link under **Protected Items**. You should see **WebVM1** and **WebVM2**. The Replication Health should be **Healthy**. The Status will show the replication progress. Once both VMs show status **Protected** replication is complete, you will be able to test the failover.
|
||||
23. Return to the Recovery Services Vault **BCDRRSV** blade and select the **Replicated Items** link under **Protected Items**. You should see **WebVM1** and **WebVM2**. The Replication Health should be **Healthy**. The Status will show the replication progress. Once both VMs show status **Protected** replication is complete, you will be able to test the failover.
|
||||
|
||||
|
||||
|
||||
|
|
@ -942,12 +944,12 @@ In this task, you will use the Front Door approach to configure a highly availab
|
|||
|
||||
|
||||
|
||||
4. Select **Next: Endpoint >**
|
||||
4. Select **Next: Endpoint >**.
|
||||
|
||||
5. Select **Add an endpoint** to set the hostname of Front Door. In the **Add an endpoint** pane, enter the following values, then select **Add**:
|
||||
|
||||
- **Endpoint name**: `contosoiaas`
|
||||
- **Status**: Leave **Enable this endpoint** selected
|
||||
- **Status**: Leave **Enable this endpoint** selected.
|
||||
|
||||
|
||||
|
||||
|
|
@ -985,13 +987,13 @@ In this task, you will use the Front Door approach to configure a highly availab
|
|||
|
||||
|
||||
|
||||
13. Enter the following values in **Add a route**. Leave all other values as default. Select **Add**
|
||||
13. Enter the following values in **Add a route**. Leave all other values as default. Select **Add**.
|
||||
|
||||
- Name: `ContosoRoute`
|
||||
- Accepted protocols: HTTP only
|
||||
- Redirect: Uncheck **Redirect all traffic to use HTTPS**
|
||||
- Origin group: ensure **ContosoOrigins** is selected
|
||||
- Forwarding protocol: HTTP only
|
||||
- **Name**: `ContosoRoute`
|
||||
- **Accepted protocols**: HTTP only
|
||||
- **Redirect**: Uncheck **Redirect all traffic to use HTTPS**.
|
||||
- **Origin group**: Ensure **ContosoOrigins** is selected.
|
||||
- **Forwarding protocol**: HTTP only
|
||||
|
||||
|
||||
|
||||
|
|
@ -1005,8 +1007,8 @@ In this task, you will use the Front Door approach to configure a highly availab
|
|||
|
||||
|
||||
|
||||
> **Note:** Be sure to use **HTTP** to access the Azure Front Door **frontend host** URL. The lab configurations only support HTTP for Front Door since WebVM1 and WebVM2 are only set up for HTTP support, not HTTPS (no SSL\TLS).
|
||||
> **Note:** If you get an "Our services aren't available right now" error (or a 404-type error) accessing the web application, then continue with the lab and come back to this later. Sometime this can take a ~10 minutes for the routing rules to publish before it's "live".
|
||||
> **Note**: Be sure to use **HTTP** to access the Azure Front Door **frontend host** URL. The lab configurations only support HTTP for Front Door since WebVM1 and WebVM2 are only set up for HTTP support, not HTTPS (no SSL\TLS).
|
||||
> **Note**: If you get an "Our services aren't available right now" error (or a 404-type error) accessing the web application, then continue with the lab and come back to this later. Sometime this can take a ~10 minutes for the routing rules to publish before it's "live".
|
||||
>
|
||||
> If you continue to have this issue beyond 15 minutes, ensure that you are using the correct backend host header (Step 5) and using HTTP for both the routing rules and the health probes of the backend pools. (Step 4).
|
||||
>
|
||||
|
|
@ -1042,13 +1044,13 @@ Azure Backup and Azure Site Recovery are implemented using the same Azure resour
|
|||
|
||||
|
||||
|
||||
> **Note:** This enables backups from the primary site to be restored in the DR site if required.
|
||||
> **Note**: This enables backups from the primary site to be restored in the DR site if required.
|
||||
|
||||
5. Still in the BackupRSV Properties blade, under **Security Settings**, select **Update**. Under Soft Delete, select **Disabled**, then **Save** your changes and close the Security Settings panel.
|
||||
|
||||
|
||||
|
||||
> **Note:** In a production environment, you should leave Soft Delete enabled. However, it is better to disable this feature for this lab since leaving it enabled makes it more difficult to clean up your lab resources once the lab is complete.
|
||||
> **Note**: In a production environment, you should leave Soft Delete enabled. However, it is better to disable this feature for this lab since leaving it enabled makes it more difficult to clean up your lab resources once the lab is complete.
|
||||
|
||||
### Task 2: Enable Backup for the Web tier
|
||||
|
||||
|
|
@ -1061,7 +1063,7 @@ In this task, you will configure Azure Backup for the Web tier virtual machines.
|
|||
2. On the 'Configure Backup' blade, Leave **Standard** selected and select **Create a new policy** and fill in the Create Policy blade as follows:
|
||||
|
||||
- **Policy name**: `WebVMPolicy`
|
||||
- **Backup schedule**: Daily, 9pm, UTC
|
||||
- **Backup schedule**: Daily, 9:00 PM, UTC
|
||||
- **Retain instant recovery snapshots for**: 2 day(s)
|
||||
- **Retention of daily backup point**: Enabled, 180 days
|
||||
- **Retention of weekly backup point**: Enabled, Sunday, 12 weeks
|
||||
|
|
@ -1085,7 +1087,7 @@ In this task, you will configure Azure Backup for the Web tier virtual machines.
|
|||
|
||||
|
||||
|
||||
6. Select **Azure Virtual Machine**. The 'Backup Items (Azure Virtual Machine' blade loads, listing **WebVM1** and **WebVM2**. In both cases, the 'Last Backup Status is 'Warning (Initial backup pending)'.
|
||||
6. Select **Azure Virtual Machine**. The 'Backup Items (Azure Virtual Machine' blade loads, listing **WebVM1** and **WebVM2**). In both cases, the 'Last Backup Status is 'Warning (Initial backup pending)'.
|
||||
|
||||
|
||||
|
||||
|
|
@ -1095,7 +1097,7 @@ In this task, you will configure Azure Backup for the Web tier virtual machines.
|
|||
|
||||
|
||||
|
||||
>**Note:** The backup policy created earlier determines the retention period for scheduled backups. For on-demand backups, the retention period is specified separately.
|
||||
>**Note**: The backup policy created earlier determines the retention period for scheduled backups. For on-demand backups, the retention period is specified separately.
|
||||
|
||||
8. Close the WebVM1 backup status blade. Then, repeat the above step to trigger an on-demand backup for **WebVM2**.
|
||||
|
||||
|
|
@ -1129,7 +1131,7 @@ Before enabling Azure Backup, you will first register the SQL Server VMs with th
|
|||
|
||||
|
||||
|
||||
> **Note:** It may take several minutes to register the resource provider. Wait until the registration is complete before proceeding to the next step. You can check the registration status using `Get-AzResourceProvider -ProviderNamespace Microsoft.SqlVirtualMachine`.
|
||||
> **Note**: It may take several minutes to register the resource provider. Wait until the registration is complete before proceeding to the next step. You can check the registration status using `Get-AzResourceProvider -ProviderNamespace Microsoft.SqlVirtualMachine`.
|
||||
|
||||
3. Register **SQLVM1** with the resource provider by executing the following command in the Cloud Shell window. Ensure that **-Location** matches the location SQLVM1 is deployed.
|
||||
|
||||
|
|
@ -1139,7 +1141,7 @@ Before enabling Azure Backup, you will first register the SQL Server VMs with th
|
|||
|
||||
|
||||
|
||||
> **Note:** This will register the resource provider using the `Full` management mode. This change causes the SQL service to restart, which may impact production applications. To avoid this restart in production environments, you can alternatively register the resource provider in `LightWeight` mode and upgrade later during a scheduled maintenance window.
|
||||
> **Note**: This will register the resource provider using the `Full` management mode. This change causes the SQL service to restart, which may impact production applications. To avoid this restart in production environments, you can alternatively register the resource provider in `LightWeight` mode and upgrade later during a scheduled maintenance window.
|
||||
|
||||
4. Register **SQLVM2** and **SQLVM3** with the resource provider using the following commands. Ensure you specify the correct locations.
|
||||
|
||||
|
|
@ -1148,7 +1150,7 @@ Before enabling Azure Backup, you will first register the SQL Server VMs with th
|
|||
New-AzSqlVM -Name 'SQLVM3' -ResourceGroupName 'ContosoRG2' -SqlManagementType Full -Location 'East US 2' -LicenseType PAYG
|
||||
```
|
||||
|
||||
> **Note:** This lab uses SQL Server under a 'Developer' tier license. When using SQL Server in production at the 'Standard' or 'Enterprise' tier, you can specify `DR` as the license type for failover servers (each full-price server includes a license for 1 DR server). The DR license type reduces your licensing cost significantly. Check the SQL Server licensing documentation for full details.
|
||||
> **Note**: This lab uses SQL Server under a 'Developer' tier license. When using SQL Server in production at the 'Standard' or 'Enterprise' tier, you can specify `DR` as the license type for failover servers (each full-price server includes a license for 1 DR server). The DR license type reduces your licensing cost significantly. Check the SQL Server licensing documentation for full details.
|
||||
|
||||
5. In the Azure portal, navigate to the **ContosoRG1** resource group. In addition to the SQLVM1 and SQLVM2 virtual machines, there are now parallel SQLVM1 and SQLVM2 resources of type 'SQL virtual machine' These additional resources provide additional management capabilities for SQL Server in Azure virtual machines.
|
||||
|
||||
|
|
@ -1184,8 +1186,9 @@ Before enabling Azure Backup, you will first register the SQL Server VMs with th
|
|||
|
||||
|
||||
|
||||
> **Note:** Using AutoProtect backups up the current database and any future databases on this Always On Availability Group.
|
||||
> **Note:** You may also want to backup system databases on each of the SQL Servers.
|
||||
> **Note**: Using AutoProtect backups up the current database and any future databases on this Always On Availability Group.
|
||||
>
|
||||
> **Note**: You may also want to backup system databases on each of the SQL Servers.
|
||||
|
||||
13. On the 'Backup' blade, note that **BCDRAOG\BCDRAOG** is now listed for backup. Leave the policy as the default `HourlyLogBackup` policy. Select **Enable Backup** and wait for the deployment to complete.
|
||||
|
||||
|
|
@ -1217,7 +1220,7 @@ Before enabling Azure Backup, you will first register the SQL Server VMs with th
|
|||
|
||||
|
||||
|
||||
> **Note:** You can continue to the next step in the lab without waiting for the backup job to complete.
|
||||
> **Note**: You can continue to the next step in the lab without waiting for the backup job to complete.
|
||||
|
||||
## Exercise 4: Validate resiliency
|
||||
|
||||
|
|
@ -1291,7 +1294,7 @@ In this task, you will validate the failover of the Contoso application from Cen
|
|||
|
||||
|
||||
|
||||
> **Note:** Do not make any changes to your VMs in the Azure portal during this process. Allow ASR to take the actions and wait for the failover notification before moving on to the next step. You can open another portal view in a new browser tab and review the output of the Azure Automation Jobs by opening the jobs and selecting Output.
|
||||
> **Note**: Do not make any changes to your VMs in the Azure portal during this process. Allow ASR to take the actions and wait for the failover notification before moving on to the next step. You can open another portal view in a new browser tab and review the output of the Azure Automation Jobs by opening the jobs and selecting Output.
|
||||
>
|
||||
> 
|
||||
|
||||
|
|
@ -1303,7 +1306,7 @@ In this task, you will validate the failover of the Contoso application from Cen
|
|||
|
||||
|
||||
|
||||
> **Note:** Do not select Start! The VM will be restarted automatically by ASR during failback.
|
||||
> **Note**: Do not select Start! The VM will be restarted automatically by ASR during failback.
|
||||
|
||||
11. Move back to the Resource group and select the **ContosoWebLBPrimaryIP** Public IP address. Copy the DNS name and paste it into a new browser tab. The website will be unreachable at the Primary location since the Web VMs at this location have been stopped by ASR during failover.
|
||||
|
||||
|
|
@ -1337,7 +1340,7 @@ In this task, you will validate the failover of the Contoso application from Cen
|
|||
|
||||
19. The portal will submit a deployment. This process will take up to 30 minutes to commit the failover and then synchronize WebVM1 and WebVM2 with the Recovery Services Vault. Once this process is complete, you will be able to failback to the primary site.
|
||||
|
||||
> **Note:** You need to wait for the re-protect process to complete before continuing with the failback. You can check the status of the Re-protect using the Site Recovery Jobs area of the BCDRSRV.
|
||||
> **Note**: You need to wait for the re-protect process to complete before continuing with the failback. You can check the status of the Re-protect using the Site Recovery Jobs area of the BCDRSRV.
|
||||
>
|
||||
> 
|
||||
>
|
||||
|
|
@ -1361,7 +1364,7 @@ In this task, you will failback the Contoso application from the DR site in your
|
|||
|
||||
4. Confirm that the Contoso application is once again accessible via the **ContosoWebLBPrimaryIP** public IP address and is **not** available at the **ContosoWebLBSecondaryIP** address. This test shows it has returned to the primary site. Open the **Current Policy Offerings** and edit a policy to confirm database access.
|
||||
|
||||
> **Note:** If you get an "Our services aren't available right now" error (or a 404-type error) accessing the web application, verify that you are utilizing the **ContosoWebLBPrimaryIP**. If it does not come up within ~10 minutes, verify that the backend system is responding.
|
||||
> **Note**: If you get an "Our services aren't available right now" error (or a 404-type error) accessing the web application, verify that you are utilizing the **ContosoWebLBPrimaryIP**. If it does not come up within ~10 minutes, verify that the backend system is responding.
|
||||
|
||||
5. Confirm that the Contoso application is also available via the Front Door URL.
|
||||
|
||||
|
|
@ -1393,7 +1396,7 @@ In this task, you will failback the Contoso application from the DR site in your
|
|||
|
||||
|
||||
|
||||
> **Note:** This task could have been done using the Azure Automation script during Failback, but most DBAs would prefer a clean failback and then do this manually once they are comfortable with the failback.
|
||||
> **Note**: This task could have been done using the Azure Automation script during Failback, but most DBAs would prefer a clean failback and then do this manually once they are comfortable with the failback.
|
||||
|
||||
### Task 4: Validate VM Backup
|
||||
|
||||
|
|
@ -1425,7 +1428,7 @@ In this task, you will validate the backup for the Contoso application WebVMs. Y
|
|||
|
||||
7. Before restoring a VM, the existing VM must be shut down. Use the Azure portal to shut down **WebVM1**.
|
||||
|
||||
> **Note:** since WebVM2 is also shut down, this will break the Contoso application. In a real-world scenario, you would keep WebVM2 running while restoring WebVM1.
|
||||
> **Note**: since WebVM2 is also shut down, this will break the Contoso application. In a real-world scenario, you would keep WebVM2 running while restoring WebVM1.
|
||||
|
||||
8. In the Azure portal, navigate to the **BackupRSV** Recovery Services Vault. Under 'Protected Items', select **Backup items**, then select **Azure Virtual Machine**.
|
||||
|
||||
|
|
@ -1437,8 +1440,8 @@ In this task, you will validate the backup for the Contoso application WebVMs. Y
|
|||
|
||||
10. Complete the Restore Virtual Machine page as follows, then select **Restore**.
|
||||
|
||||
- **Restore point:** Select the most recent restore point.
|
||||
- **Restore Configuration:** Replace existing
|
||||
- **Restore point**: Select the most recent restore point.
|
||||
- **Restore Configuration**: Replace existing
|
||||
- **Staging Location**: Choose the storage account you created earlier, starting with `backupstaging`.
|
||||
|
||||
|
||||
|
|
@ -1473,7 +1476,7 @@ In this task, you will validate the ability to restore the Contoso application d
|
|||
|
||||
|
||||
|
||||
> **Note:** For an Always On Availability Group backup, the option to overwrite the existing database is not available. You must restore to a parallel location.
|
||||
> **Note**: For an Always On Availability Group backup, the option to overwrite the existing database is not available. You must restore to a parallel location.
|
||||
|
||||
5. Select the option to choose your Restore Point. On the 'Select restore point' blade, explore the restore options. Note how the log-based option offers a point-in-time restore, whereas the full & differential option provides backup based on the backup schedule.
|
||||
|
||||
|
|
@ -1499,7 +1502,7 @@ In this task, you will validate the ability to restore the Contoso application d
|
|||
|
||||
|
||||
|
||||
> **Note:** You can now either copy data from the restored database to the production database or add this database to the Always On Availability Group and switch the Web tier to use the restored database.
|
||||
> **Note**: You can now either copy data from the restored database to the production database or add this database to the Always On Availability Group and switch the Web tier to use the restored database.
|
||||
|
||||
## After the hands-on lab
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ Microsoft may have patents, patent applications, trademarks, copyrights, or othe
|
|||
|
||||
The names of manufacturers, products, or URLs are provided for informational purposes only and Microsoft makes no representations and warranties, either expressed, implied, or statutory, regarding these manufacturers or the use of the products with any Microsoft technologies. The inclusion of a manufacturer or product does not imply endorsement of Microsoft of the manufacturer or product. Links may be provided to third party sites. Such sites are not under the control of Microsoft and Microsoft is not responsible for the contents of any linked site or any link contained in a linked site, or any changes or updates to such sites. Microsoft is not responsible for webcasting or any other form of transmission received from any linked site. Microsoft is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement of Microsoft of the site or the products contained therein.
|
||||
|
||||
© 2021 Microsoft Corporation. All rights reserved.
|
||||
© 2022 Microsoft Corporation. All rights reserved.
|
||||
|
||||
Microsoft and the trademarks listed at https://www.microsoft.com/en-us/legal/intellectualproperty/Trademarks/Usage/General.aspx are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.
|
||||
|
||||
|
|
@ -27,17 +27,17 @@ Microsoft and the trademarks listed at https://www.microsoft.com/en-us/legal/int
|
|||
|
||||
<!-- TOC -->
|
||||
|
||||
[Building a resilient IaaS architecture whiteboard design session student guide](#building-a-resilient-iaas-architecture-whiteboard-design-session-student-guide)
|
||||
[Abstract and learning objectives](#abstract-and-learning-objectives)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study)
|
||||
- [Customer situation](#customer-situation)
|
||||
[Customer needs](#customer-needs)
|
||||
[Customer objections](#customer-objections)
|
||||
- [Infographic for common scenarios](#infographic-for-common-scenarios)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution)
|
||||
[Wrap-up](#wrap-up)
|
||||
- [Additional references](#additional-references)
|
||||
- [Building a resilient IaaS architecture whiteboard design session student guide](#building-a-resilient-iaas-architecture-whiteboard-design-session-student-guide)
|
||||
- [Abstract and learning objectives](#abstract-and-learning-objectives)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study)
|
||||
- [Customer situation](#customer-situation)
|
||||
- [Customer needs](#customer-needs)
|
||||
- [Customer objections](#customer-objections)
|
||||
- [Infographic for common scenarios](#infographic-for-common-scenarios)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution)
|
||||
- [Wrap-up](#wrap-up)
|
||||
- [Additional references](#additional-references)
|
||||
|
||||
<!-- /TOC -->
|
||||
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@ Microsoft may have patents, patent applications, trademarks, copyrights, or othe
|
|||
|
||||
The names of manufacturers, products, or URLs are provided for informational purposes only and Microsoft makes no representations and warranties, either expressed, implied, or statutory, regarding these manufacturers or the use of the products with any Microsoft technologies. The inclusion of a manufacturer or product does not imply endorsement of Microsoft of the manufacturer or product. Links may be provided to third party sites. Such sites are not under the control of Microsoft and Microsoft is not responsible for the contents of any linked site or any link contained in a linked site, or any changes or updates to such sites. Microsoft is not responsible for webcasting or any other form of transmission received from any linked site. Microsoft is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement of Microsoft of the site or the products contained therein.
|
||||
|
||||
© 2021 Microsoft Corporation. All rights reserved.
|
||||
© 2022 Microsoft Corporation. All rights reserved.
|
||||
|
||||
Microsoft and the trademarks listed at https://www.microsoft.com/en-us/legal/intellectualproperty/Trademarks/Usage/General.aspx are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners.
|
||||
|
||||
|
|
@ -33,160 +33,25 @@ Microsoft and the trademarks listed at https://www.microsoft.com/en-us/legal/int
|
|||
- [Before the whiteboard design session: How to prepare](#before-the-whiteboard-design-session-how-to-prepare)
|
||||
- [During the whiteboard design session: Tips for an effective whiteboard design session](#during-the-whiteboard-design-session-tips-for-an-effective-whiteboard-design-session)
|
||||
- [Building a resilient IaaS architecture whiteboard design session student guide](#building-a-resilient-iaas-architecture-whiteboard-design-session-student-guide)
|
||||
- [Abstract and learning objectives](#abstract-and-learning-objectives)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study)
|
||||
- [Customer situation](#customer-situation)
|
||||
- [Customer needs](#customer-needs)
|
||||
- [Customer objections](#customer-objections)
|
||||
- [Infographic for common scenarios](#infographic-for-common-scenarios)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution)
|
||||
- [Wrap-up](#wrap-up)
|
||||
- [Additional references](#additional-references)
|
||||
- [Abstract and learning objectives](#abstract-and-learning-objectives)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study)
|
||||
- [Customer situation](#customer-situation)
|
||||
- [Customer needs](#customer-needs)
|
||||
- [Customer objections](#customer-objections)
|
||||
- [Infographic for common scenarios](#infographic-for-common-scenarios)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution)
|
||||
- [Wrap-up](#wrap-up)
|
||||
- [Additional references](#additional-references)
|
||||
- [Building a resilient IaaS architecture whiteboard design session trainer guide](#building-a-resilient-iaas-architecture-whiteboard-design-session-trainer-guide)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study-1)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution-1)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution-1)
|
||||
- [Wrap-up](#wrap-up-1)
|
||||
- [Preferred target audience](#preferred-target-audience)
|
||||
- [Design](#design)
|
||||
- [Pricing](#pricing)
|
||||
- [Checklist of preferred objection handling](#checklist-of-preferred-objection-handling)
|
||||
- [Customer quote (to be read back to the attendees at the end)](#customer-quote-to-be-read-back-to-the-attendees-at-the-end)
|
||||
[Wrap-up](#wrap-up)
|
||||
- [Additional references](#additional-references)
|
||||
- [Trainer information](#trainer-information)
|
||||
- [Role of the trainer](#role-of-the-trainer)
|
||||
- [Whiteboard design session flow](#whiteboard-design-session-flow)
|
||||
- [Before the whiteboard design session: How to prepare](#before-the-whiteboard-design-session-how-to-prepare)
|
||||
- [During the whiteboard design session: Tips for an effective whiteboard design session](#during-the-whiteboard-design-session-tips-for-an-effective-whiteboard-design-session)
|
||||
- [Building a resilient IaaS architecture whiteboard design session student guide](#building-a-resilient-iaas-architecture-whiteboard-design-session-student-guide)
|
||||
- [Abstract and learning objectives](#abstract-and-learning-objectives)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study)
|
||||
- [Customer situation](#customer-situation)
|
||||
- [Customer needs](#customer-needs)
|
||||
- [Customer objections](#customer-objections)
|
||||
- [Infographic for common scenarios](#infographic-for-common-scenarios)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution)
|
||||
- [Wrap-up](#wrap-up)
|
||||
- [Additional references](#additional-references)
|
||||
- [Building a resilient IaaS architecture whiteboard design session trainer guide](#building-a-resilient-iaas-architecture-whiteboard-design-session-trainer-guide)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study-1)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution-1)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution-1)
|
||||
- [Wrap-up](#wrap-up-1)
|
||||
- [Preferred target audience](#preferred-target-audience)
|
||||
- [Design](#design)
|
||||
- [Pricing](#pricing)
|
||||
- [Checklist of preferred objection handling](#checklist-of-preferred-objection-handling)
|
||||
- [Customer quote (to be read back to the attendees at the end)](#customer-quote-to-be-read-back-to-the-attendees-at-the-end)
|
||||
[Building a resilient IaaS architecture whiteboard design session student guide](#building-a-resilient-iaas-architecture-whiteboard-design-session-student-guide)
|
||||
- [Abstract and learning objectives](#abstract-and-learning-objectives)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study)
|
||||
- [Customer situation](#customer-situation)
|
||||
- [Customer needs](#customer-needs)
|
||||
- [Customer objections](#customer-objections)
|
||||
- [Infographic for common scenarios](#infographic-for-common-scenarios)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution)
|
||||
[Wrap-up](#wrap-up)
|
||||
[Additional references](#additional-references)
|
||||
- [Building a resilient IaaS architecture whiteboard design session trainer guide](#building-a-resilient-iaas-architecture-whiteboard-design-session-trainer-guide)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study-1)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution-1)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution-1)
|
||||
- [Wrap-up](#wrap-up-1)
|
||||
[Preferred target audience](#preferred-target-audience)
|
||||
- [Design](#design)
|
||||
- [Pricing](#pricing)
|
||||
- [Checklist of preferred objection handling](#checklist-of-preferred-objection-handling)
|
||||
- [Customer quote (to be read back to the attendees at the end)](#customer-quote-to-be-read-back-to-the-attendees-at-the-end)
|
||||
[Abstract and learning objectives](#abstract-and-learning-objectives)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study)
|
||||
- [Customer situation](#customer-situation)
|
||||
- [Customer needs](#customer-needs)
|
||||
- [Customer objections](#customer-objections)
|
||||
- [Infographic for common scenarios](#infographic-for-common-scenarios)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution)
|
||||
[Wrap-up](#wrap-up)
|
||||
[Additional references](#additional-references)
|
||||
- [Trainer information](#trainer-information)
|
||||
- [Role of the trainer](#role-of-the-trainer)
|
||||
- [Whiteboard design session flow](#whiteboard-design-session-flow)
|
||||
- [Before the whiteboard design session: How to prepare](#before-the-whiteboard-design-session-how-to-prepare)
|
||||
- [During the whiteboard design session: Tips for an effective whiteboard design session](#during-the-whiteboard-design-session-tips-for-an-effective-whiteboard-design-session)
|
||||
- [Building a resilient IaaS architecture whiteboard design session student guide](#building-a-resilient-iaas-architecture-whiteboard-design-session-student-guide)
|
||||
- [Abstract and learning objectives](#abstract-and-learning-objectives)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study)
|
||||
- [Customer situation](#customer-situation)
|
||||
- [Customer needs](#customer-needs)
|
||||
- [Customer objections](#customer-objections)
|
||||
- [Infographic for common scenarios](#infographic-for-common-scenarios)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution)
|
||||
- [Wrap-up](#wrap-up)
|
||||
- [Additional references](#additional-references)
|
||||
- [Building a resilient IaaS architecture whiteboard design session trainer guide](#building-a-resilient-iaas-architecture-whiteboard-design-session-trainer-guide)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study-1)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution-1)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution-1)
|
||||
- [Wrap-up](#wrap-up-1)
|
||||
- [Preferred target audience](#preferred-target-audience)
|
||||
- [Design](#design)
|
||||
- [Pricing](#pricing)
|
||||
- [Checklist of preferred objection handling](#checklist-of-preferred-objection-handling)
|
||||
- [Customer quote (to be read back to the attendees at the end)](#customer-quote-to-be-read-back-to-the-attendees-at-the-end)
|
||||
[Wrap-up](#wrap-up)
|
||||
- [Additional references](#additional-references)
|
||||
- [Trainer information](#trainer-information)
|
||||
- [Role of the trainer](#role-of-the-trainer)
|
||||
- [Whiteboard design session flow](#whiteboard-design-session-flow)
|
||||
- [Before the whiteboard design session: How to prepare](#before-the-whiteboard-design-session-how-to-prepare)
|
||||
- [During the whiteboard design session: Tips for an effective whiteboard design session](#during-the-whiteboard-design-session-tips-for-an-effective-whiteboard-design-session)
|
||||
- [Building a resilient IaaS architecture whiteboard design session student guide](#building-a-resilient-iaas-architecture-whiteboard-design-session-student-guide)
|
||||
- [Abstract and learning objectives](#abstract-and-learning-objectives)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study)
|
||||
- [Customer situation](#customer-situation)
|
||||
- [Customer needs](#customer-needs)
|
||||
- [Customer objections](#customer-objections)
|
||||
- [Infographic for common scenarios](#infographic-for-common-scenarios)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution)
|
||||
- [Wrap-up](#wrap-up)
|
||||
- [Additional references](#additional-references)
|
||||
- [Building a resilient IaaS architecture whiteboard design session trainer guide](#building-a-resilient-iaas-architecture-whiteboard-design-session-trainer-guide)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study-1)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution-1)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution-1)
|
||||
- [Wrap-up](#wrap-up-1)
|
||||
- [Preferred target audience](#preferred-target-audience)
|
||||
- [Design](#design)
|
||||
- [Pricing](#pricing)
|
||||
- [Checklist of preferred objection handling](#checklist-of-preferred-objection-handling)
|
||||
- [Customer quote (to be read back to the attendees at the end)](#customer-quote-to-be-read-back-to-the-attendees-at-the-end)
|
||||
[Building a resilient IaaS architecture whiteboard design session student guide](#building-a-resilient-iaas-architecture-whiteboard-design-session-student-guide)
|
||||
- [Abstract and learning objectives](#abstract-and-learning-objectives)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study)
|
||||
- [Customer situation](#customer-situation)
|
||||
- [Customer needs](#customer-needs)
|
||||
- [Customer objections](#customer-objections)
|
||||
- [Infographic for common scenarios](#infographic-for-common-scenarios)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution)
|
||||
[Wrap-up](#wrap-up)
|
||||
[Additional references](#additional-references)
|
||||
- [Building a resilient IaaS architecture whiteboard design session trainer guide](#building-a-resilient-iaas-architecture-whiteboard-design-session-trainer-guide)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study-1)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution-1)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution-1)
|
||||
- [Wrap-up](#wrap-up-1)
|
||||
[Preferred target audience](#preferred-target-audience)
|
||||
- [Design](#design)
|
||||
- [Pricing](#pricing)
|
||||
- [Checklist of preferred objection handling](#checklist-of-preferred-objection-handling)
|
||||
- [Customer quote (to be read back to the attendees at the end)](#customer-quote-to-be-read-back-to-the-attendees-at-the-end)
|
||||
- [Step 1: Review the customer case study](#step-1-review-the-customer-case-study-1)
|
||||
- [Step 2: Design a proof of concept solution](#step-2-design-a-proof-of-concept-solution-1)
|
||||
- [Step 3: Present the solution](#step-3-present-the-solution-1)
|
||||
- [Wrap-up](#wrap-up-1)
|
||||
- [Preferred target audience](#preferred-target-audience)
|
||||
- [Preferred solution](#preferred-solution)
|
||||
- [Checklist of preferred objection handling](#checklist-of-preferred-objection-handling)
|
||||
- [Customer quote (to be read back to the attendees at the end)](#customer-quote-to-be-read-back-to-the-attendees-at-the-end)
|
||||
|
||||
<!-- /TOC -->
|
||||
|
||||
|
|
@ -553,7 +418,7 @@ Directions: Reconvene with the larger group to hear the facilitator/SME share th
|
|||
- Jordan North, Principal Software Development Lead
|
||||
- You should also aim to identify the business owner of the claims application and the key stakeholders of the business impact analysis that provided the executive mandate for improved resiliency
|
||||
|
||||
## Design
|
||||
## Preferred solution
|
||||
|
||||
1. How will you provide an SLA in excess of 99.95% (per month) for the overall claims application?
|
||||
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче