Yousef A Khalidi Distinguished Engineer Microsoft Corporation AZR203 Session Objectives and Takeaways Session Objectives Understand business continuity support provided by Windows Azure Learn methods to maintain application availability ID: 725347
Download Presentation The PPT/PDF document "Business Continuity in the Windows Azure..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Business Continuity in the Windows Azure Cloud
Yousef A. KhalidiDistinguished EngineerMicrosoft Corporation
AZR203Slide2
Session Objectives and Takeaways
Session Objectives: Understand business continuity support provided by
Windows Azure
Learn methods to maintain application availability
Key Takeaways:
Windows Azure provides highly-available
and geo-distributed infrastructure
You have to architect your app for high availability
Your SLA requirements and budget constraints
will dictate the solutionSlide3
Cloud + Business Continuity
Some things change
New trust relationships
Plan for failure at multiple levels
Design to operate seamlessly through failures
A new option for the disaster recovery site
And some remain the sameYour business goalsYour availability and recovery objectivesWhat can you expect from the platform?How can you make your application highly available?Slide4
The Big Picture
Platform Preparedness
Preventing and recovering from outages
Platform Services
Optional availability services your applications can leverage
Application Architecture
Design your application to meet your availability goalsSlide5
What We Do to Protect the PlatformSlide6
Windows Azure World-Class By Design
State-of-the-art security and access
control
World-class data centers - redundant power, climate control, and fire prevention and suppression
Leading
innovator in power efficiency
Multi $billion cloud
infrastructure
Physical
Features
Geo-
Distribution
Platform Availability and Security
Compliance
and DR
Multiple data centers in different geographies
Local and geo-replication
Redundant platform services and failover
99.9% uptime, financially-backed SLAs
Highly available platform services
Service isolation over virtualized
compute and network
Clear boundaries and multiple lines of defense
Physical facilities have broad
compliance certifications
Service-level compliance
on near-term roadmap
Preparedness, testing, refinementSlide7
Highly Available Infrastructure
RedundancyDuplicate copies of all data
No single point of failure platform services
Redundant network switches, routers, etc.
Partitioning
Many separate compute and storage stamps
Separate fabric controller and related services for each stampOptimized for MTTRExpect and recover from failures quicklySlide8
North America Region
Europe Region
Asia Pacific Region
Major
datacenter
CDN
node
Windows Azure Global Presence
N. Central
– U.S. Sub-Region
S.E. Asia
Sub-Region
E. AsiaSub-Region
N. Europe
Sub-Region
W. Europe
Sub-Region
S. Central
– U.S. Sub-RegionEast – U.S. Sub-Region
West
– U.S. Sub-RegionSlide9
Platform-Level DR Preparedness
Capacity management
Extra capacity reserved in each
datacenter for DR purposes
“N+1” model for failover
Testing, simulations and process refinements
Platform meta state
Stored in storage system
Frequently check-pointed,
backed-up and geo replicated
On-going investment in disaster preparednessSlide10
Platform Services You Can LeverageSlide11
Platform Services
A set of building blocks
BLOB and Table
Geo-replication
SQL Azure
DB Copy
Traffic
Manager CTP
Application Health ManagementSlide12
North
Central US
South
Central US
North
Europe
West
Europe
East
Asia
South
East Asia
WA Storage Geo-Replication
Data geo-replicated across data
centers
hundreds of miles apart
Turned on right now for Blob and
Table
data Provides data durability in face of major data center disastersData geo-replicated within regions onlyUser chooses primary location during account creationOther datacenter in region is the secondary locationAsynchronous geo-replicationOff critical path of live requestsGeo-replicationSlide13
Geo-replication
WA Geo-Failover
Existing URL works
after
failover
Failover Trigger – failover would
only be used
if primary could
not
be recovered
Asynchronous Geo-replication – may lose recent updates
during failover
Typically geo-replicate
data within minutes
South Central USNorthCentral USFailover
Hostname
IP
Addressaccount.blob.core.windows.netSouth Central USUpdating…South Central US
Azure DNSUpdating IP AddressNew IP AddressNorth Central USSlide14
Location of Customer Data
Customers may specify the geographic
region
in which their Data will
be stored
Asia:
East and Southeast Europe: North and West
United States: North Central, South Central,East, West
Microsoft will not transfer Customer Data outside the major geographic region(s) customer specifies (for example, from Europe to U.S. or from U.S. to
Asia) except:
Where the customer configures the account to enable this, e.g., through use of the Content Delivery Network (CDN) featureWhere necessary for Microsoft to provide customer support, to troubleshoot the service, or comply with legal requirementsMicrosoft
does not control or limit the regions from which customers or their
end users may access Customer DataMicrosoft may transfer Customer Data within a major geographic region (e.g., within Europe) for data redundancy or other purposesSlide15
SQL Data Sync
Goals of Data Sync
Synchronization of data between
SQL Server databases and
SQL Azure databases
Synchronization of data between
two or more SQL Azure databasesChallengesPreservation of transaction boundariesSome schemas are not supportedNo support for multiple versionsSync
SQL
AzureSlide16
SQL Azure HA Recommendations
Enable resiliency by app
re-try logic
Enable point in time recovery by maintaining several snapshots
Convert to BACPAC and blobs
to minimize storage cost
Enable geo-redundancy by exporting BACPAC(s) into multiple datacentersConsider using blob geo-replication to minimize storage and bandwidth costSlide17
User initiated geo-replication
Automatic replication and synchronization
Optional RPO enforcement
Read-only geo-secondary
Multiple geo-secondaries
User-controlled termination for failover
Roadmap: Evolution of HA in SQL AzureSlide18
Backup to attached storage
Highly available
Restore to new database
Any point in time within retention period
Roadmap: Point in time recovery
P
S
S
PSlide19
Windows Azure Traffic Manager
Load balance user traffic across hosted services running in same
or different
datacenters to build globally available, high performing apps
Hosted
Service
Hosted
Service
Hosted
Service
Load-balancing
Endpoint monitoring
www.foo.comfoo.trafficmgr.cloudapp.netCNAMEPoliciesDNS based traffic management based on policies: Performance, Round- robin, FailoverImprove app performance by serving user requests with services ‘closest’ to them
Improve app availability by automatically failing over when a service goes downSlide20
Architecting Your App for High AvailabilitySlide21
Deploy to
multiple regions
Route traffic intelligently with Traffic Manager
Synchronize data
Application Design Best Practices
“Performance
” policy for active-active
“Failover” policy for active-passive
SQL Azure
Backup and Data
Sync
Other storage (custom-built replication)
Specify locations of compute and storage resources
Capacity and app arch considerationsSlide22
Consider Your Application Portfolio
Mission critical
High impact
Low impactSlide23
Application Design Patterns
Redeploy on failure
Single data center deployment
Everything ready for redeploy
Capacity as available
Active / passive
Single data center activeStaged in additional data center(s)Reserve capacity, scale as neededActive / activeMultiple data centers active
Use all of what you reserveOptimize connections for performance
Plan it, test
itAssetsPeople
ProceduresConnectionsDependencies
Balance
CostComplexityRecovery timeRecovery pointReserved capacitySlide24
Ideal Approaches
Mission critical
High impact
Low impact
Redeploy on Failure
Active/Passive
Active/ActiveSlide25
Things To Think About
Logic that
needs to be
site/instance-aware
Availability objectives
versus cost
Cold/warm/hot standby
Synchronous or
asynchronous replication,
tolerance for loss
What components can be distributed and stateless?Slide26
Important Considerations
Data stored in Windows Azure blobs and tables is automatically replicated
to
peer data center
Can't access remote data until storage failover is complete
Microsoft decides when the failover occurs
Other data and applications are not replicated and do not automatically failover between data centersMaintain deployments in secondary data center to guarantee capacitySlide27
Using Windows Azure
as a Disaster Recovery Site
Run VMs in cloud or on-premises
Periodically back up
VHDs in
blob storage
Launch VMs in the cloud
Consider application architecture and dependencies
AD,
databases, other services
Use Windows Azure for data backup
SQL Azure Sync
Backup data to blob store3rd party appliances Slide28
Using Windows Azure as Online Backup
with Windows Server 2012
Inbox Engine
Inbox UI
Windows Server 2012 Backup (Extensible)
Windows
Server
2012
3
rd
Party Cloud
Microsoft Online
Backup Service
3rd Party OnlineBackup ServiceMicrosoft OnlineBackup PortalSign up
& BillingIT Adminor VAPIT Adminor VAPRegistrationRegistrationBackup/RestoreBackup/Restore
Sign up
& BillingSlide29
Comprehensive Compliance Framework
ISO/IEC 27001:2005 certification
Certification and Attestations
SSAE 16 attestations
Predictable Audit Schedule
Controls Framework
Payment Card Industry Data Security Standard
Health Insurance Portability and Accountability Act
Industry
Standards and Regulations
Media Ratings Council
Sarbanes-Oxley, GLBA, etc.
Test effectiveness and assess riskAttain certifications and attestationsImprove and optimize
Examine root cause of non-complianceTrack until fully remediatedIdentify and integrateRegulatory requirementsCustomer requirementsAssess and remediate Eliminate or mitigate gaps in control designSlide30
More Information: Windows Azure Trust Center
http://www.windowsazure.com/en-us/support/trust-center/
One
location to aggregate
content
across Security,
Privacy
,
and ComplianceSlide31
Summary
Multi-level failure handling built into Windows Azure platform
Platform provides you building
blocks to
use in your
app
You have to architect your app for high availabilityAvailability objectives versus costDesign to operate seamlessly through failuresWindows Azure continues to invest in high availabilitySlide32
Related Content
Find Me Later
At the TLCSlide33
Track Resources
Meetwindowsazure.com
@
WindowsAzure
@
teched_europe
DOWNLOAD Windows Azure
Windowsazure.com/teched
Hands-On LabsSlide34
Resources
Connect. Share. Discuss.
http
://europe.msteched.com
Learning
Microsoft Certification & Training Resources
www.microsoft.com/learning
TechNet
Resources for IT Professionals
http://microsoft.com/technet
Resources for Developers
http://microsoft.com/msdn Slide35
Evaluations
http://europe.msteched.com/sessions
Submit your evals
online Slide36
©
2012 Microsoft
Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the
part
of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.Slide37