Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into dns-new

Author: greg-lindsay

articles/azure-netapp-files/TOC.yml

@@ -217,8 +217,8 @@
             href: azacsnap-configure-database.md?tabs=oracle
           - name: IBM Db2
             href: azacsnap-configure-database.md?tabs=db2
-          - name: Microsoft SQL Server (PREVIEW)
-            href: azacsnap-preview.md?tabs=mssql#microsoft-sql-server
+          - name: Microsoft SQL Server
+            href: azacsnap-configure-database.md?tabs=mssql
         - name: Configure Storage
           items:
           - name: All storage

articles/azure-netapp-files/azacsnap-cmd-ref-configure.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: Phil-Jensen
 ms.service: azure-netapp-files
 ms.topic: reference
-ms.date: 08/21/2023
+ms.date: 02/01/2025
 ms.author: phjensen
 ---
 
@@ -129,6 +129,14 @@ When you add a Db2 database to the configuration, the following values are requi
 > [!IMPORTANT]
 > Setting `Db2 Server Address` (`serverAddress`) aligns directly with the method that's used to communicate with Db2. Ensure that you set it correctly, as described.
 
+# [Microsoft SQL Server](#tab/mssql)
+
+When adding a Microsoft SQL Server database to the configuration, the following values are required:
+
+- `connectionString` = The Connection String used to connect to the database.  For a typical AzAcSnap installation on to the system running Microsoft SQL Server where the Database Instance is MSSQL2022 the connection string = "Trusted_Connection=True;Persist Security Info=True;Data Source=MSSQL2022;TrustServerCertificate=true".
+- `instanceName` = The database instance name.
+- `metaDataFileLocation` = The location where Microsoft SQL Server will write out the backup meta-data file (for example, "C:\\MSSQL_BKP\\").
+
 ---
 
 # [Azure Large Instances (bare metal)](#tab/azure-large-instance)

articles/azure-netapp-files/azacsnap-configure-database.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: Phil-Jensen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 05/15/2024
+ms.date: 02/01/2025
 ms.author: phjensen
 ---
 
@@ -685,6 +685,29 @@ logout
 Connection to <serverAddress> closed.
 ```
 
+# [Microsoft SQL Server](#tab/mssql)
+
+The snapshot tools issue commands to the Microsoft SQL Server database directly to enable and disable backup mode.  
+
+AzAcSnap connects directly to Microsoft SQL Server using the provided connect-string to issue SQL commands, such as `ALTER SERVER CONFIGURATION SET SUSPEND_FOR_SNAPSHOT_BACKUP = ON` or `ALTER SERVER CONFIGURATION SET SUSPEND_FOR_SNAPSHOT_BACKUP = OFF`.  The connect-string will determine if the installation is on the database server or a centralized "backup" server.  Typical installations of AzAcSnap would be onto the database server to ensure features such as flushing file buffers can  work as expected.  If AzAcSnap has been installed onto the database server, then be sure the user running azacsnap has the required permissions.
+
+##### `azacsnap` user permissions
+
+Refer to [Get started with Azure Application Consistent Snapshot tool](azacsnap-get-started.md)
+The `azacsnap` user should have permissions to put Microsoft SQL Server into backup mode, and have permissions to flush I/O buffers to the volumes configured.
+
+Configure (`.\azacsnap.exe -c configure`) with the correct values for Microsoft SQL Server and test (`.\azacsnap.exe -c test --test mssql`) azacsnap database connectivity.
+Run the `azacsnap` test command
+```shell
+.\azacsnap.exe -c test --test mssql
+```
+
+```output
+BEGIN : Test process started for 'mssql'
+BEGIN : Database tests
+PASSED: Successful connectivity to MSSQL version 16.00.1115
+END   : Test process complete for 'mssql'
+```
 
 ---
 
@@ -761,7 +784,7 @@ global.ini,SYSTEM,,,persistence,basepath_logbackup,/hana/logbackups/H80
 global.ini,SYSTEM,,,persistence,basepath_logvolumes,/hana/log/H80
 ```
 
