Merge pull request #266652 from MicrosoftDocs/main

Publish to live, Monday 4 AM PST, 2/19

Author: ttorble

articles/azure-netapp-files/TOC.yml

@@ -51,7 +51,7 @@
         href: network-file-system-group-memberships.md
       - name: Understand file locking
         href: understand-file-locks.md  
-      - name: Under volume languages
+      - name: Understand volume languages
         href: understand-volume-languages.md
       - name: Understand file path lengths 
         href: understand-path-lengths.md 

articles/mysql/TOC.yml

@@ -29,6 +29,8 @@
         items:
           - name: January 2024
             href: flexible-server/release-notes/january-2024.md
+          - name: February 2024
+            href: flexible-server/release-notes/february-2024.md
       - name: Compute and storage
         href: flexible-server/concepts-service-tiers-storage.md
   - name: Quickstarts

articles/mysql/flexible-server/release-notes/february-2024.md

@@ -0,0 +1,29 @@
+---
+title: Release notes for Azure Database for MySQL Flexible Server - February 2024
+description: Learn about the release notes for Azure Database for MySQL Flexible Server February 2024.
+author: xboxeer
+ms.author: yuzheng1
+ms.date: 02/09/2024
+ms.service: mysql
+ms.subservice: flexible-server
+ms.topic: conceptual
+---
+
+# Azure Database For MySQL Flexible Server February 2024 Maintenance
+
+We're pleased to announce the February 2024 maintenance for Azure Database for MySQL Flexible Server. This maintenance mainly focuses on known issue fix, underlying OS upgrading and vulnerability patching.
+
+## Engine version changes
+There will be no engine version changes in this maintenance update.
+
+## Features
+There will be no new features in this maintenance update.
+
+## Improvement
+There will be no new improvement in this maintenance update.
+
+## Known Issues Fix
+- Fix HA standby replication dead lock issue caused by slave_preserve_commit_order.
+- Fix promotion stuck issue when source server is unavailable or source region is down. Improve customer experience on replica promotion to better support disaster recovery.
+- Fix the default value of character_set_server & collation_server.
+- Allow customer to start InnoDB buffer pool dump.

articles/postgresql/flexible-server/concepts-business-continuity.md

@@ -95,9 +95,9 @@ Below are some unplanned failure scenarios and the recovery process.
 | ---------- |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| ------- |
 | **Database server failure** | If the database server is down, Azure will attempt to restart the database server. If that fails, the database server will be restarted on another physical node.  <br /> <br /> The recovery time (RTO) is dependent on various factors including the activity at the time of fault, such as large transaction, and the volume of recovery to be performed during the database server startup process. <br /> <br /> Applications using the PostgreSQL databases need to be built in a way that they detect and retry dropped connections and failed transactions.                                                                                                                                                                  | If the database server failure is detected, the server is failed over to the standby server, thus reducing downtime. For more information, see [HA concepts page](./concepts-high-availability.md). RTO is expected to be 60-120s, with zero data loss. |
 | **Storage failure** | Applications don't see any impact for any storage-related issues such as a disk failure or a physical block corruption. As the data is stored in three copies, the copy of the data is served by the surviving storage. The corrupted data block is automatically repaired and a new copy of the data is automatically created. | For any rare and non-recoverable errors such as the entire storage is inaccessible, the Azure Database for PostgreSQL flexible server instance is failed over to the standby replica to reduce the downtime. For more information, see [HA concepts page](./concepts-high-availability.md). |
