Added Juan's edits

Author: jjaygbay

articles/azure-vmware/migrate-sqlserver-always-on-cluster.md

@@ -14,10 +14,30 @@ In this article, you’ll learn how to migrate Microsoft SQL Server Always-On Cl
 
 ## Prerequisites
 
+These prerequisites and requirements should be met before planning to migrate your SQL server instance to Azure VMware Solution.
+
 - Review and record the storage and network configuration of every node in the cluster.
 - Take a full backup of the database.
 - Take a full backup of the virtual machine running the Microsoft SQL Server instance. 
 - Remove the virtual machine from any VMware vSphere DRS Groups and rules.
+- VMware HCX must be configured between your on-premises datacenter and the Azure VMware Solution private cloud that will run the migrated workloads. Refer to [Azure VMware Solution documentation](https://learn.microsoft.com/en-us/azure/azure-vmware/install-vmware-hcx) for the procedure.
+- Ensure that all the network segments in use by the Microsoft SQL Server are extended into your Azure VMware Solution private cloud. Please refer to [Configure VMware HCX network extension](https://learn.microsoft.com/en-us/azure/azure-vmware/configure-hcx-network-extension) documentation to verify this step.
+
+VMware HCX over VPN is supported in Azure VMware Solution for workload migration. However, due to the size of database workloads it is not recommended for Microsoft SQL Server Failover Cluster Instance and Microsoft SQL Server Always-On migrations, especially for production workloads ExpressRoute connectivity is more performant and reliable. For Microsoft SQL Server Standalone and non-production workloads this can be suitable, depending upon the size of the database, to migrate. 
+
+Microsoft SQL Server 2019 and 2022 were tested with Windows Server 2019 and 2022 Data Center edition with the virtual machines deployed in the on-premises environment. Windows Server and SQL Server have been configured following best practices and recommendations from Microsoft and VMware.
+
+## Downtime considerations
+
+Predicting downtime during a migration will depend upon the size of the database to be migrated and the speed of the private network connection to Azure cloud. Always On migration is designed to have low database downtime during its execution, plan for the migration to be executed during off-peak hours with an approved change window.
+
+The table below indicates the downtime for each Microsoft SQL Server topology.
+
+| **Scenario** | **Downtime expected** | **Notes** |
+|:---|:-----|:-----|
+| **Standalone instance** | LOW | Migration will be done using vMotion, the DB will be available during migration time, but it is not recommended to commit any critical data during it. |
+| **Always-On Availability Group** | LOW | The primary replica will always be available during the migration of the first secondary replica and the secondary replica will become the primary after the initial failover to Azure. |
+| **Failover Cluster Instance** | HIGH | All nodes of the cluster will be shut down and migrated using VMware HCX Cold Migration. Downtime duration will depend upon database size and private network speed to Azure cloud. |
 
 ## Windows Server Failover Cluster quorum considerations
 
@@ -40,15 +60,15 @@ If the cluster uses a **File share witness** running on-premises, then the type
 - Disaster Recovery and Business Continuity: For a disaster recovery scenario the best and most reliable option is to create a **Cloud Witness** running in Azure Storage. 
 - Application Modernization: For this use case the best option is to deploy a **Cloud Witness**.
 
-Full details about quorum configuration and management can be consulted in [Failover Clustering documentation](https://learn.microsoft.com/windows-server/failover-clustering/manage-cluster-quorum). Refer to [Manage  a cluster quorum for a Failover Cluster](https://learn.microsoft.com/windows-server/failover-clustering/deploy-cloud-witness) documentation for the details about deployment of Cloud witness in Azure Blob Storage.
+Full details about quorum configuration and management can be consulted in [Failover Clustering documentation](https://learn.microsoft.com/windows-server/failover-clustering/manage-cluster-quorum). Refer to [Manage a cluster quorum for a Failover Cluster](https://learn.microsoft.com/windows-server/failover-clustering/deploy-cloud-witness) documentation for the details about deployment of Cloud witness in Azure Blob Storage.
 
 ## Migrate Microsoft SQL Server Always-On cluster
 
 1. Access your Always-On cluster with SQL Server Management Studio with administration credentials.
     1. Select your primary replica and open **Availability Group** **Properties**.
 
 
-          :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-1.png" alt-text="Diagram showing how to migrate always on SQL server for  Azure VMware Solution." border="false":::
+          :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-1.png" alt-text="Always On Availability Group properties" border="false":::
 
      1. Change **Availability Mode** to **Asynchronous commit** only for the replica to be migrated.
      1. Change **Failover Mode** to **Manual** for every member of the availability group.
@@ -66,26 +86,26 @@ Full details about quorum configuration and management can be consulted in [Fail
       1. Click **Go** and the migration will initiate. 
 1. Once the migration has been completed, access the migrated replica and verify connectivity with the rest of the members in the availability group.
 1. In SQL Server Management Studio, open the **Availability Group Dashboard** and verify that the replica appears as **Online**. 
-      :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-2.png" alt-text="Diagram showing how to migrate always on SQL server for  Azure VMware Solution." border="false":::
+      :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-2.png" alt-text="Always On Availability Group Dashboard." border="false":::
 
    1. **Data Loss** status in the **Failover Readiness** column is expected since the replica has been out-of-sync with the primary during the migration. 
 1. Edit the **Availability Group** **Properties** again and set **Availability Mode** back to **Synchronous commit**.
       1. The secondary replica will start to synchronize back all the changes made to the primary replica during the migration. Wait until it appears in Synchronized state. 
 1. From the **Availability Group Dashboard** in SSMS click on **Start Failover Wizard**.
 1. Select the migrated replica and click **Next**.
 
-    :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-3.png" alt-text="Diagram showing how to migrate always on SQL server for  Azure VMware Solution." border="false":::
+    :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-3.png" alt-text="New primary replica selection for failover." border="false":::
 
 1. Connect to the replica in the next screen with your DB admin credentials.
-    :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-4.png" alt-text="Diagram showing how to connect to the replica and migrate always on SQL server for  Azure VMware Solution." border="false":::
+    :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-4.png" alt-text="New primary replica admin credentials connection." border="false":::
 
 1. Review the changes and click **Finish** to start the failover operation.
 
-    :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-5.png" alt-text="Diagram showing how to review changes and migrate always on SQL server for  Azure VMware Solution." border="false":::
+    :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-5.png" alt-text="Availability Group failover operation review." border="false":::
 
 
 1. Monitor the progress of the failover in the next screen and click **Close** when the operation is finished.
-    :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-6.png" alt-text="Diagram showing how to review results and migrate always on SQL server for  Azure VMware Solution." border="false"::: 
+    :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-6.png" alt-text="Failover successfully finished." border="false"::: 
 
 
 1. Refresh the **Object Explorer** view in SSMS and verify that the migrated instance is now the primary replica.
@@ -94,11 +114,9 @@ Full details about quorum configuration and management can be consulted in [Fail
        1. Do not migrate all the replicas at the same time using **HCX Bulk Migration**. Instead, migrate one replica at a time and verify that all changes are synchronized back to the replica after each migration.
 1. Once the migration of all the replicas is completed, access your Always-On availability group with **SQL Server Management Studio**.
     1. Open the Dashboard and verify there is no data loss in any of the replicas and that all are in     **Synchronized** state.
-          :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-7.png" alt-text="Diagram showing how to review changes and migrate always on SQL server for  Azure VMware Solution." border="false":::
+          :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-7.png" alt-text="Availability Group Dashboard with new primary replica and all migrated secondary replicas in synchronized state." border="false":::
     1. Edit the **Properties** of the availability group and set **Failover Mode** to **Automatic** in all replicas. 
-              :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-8.png" alt-text="Diagram showing how to edit the properties and  migrate always on SQL server for  Azure VMware Solution." border="false":::
-
-During the process, you will create placement policies that can recreate the Affinity or Anti-Affinity rules previously present on-premises. For more details about placement policies, see [Create a placement policy in Azure VMware Solution](https://learn.microsoft.com/azure/azure-vmware/create-placement-policy) article. 
+              :::image type="content" source="media/sql-server-hybrid-benefit/sql-alwayson-8.png" alt-text="Set Failover back to Automatic for all replicas." border="false":::
 
 ## Next steps 
 

articles/azure-vmware/migrate-sqlserver-failover-cluster.md

@@ -13,7 +13,7 @@ In this article, you learn how to migrate a Microsoft SQL Server Failover Cluste
 
 VMware HCX doesn't support migrating virtual machines with SCSI controllers in physical sharing mode attached to a virtual machine. However, we can overcome this limitation by performing the steps detailed in this procedure and using VMware HCX Cold Migration to move the different virtual machines that make up the cluster. 
 
-:::image type="content" source="media/sql-server-hybrid-benefit/migrated-sql-failover-cluster.png" alt-text="Diagram showing the architecture of always on SQL server for  Azure VMware Solution." border="false"::: 
+:::image type="content" source="media/sql-server-hybrid-benefit/migrated-sql-failover-cluster.png" alt-text="Diagram showing the architecture of SQL failover server for  Azure VMware Solution." border="false"::: 
 
 > [!NOTE]
 > This procedure requires a full shutdown of the cluster. Plan accordingly for the downtime period during the migration since the Microsoft SQL Server service will be unavailable. 
@@ -25,6 +25,24 @@ VMware HCX doesn't support migrating virtual machines with SCSI controllers in p
 - Take a full backup of the database(s) being executed in the cluster.
 - Take a full backup of the cluster virtual machines. 
 - Remove all cluster node VMs from any DRS Group and rules they're part of.
+- VMware HCX must be configured between your on-premises datacenter and the Azure VMware Solution private cloud that will run the migrated workloads. Refer to [Azure VMware Solution documentation](https://learn.microsoft.com/en-us/azure/azure-vmware/install-vmware-hcx) for the procedure.
+- Ensure that all the network segments in use by the Microsoft SQL Server are extended into your Azure VMware Solution private cloud. Please refer to [Configure VMware HCX network extension](https://learn.microsoft.com/en-us/azure/azure-vmware/configure-hcx-network-extension) documentation to verify this step.
+
+VMware HCX over VPN is supported in Azure VMware Solution for workload migration. However, due to the size of database workloads it is not recommended for Microsoft SQL Server Failover Cluster Instance and Microsoft SQL Server Always-On migrations, especially for production workloads ExpressRoute connectivity is more performant and reliable. For Microsoft SQL Server Standalone and non-production workloads this can be suitable, depending upon the size of the database, to migrate. 
+
+Microsoft SQL Server 2019 and 2022 were tested with Windows Server 2019 and 2022 Data Center edition with the virtual machines deployed in the on-premises environment. Windows Server and SQL Server have been configured following best practices and recommendations from Microsoft and VMware.
+
+## Downtime considerations
+
+Predicting downtime during a migration will depend upon the size of the database to be migrated and the speed of the private network connection to Azure cloud. Migration of SQL Server Failover Cluster Instances Always On to Azure Vmware Solution requires a full downtime of the database and all cluster nodes, however you should plan for the migration to be executed during off-peak hours with an approved change window.
+
+The table below indicates the downtime for each Microsoft SQL Server topology.
+
+| **Scenario** | **Downtime expected** | **Notes** |
+|:---|:-----|:-----|
+| **Standalone instance** | LOW | Migration will be done using vMotion, the DB will be available during migration time, but it is not recommended to commit any critical data during it. |
+| **Always-On Availability Group** | LOW | The primary replica will always be available during the migration of the first secondary replica and the secondary replica will become the primary after the initial failover to Azure. |
+| **Failover Cluster Instance** | HIGH | All nodes of the cluster will be shut down and migrated using VMware HCX Cold Migration. Downtime duration will depend upon database size and private network speed to Azure cloud. |
 
 ## Windows Server Failover Cluster quorum considerations
 
@@ -57,10 +75,10 @@ For illustration purposes in this document, we're using a two-node cluster with
 1. Access the first node of the cluster and open Failover Cluster Manager.
     1. Verify that the second node is in **Offline** state and that all clustered services and storage are under control of the first node.
 
-         :::image type="content" source="media/sql-server-hybrid-benefit/sqlfci-1.png" alt-text="Diagram showing offline state of failover cluster on SQL server for  Azure VMware Solution." border="false":::
+         :::image type="content" source="media/sql-server-hybrid-benefit/sqlfci-1.png" alt-text="Windows Server Failover Cluster Manager cluster storage verification." border="false":::
 
     1. Shut down the cluster.
-    :::image type="content" source="media/sql-server-hybrid-benefit/sqlfci-2.png" alt-text="Diagram showing offline state of failover cluster on SQL server for  Azure VMware Solution." border="false":::
+    :::image type="content" source="media/sql-server-hybrid-benefit/sqlfci-2.png" alt-text="Shut down your cluster using Windows Server Failover Cluster Manager." border="false":::
 
 
      1. Check that all cluster services are stopped gracefully and without errors.
@@ -90,32 +108,29 @@ For illustration purposes in this document, we're using a two-node cluster with
 1. Access first node VM with VMware Remote Console.
        1. Verify virtual machine network configuration and ensure it can reach on-premises and Azure resources. 
        1. Open Failover Cluster Manager and verify cluster services.
-
-        :::image type="content" source="media/sql-server-hybrid-benefit/sqlfci-3.png" alt-text="Diagram showing offline state of of failover cluster on SQL server for  Azure VMware Solution." border="false":::
+       :::image type="content" source="media/sql-server-hybrid-benefit/sqlfci-3.png" alt-text="Cluster summary in Failover Cluster Manager." border="false":::
 
 1. Power on second node virtual machine.
 1. Access the second node VM with VMware Remote Console.
    1. Verify that Windows Server can see the storage.
    1. In Failover Cluster Manager review that the second node appears as Online status.
 
-    :::image type="content" source="media/sql-server-hybrid-benefit/sqlfci-4.png" alt-text="Diagram showing offline state of failover cluster on SQL server for  Azure VMware Solution." border="false":::
+    :::image type="content" source="media/sql-server-hybrid-benefit/sqlfci-4.png" alt-text="Cluster node status in Failover Cluster Manager." border="false":::
 
 1. Using SQL Server Management Studio connect to the SQL Server cluster resource network name.
         Check the database is online and accessible.
-        :::image type="content" source="media/sql-server-hybrid-benefit/sqlfci-5.png" alt-text="Diagram showing offline state of failover cluster on SQL server for  Azure VMware Solution." border="false":::
+        :::image type="content" source="media/sql-server-hybrid-benefit/sqlfci-5.png" alt-text="SQL Server Management Studio connection verification to the migrated cluster instance database."" border="false":::
 
-1. Finally check connectivity to SQL from other systems and applications in your infrastructure and verify that all applications using the database(s) can still access it.
-
-During the process, you'll create placement policies that can recreate the Affinity or Anti-Affinity rules previously present on-premises. For details about placement policies, see [Create a placement policy in Azure VMware Solution](https://learn.microsoft.com/azure/azure-vmware/create-placement-policy). 
+1. Finally check connectivity to SQL from other systems and applications in your infrastructure and verify that all applications using the database(s) can still access it. 
 
 ## Next steps
 
-- [Enable SQL Azure hybrid benefit for Azure VMware Solution](enable-sql-azure-hybrid-benefit.md). 
-- [Create a placement policy in Azure VMware Solution](create-placement-policy.md)  
-- [Windows Server Failover Clustering Documentation](./windows-server/failover-clustering/failover-clustering-overview)
-- [Microsoft SQL Server 2019 Documentation](./sql/sql-server/?view=sql-server-ver15)
+- [Enable SQL Azure hybrid benefit for Azure VMware Solution](https://learn.microsoft.com/azure/azure-vmware/enable-sql-azure-hybrid-benefit). 
+- [Create a placement policy in Azure VMware Solution](https://learn.microsoft.com/azure/azure-vmware/create-placement-policy)  
+- [Windows Server Failover Clustering Documentation](https://learn.microsoft.com/windows-server/failover-clustering/failover-clustering-overview)
+- [Microsoft SQL Server 2019 Documentation](https://learn.microsoft.com/sql/sql-server/?view=sql-server-ver15)
 - [Microsoft SQL Server 2022 Documentation](https://learn.microsoft.com/sql/sql-server/?view=sql-server-ver16)
-- [Windows Server Technical Documentation](https://learn.microsoft.com/windows-server/)
+- [Windows Server Technical Documentation](https://learn.microsoft.com/en-us/windows-server/)
 - [Planning Highly Available, Mission Critical SQL Server Deployments with VMware vSphere](https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/solutions/vmware-vsphere-highly-available-mission-critical-sql-server-deployments.pdf)
 - [Microsoft SQL Server on VMware vSphere Availability and Recovery Options](https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/solutions/sql-server-on-vmware-availability-and-recovery-options.pdf)
 - [VMware KB 100 2951 – Tips for configuring Microsoft SQL Server in a virtual machine](https://kb.vmware.com/s/article/1002951)