• Save
AWS Summit 2013 | Auckland - Technical Lessons on How to Do Backup and Disaster Recovery in the Cloud
Upcoming SlideShare
Loading in...5
×
 

AWS Summit 2013 | Auckland - Technical Lessons on How to Do Backup and Disaster Recovery in the Cloud

on

  • 1,143 views

Maintaining data integrity and guaranteeing business continuity is of utmost importance for any organisation. However, in today's world, those systems have grown in complexity and cost, while the ...

Maintaining data integrity and guaranteeing business continuity is of utmost importance for any organisation. However, in today's world, those systems have grown in complexity and cost, while the business demands IT agility and lower costs. In this talk, we will explore how organisations should approach backup and disaster recovery, and how these two aspects can be implemented in the cloud to improve efficiency and flexibility. The talk starts with general concepts, and then dives into technical details, culminating in real customer examples that showcase some tips and tricks and the benefits of a cloud-based approach.

Statistics

Views

Total Views
1,143
Views on SlideShare
916
Embed Views
227

Actions

Likes
0
Downloads
0
Comments
0

2 Embeds 227

http://www.scoop.it 226
http://webcache.googleusercontent.com 1

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    AWS Summit 2013 | Auckland - Technical Lessons on How to Do Backup and Disaster Recovery in the Cloud AWS Summit 2013 | Auckland - Technical Lessons on How to Do Backup and Disaster Recovery in the Cloud Presentation Transcript

    • Dean SamuelsRules for Backup and Disaster Recovery in the CloudSolution Architect
    • Agenda• Prologue The need for Backup and DR• Rules Backup and DR with AWS• Customer Reference Ausenco and NZ Post
    • The need for Backup and DR
    • Some “natural” examples….after Brisbane Floods – January 13th 2011Coronation Drive, Milton, QLD.…Photos: http://www.abc.net.au/news/specials/qld-floods/
    • Some “natural” examples….after Brisbane Floods – January 13th 2011Coronation Drive, Milton, QLD.…Photos: http://www.abc.net.au/news/specials/qld-floods/
    • Some “natural” examples….after Brisbane Floods – January 13th 2011Coronation Drive, Milton, QLD.…Photos: http://www.abc.net.au/news/specials/qld-floods/
    • Some “natural” examples….Christchurch Earthquake - Feb 22nd 2011Manchester & Glouchester Street, Christchurch....Photos: http://www.abc.net.au/news/specials/christchurch-quake/
    • Some “natural” examples….after Hurricane Sandy – October 29th 2012Breezy Point, Queens, NY, USA.…Photos: http://www.abc.net.au/news/specials/hurricane-sandy-before-after-photos/
    • What about “human-made” examples….“Everything fails, all the time”Werner Vogels, CTO, Amazon.com
    • Backup and DR with AWSDrivers for Backup and DR with AWS
    • Business and Technical Drivers with AWS….Reduce costsSlash DR budgets by up to 50%Consolidate sitesEliminate the need to run asecondary siteReduce on-premiseEliminate 30%+ of on-premisephysical equipmentRemove agingtechnologiesEliminate tape for backup andarchive
    • The fundamental economic model…Utility, on-demand datacenterPrimary SiteRoutersFirewallsNetworkApplication LicensesOperating SystemsHypervisorServersSANPrimary StorageBackupArchiveAWSRoutersFirewallsNetworkApplication LicensesOperating SystemsHypervisorServersSANSnapshot StorageBackupArchiveSecondarysite costs
    • You can have different DR solutions• Easy to integrate existing vendors with DR on AWS• Approach: One vendor/hybrid/multiple vendors• One region/multi-regions (if you need geo-diversity)• Different DR ArchitecturesBackup & Restore Pilot lightWarm standby inAWSMulti-site solutionin AWS & on-premise
    • Assets will sit on a spectrum of technical complexity…DR & business continuityRebuild whenrequired fromoffsite backupRun hot-hotconfiguration withauto-failoverRecovery Time Objective(RTO)How quickly you need this asset to be recovered?e.g. 1min? 15min? 1hr? 4hrs? 1day?Recovery Point Objective(RPO)How ‘fresh’ the recovery must be for the asset?e.g. zero data loss, 15mins out of date?
    • Backup and DR with AWSBackup and Storage Options
    • Simple Storage ServiceHighly scalable object storage1 byte to 5TB in size99.999999999% durabilityElastic Block StoreHigh performance block storage device1GB to 1TB in sizeMount as drives to instances withsnapshot/cloning functionalitiesGlacierLong term object archiveExtremely low cost per gigabyte99.999999999% durabilityStorage OptionsVery fast‘instance’ disksSlow, rare accessFast web objectstorage
    • Storage Gateway – Connect On-Prem with the AWS Cloud1. Local, low-latency access to themost frequently used files whilestoring all data in Amazon S3(Cached-Volumes)Or2. Scheduled off-site backups toAmazon S3 for on-premises data(Stored-Volumes)
    • Cost($/GB/month)Performance DurabilityAmazon S3 0.095  Amazon Glacier 0.01  AWS Storage Gateway0.095(+ 125/GW) Amazon EBS 0.10  Amazon EBS (PIOPS) 0.125  *AWS Oregon pricingStorage Options
    • Backup and DR with AWSBackup and DR Rules
    • 1. My backup should be accessible2. My backup should be able to scale3. My backup should be safe4. My backup should work with a DR policy5. Someone should care about itBackup Rules
    • VPNPublic / AWS Direct ConnectAWS Import/ExportBackup Rules – My backup should be accessible
    • GW-Cached volumesGW-stored volumes“Warm” storage“Cold”Backup Rules – My backup should be accessible
    • Access both via SDKs and via third-party softwareS3 GlacierInternet WebServices APIHTTP(S)Via SDK Via 3rd parties
    • • “Infinite” scale with Amazon S3 and Amazon Glacier• Scale to multiple regions• Seamless• No need to provision• Cost tiers (cheaper at scale)Backup Rules – My backup should be able to scale
    • • SSL Endpoints (Amazon S3 and Amazon Glacier)• Signed API calls• Store encrypted files• Server-side encryption• Multiple copies across different data centers• Local/cloud with AWS Storage GatewayBackup Rules – My backup should be safe
    • Backup Rules – My backup should work with a DR policy
    • • Clear ownership• Permissions with IAM: Users, groups  roles• Logs• AWS supportBackup Rules – Someone should care about it
    • Pilot lightStoppedinstances
    • Pilot lightRunninginstances
    • Backup and DR with AWSA “Backup/Restore” & “Pilot Light” reference…
    • Remember Brisbane, QLD…..Source: http://www.abc.net.au/news/specials/qld-floods/
    • Brisbane - January 13th 2011AusencoSource: http://www.abc.net.au/news/specials/qld-floods/
    • • ASX200 company• Head office in Brisbane• 29 Offices in 19 countries• 3500 EmployeesAusenco Offices
    • The Result• Low effort• Incremental rollout• Cloud migration• Efficient, effective usage of bandwidth• Application/database servers• Regionalised deployment
    • • New Zealand Post is a state-ownedenterprise responsible for providingpostal services in New Zealand.• “Pilot Light” Disaster Recovery solutionfor NZ Post Online platform• VPN connectivity back to on-premisefor data synchronisation of businesssystemsNew Zealand Post – Agile Disaster Recovery“AWS is providing us a costeffective and highly agiledisaster recovery capabilityfor our online platform.”Rob Holmes, Head of Online
    • Backup and DR with AWSThe new HA/DR continuum…
    • The new HA/DR continuum…DR with High Availability
    • App DR with StandbyThe new HA/DR continuum…
    • Reducing Costs• AWS cost reduction (e.g, S3 cost reduction on Apr 2nd 2013)• Reduced redundancy (Amazon S3)• Retention policy• Hot/warm/cool/cold backup• Reserved capacity/tiers0–1 TB 0.095 0.0761–50 TB 0.080 0.06450–500 TB 0.070 0.056500–1,000 TB 0.065 0.0521–5 PB 0.060 0.0485+ PB 0.055 0.037Amazon S3Standard$/GB/MonthReduced$/GB/Month34PriceReductions