Skip to content

Commit a264a38

Browse files
committed
Stage - manage AG and PITR in Arc
1 parent ba99eb1 commit a264a38

8 files changed

Lines changed: 224 additions & 60 deletions

File tree

docs/database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,8 @@ This article introduces the [!INCLUDE [ssHADR](../../../includes/sshadr-md.md)]
2424

2525
The [!INCLUDE [ssHADR](../../../includes/sshadr-md.md)] feature is a high-availability and disaster-recovery solution that provides an enterprise-level alternative to database mirroring. Introduced in [!INCLUDE [ssSQL11](../../../includes/sssql11-md.md)], [!INCLUDE [ssHADR](../../../includes/sshadr-md.md)] maximizes the availability of a set of user databases for an enterprise. An *availability group* supports a failover environment for a discrete set of user databases, known as *availability databases*, that fail over together. An availability group supports a set of read-write primary databases and one to eight sets of corresponding secondary databases. Optionally, secondary databases can be made available for read-only access and/or some backup operations.
2626

27+
With [Azure Arc-enabled SQL Server](../../../sql-server/azure-arc/overview.md), you can [view availability groups](../../../sql-server/azure-arc/manage-availability-group.md) in Azure portal.
28+
2729
## Overview
2830

2931
An *availability group* supports a replicated environment for a discrete set of user databases, known as *availability databases*. You can create an availability group for high availability (HA) or for read-scale. An HA availability group is a group of databases that fail over together. A read-scale availability group is a group of databases that are copied to other instances of SQL Server for read-only workload. An availability group supports one set of primary databases and one to eight sets of corresponding secondary databases. Secondary databases aren't* backups. Continue to back up your databases and their transaction logs on a regular basis.

docs/sql-server/azure-arc/includes/features-edition.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,8 @@ The following table identifies features available by SQL Server edition:
1616
| [Microsoft Entra ID authentication](../../../relational-databases/security/authentication-access/azure-ad-authentication-sql-server-overview.md) | Yes | Yes | Yes | Yes | Yes | Yes |
1717
| [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-sql-usage) | Yes | Yes | Yes | Yes <sup>1</sup>| Yes | Yes |
1818
| [Microsoft Purview: Govern using DevOps and data owner policies](/azure/purview/tutorial-register-scan-on-premises-sql-server) | Yes | Yes | Yes | Yes | Yes | Yes |
19-
| [Automated backups](../point-in-time-restore.md) | Yes | Yes | Yes | Yes | Yes | Yes |
19+
| [Point in time restore (preview)](../point-in-time-restore.md) | Yes | Yes | Yes | Yes | Yes | Yes |
2020
| [Automated patching](../patch.md) | Yes | Yes | Yes | Yes | Yes | Yes |
2121
| [Failover cluster instances (preview)](../support-for-fci.md)| Yes | Yes | Not applicable | Not applicable | Yes | Not applicable |
22-
22+
| [Always On availability groups (preview)](../manage-availability-group.md)| Yes | Yes | Not applicable | Not applicable | Yes | Not applicable |
2323
<sup>1</sup> [Express LocalDB isn't supported.](/azure/purview/register-scan-on-premises-sql-server#supported-capabilities)

docs/sql-server/azure-arc/includes/features-operating-system.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,9 +18,10 @@ The following table identifies features available by operating system:
1818
| [Microsoft Entra ID authentication](../../../relational-databases/security/authentication-access/azure-ad-authentication-sql-server-overview.md) <sup>1</sup> | Yes | Yes |
1919
| [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-sql-usage) | Yes | No |
2020
| [Microsoft Purview](/azure/purview/tutorial-register-scan-on-premises-sql-server) | Yes | Yes |
21-
| [Automated backups](../point-in-time-restore.md) | Yes | No |
21+
| [Point in time restore (preview)](../point-in-time-restore.md) | Yes | No |
2222
| [Automated patching](../patch.md) | Yes | No |
2323
| [SQL Server 2012 extended security updates](../../end-of-support/sql-server-extended-security-updates.md) | Yes | Not applicable |
2424
| [Failover cluster instances (preview)](../support-for-fci.md) | Yes | Not applicable |
25+
| [Always On availability groups (preview)](../manage-availability-group.md) | Yes | Not applicable |
2526

2627
<sup>1</sup> [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)] only.

docs/sql-server/azure-arc/includes/features-version.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@ The following table identifies features available by SQL Server version:
1717
| [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-sql-usage) | Yes | Yes | Yes | Yes | Yes | Yes |
1818
| [Microsoft Purview: DevOps policies](/azure/purview/how-to-policies-devops-authoring-generic) | No | No | No | No | No | Yes |
1919
| [Microsoft Purview: data owner policies (preview)](/azure/purview/how-to-policies-data-owner-authoring-generic) | No | No | No | No | No | Yes |
20-
| [Automated backups](../point-in-time-restore.md) | Yes | Yes | Yes | Yes | Yes | Yes |
20+
| [Point in time restore (preview)](../point-in-time-restore.md) | Yes | Yes | Yes | Yes | Yes | Yes |
2121
| [Automated patching](../patch.md) | No | Yes | Yes | Yes | Yes | Yes |
2222
| [Failover cluster instances (preview)](../support-for-fci.md)| Yes | Yes | Yes | Yes | Yes | Yes |
23+
| [Always On availability groups (preview)](../manage-availability-group.md) | Yes | Yes | Yes | Yes | Yes | Yes |

