To initialize a Slave-DB server from a running Master-DB server.
Table of Contents
There are two ways to initialize a Slave-DB from a running Master-DB server. You can either launch a new Slave-DB that will automatically initialize with the running Master-DB at boot time or manually initialize a Slave-DB with the Master-DB by running an operational script.
When you initialize a Slave-DB from a Master-DB, new EBS volumes are created from the most recent backup snapshots of the database. By default, the most recently completed snapshots will be used (regardless of whether they are backups from a master or slave).
New volumes will be created from the chosen snapshots and mounted to the new Slave-DB. The contents of the Master-DB will then be copied over to the Slave-DB. Once all of its contents are in-sync with the master, replication will become active.
For complete details about how to set up a Slave-DB from a Master-DB for the first time, find the appropriate MySQL Database Setup tutorials.
The Events pane will highlight the progress of the operation. Click on the link to view a detailed output of the action that can be used to troubleshoot the cause of a failure, if necessary.
Typically you will configure a Slave-DB so that it automatically initializes with the Master-DB at boot time (INIT_SLAVE_AT_BOOT = True). However, perhaps you've launched a database server a different way (INIT_SLAVE_AT_BOOT = False). Follow the steps below to initialize the running database server so that it becomes a Slave-DB of the Master-DB.
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.
© 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.