-### Configure the log backup timeout
+### Configure the log backup time-out
 
 The default setting for SAP HANA to perform a log backup is `900` seconds (15 minutes). We recommend that you reduce this value to `300` seconds (5 minutes). Then it's possible to run regular backups of these files (for example, every 10 minutes). You can take these backups by adding the `log_backup` volumes to the `OTHER` volume section of the
 configuration file.
@@ -770,9 +793,9 @@ configuration file.
 hdbsql -jaxC -n <HANA_ip_address>:30013 -i 00 -u SYSTEM -p <SYSTEM_USER_PASSWORD> "ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('persistence', 'log_backup_timeout_s') = '300' WITH RECONFIGURE"
 ```
 
-### Check the log backup timeout
+### Check the log backup time-out
 
-After you make the change to the log backup timeout, ensure that the timeout is set by using the following command.
+After you make the change to the log backup time-out, ensure that the time-out is set by using the following command.
 
 In this example, the settings are displayed as `SYSTEM` settings. This query also returns the `DEFAULT` settings for comparison.
 
@@ -819,6 +842,10 @@ Apply the following changes to the Oracle database to allow for monitoring by th
 
 No special database configuration is required for Db2 because you're using the instance user's local operating system environment.
 
+# [Microsoft SQL Server](#tab/mssql)
+
+No special database configuration is required for Microsoft SQL Server as we are using the User's local operating system environment.
+
 ---
 
 

articles/azure-netapp-files/azacsnap-installation.md

@@ -26,7 +26,7 @@ First, download the AzAcSnap executable file to any directory on your computer.
   - The Linux binary has an associated [Linux signature file](https://aka.ms/azacsnap-linux-signature). This file is signed with Microsoft's public key to allow for GPG verification of the downloaded installer.
 
   > [!IMPORTANT]
-  > The installer is no longer available for Linux. Please follow the [guidelines here](azacsnap-installation.md) to setup the user's profile to run AzAcSnap and its dependencies.
+  > The installer is no longer available for Linux. Please follow the [guidelines here](azacsnap-installation.md) to set up the user's profile to run AzAcSnap and its dependencies.
 
 - [Windows 64-bit](https://aka.ms/azacsnap-windows) (executable)
   - The Windows binary is signed by Microsoft.
@@ -88,6 +88,10 @@ Follow the guidelines to set up and run the snapshots and disaster-recovery comm
     DB20000I  The QUIT command completed successfully.
     ```
 
+    # [Microsoft SQL Server](#tab/mssql)
+
+    There are no specific database connection requirements for MS SQL Server as AzAcSnap has built-in connectivity to MS SQL Server.
+   
     ---
 ## Install the snapshot tools
 

articles/azure-netapp-files/azacsnap-introduction.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: Phil-Jensen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 05/15/2024
+ms.date: 02/01/2025
 ms.author: phjensen
 ---
 
