Foglight for SQL Server (Cartridge) 7.3.0


	NOTE: Always on cannot function at the same time with Mirroring operation: enabling Mirroring requires disabling Always on and conversely. Therefore, if the monitored instance contains databases that support Always On but have Mirroring enabled, the Always On panel displays the note This instance has no database configured for Always On.

The Always On panel includes the following sections:

•

OS Cluster information — see OS Cluster Information .

•

High Availability groups table — displays all High Availability groups that are configured on the instance. For details, see High Availability groups table .

•

Availability group map — displays the dependency (primary/secondary relations) between the databases in the groups selected in the High Availability groups table, or between all groups in the table. For details, see Availability group map .

OS Cluster Information

The OS cluster information section displays the following details:

•

OS Cluster Name — the name of the OS cluster hosting the SQL Server instances that are enabled for AlwaysOn Availability Groups.

•

Quorum Type — the type of quorum used by the selected OS cluster; can have one of the following values:

•

0 — Node Majority.

The cluster is defined as healthy only if indicated so by more than 50% of the voting nodes in the cluster. For example, on a nine node cluster this quorum configuration can sustain up to four node failures.

•

1 — Node and Disk Majority.

•

2 — Node and File Share Majority.

•

3 — No Majority: Disk Only.

A shared disk cluster resource is designated as a witness, and connectivity by any node to that shared disk is counted as an affirmative vote.

•

Quorum State — the state of the quorum used by the selected OS cluster; can have one of the following values:

•

0 — Unknown quorum state

•

1 — Normal quorum

•

2 — Forced quorum

High Availability groups table

The High Availability group table displays information about the availability and health of all availability groups configured in the instance and the databases they serve.

IMPORTANT: It is possible that one or more the availability replicas that take part in a group are not currently monitored. In such a case an indication appears near the replica in the availability group map. Click this indication to launch the instance monitoring wizard. For details, see Availability group map .

The High Availability group table includes the following columns:

•

HA Group Status — displays an icon that indicates the worst severity reported within the group from the group alarms.

•

Group Name — displays the High Availability group name.

•

Role — the current state of the database that runs on the selected instance and belongs to the selected group; either Secondary or Primary. When there is no value for Secondary/Primary, this column should indicate the status Off line.

•

Alarms — displays alarms related to the health of the availability group or its associated databases.

•

Max Estimated Recovery Time — displays the maximum value of the estimated recovery time parameter within all databases that belong to the selected group. If all databases are fully synchronized, this column displays a zero value.

•

Max Estimated Data Loss — displays the maximum value of the estimated data loss parameter within all databases that belong to the selected group. If all databases are fully synchronized, this column displays a zero value.

•

Explore — contains a shortcut icon which, when clicked, displays the Availability Group details pop-up.

Figure 26. Availability Group details pop-up.

This pop-up contains the Group Info, Availability Replica, and Databases tabs.

The Group Info tab includes the following fields:

•

Primary replica — the primary replica’s name.

•

Primary recovery health — indicates the primary replica’s recovery health, with the following possible values: In progress, Online or Null.

•

Synchronization health — summarizes the synchronization status of all replicas in the availability group:

•

Healthy — if all replicas are fully synchronized.

•

Partially healthy — if only some of the replicas are fully synchronized.

•

Not healthy — if no replica is fully synchronized.

•

Automated backup preference — indicates whether backups should run on the primary replica. The possible values are:

•

0 - Primary — backups should always be carried out on the primary replica.

•

1 - Secondary_only — performing backups on a secondary replica is preferable.

•

2 - Secondary — performing backups on a secondary replica preferable, but performing backups on the primary replica is acceptable if no secondary replica is available for backup operations. This is the default behavior.

•

3 - None — no preference about whether backups are performed on the primary replica or on a secondary replica.

The Availability Replica tab lists all replicas associated with the group. This tab includes the following fields:

•

Server Name — the name of the server.

•

Join State — can have the following values:

•

Not joined

•

Joined standalone — joined as a standalone instance

•

Joined Failover — joined as failover cluster instance

•

Role — either Primary or Secondary.

•

Operational State — indicates whether the replica is online, offline or in a pending stage. The possible values are as follows:

•

•

•

•

•

•

Null — replica is not local

•

Connected State — indicates whether a secondary replica is currently connected to the primary replica. Possible values are either Connected or Disconnected.

•

Recovery Health — indicates whether all databases joined to the availability group on the availability replica, are online, or are being recovered after a failover. Possible values are:

•

Online

•

In progress — recovering from a failover

•

Synchronization Health — summarizes the synchronization status of all replicas in the availability group:

•

Healthy — if all replicas are fully synchronized.

•

Partially healthy — if only some of the replicas are fully synchronized.

•

Not healthy — if no replica is fully synchronized.

•

Secondary Role Allow Connections — indicates whether an availability replica that is performing the secondary role (that is, a secondary replica) can accept connections from clients:

•

No — no connections are allowed to the databases in the secondary replica, and the databases are not available for read access. This is the default setting.

•

Read only — read-only connections have exclusive access to the databases in the secondary replica. All databases in the replica are available for read access.

•

All — all connections are allowed to the databases in the secondary replica for read-only access.

•

Availability Mode — can have either of the following values:

•

Asynchronous commit — the primary replica can commit transactions without waiting for the secondary to write the log to disk.

•

Synchronous commit — the primary replica waits to commit a given transaction until the secondary replica has written the transaction to disk.

•

Failover Mode — either Manual or Automatic.

The Databases tab displays all databases associated with the group. This tab includes the following fields:

•

Replica Server Name — the name of the server.

•

Database Name — the name of the database.

•

Database State — indicates whether the database is online, offline or in a pending stage. The possible values are as follows:

•

•

•

•

•

•

•

•

Synchronization State — indicates the data movement state, and can have one of the following values:

•

Not Synchronizing

•

Synchronizing

•

Synchronized

•

Reverting pages from undo log

•

Initializing Undo log

•

Synchronization Health — summarizes the synchronization status of all replicas in the availability group:

•

Healthy — if all replicas are fully synchronized.

•

Partially healthy — if only some of the replicas are fully synchronized.

•

Not healthy — if no replica is fully synchronized.

•

Estimated Recovery Time (sec) — the estimated time that the secondary replica will require in order to catch up with the primary replica.

•

Estimated Data Loss (sec) — the time difference of the last transaction log record between the primary and secondary replicas. Failure of the primary replica will result in the loss of all transaction log records within the time window.

•

Is Failover Ready — indicates whether the secondary database is synchronized in the cluster with the corresponding primary database. Possible values are Yes or No.

Availability group map

The Always On configuration supports one primary replica and up to four secondary replicas for each availability group. The Availability Group Map section allows viewing the dependencies between the various replicas that form the availability group selected in the table. In addition to indicating the name of the OS cluster where the availability replicas reside, the map displays the connections between the primary replica and the secondary replicas, showing on the left the replica that resides on the currently monitored instance.


	IMPORTANT: On each replica there is an indication of the highest severity level encountered on the replica. A replica that is not currently monitored is indicated by the icon. Click this icon to launch the wizard used for configuring an instance for monitoring.