You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To configure disaster recovery in Azure Arc-enabled SQL Managed Instance, set up failover groups.
17
+
To configure disaster recovery in Azure Arc-enabled SQL Managed Instance, set up Azure failover groups.
18
18
19
19
## Background
20
20
21
-
The distributed availability groups used in Azure Arc-enabled SQL Managed Instance is the same technology that is in SQL Server. Because Azure Arc-enabled SQL Managed Instance runs on Kubernetes, there's no Windows failover cluster involved. For more information, see [Distributed availability groups](/sql/database-engine/availability-groups/windows/distributed-availability-groups).
21
+
Azure failover groups uses the same distributed availability groups technology that is in SQL Server. Because Azure Arc-enabled SQL Managed Instance runs on Kubernetes, there's no Windows failover cluster involved. For more information, see [Distributed availability groups](/sql/database-engine/availability-groups/windows/distributed-availability-groups).
22
22
23
23
> [!NOTE]
24
24
> - The Azure Arc-enabled SQL Managed Instance in both geo-primary and geo-secondary sites need to be identical in terms of their compute & capacity, as well as service tiers they are deployed in.
25
25
> - Distributed availability groups can be setup for either General Purpose or Business Critical service tiers.
26
26
27
-
To configure disaster recovery:
27
+
To configure an Azure failover group:
28
28
29
29
1. Create custom resource for distributed availability group at the primary site
30
30
1. Create custom resource for distributed availability group at the secondary site
31
-
1. Copy the mirroring certificates
31
+
1. Copy the binary data from the mirroring certificates
32
32
1. Set up the distributed availability group between the primary and secondary sites
33
33
34
34
The following image shows a properly configured distributed availability group:
0 commit comments