How to Recover After a Takeover

Language:

Note - You can also accomplish Step 5 and Step 6 by using the Oracle Solaris Cluster Manager GUI. Click Partnerships, click the partnership name, and highlight the protection group name. Click Update Protection Group and when the update is completed click Start Protection Group. For more information about Oracle Solaris Cluster Manager, see Chapter 13, Using the Oracle Solaris Cluster GUI, in Oracle Solaris Cluster System Administration Guide .

Allow the MySQL slave threads to be started if the database resource performs a restart or similar action.
Remove the skip-slave-start keyword from the appropriate my.cnf file.
Log in to MySQL as the root role, then start the slave.
```
mysql> start slave;
```
Verify that the slave is running, and wait until it is synchronized with the master.
```
mysql> show slave status\G
```
If the slave status shows that at least one slave thread is not running, fix the root cause, and retry the operation. As a last resort, you could take a backup from the current master and perform a fresh slave setup.

Connect to a node of the old primary cluster and update the protection group to change the role from a deactivated primary cluster to a secondary cluster.
Log in to a cluster node.
You must be assigned the Geo Management RBAC rights profile to complete this procedure. For more information, see Securing Geographic Edition Software in Oracle Solaris Cluster Geographic Edition Installation and Configuration Guide .

Start the protection group locally.
```
# geopg start -scope local protection-group
```
For more information, see Resynchronizing a Protection Group in Oracle Solaris Cluster Geographic Edition System Administration Guide and Activating and Deactivating a Protection Group in Oracle Solaris Cluster Geographic Edition System Administration Guide .