Overview

This page displays basic information regarding the high-available cluster and member servers. In addition, this page provides tools to create, remove, or perform maintenance on high-availability clusters and member servers.

High Availability Cluster Status

This field displays the overall status of your high-availability cluster, alerting you to any errors. The following is a table of possible conditions displayed in this field:

Status Description
Standalone The servers are not combined into a high-availability cluster.
Healthy The overall condition of your high-availability cluster is good. Data replication from the active server to the passive server is functioning normally.
Preparing The servers have been successfully combined into a high-availability cluster, but initial data replication has not yet finished. Switchover cannot be performed at this time. For more details, please refer to Switchover.
Loading The system is loading the cluster status. Switchover cannot be performed until the status loading finished.
Warning The status of HA cluster is abnormal, but the services are still functioning.
Danger Both the active and passive servers are malfunctioning. The high-availability cluster is unable to function normally. Please check the status of all storage spaces (e.g. RAID Groups, Disk Groups, volumes, and iSCSI LUNs).

Warning Messages

The following table displays warnings messages that might appear when an error occurs on the system. When more than one warning message appears, you can navigate between them with the forward/backward buttons.

Warning/Error Description
Monitored service error An error occurred on one or more monitored services.
Storage space degraded A storage space (e.g. RAID Group, Disk Group, volume, and iSCSI LUN) on the active or passive server is degraded. Please check the Storage Status page.
Storage space crashed A storage space (e.g. RAID Group, Disk Group, volume, and iSCSI LUN) on the active or passive server is crashed. Please check the Storage Status page.
Failed to detect passive server This error might occur because the passive server is offline or the active and passive servers cannot connect via the Heartbeat connection. In this case, switchover will be unavailable.
Data cannot be replicated to passive server This error might occur due to storage volume or disk failure. In this case, switchover will be unavailable. Please check the Storage Status page.
Passive server is not selected If the passive server is unbound from the high-availability cluster, this status will be displayed. In this case, switchover will be unavailable. If you wish to rebind the passive server, click the Maintain drop-down menu and click Bind. When you rebind the passive server, a full data replication will be required.

High Availability Cluster Information

This field is located below the high-availability cluster status and displays basic information regarding the cluster. If a high-availability cluster does not exist, this field will only provide an explanation of the function of high-availability clusters.

This field includes the following information:

High Availability Cluster Operation Buttons

The following two buttons are located beneath the high-availability cluster information:

Note: Once a high-availability cluster is removed, data replication will be required when you wish to create a new one.

Server and Data Replication Status

This section contains images that indicate the status of the active and passive servers, as well as the flow of data replication between the servers.

The image of data replication indicates the following possible conditions:

Server Information

This section is located beneath the server images. Information regarding the active and passive servers is displayed in this section. If no passive server has been selected, this section will read N/A.

Maintain Buttons

The Maintain drop-down menu is located beneath the server information section. This drop-down menu contains options for conducting maintenance on the passive server. When no high-availability cluster exists, this menu will be grayed out.

Note: Shutting down or unbinding the passive server will cause the high-availability cluster to be without a passive server and unable to switchover from the active server to the passive server.