Note: Please go to to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > ServerTemplates > Archive > Pre-11H1 > MySQL-S3 > Database Manager for MySQL-S3 Runbook > MySQL-S3 Problem Scenarios > The Slave-DB instance failed

The Slave-DB instance failed

Recovering from a slave failure is as easy as launching a new slave template and initialize it from the
existing master.

Verification: how do I know my system is in this situation?

  1. Access the "active instances" (Manage -> Servers)
  2. Verify that none of the running instances derive from the slave template (i.e., click on each instance and check that it's template field is not Slave MySQL v?).

Required actions: What recipes should I apply to solve the situation?

  1. Launch a new Slave-DB
  2. Initialize Slave-DB from Master-DB
You must to post a comment.
Last modified
21:34, 16 May 2013



This page has no classifications.



© 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.