Failback is a manual process that requires careful planning. If you use an RCM and it is down, in order to fail back, you may need to manually restart the RCM, and manually reverse the replication direction of the Replication Server.
Ensure that the primary Adaptive Server is in its normal running state and accepting connections.
If there is a secondary Adaptive Server running, and the direction of the replication has been switched during the failover, restore the replication direction to its original state so that the primary Adaptive Server is properly updated with the latest transactions. See the Replication Server Administration Guide for instructions.
If you are using an RCM, restart it. When the RCM is started using the OpenSwitch RCM_AUTOSTART parameter, you may need to restart the OpenSwitch servers to restart the RCM. See “Configuring an RCM to start automatically from OpenSwitch” for details.
Log in to the mutually-aware OpenSwitch as an administrator, and execute the following commands. Perform this step on only one of the OpenSwitch servers (either the primary or the secondary); the commands are automatically propagated to the other companion OpenSwitch.
rp_stop POOL, secondary_ASE, NULL, 0, 1 rp_server_status primary_ASE, UP rp_switch POOL,secondary_ASE, NULL, primary_ASE, 0, 1 rp_start POOL, secondary_ASE NULL
All future incoming clients are redirected back to the primary Adaptive Server.
