BCDR MicroHackAzureNative (#44)

* First Commit

Structure

* Create test.txt

* Initial Structure

* Changed the structure and some small fixes

* Microhack structure, C0, C1

* C0

* C0

* C0 / C1

* Create test.txt

* Create extensions.json

* Small corrections in C0 and instructions for C1 (#30)

Co-authored-by: Bernd Loehlein <[email protected]>

* Update Readme.md

* C0

* C0 walkthrough

* Adding ARM-Templates for C1

* Update Readme.md

* Deleted old files

* modified templates to fix deployment errors

* removed Backup Policies due to deployment errors

* Update for CH2

Update for CH2

* Update Readme.md

* Update Readme.md

* Add files via upload

* Add files via upload

* Delete mh-ch-screenshot-01.png

* Add files via upload

* Update Readme.md

* Delete 1_new_KV.png

* Delete 3_Assign_KeyVault_permissions.jpg

* Delete 4_Create_Secret.png

* Delete 5_result_secret.png

* Delete 2_KV_settings.jpg

* Add files via upload

* Update solution.md

* Add files via upload

* Delete mh-ch-screenshot-01.png

* Delete mh-ch-screenshot-02.png

* Delete mh-ch-screenshot-03.png

* Delete mh-ch-screenshot-04.png

* Delete mh-ch-screenshot-05.png

* Add files via upload

* Create mh-ch-screenshot-01.png

* Delete mh-ch-screenshot-01.png

* Add files via upload

* Update solution.md

* Update solution.md

* Update solution.md

* Delete mh-ch-screenshot-06.png

* Delete mh-ch-screenshot-07.png

* Delete mh-ch-screenshot-08.png

* Add files via upload

* Update solution.md

* Update solution.md

* Delete mh-ch-screenshot-06.png

* Add files via upload

* Update solution.md

* Update solution.md

* Add files via upload

* Update solution.md

* Update solution.md

* Update Readme.md

* Add files via upload

* Update solution.md

* Add files via upload

* Update solution.md

* Update solution.md

* Update Readme.md

* Update Readme.md

* Delete 7.png

* Update solution.md

* Delete 1.png

* Delete 2.png

* Delete 3.png

* Delete 4.png

* Delete 5.png

* Delete 6.png

* Add files via upload

* Delete mh-ch4-screenshot-01.png

* /img/mh-ch4-screenshot-01.png

* Delete mh-ch4-screenshot-01-1.png

* Create test

* Add files via upload

* Delete test

* Add files via upload

* Add files via upload

* Delete mh-ch4-screenshot-03.png

* Delete mh-ch4-screenshot-04.png

* Delete mh-ch4-screenshot-05.png

* Add files via upload

* Add files via upload

* Update solution.md

* Add files via upload

* Add files via upload

* Update solution.md

* Update solution.md

* Update solution.md

* Update solution.md

* Update solution.md

* Delete mh-ch4-screenshot-01.png

* Delete mh-ch4-screenshot-02.png

* Delete mh-ch4-screenshot-03.png

* Delete mh-ch4-screenshot-04.png

* Delete mh-ch4-screenshot-05.png

* Delete mh-ch4-screenshot-06.png

* Delete mh-ch4-screenshot-07.png

* Delete mh-ch4-screenshot-08.png

* Delete mh-ch4-screenshot-09.png

* Delete mh-ch4-screenshot-10.png

* Delete mh-ch4-screenshot-11.png

* Delete mh-ch4-screenshot-12.png

* Delete mh-ch4-screenshot-13.png

* Delete mh-ch4-screenshot-14.png

* Delete mh-ch4-screenshot-15.png

* Delete mh-ch4-screenshot-16.png

* Delete mh-ch4-screenshot-17.png

* Delete mh-ch4-screenshot-18.png

* Delete mh-ch4-screenshot-19.png

* Delete mh-ch4-screenshot-20.png

* Delete mh-ch4-screenshot-21.png

* Delete mh-ch4-screenshot-22.png

* Delete mh-ch4-screenshot-23.png

* Delete mh-ch4-screenshot-24.png

* Delete mh-ch4-screenshot-25.png

* Delete mh-ch4-screenshot-26.png

* Delete mh-ch4-screenshot-27.png

* Delete mh-ch4-screenshot-28.png

* Delete mh-ch4-screenshot-29.png

* Delete mh-ch4-screenshot-30.png

* Delete mh-ch4-screenshot-31.png

* Delete mh-ch4-screenshot-32.png

* Delete mh-ch4-screenshot-33.png

* Delete mh-ch4-screenshot-34.png

* Delete mh-ch4-screenshot-35.png

* Delete mh-ch4-screenshot-36.png

* Delete mh-ch4-screenshot-37.png

* Delete mh-ch4-screenshot-38.png

* Delete mh-ch4-screenshot-39.png

* Delete mh-ch4-screenshot-40.png

* Delete mh-ch4-screenshot-41.png

* Delete mh-ch4-screenshot-42.png

* Delete mh-ch4-screenshot-43.png

* Delete mh-ch4-screenshot-44.png

* Delete mh-ch4-screenshot-45.png

* Delete mh-ch4-screenshot-46.png

* Delete mh-ch4-screenshot-47.png

* Delete mh-ch4-screenshot-48.png

* Delete mh-ch4-screenshot-49.png

* Delete mh-ch4-screenshot-50.png

* Delete mh-ch4-screenshot-51.png

* Delete mh-ch4-screenshot-52.png

* Delete mh-ch4-screenshot-53.png

* Delete mh-ch4-screenshot-54.png

* Delete mh-ch4-screenshot-55.png

* Delete mh-ch4-screenshot-56.png

* Delete mh-ch4-screenshot-57.png

* Delete mh-ch4-screenshot-58.png

* Delete mh-ch4-screenshot-59.png

* Delete mh-ch4-screenshot-60.png

* Delete mh-ch4-screenshot-61.png

* Delete mh-ch4-screenshot-62.png

* Delete mh-ch4-screenshot-63.png

* Delete mh-ch4-screenshot-64.png

* Add files via upload

* Delete mh-ch4-screenshot-60.png

* Delete mh-ch4-screenshot-61.png

* Delete mh-ch4-screenshot-62.png

* Delete mh-ch4-screenshot-63.png

* Delete mh-ch4-screenshot-64.png

* Delete mh-ch4-screenshot-65.png

* Add files via upload

* Update solution.md

* Update solution.md

* Delete mh-ch4-screenshot-20.png

* Delete mh-ch4-screenshot-21.png

* Delete mh-ch4-screenshot-22.png

* Delete mh-ch4-screenshot-23.png

* Delete mh-ch4-screenshot-24.png

* Delete mh-ch4-screenshot-25.png

* Delete mh-ch4-screenshot-26.png

* Delete mh-ch4-screenshot-27.png

* Delete mh-ch4-screenshot-28.png

* Delete mh-ch4-screenshot-29.png

* Delete mh-ch4-screenshot-30.png

* Delete mh-ch4-screenshot-31.png

* Delete mh-ch4-screenshot-32.png

* Delete mh-ch4-screenshot-33.png

* Delete mh-ch4-screenshot-34.png

* Delete mh-ch4-screenshot-35.png

* Delete mh-ch4-screenshot-55-a.png

* Add files via upload

* Update solution.md

* Update solution.md

* Update Readme.md

* Update solution.md

* Update solution.md

* Updated Challenge 4 solution.md Intro

* Update solution.md

Changed something

* Update solution.md

* Template design changes

---------

Co-authored-by: Bernd Loehlein <[email protected]>
Co-authored-by: Bernd Loehlein <[email protected]>
Co-authored-by: hbigdeloo <[email protected]>
Co-authored-by: kleinmarkus <[email protected]>
Co-authored-by: taraBehtouei <[email protected]>

.vscode/extensions.json

@@ -0,0 +1,5 @@
+{
+    "recommendations": [
+        "github.vscode-pull-request-github"
+    ]
+}

03-Azure/01-03-Infrastructure/04_BCDR_Azure_Native/Readme.md

@@ -0,0 +1,275 @@
+# **MicroHack Business Continuity / Disaster Recovery**
+
+- [**MicroHack introduction**](#MicroHack-introduction)
+  - [What is Business Continuity?]()
+- [**MicroHack context**](#microhack-context)
+- [**Objectives**](#objectives)
+- [**MicroHack Challenges**](#microhack-challenges)
+  - [General prerequisites](#general-prerequisites)
+  - [Challenge 0 - Understand the Disaster Recovery terms and define a strategy](#challenge-0---understand-the-disaster-recovery-terms-and-define-a-strategy)
+  - [Challenge 1 - Prerequisites and landing zone preperation](#challenge-1---prerequisites-and-landing-zone-preperation)
+  - [Challenge 2 - Protect in Azure - Backup / Restore](#challenge-2---protect-in-azure---backup--restore)
+  - [Challenge 3 - Protect in Azure with Disaster Recovery](#challenge-3---protect-in-azure-with-disaster-recovery)
+  - [Challenge 4 - Protect to Azure with Azure Backup & Restore](#challenge-4---protect-to-azure-with-azure-backup--restore)
+  - [Challenge 5 - Protect to Azure with Disaster Recovery](#challenge-5---protect-to-azure-with-disaster-recovery)
+- [**Contributors**](#contributors)
+
+## MicroHack introduction
+
+### What is Business Continuity?
+
+When you design for resiliency, you must understand your availability requirements.
+- How much downtime is acceptable? 
+- How much will potential downtime cost your business?
+- How much should you invest in making the application highly available?
+- You also must define what it means for the application to be available.
+
+💡 For example, is the application "down" if you can submit an order but the system cannot process it within the normal timeframe? Also consider the probability of an outage occurring and whether a mitigation strategy is cost-effective. Resilience planning starts with business requirements. Here are some approaches for thinking about resiliency in those terms
+
+The following picture describes very well the individual levels / disaster recovery tier levels and gives an overview of which topics we should deal with when talking about disaster recovery. The individual terms, terminologies and categories are explained and this microhack also gives an approach and a few tips on how to deal with them in your own company.
+
+![image](./img/drcontinuum.png)
+
+## MicroHack context
+
+This MicroHack scenario walks through the use of building a Business Continuity Strategy with a focus on the best practices and the design principles and some interesting challenges for real world scenarios. Specifically, this builds up to include working with an existing infrastructure in your datacenter.
+
+Further resources: 
+
+* [Azure Business Continuity & Disaster Recovery](https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-overview#what-does-site-recovery-provide)
+* [How does Microsoft ensure business continuity](https://learn.microsoft.com/en-us/compliance/assurance/assurance-resiliency-and-continuity)
+* [Common questions about Azure Site Recovery](https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-faq)
+
+💡 Optional: Read this after completing this lab to deepen the learned!
+
+* [Overview of the reliability pillar](https://learn.microsoft.com/en-us/azure/architecture/framework/resiliency/overview)
+* [Whitepaper - Resiliency in Azure ](https://azure.microsoft.com/en-us/resources/resilience-in-azure-whitepaper/)
+
+
+## Objectives
+
+After completing this MicroHack you will:
+
+* Know how to use the right business continuity strategy for your infrastructure or your particular workload
+* Understand use cases and possible scenarios in your business continuity & disaster recovery strategy 
+* Get insights into real world challenges and scenarios
+
+## MicroHack Challenges
+
+### General prerequisites
+
+This MicroHack has a few but important prerequisites to be understood before starting this lab!
+
+* Your own Azure subscription with Owner RBAC rights at the subscription level
+  * [Azure Evaluation free account](https://azure.microsoft.com/en-us/free/search/?OCID=AIDcmmzzaokddl_SEM_0fa7acb99db91c1fb85fcfd489e5ca6e:G:s&ef_id=0fa7acb99db91c1fb85fcfd489e5ca6e:G:s&msclkid=0fa7acb99db91c1fb85fcfd489e5ca6e)
+* More will be added later if needed
+
+## Challenge 0 - Understand the Disaster Recovery terms and define a strategy
+
+If you have already worked at the senior level or have been working in IT for many years, you may be able to skip this intro challenge. These standards should be defined in every organization and the most important thing is that the Business Continuity Management and the necessary steps for disaster recovery are regularly tested.
+
+### Goal
+
+The goal from this challenge is to understand the challenges in business continuity management and the most important terms. Second dimension is to define strategy and to put yourself into different roles to view the area from different perspectives.
+
+1. What exactly is the difference between Disaster Recovery & Business Continuity?
+2. Who is responsible for BCDR?
+3. Is there a difference between High availability & Disaster Recovery?
+4. Do I really need Backup & Disaster Recovery?
+
+### Actions
+
+* Write down the first 3 steps you would go for if your company got attacked by ransomware
+* Think about if you ever participated in a business continuity test scenario
+* Put yourself in the position of an application owner and define the necessary steps to make sure your application stays available in case of a disaster
+* Who defines the requirements for Business Continuity and what are the necessary KPI´s for an application to reach a good SLA in terms of availability?
+* Define and write down four different categories of Disaster Recovery Tier Levels that applications can use incl. the availability SLA
+* Plan the different geographic regions you need to use for reaching the highest availability SLA (can also include your datacenter locations)
+
+### Success criteria
+
+* Understood the different terms from BCDR
+* Noted the first three steps after ransomware attack in you company
+* Thought about the last successful disaster recovery of the daily used applications
+* Noted the responsibilities and the roles in the company you are working
+* Defined four level of disaster recovery categories incl. availability SLA
+
+### Learning resources
+
+* [Business continuity and disaster recovery - Cloud Adoption Framework | Microsoft Learn](https://learn.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/design-area/management-business-continuity-disaster-recovery)
+* [Build high availability into your BCDR strategy - Azure Architecture Center | Microsoft Learn](https://learn.microsoft.com/azure/architecture/solution-ideas/articles/build-high-availability-into-your-bcdr-strategy)
+* [Disaster recovery with Azure Site Recovery - Azure Solution Ideas | Microsoft Learn](https://learn.microsoft.com/azure/architecture/solution-ideas/articles/disaster-recovery-smb-azure-site-recovery)
+
+### Solution - Spoilerwarning
+
+[Solution Steps](./walkthrough/challenge-0/solution.md)
+
+## Challenge 1 - Prerequisites and landing zone preparation
+
+### Goal
+
+In challenge 1 you will understand and prepare your environment for onboarding of the infrastructure to enable business continuity with Cloud Native / PaaS Services on Azure.
+
+### Actions
+
+Create all necessary Azure resources
+* Region 1: West Europe (Source enviroment)
+  * Resource Group: mh-bcdr-weu-rg
+  * Recovery Services Vault: mh-rsv-weu
+  * Storage Account with GRS (geo-redundant storage) redundancy option: mhstweu\<Suffix\>
+* Region 2: North Europe (Target environment)
+  * Resource Group: mh-bcdr-neu-rg
+  * Recovery Services Vault: mh-rsv-neu
+
+
+### Success criteria
+
+* You've created Resource Groups in both regions (North & West Europe)
+* Recovery Services Vaults have been created in both regions
+* Geo-redundant Storage Account has been created
+
+### Learning resources
+
+* [Manage resource groups - Azure Portal - Azure Resource Manager | Microsoft Learn](https://learn.microsoft.com/azure/azure-resource-manager/management/manage-resource-groups-portal)
+* [Create a storage account - Azure Storage | Microsoft Learn](https://learn.microsoft.com/azure/storage/common/storage-account-create)
+* [Create and configure Recovery Services vaults - Azure Backup | Microsoft Learn](https://learn.microsoft.com/azure/backup/backup-create-recovery-services-vault)
+
+
+### Solution - Spoilerwarning
+
+[Solution Steps](./walkthrough/challenge-1/solution.md)
+
+## Challenge 2 - Protect in Azure - Backup / Restore 
+
+### Goal
+
+In challenge 2 you will successfully onboard your Windows and Linux Virtual Machines to a centralized Recovery Services Vault and leverage Azure Backup Center to Protect with Backup in Azure. 
+
+### Actions
+
+* Deploy a Windows Server 2022 VM in West Europe Resource Group
+* Deploy a Ubuntu Server VM in North Europe Resource Group
+* Enable Azure Backup for both VMs
+* Restore a VM in Azure
+
+
+### Success criteria
+
+* You have deployed two VMs in Azure (one with Window Server 2022, the other one with Ubuntu Server)
+* You successfully enabled Azure Backup on two virtual machines
+* You have successfully setup Azure Backup Policies for both virtual machines
+* You have successfully restored a VM of your choice to Azure
+
+### Learning resources
+
+* https://learn.microsoft.com/en-us/azure/backup/quick-backup-vm-portal
+* https://learn.microsoft.com/en-us/azure/backup/quick-backup-vm-portal#apply-a-backup-policy
+* https://learn.microsoft.com/en-us/azure/backup/tutorial-backup-vm-at-scale
+* https://learn.microsoft.com/en-us/azure/backup/backup-azure-arm-restore-vms
+* https://learn.microsoft.com/en-us/azure/backup/restore-azure-encrypted-virtual-machines
+
+
+
+### Solution - Spoilerwarning
+
+[Solution Steps](./walkthrough/challenge-2/solution.md)
+
+## Challenge 3 - Protect in Azure with Disaster Recovery 
+
+### Goal
+
+In this Challenge, you will learn how to protect Azure VM with Azure Site Recovery, and enable replication to the secondary site. In addition you will successfully  run the test & production failover from Europe West to North and failback again from Europe North to West.
+
+### Actions
+
+* Set up and enable disaster recovery with Azure Site Recovery and monitor the progress
+* Perform a disaster recovery drill, create recovery plan and run a test failover 
+* Run a production failover from EU West to EU East region and Failback again to the EU West region (Source environment) and monitor the progress
+
+### Success Criteria
+
+* You could enable replication for the virtual machine to the North Europe region.
+* You successfully initiated a Testfailover from Azure Region Europe West to Europe North with a near zero downtime requirement.
+* You run successfully the production failover to the Europe North region.
+* Failback to the Europe West region has been successfully performed. 
+
+### Learning resources
+
+* https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-how-to-enable-replication
+* https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-create-recovery-plans
+* https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-test-failover-to-azure
+* https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-how-to-reprotect
+* https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-failback
+* https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-enable-replication
+
+### Solution - Spoilerwarning
+
+[Solution Steps](./walkthrough/challenge-3/solution.md)
+
+## Challenge 4 - Protect to Azure with Azure Backup & Restore 
+
+### Goal
+
+In challenge 4, you will successfully protect your on-premise Hyper-V virtual machines with Microsoft Azure Backup Server (MABS).
+
+### Actions
+
+* Install the Microsoft Azure Backup Server (MABS) in the on-premise infrastructure
+* Add a Backup Storage to the MABS disk storage
+* Register an on-premise Windows server (Windows server 2016) and the on-premise Hyper-V host to the MABS
+* Protect the registered VM with MABS
+* Recover a Virtual Machine using MABS backup
+
+### Success criteria
+
+* You successfully installed Microsoft Azure Backup Server (MABS) in the on-premise infrastructure
+* You successfully registered two Hyper-V servers to the MABS
+* You successfully protected two virtual machines with MABS
+* You successfully restored a VM of your choice
+
+### Learning resources
+
+* https://learn.microsoft.com/en-us/azure/backup/backup-azure-microsoft-azure-backup
+* https://learn.microsoft.com/en-us/azure/backup/back-up-hyper-v-virtual-machines-mabs
+* https://learn.microsoft.com/en-us/system-center/dpm/create-dpm-protection-groups?view=sc-dpm-2022
+* https://learn.microsoft.com/en-us/system-center/dpm/deploy-dpm-protection-agent?view=sc-dpm-2022
+* https://learn.microsoft.com/en-us/azure/backup/backup-mabs-protection-matrix
+
+### Solution - Spoilerwarning
+
+[Solution Steps](./walkthrough/challenge-4/solution.md)
+
+## Challenge 5 - Protect to Azure with Disaster Recovery 
+
+### Actions
+
+* 
+
+### Success criteria
+
+*
+
+### Learning resources
+
+* 
+
+### Solution - Spoilerwarning
+
+[Solution Steps](./walkthrough/challenge-5/solution.md)
+
+## Finish
+
+Congratulations! You finished the MicroHack Business Continuity / Disaster Recovery. We hope you had the chance to learn about the how to implement a successful DR strategy to protect resources in Azure and to Azure. 
+If you want to give feedback please dont hesitate to open an Issue on the repository or get in touch with one of us directly.
+
+Thank you for investing the time and see you next time!
+
+
+## Contributors
+* Markus Klein 
+* Bernd Loehlein 
+* Hengameh Bigdeloo 
+* Tara
+* Nils Bankert [GitHub](https://github.com/nilsbankert); [LinkedIn](https://www.linkedin.com/in/nilsbankert/)
+
+

03-Azure/01-03-Infrastructure/04_BCDR_Azure_Native/resources/ARM-Templates/challenge-1-northeurope.json

@@ -0,0 +1,24 @@
+{
+    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
+    "contentVersion": "1.0.0.0",
+    "parameters": {
+        "recoveryServicesVaultName": {
+            "defaultValue": "mh-rsv-neu",
+            "type": "String"
+        }
+    },
+    "variables": {},
+    "resources": [
+        {
+            "type": "Microsoft.RecoveryServices/vaults",
+            "apiVersion": "2022-09-10",
+            "name": "[parameters('recoveryServicesVaultName')]",
+            "location": "northeurope",
+            "sku": {
+                "name": "RS0",
+                "tier": "Standard"
+            },
+            "properties": {}
+        }
+    ]
+}