Before testing a failover
Before testing a failover, terminate the following process by sending the signal "SIGTERM" to the process:
Jobscheduler: tskwnsrv
A failover does not take place if the daemon has been stopped using the poperationmgr command.
This is because the daemons (Jobscheduler, Job Execution Control) to be registered in the cluster are excluded from the targets for automatic startup/stop using the soperationmgr/poperationmgr command when creating a cluster system.
Triggering a failover
There are many types of events that can trigger a failover. However, do not forcefully unmount the shared disk to start a failover.
Systemwalker Operation Manager references shared disk information in the process of stopping the Jobscheduler daemon. Therefore, after the shared disk is forcefully unmounted, the process of stopping the Jobscheduler daemon cannot be performed correctly. (The failover is completed.)
If a failover occurs because the shared disk is unmounted, send the SIGTERM signal to the tskwnsrv process on the node from which the shared disk has been unmounted.
Note that the SIGKILL signal should not be sent.
