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: pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_migration_use-cases/guide.de-de.md
+16-4Lines changed: 16 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "VMware Cloud Director - Migrate from VMware vSphere on OVHcloud"
3
3
excerpt: "Find out how to prepare a migration from managed VMware vSphere on OVHcloud to a solution based on a managed VMware Cloud Director (VCD) on OVHcloud environnement"
4
-
updated: 2025-04-23
4
+
updated: 2025-04-28
5
5
---
6
6
7
7
> [!primary]
@@ -32,6 +32,18 @@ This hot migration will minimize disruptions to your public or private networks.
32
32
33
33
Your virtual machines will remain operational during the migration, with no downtime. However, there is a risk that some network packets will be lost during vMotion.
34
34
35
+
> [!warning]
36
+
> **Network availability during migration**
37
+
>
38
+
> During the migration, your virtual machines (VMs) are moved using vMotion.
39
+
> Depending on your network topology, some VMs may temporarily lose connectivity:
40
+
>
41
+
> -**Public network (VMNetwork)**: no impact, as the public network is extended to the new infrastructure.
42
+
> -**Private network without inter-VM communication**: no impact.
43
+
> -**Private network with inter-VM communication**: possible brief downtime between VMs during the migration phase, as encapsulation technology changes from VLAN/VXLAN to Geneve.
44
+
>
45
+
> We recommend that you plan accordingly and monitor your environment during the migration.
46
+
35
47
This migration should be done with no noticeable impact for most applications, but we recommend that you monitor them closely throughout the process.
36
48
37
49
As a reminder, if you decide to switch to the managed VCD on OVHcloud offer, the new prices will not be applied to your existing servers/hosts. We will cover the increase of licensing prices until the migration is complete.
@@ -53,11 +65,11 @@ Migrations will be carried out in 4 waves, from november 2024, depending on the
53
65
54
66
The planned schedule, which is compatible with these environments during the migration, is as follows:
55
67
56
-
|**Waves** |**Dates**|**Target<br/>Offers**|**NSX**|**vRack**|**Microsoft<br/>(SPLA)**|**Summary of migration compatible environments**|
68
+
|**Waves** |**From**|**Target<br/>Offers**|**NSX**|**vRack**|**Microsoft<br/>(SPLA)**|**Summary of migration compatible environments**|
|`Wave 1`|**January 2025<br/>February 2025**|`Standard`| ❌ | ❌ | ❌ | - **Without** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **Without** NSX<br/>- **Without** High performance storage (vSAN) |
59
-
|`Wave 2`|**March 2025**|`Standard`| ❌ | ❌ | ✅ | - **With** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **Without** NSX<br/>- **Without** High performance storage (vSAN) |
60
-
|`Wave 3`|**April 2025**|`Advanced`| ✅ |✅|✅| - **With** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **With** NSX + vRack support<br/>- **Without** High performance storage (vSAN) |
71
+
|`Wave 2`|**Mid-May 2025**|`Standard`| ❌ | ❌ | ✅ | - **With** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **Without** NSX<br/>- **Without** High performance storage (vSAN) |
72
+
|`Wave 3`|**Mid-June 2025**|`Advanced`| ✅ |❌|❌| - **With** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **Without** NSX<br/>- **Without** High performance storage (vSAN) |
61
73
|`Wave 4`|**May 2025**|`Premium`| ✅ | ✅ | ✅ | - **With** Microsoft Windows license (SPLA) provided by OVHcloud<br/>- **With** NSX + vRack support<br/>- **With** High performance storage (vSAN) |
62
74
63
75
During this process, your data will remain unchanged, except for vSAN Storage. Your IP addresses will also remain unchanged.
Copy file name to clipboardExpand all lines: pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_migration_use-cases/guide.en-asia.md
+16-4Lines changed: 16 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "VMware Cloud Director - Migrate from VMware vSphere on OVHcloud"
3
3
excerpt: "Find out how to prepare a migration from managed VMware vSphere on OVHcloud to a solution based on a managed VMware Cloud Director (VCD) on OVHcloud environnement"
4
-
updated: 2025-04-23
4
+
updated: 2025-04-28
5
5
---
6
6
7
7
> [!primary]
@@ -32,6 +32,18 @@ This hot migration will minimize disruptions to your public or private networks.
32
32
33
33
Your virtual machines will remain operational during the migration, with no downtime. However, there is a risk that some network packets will be lost during vMotion.
34
34
35
+
> [!warning]
36
+
> **Network availability during migration**
37
+
>
38
+
> During the migration, your virtual machines (VMs) are moved using vMotion.
39
+
> Depending on your network topology, some VMs may temporarily lose connectivity:
40
+
>
41
+
> -**Public network (VMNetwork)**: no impact, as the public network is extended to the new infrastructure.
42
+
> -**Private network without inter-VM communication**: no impact.
43
+
> -**Private network with inter-VM communication**: possible brief downtime between VMs during the migration phase, as encapsulation technology changes from VLAN/VXLAN to Geneve.
44
+
>
45
+
> We recommend that you plan accordingly and monitor your environment during the migration.
46
+
35
47
This migration should be done with no noticeable impact for most applications, but we recommend that you monitor them closely throughout the process.
36
48
37
49
As a reminder, if you decide to switch to the managed VCD on OVHcloud offer, the new prices will not be applied to your existing servers/hosts. We will cover the increase of licensing prices until the migration is complete.
@@ -53,11 +65,11 @@ Migrations will be carried out in 4 waves, from november 2024, depending on the
53
65
54
66
The planned schedule, which is compatible with these environments during the migration, is as follows:
55
67
56
-
|**Waves** |**Dates**|**Target<br/>Offers**|**NSX**|**vRack**|**Microsoft<br/>(SPLA)**|**Summary of migration compatible environments**|
68
+
|**Waves** |**From**|**Target<br/>Offers**|**NSX**|**vRack**|**Microsoft<br/>(SPLA)**|**Summary of migration compatible environments**|
|`Wave 1`|**January 2025<br/>February 2025**|`Standard`| ❌ | ❌ | ❌ | - **Without** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **Without** NSX<br/>- **Without** High performance storage (vSAN) |
59
-
|`Wave 2`|**March 2025**|`Standard`| ❌ | ❌ | ✅ | - **With** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **Without** NSX<br/>- **Without** High performance storage (vSAN) |
60
-
|`Wave 3`|**April 2025**|`Advanced`| ✅ |✅|✅| - **With** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **With** NSX + vRack support<br/>- **Without** High performance storage (vSAN) |
71
+
|`Wave 2`|**Mid-May 2025**|`Standard`| ❌ | ❌ | ✅ | - **With** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **Without** NSX<br/>- **Without** High performance storage (vSAN) |
72
+
|`Wave 3`|**Mid-June 2025**|`Advanced`| ✅ |❌|❌| - **With** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **Without** NSX<br/>- **Without** High performance storage (vSAN) |
61
73
|`Wave 4`|**May 2025**|`Premium`| ✅ | ✅ | ✅ | - **With** Microsoft Windows license (SPLA) provided by OVHcloud<br/>- **With** NSX + vRack support<br/>- **With** High performance storage (vSAN) |
62
74
63
75
During this process, your data will remain unchanged, except for vSAN Storage. Your IP addresses will also remain unchanged.
Copy file name to clipboardExpand all lines: pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_migration_use-cases/guide.en-au.md
+16-4Lines changed: 16 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "VMware Cloud Director - Migrate from VMware vSphere on OVHcloud"
3
3
excerpt: "Find out how to prepare a migration from managed VMware vSphere on OVHcloud to a solution based on a managed VMware Cloud Director (VCD) on OVHcloud environnement"
4
-
updated: 2025-04-23
4
+
updated: 2025-04-28
5
5
---
6
6
7
7
> [!primary]
@@ -32,6 +32,18 @@ This hot migration will minimize disruptions to your public or private networks.
32
32
33
33
Your virtual machines will remain operational during the migration, with no downtime. However, there is a risk that some network packets will be lost during vMotion.
34
34
35
+
> [!warning]
36
+
> **Network availability during migration**
37
+
>
38
+
> During the migration, your virtual machines (VMs) are moved using vMotion.
39
+
> Depending on your network topology, some VMs may temporarily lose connectivity:
40
+
>
41
+
> -**Public network (VMNetwork)**: no impact, as the public network is extended to the new infrastructure.
42
+
> -**Private network without inter-VM communication**: no impact.
43
+
> -**Private network with inter-VM communication**: possible brief downtime between VMs during the migration phase, as encapsulation technology changes from VLAN/VXLAN to Geneve.
44
+
>
45
+
> We recommend that you plan accordingly and monitor your environment during the migration.
46
+
35
47
This migration should be done with no noticeable impact for most applications, but we recommend that you monitor them closely throughout the process.
36
48
37
49
As a reminder, if you decide to switch to the managed VCD on OVHcloud offer, the new prices will not be applied to your existing servers/hosts. We will cover the increase of licensing prices until the migration is complete.
@@ -53,11 +65,11 @@ Migrations will be carried out in 4 waves, from november 2024, depending on the
53
65
54
66
The planned schedule, which is compatible with these environments during the migration, is as follows:
55
67
56
-
|**Waves** |**Dates**|**Target<br/>Offers**|**NSX**|**vRack**|**Microsoft<br/>(SPLA)**|**Summary of migration compatible environments**|
68
+
|**Waves** |**From**|**Target<br/>Offers**|**NSX**|**vRack**|**Microsoft<br/>(SPLA)**|**Summary of migration compatible environments**|
|`Wave 1`|**January 2025<br/>February 2025**|`Standard`| ❌ | ❌ | ❌ | - **Without** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **Without** NSX<br/>- **Without** High performance storage (vSAN) |
59
-
|`Wave 2`|**March 2025**|`Standard`| ❌ | ❌ | ✅ | - **With** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **Without** NSX<br/>- **Without** High performance storage (vSAN) |
60
-
|`Wave 3`|**April 2025**|`Advanced`| ✅ |✅|✅| - **With** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **With** NSX + vRack support<br/>- **Without** High performance storage (vSAN) |
71
+
|`Wave 2`|**Mid-May 2025**|`Standard`| ❌ | ❌ | ✅ | - **With** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **Without** NSX<br/>- **Without** High performance storage (vSAN) |
72
+
|`Wave 3`|**Mid-June 2025**|`Advanced`| ✅ |❌|❌| - **With** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **Without** NSX<br/>- **Without** High performance storage (vSAN) |
61
73
|`Wave 4`|**May 2025**|`Premium`| ✅ | ✅ | ✅ | - **With** Microsoft Windows license (SPLA) provided by OVHcloud<br/>- **With** NSX + vRack support<br/>- **With** High performance storage (vSAN) |
62
74
63
75
During this process, your data will remain unchanged, except for vSAN Storage. Your IP addresses will also remain unchanged.
Copy file name to clipboardExpand all lines: pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vcd_migration_use-cases/guide.en-ca.md
+16-4Lines changed: 16 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: "VMware Cloud Director - Migrate from VMware vSphere on OVHcloud"
3
3
excerpt: "Find out how to prepare a migration from managed VMware vSphere on OVHcloud to a solution based on a managed VMware Cloud Director (VCD) on OVHcloud environnement"
4
-
updated: 2025-04-23
4
+
updated: 2025-04-28
5
5
---
6
6
7
7
> [!primary]
@@ -32,6 +32,18 @@ This hot migration will minimize disruptions to your public or private networks.
32
32
33
33
Your virtual machines will remain operational during the migration, with no downtime. However, there is a risk that some network packets will be lost during vMotion.
34
34
35
+
> [!warning]
36
+
> **Network availability during migration**
37
+
>
38
+
> During the migration, your virtual machines (VMs) are moved using vMotion.
39
+
> Depending on your network topology, some VMs may temporarily lose connectivity:
40
+
>
41
+
> -**Public network (VMNetwork)**: no impact, as the public network is extended to the new infrastructure.
42
+
> -**Private network without inter-VM communication**: no impact.
43
+
> -**Private network with inter-VM communication**: possible brief downtime between VMs during the migration phase, as encapsulation technology changes from VLAN/VXLAN to Geneve.
44
+
>
45
+
> We recommend that you plan accordingly and monitor your environment during the migration.
46
+
35
47
This migration should be done with no noticeable impact for most applications, but we recommend that you monitor them closely throughout the process.
36
48
37
49
As a reminder, if you decide to switch to the managed VCD on OVHcloud offer, the new prices will not be applied to your existing servers/hosts. We will cover the increase of licensing prices until the migration is complete.
@@ -53,11 +65,11 @@ Migrations will be carried out in 4 waves, from november 2024, depending on the
53
65
54
66
The planned schedule, which is compatible with these environments during the migration, is as follows:
55
67
56
-
|**Waves** |**Dates**|**Target<br/>Offers**|**NSX**|**vRack**|**Microsoft<br/>(SPLA)**|**Summary of migration compatible environments**|
68
+
|**Waves** |**From**|**Target<br/>Offers**|**NSX**|**vRack**|**Microsoft<br/>(SPLA)**|**Summary of migration compatible environments**|
|`Wave 1`|**January 2025<br/>February 2025**|`Standard`| ❌ | ❌ | ❌ | - **Without** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **Without** NSX<br/>- **Without** High performance storage (vSAN) |
59
-
|`Wave 2`|**March 2025**|`Standard`| ❌ | ❌ | ✅ | - **With** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **Without** NSX<br/>- **Without** High performance storage (vSAN) |
60
-
|`Wave 3`|**April 2025**|`Advanced`| ✅ |✅|✅| - **With** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **With** NSX + vRack support<br/>- **Without** High performance storage (vSAN) |
71
+
|`Wave 2`|**Mid-May 2025**|`Standard`| ❌ | ❌ | ✅ | - **With** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **Without** NSX<br/>- **Without** High performance storage (vSAN) |
72
+
|`Wave 3`|**Mid-June 2025**|`Advanced`| ✅ |❌|❌| - **With** Microsoft Windows VM license (SPLA) provided by OVHcloud<br/>- **Without** NSX<br/>- **Without** High performance storage (vSAN) |
61
73
|`Wave 4`|**May 2025**|`Premium`| ✅ | ✅ | ✅ | - **With** Microsoft Windows license (SPLA) provided by OVHcloud<br/>- **With** NSX + vRack support<br/>- **With** High performance storage (vSAN) |
62
74
63
75
During this process, your data will remain unchanged, except for vSAN Storage. Your IP addresses will also remain unchanged.
0 commit comments