Book Image

OpenStack Trove Essentials

By : Alok Shrivastwa, Sunil Sarat, Doug Shelley, Amrith Kumar
Book Image

OpenStack Trove Essentials

By: Alok Shrivastwa, Sunil Sarat, Doug Shelley, Amrith Kumar

Overview of this book

OpenStack has become an extremely popular solution to build public and private clouds with. Database as a Service (DBaaS) enables the delivery of more agile database services at lower costs. Some other benefits of DBaaS are secure database deployments and compliance to standards and best practices. Trove is a DBaaS built on OpenStack and is becoming more popular by the day. Since Trove is one of the most recent projects of OpenStack, DBAs and system administrators can find it difficult to set up and run a DBaaS using OpenStack Trove. This book helps DBAs make that step. We start by introducing you to the concepts of DBaaS and how is it implemented using OpenStack Trove. Following this, we look at implementing OpenStack and deploying Trove. Moving on, you will learn to create guest images to be used with Trove. We then look at how to provision databases in self-service mode, and how to perform administration tasks such as backup and recovery, and fine-tuning databases. At the end of the book, we will examine some advanced features of Trove such as replication.
Table of Contents (15 chapters)
OpenStack Trove Essentials
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Preface
Index

Formulating a backup and recovery plan


There are two kinds of backups: full backup and incremental backup. Trove helps with both of the backups (with certain data stores), as we will see later in the chapter. A plan needs to be formulated in order to successfully execute these.

The frequency of both or either of these backups needs to be based on the following parameters:

  • Importance of the data

  • Frequency of changes in the database

  • Recovery objectives (RTO, RPO)

Based on the preceding parameters, we will need to derive the following key points:

  • Frequency of full backups

  • Frequency of incremental backups (if any)

  • Frequency of testing the backups (by restoring the database)

  • Need for offsite shipping of the database backup

  • Frequency and modes of offsite shipping

This plan is applicable to any form of backup and this will help us with scripting and automating the backup tasks.