Launch a new Slave-DB

Objective

To launch a new Slave-DB server that will start replicating with the Master-DB. 

Table of Contents

Background

You should only launch a Slave-DB if you already have an operational Master-DB and a completed backup (snapshots).   When the Slave-DB becomes operational, it will automatically start replicating data from the Master-DB.  Since the Slave-DB will typically be initialized with the most recent backup of the Master-DB, the time required for the Slave-DB to become in-sync with the Master-DB should be minimized.

If you have a running Master-DB instance, you can launch a new Slave-DB and have it automatically start replicating with the Master-DB by setting the INIT_SLAVE_AT_BOOT input variable set to "True" at launch time.  After a slave has been initialized, its contents will be in-sync with the master and the replication will be active.

Note: If you are launching a Slave-DB server for the first time with RightScale's premium MySQL ServerTemplates, it's recommended that you follow the appropriate "stripe" MySQL Database Setups tutorials.

If you are launching a master and slave for the first time, you should follow the MySQL-EBS v2 Database Setup tutorial.

Steps

1. Verify that you have a completed backup (set of snapshots) that's available for creating the volume stripe for the Slave-DB.  It doesn't matter if the backup is of a master or slave.  Verify that all of the backup snapshots are 100% complete before going to the next step. For example, if your stripe count is 3, you must wait for all 3 EBS Snapshots to be 100% complete before going to the next step. To track the status of the snapshots, go to Clouds -> AWS Region -> EBS Snapshots.
2. Go to your Deployment (Manage -> Deployments).
3. Verify that the Master-DB is operational.
4. Launch the Slave-DB server.  When viewing the input confirmation screen, set the input variable, INIT_SLAVE_AT_BOOT = True, so that the Slave-DB server will become a "slave" of the Master-DB.

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 Slave-DB server can become operational.
• New volumes will be created and attached to the Slave-DB.
• To verify that the Slave-DB is properly connected to the Master-DB, see Checking master or slave database status.

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.