Merge pull request #300214 from Phil-Jensen/patch-2

Add guidance to use latest release.

Author: prmerger-automator[bot]

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

@@ -5,14 +5,19 @@ services: azure-netapp-files
 author: Phil-Jensen
 ms.service: azure-netapp-files
 ms.topic: concept-article
-ms.date: 02/01/2025
+ms.date: 05/21/2025
 ms.author: phjensen
 ---
 
 # Release Notes for Azure Application Consistent Snapshot tool
 
 This page lists major changes made to AzAcSnap to provide new functionality or resolve defects.
 
+We recommend that customers always use the latest release of the Azure Application Consistent Snapshot tool (AzAcSnap) to benefit from the most up-to-date security enhancements, performance improvements, and expanded platform support. Each release is designed to strengthen the tool’s reliability and security posture, ensuring alignment with Microsoft’s evolving best practices for data protection and compliance.
+
+> [!IMPORTANT]
+> To ensure accurate troubleshooting and support, issues should be reproduced using the latest AzAcSnap release. Please update to the most recent version before reporting any problems.
+
 Download the latest release of the binary for [Linux](https://aka.ms/azacsnap-linux) or [Windows](https://aka.ms/azacsnap-windows) and review how to [get started](azacsnap-get-started.md).  
 
 For specific information on Preview features, refer to the [AzAcSnap Preview](azacsnap-preview.md) page.

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

@@ -1,11 +1,11 @@
 ---
 title: Troubleshoot Azure Application Consistent Snapshot tool - Azure NetApp Files
-description: Troubleshoot communication issues, test failures, and other SAP HANA issues when using the Azure Application Consistent Snapshot (AzAcSnap) tool.
+description: Troubleshoot communication issues, test failures, and other issues when using the Azure Application Consistent Snapshot (AzAcSnap) tool.
 services: azure-netapp-files
 author: Phil-Jensen
 ms.service: azure-netapp-files
 ms.topic: troubleshooting
-ms.date: 05/15/2024
+ms.date: 05/21/2025
 ms.author: phjensen
 ms.custom: kr2b-contr-experiment
 ---
@@ -14,15 +14,19 @@ ms.custom: kr2b-contr-experiment
 
 This article describes how to troubleshoot issues when using the Azure Application Consistent Snapshot (AzAcSnap) tool for Azure NetApp Files and Azure Large Instance.
 
-You might encounter several common issues when running AzAcSnap commands. Follow the instructions to troubleshoot the issues. If you still have issues, open a Service Request for Microsoft Support from the Azure portal and assign the request to the SAP HANA Large Instance queue.
+You might encounter several common issues when running AzAcSnap commands. Follow the instructions to troubleshoot the issues. 
+
+> [!IMPORTANT]
+> To ensure accurate troubleshooting and support, issues should be reproduced using the latest AzAcSnap release. Update to the most recent version before reporting any problems.
+> If you still have issues, go to the Azure portal and select Support + troubleshooting and search for guidance on issues with AzAcSnap, this allows you to open a Service Request for Microsoft Support.
 
 ## AzAcSnap command won't run
 
 In some cases AzAcSnap won't start due to the user's environment.
 
 ### Failed to create CoreCLR
 
-AzAcSnap is written in .NET and the CoreCLR is an execution engine for .NET apps, performing functions such as IL byte code loading, compilation to machine code and garbage collection.  In this case there is an environmental problem blocking the CoreCLR engine from starting.
+AzAcSnap is written in .NET and the CoreCLR is an execution engine for .NET apps.  It performs functions such as IL byte code loading, compilation to machine code, and garbage collection.  In the case of CoreCLR errors, there's an environmental problem blocking the CoreCLR engine from starting.
 
 A common cause is limited permissions or environmental setup for the AzAcSnap operating system user, usually 'azacsnap'.
 
@@ -82,7 +86,7 @@ Make a `TMPDIR` for the `azacsnap` user:
 ```
 
 > [!IMPORTANT]
-> Changing the user's `TMPDIR` would need to be made permanent by changing the user's profile (e.g. `$HOME/.bashrc` or `$HOME/.bash_profile`).  There would also be a need to clean-up the `TMPDIR` on system reboot, this is typically automatic for `/tmp`.
+> Changing the user's `TMPDIR` would need to be made permanent by changing the user's profile (for example, `$HOME/.bashrc` or `$HOME/.bash_profile`). Making this change means a manual clean up of the `TMPDIR` would be needed on system reboot. This `TMPDIR` clean up is typically automatic for `/tmp`.
 
 ## Check log files, result files, and syslog
 
@@ -92,13 +96,13 @@ Some of the best sources of information for investigating AzAcSnap issues are th
 
 The AzAcSnap log files are stored in the directory configured by the `logPath` parameter in the AzAcSnap configuration file. The default configuration filename is *azacsnap.json*, and the default value for `logPath` is *./logs*, which means the log files are written into the *./logs* directory relative to where the `azacsnap` command runs. If you make the `logPath` an absolute location, such as */home/azacsnap/logs*, `azacsnap` always outputs the logs into */home/azacsnap/logs*, regardless of where you run the `azacsnap` command.
 
-The log filename is based on the application name, `azacsnap`, the command run with `-c`, such as `backup`, `test`, or `details`, and the default configuration filename, such as *azacsnap.json*. With the `-c backup` command, a default log filename would be *azacsnap-backup-azacsnap.log*, written into the  directory configured by `logPath`.
+The log filename is based on the application name, `azacsnap`, the command run with `-c`, such as `backup`, `test`, or `details`, and the default configuration filename, such as *azacsnap.json*. With the `-c backup` command, a default log filename would be *azacsnap-backup-azacsnap.log*, written into the directory configured by `logPath`.
 
 This naming convention allows for multiple configuration files, one per database, to help locate the associated log files. If the configuration filename is *SID.json*, then the log filename when using the `azacsnap -c backup --configfile SID.json` option is *azacsnap-backup-SID.log*.
 
 ### Result files and syslog
 
-For the `-c backup` command, AzAcSnap writes to a *\*.result* file.  The purpose of the *\*.result* file is to provide high-level confirmation of success/failure.  If the *\*.result* file is empty, then assume failure.  Any output written to the *\*.result* file is also output to the system log (for example, `/var/log/messages`) by using the `logger` command. The *\*.result* filename has the same base name as the log file to allow for matching the result file with the configuration file and the backup log file.  The *\*.result* file goes into the same location as the other log files and is a simple one line output file.
+For the `-c backup` command, AzAcSnap writes to a *\*.result* file. The purpose of the *\*.result* file is to provide high-level confirmation of success/failure. If the *\*.result* file is empty, then assume failure. Any output written to the *\*.result* file is also output to the system log (for example, `/var/log/messages`) by using the `logger` command. The *\*.result* filename has the same base name as the log file to allow for matching the result file with the configuration file and the backup log file. The *\*.result* file goes into the same location as the other log files and is a simple one line output file.
 
 1. Example for successful completion:
 
@@ -114,7 +118,7 @@ For the `-c backup` command, AzAcSnap writes to a *\*.result* file.  The purpose
       Dec 17 09:01:13 azacsnap-rhel azacsnap: Database # 1 (PR1) : completed ok
       ```
 
-1. Example output where a failure has occurred and AzAcSnap captured the failure:
+1. Example output where a failure occurred and AzAcSnap captured the failure:
 
    1. Output to *\*.result* file:
    
@@ -236,14 +240,14 @@ To troubleshoot this error:
    [19/Nov/2020:18:39:49 +13:00] DEBUG: [PID:0020080:StorageANF:659] [1] Innerexception: Microsoft.IdentityModel.Clients.ActiveDirectory.AdalServiceException AADSTS7000215: Invalid client secret is provided.
    ```
 
-1. Check the log file to see if the service principal has expired. The following log file example shows that the client secret keys are expired.
+1. Check the log file to see if the service principal is expired. The following log file example shows that the client secret keys are expired.
 
    ```output
-   [19/Nov/2020:18:41:10 +13:00] DEBUG: [PID:0020257:StorageANF:659] [1] Innerexception: Microsoft.IdentityModel.Clients.ActiveDirectory.AdalServiceException AADSTS7000222: The provided client secret keys are expired. Visit the Azure Portal to create new keys for your app, or consider using certificate credentials for added security: https://learn.microsoft.com/azure/active-directory/develop/active-directory-certificate-credentials
+   [19/Nov/2020:18:41:10 +13:00] DEBUG: [PID:0020257:StorageANF:659] [1] Innerexception: Microsoft.IdentityModel.Clients.ActiveDirectory.AdalServiceException AADSTS7000222: The provided client secret keys are expired. Visit the Azure portal to create new keys for your app, or consider using certificate credentials for added security: https://learn.microsoft.com/azure/active-directory/develop/active-directory-certificate-credentials
    ```
 
 > [!TIP]
-> For more information on generating a new Service Principal, refer to the section [Enable communication with Storage](azacsnap-configure-storage.md?tabs=azure-netapp-files#enable-communication-with-storage) in the [Install Azure Application Consistent Snapshot tool](azacsnap-installation.md) guide.
+> For more information on generating a new Service Principal, see the section [Enable communication with Storage](azacsnap-configure-storage.md?tabs=azure-netapp-files#enable-communication-with-storage) in the [Install Azure Application Consistent Snapshot tool](azacsnap-installation.md) guide.
 
 ## Troubleshoot failed 'test hana' command
 
@@ -277,7 +281,7 @@ Make sure the installer added the location of these files to the AzAcSnap user's
 
 ### Invalid value for key
 
-This command output shows that the connection key hasn't been set up correctly with the `hdbuserstore Set` command.
+This command output shows that the connection key isn't set up correctly with the `hdbuserstore Set` command.
 
 ```bash
 hdbsql -n 172.18.18.50 -i 00 -U AZACSNAP "select version from sys.m_database"