No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OceanStor BCManager 6.5.0 eReplication User Guide 02

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
What Can I Do If I Cannot Restart Databases When Only One Cluster Resource Node at the DR Center Fails During a SQL Server Cluster Test

What Can I Do If I Cannot Restart Databases When Only One Cluster Resource Node at the DR Center Fails During a SQL Server Cluster Test

Symptom

If a cluster resource node at the DR center fails during a SQL Server cluster test, databases cannot be restarted.

Possible Causes

When a resource failure on the active node occurs, a local fault recovery is initiated first based on the resources' fault response policy, and then the switchover of resource groups. The fault response policy can be configured based on site requirements.

Procedure

  1. Select a resource from the resource group. Right-click and choose Properties. From the dialog box that is displayed, select Policy.
  2. Configuring a Resource Sharing Control Policy as described in the following table:
    • Restart time period (mm:ss)

      specifies a period (in minute and second) during which the cluster service counts the resource restart times.

    • Maximum number of restart trails in a specified time period

      specifies the restart trials that the cluster service can perform in a specified time period. If this number is exceeded and the resource still cannot be restarted, perform operations specified by other fields on this tab.

      For example, if the maximum number of restart trials in a specified time period is set to 3 trials in 15 minutes, the cluster service is allowed to restart the resource for three times in 15 minutes. If the service cannot be restarted, the cluster service will try operations specified in other fields on this tab.

    • If the restart fails, fault recovery will be performed on all resources of the role.
      When the maximum number of restart trials reaches and the restart fails, the control cluster service will respond in the following ways:
      • Select this if you want to switch the cluster role to another node.
      • Deselect this if you want to keep the cluster role running on this node.
    • If all methods for restart fail, try to restart the resources after the specified period passes.

      Select this if you want to prolong the waiting period after the cluster service fails to restart the resources at the maximum number of trials. The prolong period is measured in hour and minute. After the prolonged period passes, the cluster service can start another round of restart trials. This setting works for all nodes that own cluster roles.

  3. Configure cluster roles.

    Select and right-click the resource group that owns the resource. Select Properties from the shortcut menu to go to Failover. The default maximum number of fault occurrences is n-1, where n is the node quantity. This value is configurable. You are advised to use a comparatively small value. This can avoid indefinitely moving of application programs and services among nodes when multiple nodes are faulty.

Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 10665

Downloads: 55

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next