The Database service provides scalable and reliable cloud provisioning functionality for both relational and non-relational database engines. Users can quickly and easily use database features without the burden of handling complex administrative tasks.

Before you create a database instance, you need to configure a default datastore and make sure you have an appropriate flavor for the type of database instance you want. Because the dashboard does not let you choose a specific datastore to use with an instance, you need to configure a default datastore. The dashboard then uses the default datastore to create the instance. Add the following line to /etc/trove/trove.conf: default_datastore = DATASTORE_NAME Replace DATASTORE_NAME with the name that the administrative user set when issuing the trove-manage command to create the datastore. You can use the trove datastore-list command to display the datastores that are available in your environment. For example, if your MySQL datastore name is set to mysql, your entry would look like this: default_datastore = mysql Restart Database services on the controller node: # service trove-api restart # service trove-taskmanager restart # service trove-conductor restart Make sure an appropriate flavor exists for the type of database instance you want. Once you have configured a default datastore and verified that you have an appropriate flavor, you can create a database instance. Log in to the dashboard, choose a project, and click Databases. Click Database Instances. This lists the instances that already exist in your environment. Click Launch Instance. In the Launch Database dialog box, specify the following values. Details Database Name Specify a name for the database instance. Flavor Select an appropriate flavor for the instance. Volume Size Select a volume size. Volume size is expressed in GB. Initialize Databases Initial Database Optionally provide a comma separated list of databases to create, for example: database1, database2, database3 Initial Admin User Create an initial admin user. This user will have access to all the databases you create. Password Specify a password associated with the initial admin user you just named. Host Optionally, allow the user to connect only from this host. If you do not specify a host, this user will be allowed to connect from anywhere. Click the Launch button. The new database instance appears in the databases list.

You can use Database services to backup a database and store the backup artifact in the Object Storage module. Later on, if the original database is damaged, you can use the backup artifact to restore the database. The restore process creates a database instance. This example shows you how to back up and restore a MySQL database. Log in to the dashboard, choose a project, and click Databases. Click Database Instances. This displays the existing instances in your system. Click Create Backup. In the Backup Database dialog box, specify the following values: Name Specify a name for the backup. Database Instance Select the instance you want to back up. Description Specify an optional description. Click Backup. The new backup appears in the backup list. Now assume that your original database instance is damaged and you need to restore it. You do the restore by using your backup to create a new database instance. Log in to the dashboard, choose a project, and click Databases. Click Database Backups. This lists the available backups. Check the backup you want to use and click Restore Backup. In the Launch Database dialog box, specify the values you want to use for the new database instance. Click the Restore From Database tab and make sure that this new instance is based on the correct backup. Click Launch. The new instance appears in the database instances list.