Once you've launched a new Slave-DB instance, the DB is fully operational. If INIT_SLAVE_AT_BOOT is set to false then DB contents initialization and replication start needs to be executed as a separate action using the DB EBS init slave operational script. Initializing the slave from a master involves, first creating an new EBS volume from the latest master snapshot, and then start replication from the first transaction after the copied contents. After a slave has been initialized, its contents will be in in sync with the master and the replication will be active.
A notification on the Recent Events pane should indicate that the Slave-DB server is pending.
To confirm it, we can:
IMPORTANT! When you are through make sure your Servers are named appropriately! For example, if you have a new master and a new slave Server, make sure you name (or rename) your Servers appropriately.
© 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.