6.1.6 Processing performed when failover occurs on SLM - UR
When failover occurs on SLM - UR, SLM - UR on the active server is terminated and SLM - UR on the standby server is started. Note that the shared disk does not contain any SLM - UR information that is to be inherited to the standby server.
After SLM - UR starts on the standby server, SLM - UR is connected to SLM - Manager. After that, SLM - UR starts its processing according to the business operations underway in SLM - Manager.
The following figure shows the processing that is performed when failover occurs on SLM - UR.
|
![[Figure]](GRAPHICS/F0000158.GIF)
The following subsections explain the failover processing flows depending on the timing of the failover.
- Organization of this subsection
(1) While neither monitoring nor detection of monitored services is being performed
When failover occurs on SLM - UR while neither monitoring nor detection of monitored services is being performed, only connection to SLM - Manager is restored after SLM - UR is started on the standby server. Neither monitoring nor detection processing is started.
(2) While monitored services are being monitored
When failover occurs on SLM - UR while monitored services are being monitored, monitoring is restarted after SLM - UR has started on the standby server.
The following figure shows the processing flow when failover occurs on SLM - UR while monitored services are being monitored.
|
![[Figure]](GRAPHICS/F0000114.GIF)
The following explains the processing flow shown in the figure, where the numbers correspond to the numbers in the figure:
The cluster software (active server) starts SLM - UR (active server). The cluster software (active server) also starts periodic monitoring of server status.
Upon receiving a notification that SLM - Manager has started monitoring the monitored services, SLM - UR (active server) starts monitoring and sends performance information.
Because a failure has occurred on SLM - UR (active server), the Windows services stop.
All Windows services for SLM - UR that have been registered into SLM - UR (active server) are stopped by the cluster software (active server) after which failover processing starts.
The cluster software (standby server) starts SLM - UR (standby server). The cluster software (standby server) also starts periodic monitoring of server status.
A notification of the start event is sent from the started SLM - UR (standby server) to SLM - Manager and transmission of performance information is restarted.
(3) While detection of monitored services is being performed
When failover occurs on SLM - UR while detection of monitored services is being performed, the SLM - Manager status changes from Detecting to Stopped. Once SLM - UR has started on the standby server, its connection to SLM - Manager is restored.
The following figure shows the processing flow when failover occurs on SLM - UR while monitored services are being detected.
|
![[Figure]](GRAPHICS/F0000076.GIF)
The following explains the processing flow shown in the figure, where the numbers correspond to the numbers in the figure:
The cluster software (active server) starts SLM - UR (active server). The cluster software (active server) also starts periodic monitoring of server status.
Upon receiving a notification that SLM - Manager has started detecting monitored services, SLM - UR (active server) starts detection processing.
Because a failure has occurred on SLM - UR (active server), the Windows services stop.
All Windows services for SLM - UR that have been registered into SLM - UR (active server) are stopped by the cluster software (active server), after which failover processing starts.
The cluster software (standby server) starts SLM - UR (standby server). The cluster software (standby server) also starts periodic monitoring of server status.
A notification indicating that SLM - UR (standby server) has started is sent to SLM - Manager and connection is restored.