150 likes | 478 Views
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 .
E N D
Enabling DraaS on OpenStack Speakers: Haribabu Kasturi, Amitabh Shukla
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 • A DR option on homogenous environments enables workloads to use services from platforms effectively • Simpler Implementation of failback • 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
Sources for DR Virtual Machines Private Cloud Physical Machines DRaas
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 failure • Ex: 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
DraaS on OpenStack alternative #1 DR-VM Virtual Machines 6 Dash Board 4 5 DraaS Agent 1 DraaS Service 2 Cinder RPO > 30 Min RTO < 10 Min 3 Cinder- Volumes
Steps involved • DraaS Agent Requests Back UP • DraaS Service assigns the Data VM that stores the delta snapshot • Data VM is writes deltas to the cinder volume such that exact replica of source disk is maintained • User/ Backup program initiates backup • DraaS Service requests Compute cluster to boot from cinder • DR VM comes up and accessible
DraaS on OpenStack alternative #2 DR-VM Virtual Machines Dash Board 6 5 3 4 Swift Merged Image DraaS Agent 1 DraaS Service 2 Glance RPO > 12 hrs RTO < 1 Hr Compute
Steps Involved • DraaS Agent pushes Snapshots periodically to DraaS service • DraaS Service pushes objects to swift • User/ Backup program initiates backup • DraaS service requests compute to boot machine • DraaS Service merges snapshots and uploads to glance • DR VM comes up and accessible
Challenges • Huge Data movement between Crystals • RTO and RPO requirements • “No change” syndrome for already existing Cloud • Application Quiescing involves in Synchronous backing of various VM’s on timeline • Small implementation issues
Next Steps • Define incubated project for DRaaS for OpenStack • Enhance Disk Replication Service in OpenStack for DRaaS support • Define and develop Agents for various types of end points as OpenStack Projects
Thank you all on behalf of Persistent. Feedback / Questions: haribabu_kasturi@persistent.co.in vijesh_rangaswami@persistent.co.in shriram_natarajan@persistent.co.in