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
Copy file name to clipboardExpand all lines: articles/azure-arc/data/managed-instance-disaster-recovery.md
+1-6Lines changed: 1 addition & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,14 +65,9 @@ The following image shows a properly configured distributed availability group:
65
65
66
66
4. Create the failover group resource on both sites.
67
67
68
-
If the managed instance names are identical between the two sites, you do not need to use the `--shared-name <name of failover group>` parameter.
69
68
70
-
If the managed instance names are different between the two sites, use the `--shared-name <name of failover group>` parameter.
71
-
72
-
The following examples use the `--shared-name <name of failover group>...` to complete the task. The command seeds system databases in the disaster recovery instance, from the primary instance.
73
-
74
69
> [!NOTE]
75
-
> The`shared-name` value should be identical on both sites.
70
+
> Ensure the SQL instances have different names for both primary and secondary sites, and the`shared-name` value should be identical on both sites.
76
71
77
72
```azurecli
78
73
az sql instance-failover-group-arc create --shared-name <name of failover group> --name <name for primary DAG resource> --mi <local SQL managed instance name> --role primary --partner-mi <partner SQL managed instance name> --partner-mirroring-url tcp://<secondary IP> --partner-mirroring-cert-file <secondary.pem> --k8s-namespace <namespace> --use-k8s
0 commit comments