You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-vmware/migrate-sql-server-always-on-availability-group.md
+14-8Lines changed: 14 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,24 +29,30 @@ These are the prerequisites to migrating your SQL Server instance to Azure VMwar
29
29
- VMware HCX must be configured between your on-premises datacenter and the Azure VMware Solution private cloud that runs the migrated workloads. For more information on how to configure HCX, see [Azure VMware Solution documentation](install-vmware-hcx.md).
30
30
- Ensure that all the network segments in use by SQL Server and workloads using it are extended into your Azure VMware Solution private cloud. To verify this step, see [Configure VMware HCX network extension](configure-hcx-network-extension.md).
31
31
32
-
VMware HCX over VPN is supported in Azure VMware Solution for workload migration.
33
-
However, due to the size of database workloads, VMware HCX over VPN is not recommended for Microsoft SQL Server Always On FCI or AG migrations for production workloads.
34
-
ExpressRoute connectivity is recommended as more performant and reliable.
35
-
For Microsoft SQL Server standalone and non-production workloads this may be suitable, depending upon the size of the database, to migrate.
32
+
Either VMware HCX over VPN or ExpressRoute connectivity can be used as the networking configuration for the migration.
33
+
VMWare HCX over VPN, due to its limited bandwidth, is typically suited for workloads that can sustain longer periods of downtime (such as non-production environments).
34
+
35
+
For any of the following scenarios, ExpressRoute connectivity is recommended for a migration:
36
+
37
+
- Production environments
38
+
- Workloads with large database sizes
39
+
- Any case where there is a need to minimize downtime for migration the ExpressRoute connectivity is recommended for the migration.
40
+
41
+
Further downtime considerations are discussed in the next section.
36
42
37
43
38
44
## Downtime considerations
39
45
40
46
Downtime during a migration depends upon the size of the database to be migrated and the speed of the private network connection to Azure cloud.
41
47
While SQL Server Availablity Group migrations can be executed with minimal solution downtime, it is optimal to conduct the migration during off-peak hours within a pre-approved change window.
42
48
43
-
The table below indicates the estimated downtime for migraton of each SQL Server topology.
49
+
The following table indicates the estimated downtime for migration of each SQL Server topology.
44
50
45
51
|**Scenario**|**Downtime expected**|**Notes**|
46
52
|:---|:-----|:-----|
47
-
|**Standalone instance**| Low |Migrate with VMware vMotion, the database is available during migration, but it is not recommended to commit any critical data during it. |
48
-
|**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. |
49
-
|**Always On Failover Cluster Instance**| High | All nodes of the cluster are shutdown and migrated using VMware HCX Cold Migration. Downtime duration depends upon database size and private network speed to Azure cloud. |
53
+
|**Standalone instance**| Low |Migration is done using VMware vMotion, the database is available during migration time, but it isn't recommended to commit any critical data during it. |
54
+
|**Always On SQL Server 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. |
55
+
|**Always On SQL Server Failover Cluster Instance**| High | All nodes of the cluster are shutdown and migrated using VMware HCX Cold Migration. Downtime duration depends upon database size and private network speed to Azure cloud. |
50
56
51
57
## Windows Server Failover Cluster quorum considerations
Copy file name to clipboardExpand all lines: articles/azure-vmware/migrate-sql-server-failover-cluster.md
+14-8Lines changed: 14 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,24 +40,30 @@ The on-premises source infrastructure was VMware vSphere 7.0 Update 3 and VMware
40
40
- VMware HCX must be configured between your on-premises datacenter and the Azure VMware Solution private cloud that runs the migrated workloads. For more details about installing VMware HCX, see [Azure VMware Solution documentation](install-vmware-hcx.md).
41
41
- Ensure that all the network segments in use by SQL Server and workloads using it are extended into your Azure VMware Solution private cloud. To verify this step, see [Configure VMware HCX network extension](configure-hcx-network-extension.md).
42
42
43
-
VMware HCX over VPN is supported in Azure VMware Solution for workload migration.
44
-
However, due to the size of database workloads it isn't recommended for Microsoft SQL Server Failover Cluster Instance and Microsoft SQL Server Always On migrations, especially for production workloads.
45
-
ExpressRoute connectivity is recommended as more performant and reliable.
46
-
For Microsoft SQL Server Standalone and non-production workloads this can be suitable, depending upon the size of the database, to migrate.
43
+
Either VMware HCX over VPN or ExpressRoute connectivity can be used as the networking configuration for the migration.
44
+
VMWare HCX over VPN, due to its limited bandwidth, is typically suited for workloads that can sustain longer periods of downtime (such as non-production environments).
45
+
46
+
For any of the following scenarios, ExpressRoute connectivity is recommended for a migration:
47
+
48
+
- Production environments
49
+
- Workloads with large database sizes
50
+
- Any case where there is a need to minimize downtime for migration the ExpressRoute connectivity is recommended for the migration.
51
+
52
+
Further downtime considerations are discussed in the next section.
47
53
48
54
49
55
## Downtime considerations
50
56
51
57
Downtime during a migration depends on the size of the database to be migrated and the speed of the private network connection to Azure cloud.
52
58
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.
53
59
54
-
The table below indicates the downtime for each Microsoft SQL Server topology.
60
+
The following table indicates the estimated downtime for migration of each SQL Server topology.
55
61
56
62
|**Scenario**|**Downtime expected**|**Notes**|
57
63
|:---|:-----|:-----|
58
-
|**Standalone instance**| Low | Migration will be done using vMotion, the database will be available during migration time, but it isn't recommended to commit any critical data during it. |
59
-
|**Always-On SQL Server 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. |
60
-
|**Always On SQL Server 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. |
64
+
|**Standalone instance**| Low | Migration is done using VMware vMotion, the database is available during migration time, but it isn't recommended to commit any critical data during it. |
65
+
|**AlwaysOn SQL Server 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. |
66
+
|**Always On SQL Server Failover Cluster Instance**| High | All nodes of the cluster are shutdown and migrated using VMware HCX Cold Migration. Downtime duration depends upon database size and private network speed to Azure cloud. |
61
67
62
68
## Windows Server Failover Cluster quorum considerations
Copy file name to clipboardExpand all lines: articles/azure-vmware/migrate-sql-server-standalone-cluster.md
+7-4Lines changed: 7 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,11 +42,14 @@ This scenario was validated using the following editions and configurations:
42
42
- Configure VMware HCX between your on-premises datacenter and the Azure VMware Solution private cloud that runs the migrated workloads. For more information about configuring VMware HCX, see [Azure VMware Solution documentation](install-vmware-hcx.md).
43
43
- Ensure that all the network segments in use by the SQL Server and workloads using it are extended into your Azure VMware Solution private cloud. To verify this step in the process, see [Configure VMware HCX network extension](configure-hcx-network-extension.md).
44
44
45
-
Either VMware HCX over VPN or ExpressRoute connectivity can be used as the networking configuration for the migration.
45
+
Either VMware HCX over VPN or ExpressRoute connectivity can be used as the networking configuration for the migration.
46
+
VMWare HCX over VPN, due to its limited bandwidth, is typically suited for workloads that can sustain longer periods of downtime (such as non-production environments).
46
47
47
-
With VMWare HCX over VPN, due to its limited bandwidth it is typically suited for workloads that can sustain longer periods of downtime (such as non-production environments).
48
+
For any of the following scenarios, ExpressRoute connectivity is recommended for a migration:
48
49
49
-
For production environments, or workloads with large database sizes or where there is a need to minimize downtime the ExpressRoute connectivity is recommended for the migration.
50
+
- Production environments
51
+
- Workloads with large database sizes
52
+
- Any case where there is a need to minimize downtime for migration the ExpressRoute connectivity is recommended for the migration.
50
53
51
54
Further downtime considerations are discussed in the next section.
52
55
@@ -55,7 +58,7 @@ Further downtime considerations are discussed in the next section.
55
58
Downtime during a migration depends on the size of the database to be migrated and the speed of the private network connection to Azure cloud.
56
59
Migration of a SQL Server standalone instance using the VMware HCX vMotion mechanism is intended to minimize the solution downtime, however we still recommend the migration take place during off-peak hours within an pre-approved change window.
57
60
58
-
This table indicates the estimated downtime for migration of each SQL Server topology.
61
+
The following table indicates the estimated downtime for migration of each SQL Server topology.
0 commit comments