Disaster Recovery using Azure Services - Adil Arif More Details https://www.anoopcnair.com/download-powerpoint-slides-bitpro-gab-2018-overview/

1. Disaster Recovery Using
Azure Services

2. GAB 2018 Agenda

3. Our Supporters

4. Collaborating Communities

5. Who am I?
• Twitter @adilarif001
• Blog EnterpriseDaddy.com
• I have a job! Senior Technical Support Engineer @ Rubrik
• Background Sysadmin working with some of the largest IT
organizations at IGATE (now Capgemini).
Most recently @VMware as a TSE with the
vSphere product line keeping customers
happy!

6. Agenda
• Disaster Recovery Fundamentals
• Azure Site Recovery
• Azure Backup

7. Disasters happen…

8. What is Disaster Recovery?
Disaster recovery is a set of policies and procedures which focus
on protecting an organization from any significant effects in
case of a negative event, which may include cyberattacks,
natural disasters or building or device failures

9. Types of Disaster
• Natural
• Hardware or Software failure
• Malicious
• Human Error
• Many more….

10. Common Definitions
• Recovery Point Objective (RPO)
• Recovery Time Objective (RTO)
• Work Recovery Time (WRT)
• Maximum Tolerable Downtime (MTD)
• Business Impact Analysis (BIA)

11. Visualizing Disaster Recovery Planning
Source: GoVanGuard

12. Phases of Disaster Recovery Planning
• Identify: Risk Assessment
• Analyze: Business Impact Analysis (BIA)
• Design: Strategy Selection
• Implement: Create/Execute
• Measure: Test and Maintenance

13. Failover Types
• Planned: The process is tested regularly in a manner that does
not impact production.
• Unplanned: The process is tested regularly in a manner that
does not impact production.
• Test: The process is tested regularly in a manner that does not
impact production.

14. Disaster Recovery Site Types
• Hot Site: Duplicate of the original with real-time replication of
protected systems
• Warm Site: Systems but without replication of data. Typically
backups must be restored
• Cold Site: A location but may not have required equipment
readily available

15. Why Choose Cloud as a DR Site?
• Traditional DR sites are expensive and are used only for testing
in most cases.
• Consumption based Model.
• Compute charges are minimal, pay only for storage
consumption.
• Scalability.
• Highly secure.

16. Azure Site Recovery

17. One Solution for multiple infrastructures
Hyper-V toHyper-V
(on-premises)
Hyper-V Hyper-V
Replication
Hyper-VtoMicrosoftAzure
Hyper-V
Microsoft
Azure
Replication
VMwareor Physicalto
VMware(on-premises)
VMwareor Physical VMware
Replication
VMwareor Physicalto
MicrosoftAzure
VMwareor Physical
Microsoft
Azure
Replication
Hyper-V toHyper-V
(on-premises)
Hyper-V Hyper-V
Replication
SAN SAN

18. One Solution for multiple infrastructures
• Automated VM level Replication and Failover.
• Planned and Unplanned Failover.
• Orchestrated Recovery Plans for Disaster Recovery.
• Test failover capabilities without impact to Production.
• Migrate to Azure from Anywhere.

19. Recovery Services Vault
• A Recovery Services vault is a storage entity in Azure that houses
data.
• Created a specific region as any other ARM resource.
• Some of the key features are:
• Enhanced capabilities to help secure backup data
• Central monitoring for your hybrid IT environment
• Role-Based Access Control (RBAC)
• Protect all configurations of Azure Virtual Machines
• Instant restore for IaaS VMs

20. Hyper-V to Azure Replication
Architecture

21. Hyper-V to Azure Replication
Architecture

22. ASR for Hyper-V workloads
• Prepare Azure.
• Prepare On-premises Hyper-V.
• Set up Disaster Recovery for Hyper-V VMs.
• Set up Disaster Recovery for Hyper-V VMs in VMM clouds (optional).
• Run a Disaster Recovery drill.
• Run failover and failback.

23. Prepare Azure
• Create an Azure Storage Account.
• Create an Azure Recovery Services Vault.
• Set an Azure network.

24. Prepare On-premises Hyper-V
• Review Hyper-V hosts and VMs requirements.
• Verify Internet Access.
• Prepare VMs so that they are accessible after failover.

25. Setup Disaster Recovery for Hyper-V
VMs
• Select a Protection Goal.
• Set up the source and target Replication environment.
• Create a Replication Policy.
• Enable Replication for a VM.

26. Run a Disaster Recovery drill
• Set up an isolated network for the test failover.
• Run a test failover for a single machine.

27. Run failover and failback
• Run a failover to Azure.
• Reprotect Azure VMs to the on-premises site.
• Failback from Azure to on-premises.
• Reprotect on-premises VMs to start replication to Azure again.

28. VMware to Azure Replication
Architecture

29. ASR for VMware workloads
• Prepare Azure.
• Prepare on-premises VMware.
• Setup Disaster Recovery.
• Run a Disaster Recovery drill.
• Run failover and failback.
Note: Steps 1, 4 and 5 are same as Hyper-V workloads

30. Prepare On-premises VMware
• Prepare an account on the vCenter server or vSphere ESXi host, to
automate VM discovery
• Prepare an account for automatic installation of the Mobility service
on VMware VMs
• Review VMware server requirements
• Review VMware VM requirements

31. Setup Disaster Recovery
• Enter the replication source and target.
• Set up the source replication environment, including on-premises
Azure Site Recovery components, and the target replication
environment.
• Create a replication policy.
• Enable replication for a VM.

33. Azure Backup

34. What is Azure Backup?
Azure Backup is the Azure-based service you can use to back
up (or protect) and restore your data in the Microsoft cloud.

35. Why use Azure Backup?
• Automatic Storage Management.
• Unlimited Scaling.
• Multiple Storage Options.
• Unlimited Data Transfer.
• Data Encryption.
• Application-consistent Backups.
• Long-term retention.

36. Azure Backup Components
• Azure Backup (MARS) agent.
• System Center DPM
• Azure Backup Server
• Azure IaaS VM Backup (VM Extension).

37. Supported Functionality

39. Questions?