Auto resending after a failover (on the sending side)
If a failover occurs while sending (data transfer), auto resending can be carried out from the switched STANDBY node. If the failover occurs on the sending side, auto resending (on the sending side) is carried out only when the sending is terminated unsuccessfully by the termination synchronization function (in Forced Stop mode).
-
590-000 is the error code of HULFT on the sending side for which the auto resending (on the sending side) is carried out after the failover.
-
To suppress the auto resending after failover (on the sending side), specify the '--noautoretry' parameter when starting the Send daemon. For details on the startup method of the HULFT systems, refer to the following:
HULFT10 for Linux/AIX Operation Manual :
-
Auto resending is not carried out for error code 590-271 of HULFT on the sending side.
HULFT on the sending side is forcibly stopped during the termination processing. The data transfer finished but the sending was not completed.
1) Error Detection
The clustering software detects an error in a cluster (or within the group where a failover occurs).
2) Forced stop of the Send daemon
HULFT on the sending side (ACTIVE node) stops the currently running Send process by using the termination synchronization function (in Forced Stop mode) and then stops the Send daemon.
3) Failover
The processing is taken over by the STANDBY node from the ACTIVE node.
4) Send daemon startup
The Start Synchronization function starts the Send daemon on the node that has taken over the operation.
5) Auto resending after failover (on the sending side)
In order to restart the file transfer processing that was forcibly stopped in 2) , HULFT on the sending side generates a new Send process and connects to HULFT on the receiving side to carry out an auto resending (on the sending side).