README.md

Design a business continuity strategy (15-20%)

Design a site recovery strategy

• Azure Site Recovery

• design a recovery solution

  • Plan and be ready to deploy to another region without using the resources until needed

    • Create Recovery Services Vault

  • Recovery can be done between Azure regions or on-prem data center and Azure region

• design a site recovery replication policy

  • Configure and manage replication policies for VMware disaster recovery

• design for site recovery capacity

  • Azure Site Recovery capacity-planning guide for migrations

• design for storage replication

  • Lynda Video - https://www.lynda.com/Azure-tutorials/Implement-Azure-Storage-replication/797734/5032317-4.html

• design site failover and failback

  • Fail over and fail back physical servers replicated to Azure

• design the site recovery network

  • About networking in Azure VM disaster recovery

• recommend recovery objectives (Azure, on-prem, hybrid, Recovery Time Objective (RTO), Recovery Level Objective (RLO), Recovery Point Objective (RPO))

  • RPO stands for recovery POINT objective, i.e., how much data is one potentially prepared and willing to lose, worse case
  • RTO stands for recovery TIME objective, i.e., if/when the ‘bad thing’ happens, how much time does it take to be back up and running again
  • RLO stands for Recovery Level Objective (business continuity management) - defines a level to which software should be restored to

• identify resources that require site recovery

• identify supported and unsupported workloads

  • Support matrix for Azure VM disaster recovery between Azure regions

• recommend a geographical distribution strategy

  • Business continuity and disaster recovery (BCDR): Azure Paired Regions

    • Azure does not deploy/upgrage to both paired regions simultaniously

Design for high availability

% Uptime	Downtime per week	Downtime per month	Downtime per year
99%	1.68 hours	7.2 hours	3.65 days
99.9%	10 minutes	43.2 minutes	8.76 hours
99.95%	5 minutes	21.6 minutes	4.38 hours
99.99%	1 minute	4.32 minutes	52.56 minutes
99.999%	6 seconds	26 seconds	5.26 minutes

• design for application redundancy

  • Follow architectural principle of making "all things" redundant

  • Architecting Azure applications for resiliency and availability

• design for autoscaling

  • Plularsight - Autoscaling

  • Autoscaling best practices

  • Design to scale out

• design for data center and fault domain redundancy

  • Lynda Video - design for data center and fault domain redundancy

• design for network redundancy

  • Lynda Video - Network Redundancy

  • Highly Available Cross-Premises and VNet-to-VNet Connectivity

• identify resources that require high availability

• identify storage types for high availability

• design a disaster recovery strategy for individual workloads

  • About disaster recovery for on-premises apps

  • Set up disaster recovery for SQL Server

• design failover/failback scenarios

  • Lynda Video - design failover/failback scenarios

• document recovery requirements

• identify resources that require backup

• recommend a geographic availability strategy

Design a data archiving strategy

• recommend storage types and methodology for data archiving

  • Lynda Video - recommend storage types and methodology for data archiving

  • Only standard blob or file storage supports archive tier

    • Hot access 99.9% availability

    • Cool: Must keep data at least 30 days, 99% availability

    • Archive: High retrieval cost, must keep 180 days at least, data must be rehydrated to be retrieved (might take several hours)

    • Archive tier can be changed after creating the storage account

• identify business compliance requirements for data archiving

• identify requirements for data archiving

• identify SLA(s) for data archiving