NetBackup services may start on the same active node after resource failure in a Solaris cluster setup
In the case of a NetBackup clustered master server in a Solaris cluster setup, NetBackup services may restart on the same active cluster node after failure instead of failing over to another node. The cluster log contains the following log message:
SC[,VRTS.scnb,scnb-harg,scnb-hars,gethostnames]: [ID 758691 daemon.warning] Current setting of Retry_interval= 300, might prevent failover on repeated probe failures. It is recommended that Retry_interval be greater than or equal to [(Thorough_probe_interval + Probe_timeout) * 2 * Retry_count]. Current values are (Thorough_probe_interval = 60,Retry_count = 2,Probe_timeout = 30).
To resolve the issue, perform the following steps:
- Set the Retry_interval option for resource scnb_hars to more than 360 using the following command:
#/usr/cluster/bin/clrs set -y Retry_interval=400 scnb-hars
- Verify the updated value of the Retry_interval option using the following command:
# /usr/cluster/bin/clrs show -y Retry_interval scnb-hars