-| ** Logical/user errors** | To recover from user errors, such as accidentally dropped tables or incorrectly updated data, you have to perform a [point-in-time recovery](../concepts-backup.md) (PITR). While performing the restore operation, you specify the custom restore point, which is the time right before the error occurred.<br> <br>  If you want to restore only a subset of databases or specific tables rather than all databases in the database server, you can restore the database server in a new instance, export the table(s) via [pg_dump](https://www.postgresql.org/docs/current/app-pgdump.html), and then use [pg_restore](https://www.postgresql.org/docs/current/app-pgrestore.html) to restore those tables into your database. | These user errors aren't protected with high availability as all changes are replicated to the standby replica synchronously. You have to perform point-in-time restore to recover from such errors. |
-| ** Availability zone failure** | To recover from a zone-level failure, you can perform point-in-time restore using the backup and choosing a custom restore point with the latest time to restore the latest data. A new Azure Database for PostgreSQL flexible server instance is deployed in another non-impacted zone. The time taken to restore depends on the previous backup and the volume of transaction logs to recover. | Azure Database for PostgreSQL flexible server is automatically failed over to the standby server within 60-120s with zero data loss. For more information, see [HA concepts page](./concepts-high-availability.md). | 
-| ** Region failure** | If your server is configured with geo-redundant backup, you can perform geo-restore in the paired region. A new server will be provisioned and recovered to the last available data that was copied to this region. <br /> <br /> You can also use cross region read replicas. In the event of region failure you can perform disaster recovery operation by promoting your read replica to be a standalone read-writeable server. RPO is expected to be up to 5 minutes (data loss possible) except in the case of severe regional failure when the RPO can be close to the replication lag at the time of failure.                                                                                                               | Same process. |
+| **Logical/user errors** | To recover from user errors, such as accidentally dropped tables or incorrectly updated data, you have to perform a [point-in-time recovery](../concepts-backup.md) (PITR). While performing the restore operation, you specify the custom restore point, which is the time right before the error occurred.<br> <br>  If you want to restore only a subset of databases or specific tables rather than all databases in the database server, you can restore the database server in a new instance, export the table(s) via [pg_dump](https://www.postgresql.org/docs/current/app-pgdump.html), and then use [pg_restore](https://www.postgresql.org/docs/current/app-pgrestore.html) to restore those tables into your database. | These user errors aren't protected with high availability as all changes are replicated to the standby replica synchronously. You have to perform point-in-time restore to recover from such errors. |
+| **Availability zone failure** | To recover from a zone-level failure, you can perform point-in-time restore using the backup and choosing a custom restore point with the latest time to restore the latest data. A new Azure Database for PostgreSQL flexible server instance is deployed in another non-impacted zone. The time taken to restore depends on the previous backup and the volume of transaction logs to recover. | Azure Database for PostgreSQL flexible server is automatically failed over to the standby server within 60-120s with zero data loss. For more information, see [HA concepts page](./concepts-high-availability.md). | 
+| **Region failure** | If your server is configured with geo-redundant backup, you can perform geo-restore in the paired region. A new server will be provisioned and recovered to the last available data that was copied to this region. <br /> <br /> You can also use cross region read replicas. In the event of region failure you can perform disaster recovery operation by promoting your read replica to be a standalone read-writeable server. RPO is expected to be up to 5 minutes (data loss possible) except in the case of severe regional failure when the RPO can be close to the replication lag at the time of failure.                                                                                                               | Same process. |
 
 
 ### Configure your database after recovery from regional failure

articles/site-recovery/avs-tutorial-dr-drill-azure.md

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 manager: rochakm
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 12/04/2023
+ms.date: 02/19/2024
 ms.author: ankitadutta
 ms.custom: MVC
 
@@ -72,7 +72,7 @@ When you run a test failover, the following actions happen:
 2. Failover processes the data, so that an Azure VM can be created. If you select the latest recovery point, a recovery point is created from the data.
 3. An Azure VM is created from the data processed in the previous step.
 
-Run the test failover as follows:
+**Run the test failover as follows:**
 
 1. In **Settings** > **Replicated Items**, select the VM, and then select **+Test Failover**.
 2. Select the **Latest processed** recovery point for this tutorial. This step fails over the VM to the latest available point in time. The time stamp is shown.
@@ -99,5 +99,4 @@ If you want to connect to Azure VMs by using Remote Desktop Protocol (RDP) or Se
 
 ## Next step
 
-> [!div class="nextstepaction"]
-> [Learn more about running a failover](avs-tutorial-failover.md)
+- [Learn more about running a failover](avs-tutorial-failover.md).

articles/site-recovery/avs-tutorial-failover.md

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 manager: rochakm
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 12/04/2023
+ms.date: 02/19/2024
 ms.author: ankitadutta
 ms.custom: MVC, engagement-fy23
 ---
@@ -97,8 +97,7 @@ If you encounter any connectivity problems after failover, follow the [troublesh
 
 After failover, reprotect the Azure VMs to the Azure VMware Solution private cloud. Then, after the VMs are reprotected and replicating to the Azure VMware Solution private cloud, fail back from Azure when you're ready.
 
-> [!div class="nextstepaction"]
-> [Reprotect Azure VMs](avs-tutorial-reprotect.md)
 
-> [!div class="nextstepaction"]
-> [Fail back from Azure](avs-tutorial-failback.md)
+- Learn how to [reprotect Azure VMs](avs-tutorial-reprotect.md).
+- Learn how to [fail back from Azure](avs-tutorial-failback.md).
+

articles/site-recovery/avs-tutorial-prepare-avs.md

@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
 manager: rochakm
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 12/04/2023
+ms.date: 02/19/2024
 ms.author: ankitadutta
 ms.custom: MVC, engagement-fy23
 ---
@@ -74,10 +74,12 @@ Make sure that the VMware vCenter server and VMs comply with requirements:
 * Verify that the Azure VMware Solution VMs that you'll replicate to Azure comply with [Azure VM requirements](vmware-physical-azure-support-matrix.md#azure-vm-requirements).
 * For Linux VMs, ensure that no two devices or mount points have the same names. These names must be unique and aren't case-sensitive. For example, you can't name two devices for the same VM as *device1* and *Device1*.
 
+
 ## Prepare to connect to Azure VMs after failover
 
 After failover, you might want to connect to the Azure VMs from your Azure VMware Solution network.
 
+
 ### Connect to a Windows VM by using RDP
 
 Before failover, enable Remote Desktop Protocol (RDP) on the Azure VMware Solution VM:
@@ -93,6 +95,7 @@ There should be no Windows updates pending on the VM when you trigger a failover
 
 After failover, check **Boot diagnostics** to view a screenshot of the VM. If you can't connect, check that the VM is running and review [troubleshooting tips](https://social.technet.microsoft.com/wiki/contents/articles/31666.troubleshooting-remote-desktop-connection-after-failover-using-asr.aspx).
 
+
 ### Connect to Linux VMs by using SSH
 
 On the Azure VMware Solution VM before failover:
@@ -104,16 +107,14 @@ After failover, allow incoming connections to the SSH port for the network secur
 
 You can check **Boot diagnostics** to view a screenshot of the VM.
 
+
 ## Failback requirements
 
 If you plan to fail back to your Azure VMware Solution cloud, there are several [prerequisites for failback](avs-tutorial-reprotect.md#before-you-begin). You can prepare these now, but you don't need to. You can prepare after you fail over to Azure.
 
-## Next steps
 
-> [!div class="nextstepaction"]
-> [Set up disaster recovery](avs-tutorial-replication.md)
+## Next steps
 
-If you're replicating multiple VMs:
+- Learn how to [set up disaster recovery](avs-tutorial-replication.md).
+- If you're replicating multiple VMs, perform [capacity planning](site-recovery-deployment-planner.md).
 
-> [!div class="nextstepaction"]
-> [Perform capacity planning](site-recovery-deployment-planner.md)

articles/site-recovery/avs-tutorial-prepare-azure.md

@@ -6,7 +6,7 @@ author: ankitaduttaMSFT
 manager: rochakm
 ms.service: site-recovery
 ms.topic: tutorial
-ms.date: 12/04/2023
+ms.date: 02/19/2024
 ms.author: ankitadutta
 ms.custom: MVC, engagement-fy23
 
@@ -108,11 +108,6 @@ The virtual network takes a few seconds to create. After it's created, it appear
 
 Learn more about:
 
-> [!div class="nextstepaction"]
-> [Preparing your infrastructure](avs-tutorial-prepare-avs.md)
-
-> [!div class="nextstepaction"]
-> [Azure networks](../virtual-network/virtual-networks-overview.md)
-
-> [!div class="nextstepaction"]
-> [Managed disks](../virtual-machines/managed-disks-overview.md)
+- [Preparing your infrastructure](avs-tutorial-prepare-avs.md)
+- [Azure networks](../virtual-network/virtual-networks-overview.md)
+- [Managed disks](../virtual-machines/managed-disks-overview.md).