In a SQL Server Cluster Test, the Database Cannot Start When a DR Cluster Resource Node Fails and the Other Node Is Normal

13

1.Select a resource in the resource group. Right-click the resource. The Properties dialog box is displayed. Click the Policy tab.
2.Instructions on the configuration of the resource fault response policy are as follows:
Period of restarts (mm:ss)
Duration of a specific period (mm:ss), in which the cluster service counts the number of resource restarts.

Maximum number of restarts in the specific period
Specify the number of resource restarts you want the cluster service to perform in the specific period. If multiple attempts to restart the resource fail in the specified period, the cluster service will perform operations specified by other fields on this tab page.

For example, if you set the maximum number of restarts in the specific period to 3 and the specific period to 15:00, then the cluster service restarts the resource three times in15 minutes. If the resource still fails to run, restart for the fourth time, and the cluster service will perform operations specified by other fields on the tab page.

If restarts fail, switch over all the resources in this node.
If restarts fail after you have tried for specified maximum times, control the response method of the cluster service:
If you want to switch over the cluster service to the other node, select this box.
If you want the cluster to continue to run on this node, delete this box.
If all the restart attempts fail, restart it again after the specific period.
If you want the cluster service to have an extended waiting period after you have tried to restart for specified maximum times, select this box. The extended waiting period is measured by hour and minute. After the waiting period, the cluster service will begin another restart cycle. The situation is the same no matter which node the cluster resides.

3.Configure cluster roles.

Select the resource group where the resource resides. Right-click the resource group property. Click the Failover tab. The default maximum number of failures is n-1, where n is the number of nodes. You can modify this value. It is recommended that you set a smaller value, so that applications or services will not be switched between nodes all the time when multiple nodes fail.

Other related questions:
Two-node cluster hot backup of a WLAN device fails
Two-node cluster hot backup modes include HSB+VRRP and HSB+dual-link. HSB+VRRP hot backup implements traffic switching through VRRP, and HSB+dual-link hot backup implements traffic switching through dual links. - For details on troubleshooting of HSB+VRRP hot backup faults, see: VRRP HSB Fails. - For details on troubleshooting of HSB+dual-link hot backup faults, see: HSB Between Two Links Fails.

Maximum number of nodes supported by a FusionInsight cluster
According to the specifications of FusionInsight HD, a cluster can contain a maximum of 5000 nodes. 512 nodes are configured by default. If you need a larger cluster, contact Huawei technical support engineers to obtain professional solutions.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top