SQL Azure Copy Status Test

Replication provides redundancy and increases data availability. With multiple copies of data on different database servers, replication provides a level of fault tolerance against the loss of a single database server.

Active geo-replication enables you to configure up to four readable secondary databases in the same or different data center locations (regions). Secondary databases are available for querying and for failover if there is a data center outage or the inability to connect to the primary database. The failover must be initiated manually by the application of the user. After failover, the new primary has a different connection end-point. Azure SQL Database auto-failover groups is a SQL Database feature designed to automatically manage geo-replication relationship, connectivity, and failover at scale. With it, the customers gain the ability to automatically recover multiple related databases in the secondary region after catastrophic regional failures or other unplanned events that result in full or partial loss of the SQL Database service's availability in the primary region. Additionally, they can use the readable secondary databases to offload read-only workloads. If you are using active geo-replication and for any reason your primary database fails, or simply needs to be taken offline, you can initiate failover to any of your secondary databases. When failover is activated to one of the secondary databases, all other secondaries are automatically linked to the new primary. If swift failover does not occur, then, there may be a lag in data transfer to the secondary databases. This may lead to the unavailability of data to the secondary databases which would eventually hamper the replication process. Therefore, it is necessary to check whether the geo-replication feature is enabled, and if enabled, it becomes mandatory to check the status of the primary and secondary databases and the status of replication to the secondary databases. The SQL Azure Copy Status test helps administrators in this regard!

This test auto-discovers the database instances on the target Microsoft SQL Azure database server and for each database instance, reports whether/not geo-replication is enabled. If geo-replication is enabled, this test reports whether the database instance is a primary or secondary database and also reports the current status of replication.

Target of the test : A Microsoft SQL Azure database server

Agent deploying the test : An external/remote agent

Outputs of the test : One set of results for every Microsoft SQL Azure database server instance being monitored

Configurable parameters for the test
  1. Test period - How often should the test be executed
  2. Host - The host for which the test is to be configured.
  3. ssl – If the Microsoft SQL server being monitored is an SSL-enabled server, then set the ssl flag to Yes. If not, then set the ssl flag to No.
  4. instance - In this text box, enter the name of a specific Microsoft SQL instance that is to be monitored. The default value of this parameter is “default”. To monitor an Microsoft SQL instance named “CFS”, enter this as the value of the INSTANCE parameter.
  5. USER – Provide the name of a SQL user with the view server state role.
  6. password - The password of the specified user.
  7. confirm password - Confirm the password by retyping it
  8. domain - By default, none is displayed in the DOMAIN text box. If the ‘SQL server and Windows’ authentication has been enabled for the server being monitored, then the DOMAIN can continue to be none. On the other hand, if ‘Windows only’ authentication has been enabled, then, in the DOMAIN text box, specify the Windows domain in which the managed Microsoft SQL server exists. Also, in such a case, the USER name and PASSWORD that you provide should be that of a user authorized to access the monitored SQL server.
  9. isntlmv2 - In some Windows networks, NTLM (NT LAN Manager) may be enabled. NTLM is a suite of Microsoft security protocols that provides authentication, integrity, and confidentiality to users. NTLM version 2 (“NTLMv2”) was concocted to address the security issues present in NTLM. By default, the isntlmv2 flag is set to No, indicating that NTLMv2 is not enabled by default on the target Microsoft SQL host. Set this flag to Yes if NTLMv2 is enabled on the target host.
  10. ISPASSIVE – If the value chosen is yes, then the Microsoft SQL server under consideration is a passive server in a SQL cluster. No alerts will be generated if the server is not running. Measures will be reported as “Not applicable’ by the agent if the server is not up.
  11. REPORTMANAGERTIME – By default, this flag is set to Yes, indicating that, by default, the detailed diagnosis of this test, if enabled, will report the shutdown and reboot times of the device in the manager’s time zone. If this flag is set to No, then the shutdown and reboot times are shown in the time zone of the system where the agent is running(i.e., the system being managed for agent-based monitoring, and the system on which the remote agent is running - for agentless monitoring).
  12. To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability
    • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Is Geo-replication enabled?

Indicates whether/not the geo-replication feature is enabled on this database instance.

 

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
Yes 1
No 0

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not the geo-replication feature is enabled on this database instance. The graph of this measure however, represents the status of a server using the numeric equivalents only.

Is Primary?

Indicates whether/not this database instance is the primary database.

 

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
Yes 1
No 0

Note: By default, this measure reports the Measure Values listed in the table above to indicate whether/not this database instance is the primary database. However, the graph of this measure is represented using its corresponding numeric equivalents only - 0 or 1.

Is Secondary?

Indicates whether/not this database instance is the secondary database.

 

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
Yes 1
No 0

Note:

By default, this measure reports the Measure Values listed in the table above to indicate whether/not this database instance is the secondary database. However, the graph of this measure is represented using its corresponding numeric equivalents only - 0 or 1.

Replication Status

Indicates the current status of replication on this database instance.

 

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
Seeding 1
Catch up 2
Pending 3

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the current status of replication on this database instance. However, the graph of this measure is represented using its corresponding numeric equivalents - 1 to 3.

Replication lagging

Indicates the time duration in seconds, that replication to this database instance lags.

Seconds

A high value for this measure is a cause of concern. If the value of this measure is high, then, it may indicate that the databases are out of sync and data cannot be accessed from the databases when a failover occurs.

Secondary database mode

Indicates the mode of the secondary database.

 

The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure Value Numeric Value
No 0
All 1

Note:

By default, this measure reports the Measure Values listed in the table above to indicate the mode of the secondary database. However, the graph of this measure is represented using its corresponding numeric equivalents only - 0 or 1.