If you want to take the Master-DB instance offline, it's important that the availability of the data is not effected. The safest way to take an existing master DB offline is to promote the existing slave to master, launch and initialize a new Slave-DB, and then safely terminate the old Master-DB.
You should only be in this situation if you need to perform an action that requires disconnecting the current Master-DB from the deployment. Remember, in the cloud you always roll-forward by promoting a slave to become the new master. You never want to take the Master-DB instance offline and then make it your Master-DB again.
Common situations may include:
© 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.