enabling draas on openstack
DESCRIPTION
Enabling DraaS on OpenStack. Speakers: Haribabu Kasturi, Amitabh Shukla. Why Disaster Recovery?. Why DraaS on OpenStack?. Co-located DR infrastructure enables highest level of RTO & RPO Less number of failures and low latency to data backup. New customers from SME customers . - PowerPoint PPT PresentationTRANSCRIPT
© 2014 Persistent Systems Ltd
www.persistentsys.com
Enabling DraaS on OpenStackSpeakers: Haribabu Kasturi, Amitabh Shukla
© 2014 Persistent Systems Ltd 2
Why Disaster Recovery?
© 2014 Persistent Systems Ltd 3
Why DraaS on OpenStack?
Bring new customers to Cloud
Co-located DR
Infrastructure
Flexible Options for RTO & RPO
Business Continuity
for OpenStack
loads
New customers from SME customers
Various businesses require affordable & simple solution to a near real time CDP solution
Different RTO and options allow same stack to serve various customers with different solutions
A DR option on homogenous environments enables workloads to use services from platforms effectively
Simpler Implementation of failback
Co-located DR infrastructure enables highest level of RTO & RPO
Less number of failures and low latency to data backup
© 2014 Persistent Systems Ltd 4
Agenda
Evaluation of Sources for DraaS
Various DraaS
architecture
Evaluation of Current OpenStack
and features
Next Steps towards
DraaS on OpenStack
© 2014 Persistent Systems Ltd 5
Sources for DR
Physical Machines
Virtual Machines
Private Cloud
DRaas
© 2014 Persistent Systems Ltd 6
Basic Steps involved in DR
Source
• Convert P2V ?• Live Snapshotting?
Data capture and Transfer
• Capture Delta differences • Sync data with DR Cloud• Ensure confirmed State
Incident Detection
• Manual incident detection• Automated incident detection algorithms
Provision
• Challenges in provisioning• The RTO Challenge
© 2014 Persistent Systems Ltd 7
A little re-introduction of terms RPO : Recovery Point Objective is the age of files that must be recovered from
backup storage for normal operations to resume after failureEx: if the RPO is one hour, backups must be made at least once per hour.
RTO : Recovery Time Objective is the duration of time within which a Machine must be restored after a disaster (or disruption)Ex: if RTO is 10 minutes then the service must be recovered with in 10 minutes of
reporting failure.Delta Backups: Delta backups are the differences between the last Recovery
Point and now. These can be disk, configuration or meta data information
© 2014 Persistent Systems Ltd 8
DraaS on OpenStack alternative #1
Cin
der
DraaSService
Virtual Machines
DraaS Agent
Cinder- Volumes
1
2
3
RPO > 30 MinRTO < 10 Min
5
4
Dash Board 6
DR-VM
© 2014 Persistent Systems Ltd 9
Steps involved
1. DraaS Agent Requests Back UP2. DraaS Service assigns the Data VM that stores the delta snapshot3. Data VM is writes deltas to the cinder volume such that exact replica of
source disk is maintained4. User/ Backup program initiates backup5. DraaS Service requests Compute cluster to boot from cinder 6. DR VM comes up and accessible
© 2014 Persistent Systems Ltd 10
DraaS on OpenStack alternative #2 Virtual Machines
DraaS Agent
RPO > 12 hrsRTO < 1 Hr
Snapshot4
Snapshot3
Snapshot2
Snapshot1 Swift
Snapshot4
Snapshot3
Snapshot2
Snapshot1
DraaSService
Dash Board
Glance
Merged Image
Compute
DR-VM
1
2
43
6
5
© 2014 Persistent Systems Ltd 11
Steps Involved
1. DraaS Agent pushes Snapshots periodically to DraaS service 2. DraaS Service pushes objects to swift 3. User/ Backup program initiates backup4. DraaS service requests compute to boot machine5. DraaS Service merges snapshots and uploads to glance6. DR VM comes up and accessible
© 2014 Persistent Systems Ltd 12
Huge Data movement between CrystalsRTO and RPO requirements “No change” syndrome for already existing Cloud Application Quiescing involves in Synchronous backing of various VM’s on
timelineSmall implementation issues
Challenges
© 2014 Persistent Systems Ltd 13
Define incubated project for DRaaS for OpenStackEnhance Disk Replication Service in OpenStack for DRaaS supportDefine and develop Agents for various types of end points as OpenStack
Projects
Next Steps
© 2014 Persistent Systems Ltd 1414
© 2014 Persistent Systems Ltd
Thank you all on behalf of Persistent.
Feedback / Questions: [email protected][email protected]