Planning for disaster recovery
Since workloads that require backup on OpenStack consist mainly of persistent instances, we must back up all parts of the instance; not only the disk image(s) that holds all of the runtime and persistent data but also the metadata that is required to make the workload instance(s) able to be restored from backup. However, OpenStack lacks the ability to provide a policy-based, automated, comprehensive backup and recovery solution. While OpenStack provides a patchwork of tools and APIs to provide some sort of backup effort, even tools such as OpenStack's Cinder API, which provides support for taking full and incremental volume snapshots, are still disruptive and the workload has to be taken offline to take a snapshot ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access