Note: Please go to docs.rightscale.com to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > ServerTemplates > Archive > 11H1 > Runbooks > Database Manager for MySQL Stripe Runbook > MySQL Stripe Recipes > Launch a new Master-DB

Launch a new Master-DB

Objective

To launch a new Master-DB instance where you manually restore the MySQL database by using an existing set of backup snapshots to create and attach all volumes in the EBS stripe. 

Note: If you do not have a previous set of backup snapshots to restore from and are launching a Master-DB server for the first time with RightScale's premium MySQL ServerTemplates, you will need to follow the appropriate "stripe" MySQL Database Setups tutorials to launch a new Master-DB.

 

Table of Contents

Background

By default, the backup that will be used to initialize and restore the database will be the most recently completed set of backup snapshots that match the lineage as specified by the DB_LINEAGE_NAME input variable (regardless of whether they are snapshots of the master or slave).  If you don't want to use the most recent set of backup snapshots you can use the OPT_DB_RESTORE_LINEAGE_OVERRIDE and OPT_DB_RESTORE_TIMESTAMP_OVERRIDE input variables to override and select a specific backup (set of EBS snapshots).    For example, if your database is corrupted, you can perform database restorations to find your last clean (uncorrupted) copy.  If you're creating a Staging Deployment, you may want to setup your database servers with the most recent backup of the Production Deployment.  But be careful!  If you forget to change the DB_LINEAGE_NAME to be different than your Production Deployment, you could accidentally create backups for your live production environment!

Note: If you use the override inputs to restore from a backup (set of snapshots) with a different lineage name (DB_LINEAGE_NAME), it's important to realize that future backups will be created and named according to the DB_LINEAGE_NAME input.  As a best practice, the lineage name input should always be set at the Deployment level.

Steps

  1. Go to your Deployment (Manage -> Deployments).
  2. Find the Master-DB instance and click the Launch button.
  3. Set the input variable, INIT_SLAVE_AT_BOOT = False
  4. Once the Server is operational, go to the Deployment's Inputs tab. 
  5. Determine which backup snapshots will be used for the database restoration.  By default, the DB_LINEAGE_NAME input variable will select the most recent completed backup (regardless of whether they are snapshots of the master or slave).  However, you can use the OPT_DB_RESTORE_LINEAGE_OVERRIDE and/or OPT_DB_RESTORE_TIMESTAMP_OVERRIDE input variables to override and select a specific set of EBS snapshots.   (Click the Server's Inputs tab to check and make sure that these inputs are not being overwritten at the Server level.)
  6. Go to the Server's Scripts tab.
  7. Run the "DB EBS restore and become master" operational script.    The script will restore the MySQL database from the specified set of backup snapshots and update the DNS A record for the Master-DB.  A backup will also be initiated so that a set up snapshots will be available when you launch a new Slave-DB.  The new backup snapshots will be named using the DB_LINEAGE_NAME input.   Note:  Before launching a new Slave-DB you must wait for the new snapshots to become available (i.e. 100% complete).

What feedback to expect

The Events pane will highlight the progress of the operation.  Click on the name of an action in the pane to view a detailed output of the action that can be used to troubleshoot the cause of a failure, if necessary. 

  • The Master-DB will become operational.
  • New volumes will be created from the chosen set of backup snapshots and attached to the Master-DB.
  • The Master-DB's A Record will be updated with the Master-DBs private IP address.  To verify, you can log into your account with your DNS Provider.
  • Lastly, a new set of backup snapshots will be created.

 

IMPORTANT!   When you are done, make sure your Servers are named appropriately!  Make sure you know which Server is your master and which one is your slave.

You must to post a comment.
Last modified
14:12, 7 Oct 2014

Tags

Classifications

This page has no classifications.

Announcements

None


© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.