SPAJAMO TEHNOLOGIJUI ZNANJE

KONFERENCIJA 2017.

Azure kao backup i

disaster recovery

rješenje

Tomica Kaniškitomica@kaniski.eu | https://blog.kaniski.eu/

SPONZORI

Pokrovitelji

SPONZORI I POKROVITELJI

THE BACKUP 3-2-1 RULE

2Different media

3Different copies

of data

1of which is off-site

Azure

(https://www.veeam.com/)

• Recovery point objective (RPO) – the amount of

acceptable data loss if a recovery needs to be done("How much data can I lose?")

• Recovery time objective (RTO) – the amount of time that it

takes to complete a recovery or restore("How much time do I require to be back online?")

• Retention - How long data needs to be stored("Is there any regulation on storing my data?")

CONCEPTS

BACKUP OPTIONS

(https://docs.microsoft.com/en-us/azure/backup/backup-introduction-to-azure-backup)

• Azure-based service you can use to back up (or protect)

and restore your data in the Microsoft cloud

• replaces (or extends) your existing on-premises or off-site

backup solution with a cloud-based solution that is reliable,

secure, and cost-competitive

• agent-based protection

AZURE BACKUP (AB)

https://azure.microsoft.com/documentation/videos/what-is-azure-backup/

• Automatic storage management & pay-as-you-use

• Unlimited scaling

• Multiple storage options (LRS, GRS)

• Unlimited data transfer (does not limit or charge for the data

that is transferred)

• Data encryption (only you have the passphrase)

• Application-consistent backup (VM, SQL, Exchange, ...)

• Long-term retention (9999 recovery points per protected

instance)

WHY AZURE BACKUP?

• Azure Backup (MARS) agent

• System Center DPM

• Azure Backup Server

• Azure IaaS VM Backup

COMPONENTS

https://docs.microsoft.com/en-us/azure/backup/backup-introduction-to-azure-backup

• on-premises or in Azure

• locally on the server it protects

• on the "platform" (Hyper-V host, Azure)

• as an "extension" of the current backup solution

DEPLOYMENT SCENARIOS

• online storage entity in Azure used to hold data such as

backup copies, recovery points, and backup policies (to

organize stuff)

• Backup Vault – v1, if you used backup services before

• Recovery Services Vault – v2, advanced... for a fresh start

VAULT

https://docs.microsoft.com/en-us/azure/backup/backup-azure-recovery-services-vault-overview

STORAGE SUPPORT

(https://docs.microsoft.com/en-us/azure/backup/backup-introduction-to-azure-backup)

• all backup traffic from your servers to the Recovery

Services vault is encrypted (AES-256)

• backups are sent over HTTPS and stored encrypted

• only you have the passphrase to unlock the data!

(Microsoft doesn't know it)

• for encrypting the Azure VM backups, use BitLocker or

dm-crypt

• throttling and compression are supported

SECURITY

• application failure

• virtual machine failure

• network failure

• chassis failure (single host or blades?)

• rack failure

• datacenter disaster

• building disaster

• campus disaster

• planet disaster (☺)

DISASTERS

• (relatively) old and proven technology ("Windows Server 2012 era")

• it's not a backup or HA solution!!!

• part of the Windows Server Hyper-V role

• replicates live virtual machines from one Hyper-V host server to

another to keep your workloads available in case of...

• failover isn’t automatic and it shouldn't be!

(when you have a disaster, you want to be in charge of recovery ☺)

HYPER-V REPLICA

https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/manage/set-up-hyper-v-replica

(http://windowsitpro.com/hyper-v/configuring-hyper-v-replica-windows-server-2012)

• keep your apps running on VMs and physical servers

available if a site goes down

• replicate workloads running on VMs and physical servers

so that they remain available in a secondary location if the

primary site isn't available

• recover workloads to the primary site when it's up and

running again

AZURE SITE RECOVERY (ASR)

• simple BCDR solution

• on-premises and Azure VMs replication

• support for any workload (Hyper-V, VMware, Azure VMs, physical)

• consistent application failover (application-consistent snapshots)

• continuous replication (30+ seconds frequency)

• disaster recovery testing without disruption of replication

• recovery plans (multiple replica failover plans)

• integration with Azure Automation

ASR PROVIDES

• replicates/orchestrates:

• Azure VMs between Azure regions (in preview)

• on-premises Hyper-V VMs, VMware VMs, physical servers (Windows and

Linux) to Azure or to a secondary site (use VMM for full support)

• can replicate any application (on a supported machine), but

additionally tested with https://docs.microsoft.com/en-us/azure/site-

recovery/site-recovery-workload#workload-summary

• supported regions are https://azure.microsoft.com/en-

us/regions/services/

ASR SUPPORTS

https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-overview

HYPER-V TO AZURE

(https://docs.microsoft.com/en-us/azure/site-recovery/concepts-hyper-v-to-azure-architecture)

VMM TO AZURE

(https://docs.microsoft.com/en-us/azure/site-recovery/concepts-hyper-v-to-azure-architecture)

HYPER-V TO HYPER-V

(https://docs.microsoft.com/en-us/azure/site-recovery/concepts-hyper-v-to-azure-architecture)

• IP addresses after failover:

• different – new IP, requires DNS update

• same – old IP, requires route update

(IP is in Azure now)

• subnet failover

• subnet is present on either site (not on both!)

• during the failover, the whole subnet

moves with the VMs!

• requires network-level "action" and support

• you decide which one is right for you (☺)

NETWORKING

https://docs.microsoft.com/en-us/azure/site-recovery/concepts-on-premises-to-azure-networking

• there is a tool that helps you to plan disaster recovery resources

• evaluate size/churn requirements in your source deployment (Hyper-V

and VMware/Physical) and understand the resources you need for

seamless disaster recovery

• planner "modes":

• quick planning

• detailed planning

CAPACITY PLANNER

https://docs.microsoft.com/en-us/azure/site-recovery/site-recovery-capacity-planner

DEMO

Azure Backup & Azure Site Recovery

• disaster will happen.

• "backup and disaster recovery business" is not simple!

• there are tools and products that can help simplify it!

• good planning is crucial! (as always)

• there are many options – choose

what's best for you (only you know

your environment completely)!

• restore it, test it, repeat it!

KEY TAKEAWAYS

• https://1drv.ms/f/s!AriQqPJmIhX7iR_YqvGk6nxQqj-T

• https://azure.microsoft.com/en-us/free/

• https://azure.microsoft.com/en-us/pricing/details/backup/

• https://docs.microsoft.com/en-us/azure/backup/backup-

introduction-to-azure-backup

• https://docs.microsoft.com/en-us/azure/site-recovery/site-

recovery-overview

RESOURCES

HVALA!