Skip to content

Commit d510ef3

Browse files
committed
Minor edits
1 parent fb64b91 commit d510ef3

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

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

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -3,13 +3,13 @@ title: Migrate SQL Server failover cluster to Azure VMware Solution
33
description: Learn how to migrate SQL Server failover cluster to Azure VMware Solution
44
ms.topic: how-to
55
ms.service: azure-vmware
6-
ms.date: 3/7/2023
6+
ms.date: 3/15/2023
77
ms.custom: engagement-fy23
88
---
99

1010
# Migrate SQL Server failover cluster to Azure VMware Solution
1111

12-
In this article, you learn how to migrate a Microsoft SQL Server Failover Cluster Instance to Azure VMware Solution. Currently Azure VMware Solution service doesn't support VMware Hybrid Linked Mode to connect an on-premises vCenter Server with one running in Azure VMware Solution. Due to this constraint, the process requires the use of VMware HCX for the migration. Review the [Install and activate VMware HCX in Azure VMware Solution](https://learn.microsoft.com/en-us/azure/azure-vmware/install-vmware-hcx) article for more details about HCX configuration procedure.
12+
In this article, you learn how to migrate a Microsoft SQL Server Failover Cluster Instance to Azure VMware Solution. Currently Azure VMware Solution service doesn't support VMware Hybrid Linked Mode to connect an on-premises vCenter Server with one running in Azure VMware Solution. Due to this constraint, the process requires the use of VMware HCX for the migration. For more details about configuring HCX, see [Install and activate VMware HCX in Azure VMware Solution](install-vmware-hcx).
1313

1414
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.
1515

@@ -25,8 +25,8 @@ VMware HCX doesn't support migrating virtual machines with SCSI controllers in p
2525
- Take a full backup of the database(s) being executed in the cluster.
2626
- Take a full backup of the cluster virtual machines.
2727
- Remove all cluster node VMs from any DRS Group and rules they're part of.
28-
- 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.
29-
- 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.
28+
- VMware HCX must be configured between your on-premises datacenter and the Azure VMware Solution private cloud that will run the migrated workloads. For more details about installing VMware HCX, see [Azure VMware Solution documentation](install-vmware-hcx).
29+
- Ensure that all the network segments in use by the Microsoft SQL Server are extended into your Azure VMware Solution private cloud. To verify this step, see [Configure VMware HCX network extension](configure-hcx-network-extension).
3030

3131
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.
3232

@@ -117,20 +117,20 @@ For illustration purposes in this document, we're using a two-node cluster with
117117

118118
:::image type="content" source="media/sql-server-hybrid-benefit/sqlfci-4.png" alt-text="Cluster node status in Failover Cluster Manager." border="false":::
119119

120-
1. Using SQL Server Management Studio connect to the SQL Server cluster resource network name.
121-
Check the database is online and accessible.
120+
1. Using SQL Server Management Studio connect to the SQL Server cluster resource network name. Check the database is online and accessible.
121+
122122
:::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":::
123123

124124
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.
125125

126126
## Next steps
127127

128-
- [Enable SQL Azure hybrid benefit for Azure VMware Solution](https://learn.microsoft.com/azure/azure-vmware/enable-sql-azure-hybrid-benefit).
129-
- [Create a placement policy in Azure VMware Solution](https://learn.microsoft.com/azure/azure-vmware/create-placement-policy)
128+
- [Enable SQL Azure hybrid benefit for Azure VMware Solution](enable-sql-azure-hybrid-benefit.md).
129+
- [Create a placement policy in Azure VMware Solution](create-placement-policy.md)
130130
- [Windows Server Failover Clustering Documentation](https://learn.microsoft.com/windows-server/failover-clustering/failover-clustering-overview)
131131
- [Microsoft SQL Server 2019 Documentation](https://learn.microsoft.com/sql/sql-server/?view=sql-server-ver15)
132132
- [Microsoft SQL Server 2022 Documentation](https://learn.microsoft.com/sql/sql-server/?view=sql-server-ver16)
133-
- [Windows Server Technical Documentation](https://learn.microsoft.com/en-us/windows-server/)
133+
- [Windows Server Technical Documentation](https://learn.microsoft.com/windows-server/)
134134
- [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)
135135
- [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)
136136
- [VMware KB 100 2951 – Tips for configuring Microsoft SQL Server in a virtual machine](https://kb.vmware.com/s/article/1002951)

0 commit comments

Comments
 (0)