NOTE: The time needed to complete a database restoration will vary depending on the size of the database.
The Recent 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.
Once the action is successfully completed, the DB instance where we have executed the script should stop performing the periodic backups (in case of a "freeze"), or resume performing backups (in case of an "unfreeze").
An easy way to confirm that the action took effect is to browse the snapshots (Clouds -> AWS -> EBS Snapshots), and check that the time of the most recent completed snapshot is the same (if you "froze" backups) or that backup snapshots have resumed (if you have "unfrozen" them).
For example, if DB_EBS_PREFIX = mydb
For slave instances, the snapshots have names like 'mydb-slave-YYYYMMDDHHMM.'
For master instances, the snapshots have names like 'mydb-master-YYYYMMDDHHMM.'
NOTE: Slave and master DB backups are performed as defined by the input variables, DB_BACKUP_MASTER_FREQ and DB_BACKUP_SLAVE_FREQ. So you may have to wait an appropriate amount of time in order to confirm that backups have been successfully frozen or unfrozen.
© 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.