The AlwaysOn Availability Groups view allows you to monitor availability groups, availability databases, and availability replicas.
If you have configured the AlwaysOn Availability Groups feature on your SQL 2012 Server, SQL Diagnostic Manager automatically recognizes the availability databases and starts to monitor them. |
AlwaysOn Availability Groups are part of an integrated solution, introduced in SQL Server 2012 with the goal of achieving the highest level of data availability and disaster recovery for organizations. Availability Groups grant DBAs the ability to automatically or manually failover a group of databases as a single unit with support for up to four secondary replicas. For additional information on availability groups, see the Microsoft document, .
To open the AlwaysOn Availability Groups view click the appropriate monitored SQL Server instance, select Databases, and click Availability Group.
In this view, you can see the health of all your availability groups, availability databases and monitored availability replicas.The database table provides the following information for each availability group (as seen in the view by default):
Displays the name of the availability database.
Displays the name of the availability group for which the connected server instance hosts a replica.
Displays the name of the server instance that hosts the availability replica.
Displays the failover mode for which the availability replica is configured. The possible failover modes are automatic or manual.
Describes if data synchronization will use either the synchronous-commit or asynchronous-commit availability mode.
Indicates the current role of the availability replica. Possible values are primary or secondary.
Displays database synchronization state in the availability group. Possible values include: not healthy, partially healthy, and healthy.
Displays the amount of log records from log files in KB that need redoing in the secondary replica to complete synchronization.
Rate in KB per second at which log records are redone in the secondary database to complete synchronization.
Amount of log records in KB needed to ship to the secondary replica to complete synchronization.
Indicates the rate in KB per second at which log records are being sent to the secondary replica to complete synchronization.
The network name of the availability group listener.
The IP address reserved for the availability group listener. If the nodes of your Windows cluster are on different subnets you will need an IP address for each of those subnets.
Indicates whether the secondary database is synchronized with the corresponding primary database. Possible values include: True (the database is marked as synchronized and is ready for a failover) and False (the database is not synchronized and not ready for a failover).
Indicates whether the availability database is currently synchronized with the primary replica. Possible synchronization states are: not synchronizing, synchronizing, synchronized, reverting, and initializing.
Description of the database state of the availability replica. Possible values include: online, restoring, recovering, recovery_pending, suspect, emergency, and offline.
An AlwaysOn availability database is suspended. Possible values are true or false.
Indicates the time when the log-block identifier was received for the last hardened LSN on the secondary replica.
Indicates the current operational state of the secondary replica. Possible state values include: pending failover, pending, online, offline, failed, failed no quorum, and NULL.
Indicates whether a secondary replica is currently connected to the primary replica. Possible values include: connected and disconnected.
Indicates the time in seconds it takes to synchronize between the primary and secondary replicas.
Indicates the time difference in seconds of the last transaction log record in the primary replica and secondary replica. If the primary replica fails, all transaction log records within the time window will be lost.
Indicates the time in seconds it takes to redo the catch-up time. The catch-up time is the time it will take for the secondary replica to catch up with the primary replica.
Additional columns available through the Column Chooser:
Identifier of the database, unique within an instance of SQL Server.
Indicates the rate of the FileStream in KB per second at which transactions are being sent to the secondary replicas.
Unique identifier (GUID) of the availability group.
Number of the last connection error.
Description of the last connection error.
Timestamp of the last connection error.
The TPC port used by the availability group listener.
Identifier of the availability replica within the availability group.
You can hide and unhide additional columns in the Availability Groups table by right clicking on any header in the grid and selecting a column from the Column Chooser dialog. |
The AlwaysOn Availability Groups view includes charts that display the queue size and transfer rates of different availability groups.
Provides users with graphical details about queues in the AlwaysOn Availability Groups feature. This chart is a stacked bar chart for the "Log Send Queue Size" and "Redo Queue Size."
Provides users with graphical details about data transfer rates for redo and logs. This chart is a line chart for the "Log Send Rate" and "Redo Rate."
To view a list of all available alerts, see Metric alerts.
The AlwaysOn Availability Groups view uses a color-based alert system. The following colors are associated with a status and action within SQL Diagnostic Manager:
Color | Alert Status | Action |
---|---|---|
Green | OK | Acceptable threshold where SQL Diagnostic Manager does not generate an alert. |
Blue | Informational | Informational threshold where SQL Diagnostic Manager generates an informational alert. |
Yellow | Warning | Warning threshold where SQL Diagnostic Manager generates a warning alert. |
Red | Critical | Critical threshold where SQL Diagnostic Manager generates a critical alert. |
SQL Diagnostic Manager identifies and resolves SQL Server performance problems before they happen. Learn more > >
|