Manager for MySQL Runbook

Manager for MySQL interface has been designed to hide the low level complexities of managing distributed DB systems and to provide a simple and intuitive interface. Despite its simplicity, there are still different paths that users can take in trying to resolve the various situations that might arise during the lifetime of the DB system. Not all of these possible resolution choices are always appropriate or even valid. This runbook is designed to guide Manager for MySQL operators in taking decisions that follow the best practices when facing the most typical situations.

This runbook is organized in sections corresponding to the most common situations that you may encounter when managing your MySQL databases.  To resolve common problem scenarios, identify and verify your problem, and then follow the list of suggested solution recipes.  Links to solution recipes will be listed at the end of each MySQL problem scenario.

While unexperienced operators might need to consult the solution recipe details to resolve the situations at the beginning, more seasoned operators will be able to quickly resolve them by simply looking at their names.

NOTE: The MySQL Runbook is not meant to provide a substantial background of the underlying architecture of Manager for MySQL.

Use the links below or download the pdf version: Manager for MySQL Runbook

• Overview
  • MySQL Server Templates
    
    
• MySQL Setup Tutorial
  • Create a Redundant MySQL Setup

• MySQL Problem Scenarios
  • There are no running DB instances! (master or slave)
  • The master DB instance failed
  • The slave DB instance failed
  • I want to take the master DB instance offline
  • I want to perform a manual backup at this moment
  • The master DB is corrupted
  • The slave DB is corrupted
  • Both the master and slave are corrupted
    
    

• MySQL Recipes
  
  • Launch a new master DB
  • Launch a new slave DB
  • Reinitialize master DB contents
  • Initialize slave DB from master DB
  • Promote slave DB to master DB
  • Backup master DB
  • Restore a previous DB backup
  • Disable or enable continuous backups
  • Perform a clean, full system shutdown