docs/sql-server/azure-arc/includes/license-types.md

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.topic: include
77

88
The following table identifies features enabled depending on license type:
99

10-
|Feature |License only <sup>*</sup> |License with Software Assurance<br/>or SQL subscription |Pay-as-you-go |
10+
|Feature |License only <sup>1</sup> |License with Software Assurance<br/>or SQL subscription |Pay-as-you-go |
1111
|---------|---------|---------|---------|
1212
|[Connect to Azure](../connect.md) |Yes |Yes |Yes |
1313
|[SQL Server inventory](../overview.md#manage-your-sql-servers-at-scale-from-a-single-point-of-control)|Yes |Yes |Yes |
@@ -16,8 +16,9 @@ The following table identifies features enabled depending on license type:
1616
|[Microsoft Entra ID authentication](../../../relational-databases/security/authentication-access/azure-ad-authentication-sql-server-overview.md) |Yes |Yes |Yes |
1717
|[Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-sql-usage)|Yes |Yes |Yes |
1818
|[Govern through Microsoft Purview](/azure/purview/tutorial-register-scan-on-premises-sql-server)|Yes |Yes |Yes |
19-
|[Automated backups](../point-in-time-restore.md)|No |Yes |Yes |
19+
|[Point in time restore (preview)](../point-in-time-restore.md)|No |Yes |Yes |
2020
|[Automated patching](../patch.md)|No |Yes |Yes |
2121
|[Failover cluster instances (preview)](../support-for-fci.md) |Yes | Yes | Yes|
22+
| [Always On availability groups (preview)](../manage-availability-group.md) |Yes | Yes | Yes|
2223

23-
<sup>*</sup>License only includes SQL Server instances that are Developer, Express, Web, or Evaluation Edition and instances using a Server/CAL license.
24+
<sup>1</sup>License only includes SQL Server instances that are Developer, Express, Web, or Evaluation Edition and instances using a Server/CAL license.
Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
---
2+
title: Always On availability groups inventory and status
3+
description: Describes how to view Always On availability groups and their status in Azure portal
4+
author: dnethi
5+
ms.author: dinethi
6+
ms.reviewer: mikeray, randolphwest
7+
ms.date: 10/20/2023
8+
ms.topic: conceptual
9+
---
10+
11+
# Always On availability groups inventory and status
12+
13+
An Always On availability group is an enterprise level high availability and disaster recovery solution for SQL Server. This article describes how to view a list of availability groups and their real time health status for a given Azure Arc-enabled SQL Server, in Azure portal.
14+
15+
## View list of availability groups and Status
16+
17+
Follow the steps to view the availability groups that are configured for the Azure Arc-enabled SQL Server:
18+
19+
1. Browse to the overview page of the Arc-enabled SQL Server in your Azure portal
20+
1. Select **Availability Groups**
21+
22+
Azure portal will display the availability groups configured for the SQL Server instance on the right
23+
24+
1. Select the availability group that you want to review
25+
26+
Azure portal displays the health and status of the availability group similar to the availability group dashboard shown in SQL Server Management Studio, is displayed. This includes:
27+
28+
- The current primary replica
29+
- Availability group state
30+
- Availability group replicas
31+
- Failover mode
32+
- Synchronization state
33+
34+
When the availability group (AG) dashboard loads, fetching the dashboard details is done via a roundtrip down to the Azure Arc-enabled SQL Server instance. The Arc SQL extension agent connects to the SQL Server, queries the AG related DMV (Dynamic Management Views) metadata, and sends the information back to the Azure portal where it is displayed.
35+
36+
## Failover
37+
38+
Always On availability groups support different failover modes depending on the data synchronization mode.
39+
40+
- Synchronous-commit mode supports two forms of failover
41+
- Planned manual failover
42+
- Automatic failover
43+
- Asynchronous-commit mode supports forced manual failover (with possible data loss), typically called, forced failover
44+
45+
Azure Arc-Arc enabled SQL Server supports planned manual failover.
46+
47+
Follow the steps below to initiate a planned manual failover:
48+
49+
1. Browse to the overview page of the Arc enabled SQL Server in your Azure portal
50+
1. Select **Availability Groups**
51+
52+
Azure portal will display the availability groups configured for the SQL Server instance on the right
53+
54+
1. Select the availability group that you want to fail over
55+
1. Select **Failover**
56+
57+
This will initiate a planned, manual failover on the AG replica.
58+
59+
### Considerations
60+
61+
- Currently, manual planned failover is the only mode of failover supported
62+
63+
## Related content
64+
65+
- [What is an Always On availability group?](../../database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server.md)
66+
- [View SQL Server databases - Azure Arc](view-databases.md)
67+
- [Recovery Models (SQL Server)](../../relational-databases/backup-restore/recovery-models-sql-server.md)

0 commit comments

Comments
 (0)