1.
23 NOIEMBRIE 2017 | BUCUREȘTI
Azure Site Recovery & Backup în
Microsoft Azure
FLORIN LOGHIADE
Cloud & DevOps Engineer / Avaelgo
Microsoft Azure MVP
Twitter: @FlorinLoghiade
Blog: FlorinLoghiade.ro

2.
23 NOIEMBRIE 2017 | BUCUREȘTI
Mulțumiri sponsorilor și partenerilor
SPONSORI
ORGANIZATOR
PARTENER MEDIA
PARTENER DE IMAGINE

3.
23 NOIEMBRIE 2017 | BUCUREȘTI
Agenda
• Azure Backup
• Azure Site Recovery

4.
23 NOIEMBRIE 2017 | BUCUREȘTI
AZURE BACKUP

5.
23 NOIEMBRIE 2017 | BUCUREȘTI
• Reliable Offsite Data Protection
• Easy replacement for tape backup
• Protect individual servers on-premises or in the Cloud
• Integrates with DPM and Windows Server Backup
• Stores Backup Data in Azure Storage
Microsoft Azure Backup

6.
23 NOIEMBRIE 2017 | BUCUREȘTI
Backup and recovery
• The support team should:
–Protect from unwanted updates / deletions
–Long-term archive
–Tenant-specific backup/restore
• Not done 100% by Microsoft

7.
23 NOIEMBRIE 2017 | BUCUREȘTI
Conventional backup approaches

8.
23 NOIEMBRIE 2017 | BUCUREȘTI
Azure Backup – Architecture matters
Recovery Point
Management
Storage
Management
Data Pruning
Data Packing
Authentication
Policy
Management
Access Control
Monitoring
&
Reporting
No infrastructure Enterprise scale Extensible Central management

9.
23 NOIEMBRIE 2017 | BUCUREȘTI
Linux application-consistent backup

10.
23 NOIEMBRIE 2017 | BUCUREȘTI
DEMO
Protecting Azure Workloads

11.
23 NOIEMBRIE 2017 | BUCUREȘTI
Windows Server System State Backup
System
State
IIS
File Server
Active Directory
Microsoft
Microsoft
Microsoft

12.
23 NOIEMBRIE 2017 | BUCUREȘTI
Microsoft Azure Recovery Services (MARS)
• All data is encrypted at source, and Microsoft does not have the
secret to decrypt the data
• Data is compressed and backup works on an efficient synthetic
full basis, just taking changes
• MARS can only backup files and folders at this time
• There’s no centralized alerting at this time
• The scenarios where MARS suits include:
– Backing up laptops that are rarely in the office.
– A small business or branch office with a file server.
– Providing granular protection for files and folders in a cloud virtual
machine.

13.
23 NOIEMBRIE 2017 | BUCUREȘTI
Microsoft Azure Backup Server

14.
23 NOIEMBRIE 2017 | BUCUREȘTI
AZURE SITE RECOVERY

15.
23 NOIEMBRIE 2017 | BUCUREȘTI
Why disaster recovery is needed
• Every company relies on IT systems to
operate in this digital world
• Implementing disaster recovery across
your enterprise can be daunting and
therefore avoided
• Yet, nearly every company is
susceptible to some kind of disaster
• Failure to provide service can lead to
not only a service outage but long
term brand damage

16.
23 NOIEMBRIE 2017 | BUCUREȘTI
• Cost
• Data center cost
• Resource cost
• Hardware cost
• Complexity
• Multiple data centers
• Replication technologies/restore hardware
• Managing management software
• Reliability
• Recovery of data
• Providing service
Challenges implementing disaster recovery

17.
23 NOIEMBRIE 2017 | BUCUREȘTI
• Alternative location
• Meet tight RPO and RTO objectives
How is disaster recovery achieved on-premises?
Primary Secondary

18.
23 NOIEMBRIE 2017 | BUCUREȘTI
• The same process as on-premises, but with the
benefits of Azure
Disaster recovery to Azure
Primary Cloud
StorSimple/Azure Files Sync
Azure Site Recovery
Azure Site Recovery
SQL AlwaysOn, etc.

19.
23 NOIEMBRIE 2017 | BUCUREȘTI
• Should the service just move to the cloud?
• Consider services like Exchange, SharePoint, Skype
• These would be critical during a DR failover to
facilitate communication between parties
• A better option may be to move to a SaaS based
solution in the cloud, e.g. Office 365
• Could also use similar approach for other services
that are available as SaaS or even move to cloud
PaaS/IaaS for regular production use
Service migration to Azure?

20.
23 NOIEMBRIE 2017 | BUCUREȘTI
• Enables Azure to be the replication target for Hyper-
V VMs via ASR
Hyper-V Replication to Azure
VM HRL
Azure
Write
HRL

21.
23 NOIEMBRIE 2017 | BUCUREȘTI
• VMs on VMware or OS instances on physical
hardware
• Guest-based replication solution
• Disk driver writes are sent to Azure via an on-
premises process server
OS-Level replication
Write
Write VHDWrite

22.
23 NOIEMBRIE 2017 | BUCUREȘTI
Side Note
• These same technologies
can be used to migrate to
Azure
• What is a migration?
–Replication
–Failover
• Free for the first 31 days per
OS instance

23.
23 NOIEMBRIE 2017 | BUCUREȘTI
• Running an instance in Azure requires:
• Network connectivity (S2S VPN/ExpressRoute)
• Compute charges
• Services requiring the highest RPO/RTO are
good candidates such as tier 1 SQL Servers
or domain controllers
• Other less critical applications may use a
cheaper option such as ASR
Application-level replication
SQLAvailabilityGroup

24.
23 NOIEMBRIE 2017 | BUCUREȘTI
• Azure can create 100’s of service instances in minutes
• For stateless services, e.g. web front end rather than
replicating consider using VM Scale Sets (VMSS)
• Removes the need for licensing and compute charges
Not all components need replication
Gold Image
Declarative Configuration
VMSS
Config

25.
23 NOIEMBRIE 2017 | BUCUREȘTI
• For each workload and its
dependencies a failover technology
will be selected
• The failover process should be a
single-click action
• Azure Site Recovery provides
recovery plans that enable each step
of the failover to be designed
Orchestration

26.
23 NOIEMBRIE 2017 | BUCUREȘTI
• Remember that just moving something to the cloud to IaaS/PaaS
does not mean DR is handled
• Still consider full resiliency for services
• Consider services deployed to multiple regions and utilize Azure
Traffic Manager with scale as required
Azure Service Protection
GRS
Azure Site Recovery
SQL AlwaysOn
Azure SQL DB Active Geo Replication

27.
23 NOIEMBRIE 2017 | BUCUREȘTI
• Same failover
experience and features
of on-premises to Azure
replication
• Setup and test disaster
recovery in 3 steps
• Quickly ensure your
applications are
compliant
Azure to Azure disaster recovery

28.
23 NOIEMBRIE 2017 | BUCUREȘTI
Q & A

29.
23 NOIEMBRIE 2017 | BUCUREȘTI
Thank you!