Merge pull request #189753 from MicrosoftDocs/release-arc-data

Publish Arc-enabled data services February, 2022 release

Author: PRMerger18

articles/azure-arc/data/managed-instance-high-availability.md

@@ -72,7 +72,7 @@ After all containers within the pod have recovered, you can connect to the manag
 
 ## High availability in Business Critical service tier
 
-In the Business Critical service tier, in addition to what is natively provided by Kubernetes orchestration, there is a new technology called Contained availability group that provides higher levels of availability. Azure Arc-enabled SQL managed instance deployed with `Business Critical` service tier can be deployed with either 2 or 3 replicas. These replicas are always kept in sync with each other. Contained availability group is built on SQL Server Always On availability groups. With contained availability groups, any pod crashes or node failures are transparent to the application as there is at least one other pod that has the SQL managed instance that has all the data from the primary and ready to take on connections.  
+In the Business Critical service tier, in addition to what is natively provided by Kubernetes orchestration, Azure SQL Managed Instance for Azure Arc provides a contained availability group. The contained availability group is built on SQL Server Always On technology. It provides higher levels of availability. Azure Arc-enabled SQL managed instance deployed with *Business Critical* service tier can be deployed with either 2 or 3 replicas. These replicas are always kept in sync with each other. With contained availability groups, any pod crashes or node failures are transparent to the application as there is at least one other pod that has the instance that has all the data from the primary and is ready to take on connections.  
 
 ## Contained availability groups
 
@@ -241,11 +241,14 @@ Additional steps are required to restore a database into an availability group.
 
 1. Expose the primary instance external endpoint by creating a new Kubernetes service.
 
-    Determine the pod that hosts the primary replica by connecting to the managed instance and run:
+    Determine the pod that hosts the primary replica. Connect to the managed instance and run:
 
     ```sql
     SELECT @@SERVERNAME
     ```
+
+    The query returns the pod that hosts the primary replica.
+
     Create the Kubernetes service to the primary instance by running the command below if your Kubernetes cluster uses nodePort services. Replace `podName` with the name of the server returned at previous step, `serviceName` with the preferred name for the Kubernetes service created.
 
     ```console
@@ -269,6 +272,7 @@ Additional steps are required to restore a database into an availability group.
     ```console
     kubectl get services -n <namespaceName>
     ```
+
 2. Restore the database to the primary instance endpoint.
 
     Add the database backup file into the primary instance container.
@@ -326,7 +330,7 @@ Additional steps are required to restore a database into an availability group.
     ```
 
 > [!IMPORTANT]
-> As a best practice, you should cleanup by deleting the Kubernetes service created above by running this command:
+> As a best practice, you should delete the Kubernetes service created above by running this command:
 >
 >```console
 >kubectl delete svc sql2-0-p -n arc

articles/azure-arc/data/release-notes.md

@@ -7,7 +7,7 @@ ms.reviewer: mikeray
 services: azure-arc
 ms.service: azure-arc
 ms.subservice: azure-arc-data
-ms.date: 01/27/2022
+ms.date: 02/25/2022
 ms.topic: conceptual
 ms.custom: references_regions, devx-track-azurecli
 # Customer intent: As a data professional, I want to understand why my solutions would benefit from running with Azure Arc-enabled data services so that I can leverage the capability of the feature.
@@ -17,10 +17,47 @@ ms.custom: references_regions, devx-track-azurecli
 
 This article highlights capabilities, features, and enhancements recently released or improved for Azure Arc-enabled data services.
 
+## February 2022
+
+This release is published February 25, 2022.
+
+### Image tag
+
+`v1.4.0_2022-02-25`
+
+For complete release version information, see [Version log](version-log.md).
+
+### SQL Managed Instance
+
+- Support for readable secondary replicas:
+    - To set readable secondary replicas use `--readable-secondaries` when you create or update an Arc-enabled SQL Managed Instance deployment. 
+    - Set `--readable secondaries` to any value between 0 and the number of replicas minus 1.
+    - `--readable-secondaries` only applies to Business Critical tier. 
+- Automatic backups are taken on the primary instance in a Business Critical service tier when there are multiple replicas. When a failover happens, backups move to the new primary. 
+- RWX capable storage class is required for backups, for both General Purpose and Business Critical service tiers.
+- Billing support when using multiple read replicas.
+
+For additional information about service tiers, see [High Availability with Azure Arc-enabled SQL Managed Instance (preview)](managed-instance-high-availability.md).
+
+### User experience improvements
+
+The following improvements are available in [Azure Data Studio](/sql/azure-data-studio/download-azure-data-studio).
+
+- Azure Arc and Azure CLI extensions now generally available. 
+- Changed edit commands for SQL Managed Instance for Azure Arc dashboard to use `update`, reflecting Azure CLI changes. This works in indirect or direct mode. 
+- Data controller deployment wizard step for connectivity mode is now earlier in the process.
+- Removed an extra backups field in SQL MI deployment wizard.
+
 ## January 2022
 
 This release is published January 27, 2022.
 
+### Image tag
+
+`v1.3.0_2022-01-27`
+
+For complete release version information, see [Version log](version-log.md).
+
 ### Data controller
 
 - Initiate an upgrade of the data controller from the portal in the direct connected mode

articles/azure-arc/data/version-log.md

@@ -7,7 +7,7 @@ ms.reviewer: mikeray
 services: azure-arc
 ms.service: azure-arc
 ms.subservice: azure-arc-data
-ms.date: 12/16/2021
+ms.date: 02/25/2022
 ms.topic: conceptual
 # Customer intent: As a data professional, I want to understand what versions of components align with specific releases.
 ---
@@ -16,6 +16,17 @@ ms.topic: conceptual
 
 This article identifies the component versions with each release of Azure Arc-enabled data services.
 
+### February 25, 2022
+
+|Component  |Value  |
+|--------------------------------------------------------|---------|
+|Container images tag |`v1.4.0_2022-02-25`
+|CRD names and versions	|`datacontrollers.arcdata.microsoft.com`: v1beta1, v1, v2, v3</br>`exporttasks.tasks.arcdata.microsoft.com`: v1beta1, v1, v2</br>`kafkas.arcdata.microsoft.com`: v1beta1</br>`monitors.arcdata.microsoft.com`: v1beta1, v1, v2</br>`sqlmanagedinstances.sql.arcdata.microsoft.com`: v1beta1, v1, v2, v3, v4</br>`postgresqls.arcdata.microsoft.com`: v1beta1, v1beta2</br>`sqlmanagedinstancerestoretasks.tasks.sql.arcdata.microsoft.com`: v1beta1, v1</br>`dags.sql.arcdata.microsoft.com`: v1beta1, v2beta2</br>`activedirectoryconnectors.arcdata.microsoft.com`: v1beta1|
+|ARM API version|2021-11-01|
+|`arcdata` Azure CLI extension version|	1.2.1|
+|Arc enabled Kubernetes helm chart extension version|1.1.18791000|
+|Arc Data extension for Azure Data Studio|1.0|
+
 ### January 27, 2022
 
 |Component  |Value  |