@@ -60,11 +60,13 @@ AzAcSnap is a single binary. It doesn't need additional agents or plug-ins to in
   - SAP HANA (see the [support matrix](#snapshot-support-matrix-from-sap) for details)
   - Oracle Database release 12 or later (see [Oracle VM images and their deployment on Microsoft Azure](/azure/virtual-machines/workloads/oracle/oracle-vm-solutions) for details)
   - IBM Db2 for LUW on Linux-only version 10.5 or later (see [IBM Db2 Azure Virtual Machines DBMS deployment for SAP workload](/azure/virtual-machines/workloads/sap/dbms_guide_ibm) for details)
+  - MS SQL Server 2022+
 
 - **Operating systems**
   - SUSE Linux Enterprise Server 12+
-  - Red Hat Enterprise Linux 7+
-  - Oracle Linux 7+
+  - Red Hat Enterprise Linux 8+
+  - Oracle Linux 8+
+  - Windows Server 2016+
 
 - **Azure platforms**
   - Azure Virtual Machines with Azure NetApp Files storage

articles/azure-netapp-files/azacsnap-preview.md

@@ -5,17 +5,16 @@ services: azure-netapp-files
 author: Phil-Jensen
 ms.service: azure-netapp-files
 ms.topic: reference
-ms.date: 05/15/2024
+ms.date: 02/01/2025
 ms.author: phjensen
 ---
 
 # Preview features of the Azure Application Consistent Snapshot tool
 
 This article provides a guide on setup and usage of the new features in preview for the Azure Application Consistent Snapshot tool (AzAcSnap). For basic information about the tool, see [What is the Azure Application Consistent Snapshot tool?](./azacsnap-introduction.md).
 
-The preview features provided with AzAcSnap 10 are:
+The preview features provided with AzAcSnap 11 are:
 
-- Microsoft SQL Server
 - Azure NetApp Files backup
 - Azure managed disks
 
@@ -31,76 +30,6 @@ AzAcSnap preview features are offered together with generally available features
 
 You can provide feedback on AzAcSnap, including this preview, [online](https://aka.ms/azacsnap-feedback).
 
-## Microsoft SQL Server
-
-### Supported platforms and operating systems
-
-> [!NOTE]
-> Support for Microsoft SQL Server is Preview feature.  
-> This section's content supplements [What is Azure Application Consistent Snapshot tool](azacsnap-introduction.md) page.
-
-New database platforms and operating systems supported with this preview release.
-
-- **Databases**
-  - Microsoft SQL Server 2022 (or later) on Windows Server 2019 (or later) only is in preview.
-
-
-### Enable communication with database
-
-> [!NOTE]
-> Support for Microsoft SQL Server is Preview feature.  
-> This section's content supplements [Install Azure Application Consistent Snapshot tool](azacsnap-installation.md) page.
-This section explains how to enable communication with the database. Ensure the database you're using is correctly selected from the tabs.
-
-# [Microsoft SQL Server](#tab/mssql)
-
-The snapshot tools issue commands to the Microsoft SQL Server database directly to enable and disable backup mode.  
-
-AzAcSnap connects directly to Microsoft SQL Server using the provided connect-string to issue SQL commands, such as `ALTER SERVER CONFIGURATION SET SUSPEND_FOR_SNAPSHOT_BACKUP = ON` or `ALTER SERVER CONFIGURATION SET SUSPEND_FOR_SNAPSHOT_BACKUP = OFF`.  The connect-string will determine if the installation is on the database server or a centralized "backup" server.  Typical installations of AzAcSnap would be onto the database server to ensure features such as flushing file buffers can  work as expected.  If AzAcSnap has been installed onto the database server, then be sure the user running azacsnap has the required permissions.
-
-##### `azacsnap` user permissions
-
-Refer to [Get started with Azure Application Consistent Snapshot tool](azacsnap-get-started.md)
-The `azacsnap` user should have permissions to put Microsoft SQL Server into backup mode, and have permissions to flush I/O buffers to the volumes configured.
-
-Configure (`.\azacsnap.exe -c configure`) with the correct values for Microsoft SQL Server and test (`.\azacsnap.exe -c test --test mssql`) azacsnap database connectivity.
-Run the `azacsnap` test command
-```shell
-.\azacsnap.exe -c test --test mssql
-```
-
-```output
-BEGIN : Test process started for 'mssql'
-BEGIN : Database tests
-PASSED: Successful connectivity to MSSQL version 16.00.1115
-END   : Test process complete for 'mssql'
-```
----
-### Configuring the database
-This section explains how to configure the data base.
-# [Microsoft SQL Server](#tab/mssql)
-No special database configuration is required for Microsoft SQL Server as we are using the User's local operating system environment.
-
----
-
-### Configuring AzAcSnap
-
-This section explains how to configure AzAcSnap for the specified database.
-
-> [!NOTE]
-> Support for Microsoft SQL Server is Preview feature.  
-> This section's content supplements [Configure Azure Application Consistent Snapshot tool](azacsnap-cmd-ref-configure.md) website page.
-### Details of required values
-The following sections provide detailed guidance on the various values required for the configuration file.
-# [Microsoft SQL Server](#tab/mssql)
-#### Microsoft SQL Server Database values for configuration
-When adding a Microsoft SQL Server database to the configuration, the following values are required:
-- **connectionString** = The Connection String used to connect to the database.  For a typical AzAcSnap installation on to the system running Microsoft SQL Server where the Database Instance is MSSQL2022 the connection string = "Trusted_Connection=True;Persist Security Info=True;Data Source=MSSQL2022;TrustServerCertificate=true".
-- **instanceName** = The database instance name.
-- **metaDataFileLocation** = The location where Microsoft SQL Server will write out the backup meta-data file (for example, "C:\\MSSQL_BKP\\").
-
----
-
 ## Azure NetApp Files backup
 
 When you're taking snapshots by using AzAcSnap on multiple volumes, all the snapshots have the same name by default. Due to the removal of the volume name from the resource ID hierarchy when the snapshot is archived into an Azure NetApp Files backup, you must ensure that the snapshot name is unique.

articles/azure-netapp-files/azacsnap-release-notes.md

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: Phil-Jensen
 ms.service: azure-netapp-files
 ms.topic: conceptual
-ms.date: 01/14/2025
+ms.date: 02/01/2025
 ms.author: phjensen
 ---
 
@@ -17,6 +17,27 @@ Download the latest release of the binary for [Linux](https://aka.ms/azacsnap-li
 
 For specific information on Preview features, refer to the [AzAcSnap Preview](azacsnap-preview.md) page.
 
+## Feb-2025
+
+### AzAcSnap 11 (Build: 1BA0C3*)
+
+AzAcSnap 11 is being released with the following fixes and improvements:
+
+
+- Features moved to GA (generally available):
+  - Microsoft SQL Server 2022 on Windows.
+- Dependency updates:
+  - Updated to .NET 8
+    - List of supported operation systems [.NET 8 - Supported OS versions](https://github.com/dotnet/core/blob/main/release-notes/8.0/supported-os.md).
+  -	Azure SDK updated to Track 2 (latest security and performance improvements).
+- Fixes and Improvements:
+  - (NEW) Configurable Data Volume Backup Attempts:
+    - This feature allows you to set the number of times the system will try to perform a data volume backup. It's useful for databases where locking issues might occur. By default, the system will try 3 times, but you can set it to any number from 1. You can configure this by adding the `DATA_BACKUP_ATTEMPTS` variable to the `.azacsnaprc` file or as an environment variable.  Currently, this feature is only available for Microsoft SQL Server.  For details on configuration refer to the [global override settings to control AzAcSnap behavior](azacsnap-tips.md#global-override-settings-to-control-azacsnap-behavior).
+  -	Backup (-c backup) changes:
+    -	Storage snapshot retention management moved to after database taken out of "backup-mode" to reduce time the database is in a "backup-enabled" state.
+
+Download the binary of [AzAcSnap 11 for Linux](https://aka.ms/azacsnap-11-linux) ([signature file](https://aka.ms/azacsnap-11-linux-signature)) or [AzAcSnap 11 for Windows](https://aka.ms/azacsnap-11-windows).
+
 ## Oct-2024
 
 ### AzAcSnap 10a (Build: 1B79BA*)
@@ -27,7 +48,7 @@ AzAcSnap 10a is being released with the following fixes and improvements:
   - Allow configurable wait time-out for Microsoft SQL Server. This option helps you increase time-out for slow responding systems (default and minimum value is 30 seconds).
     - Added a global override variable `MSSQL_CMD_TIMEOUT_SECS` to be used in either the `.azacsnaprc` file or as an environment variable set to the required wait time-out in seconds. For details on configuration refer to the [global override settings to control AzAcSnap behavior](azacsnap-tips.md#global-override-settings-to-control-azacsnap-behavior).
 
-Download the binary of [AzAcSnap 10a for Linux](https://aka.ms/azacsnap-10a-linux)([signature file](https://aka.ms/azacsnap-10a-linux-signature)) or [AzAcSnap 10a for Windows](https://aka.ms/azacsnap-10a-windows).
+Download the binary of [AzAcSnap 10a for Linux](https://aka.ms/azacsnap-10a-linux) ([signature file](https://aka.ms/azacsnap-10a-linux-signature)) or [AzAcSnap 10a for Windows](https://aka.ms/azacsnap-10a-windows).
 
 ## Jul-2024
 

articles/network-watcher/vnet-flow-logs-overview.md

@@ -6,7 +6,7 @@ author: halkazwini
 ms.author: halkazwini
 ms.service: azure-network-watcher
 ms.topic: concept-article
-ms.date: 11/04/2024
+ms.date: 02/04/2025
 
 #CustomerIntent: As an Azure administrator, I want to learn about virtual network flow logs so that I can log my network traffic to analyze and optimize network performance.
 ---
@@ -219,6 +219,23 @@ For continuation (`C`) and end (`E`) flow states, byte and packet counts are agg
 
 Traffic can't be recorded at the private endpoint itself. You can capture traffic to a private endpoint at the source VM. The traffic is recorded with source IP address of the VM and destination IP address of the private endpoint. You can use `PrivateEndpointResourceId` field to identify traffic flowing to a private endpoint. For more information, see [Traffic analytics schema](traffic-analytics-schema.md?tabs=vnet#traffic-analytics-schema).
 
+### Incompatible services
+
+Currently, these Azure services don't support virtual network flow logs:
+
+- [Azure Container Instances](/azure/container-instances/container-instances-overview)
+- [Azure Logic Apps](../logic-apps/logic-apps-overview.md) 
+- [Azure Functions](../azure-functions/functions-overview.md)
+- [Azure DNS Private Resolver](../dns/dns-private-resolver-overview.md)
+- [App Service](../app-service/overview.md)
+- [Azure Database for MariaDB](/azure/mariadb/overview)
+- [Azure Database for MySQL](/azure/mysql/single-server/overview)
+- [Azure Database for PostgreSQL](/azure/postgresql/single-server/overview)
+- [Azure NetApp Files](/azure/azure-netapp-files/azure-netapp-files-introduction)
+
+> [!NOTE]
+> App services deployed under an Azure App Service plan don't support virtual network flow logs. To learn more, see [How virtual network integration works](../app-service/overview-vnet-integration.md#how-regional-virtual-network-integration-works).
+
 ## Pricing
 
 - Virtual network flow logs are charged per gigabyte of ***Network flow logs collected*** and come with a free tier of 5 GB/month per subscription.

articles/operator-nexus/TOC.yml

@@ -326,6 +326,12 @@
       items:
         - name: Troubleshoot Isolation Domain
           href: troubleshoot-isolation-domain.md
+        - name: Troubleshoot LACP Bonding
+          href: troubleshoot-lacp-bonding.md
+        - name: Troubleshoot DNS Issues
+          href: troubleshoot-dns-issues.md
+        - name: Troubleshoot TWAMP (UDP) not working
+          href: troubleshoot-twamp-udp-not-working.md
     - name: Cluster or BMM
       expanded: false
       items:
@@ -341,14 +347,6 @@
           href: troubleshoot-accepted-cluster-hydration.md
         - name: Troubleshoot Out of Memory Pods
           href: troubleshoot-memory-limits.md
-        - name: Troubleshoot LACP Bonding
-          href: troubleshoot-lacp-bonding.md
-        - name: Troubleshoot DNS Issues
-          href: troubleshoot-dns-issues.md
-        - name: Troubleshoot NAKS Cluster Node Packet Loss
-          href: troubleshoot-packet-loss.md
-        - name: Troubleshoot TWAMP (UDP) not working
-          href: troubleshoot-twamp-udp-not-working.md
     - name: Tenant Workload
       expanded: false
       items:
@@ -371,6 +369,8 @@
           href: troubleshoot-kubernetes-cluster-dual-stack-configuration.md
         - name: Troubleshoot Neighbor Group Creation Error
           href: troubleshoot-neighbor-group-creation-error.md
+        - name: Troubleshoot NAKS Cluster Node Packet Loss
+          href: troubleshoot-packet-loss.md
 - name: FAQ
   href: azure-operator-nexus-faq.md
 - name: Reference