The following sections describe failure scenarios in a solidDB® HotStandby configuration.
Primary solidDB® server fails
If the primary solidDB® server fails, a high availability manager, like the High Availability Controller (HAC), performs a failover to the secondary solidDB® server as a standard procedure. If the 2-Safe protocol is used, the database and log states are fully preserved. The applications typically perceive a failover time of less than one second.
▪If the IBM InfoSphere CDC replication system is configured so that the data is replicated only from the solidDB® server in the HA setup to another server, the IBM InfoSphere CDC instance reconnects automatically to the new primary, and replication continues.
▪If the IBM InfoSphere CDC replication system is configured so that the data is replicated to the solidDB® server in the HA setup from another server, replication on the subscriptions ends. The subscription needs to be restarted with the Management Console or with the IBM InfoSphere CDC command dmstartmirror.
For instructions, see “Starting and ending replication on subscriptions” in the IBM InfoSphere Change Data Capture Management Console, Administration Guide.
During the scenarios above, the IBM InfoSphere CDC instance is considered to be in operation all the time.
Tip: For more information about the HA (HotStandby) functionality and the High-Availability Controller (HAC), see solidDB® High Availability User Guide.
Secondary solidDB® server fails
In the case of secondary front-end failure, no manual intervention is needed.
If the secondary front-end fails, the secondary front-end node is recovered in a normal way that is specific to the installation (for example, automatically rebooted). HAC automatically performs the rest of the recovery. The failure is not visible to applications or to the IBM InfoSphere CDC.