Skip to content

Commit 174ae0d

Browse files
benchbzhbenchbzh
authored
Merge pull request #7735 from ovh/ds-vmware-secnumcloud
Guide creation - Migrating VMware Workloads to OVHcloud SecNumCloud with Veeam Replication
2 parents 381d280 + efc3d19 commit 174ae0d

File tree

18 files changed

+2459
-0
lines changed

18 files changed

+2459
-0
lines changed

‎pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vmware_migration_veeam_secnumcloud/guide.de-de.md

Lines changed: 164 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,164 @@
1+
---
2+
title: Move2Cloud - Migrating VMware Workloads to OVHcloud SecNumCloud with Veeam Replication
3+
excerpt: Learn how to migrate your on-prem VMware workloads to an OVHcloud Hosted Private Cloud SecNumCloud environment using Veeam Replication
4+
updated: 2025-04-09
5+
---
6+
7+
## Objective
8+
9+
This guide explains how to migrate your on-premises VMware workloads to an **OVHcloud Hosted Private Cloud (HPC) SecNumCloud environment** using **Veeam Replication**.
10+
11+
>[!primary]
12+
> **This guide applies to Hosted Private Cloud environments qualified for SecNumCloud (SNC).**
13+
> Some features such as OVHcloud IAM are not available in SNC environments.
14+
15+
## Requirements
16+
17+
Before getting started, make sure you have:
18+
19+
- An up-to-date inventory of VMs with FQDNs, IP addresses, OS versions, and dependencies.
20+
- A plan to group VMs into migration batches (per application stack).
21+
- A complete list of subnets and VLAN IDs for the target HPC.
22+
- Correctly sized compute and storage resources (hosts, datastores, vSAN).
23+
- A configured VPN or OVHcloud Connect link (non-NAT).
24+
- Access to [Veeam Backup & Replication](https://www.veeam.com/downloads.html?ad=top-sub-menu).
25+
- A second OVHcloud account (NIC) for ordering the Veeam Enterprise Service (required in SNC environments).
26+
27+
## Instructions
28+
29+
![migration](images/secnumcloud.png){.thumbnail}
30+
31+
### Step 1: Make an inventory of source VMs and network configuration
32+
33+
- List all source VMs with their FQDNs, IPs, and OS versions.
34+
- Group VMs by application dependency (web/app/db) to define migration batches.
35+
- List subnets and VLANs. OVHcloud vRack supports over 4000 VLANs, allowing you to keep your original IP plan.
36+
37+
### Step 2: Size your HPC resources
38+
39+
- Define your core, RAM, and storage needs based on your current consolidation ratio (e.g., vCPU/pCPU).
40+
- Choose between **NFS datastores** and **vSAN** depending on IOPS requirements.
41+
- If using NSX-T:
42+
- Plan segments and overlays.
43+
- Assess north/south traffic.
44+
- Decide on virtual firewalls (Stormshield, FortiVM, Palo Alto VM-Series).
45+
- For internet-facing services, request additional public IPs or use the [BYOIP feature](/links/network/byoip).
46+
47+
### Step 3: Authorize vCenter access via IP whitelisting
48+
49+
vCenter access is restricted by default in OVHcloud environments. To allow access:
50+
51+
- Follow the [dedicated guide](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/autoriser_des_ip_a_se_connecter_au_vcenter) to whitelist the IP addresses of your source infrastructure and Veeam components.
52+
- To enable access without triggering 2FA on Veeam components, refer to the *Application access permission* section of [this guide](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/utilisation_2FA).
53+
54+
### Step 4: Configure roles and permissions
55+
56+
As IAM is not available in SecNumCloud environments, you need to define and manage user access directly within vSphere.
57+
58+
To learn how to set up local users and activate two-factor authentication, follow [this documentation](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/interface-secure).
59+
60+
### Step 5: Build your target network
61+
62+
Plan your network architecture in advance:
63+
64+
- Create a **flow matrix** showing allowed traffic between VMs by VLAN and protocol.
65+
- Use the preconfigured **distributed vSwitches (dVS)** and VLANs provided by OVHcloud.
66+
- If you are using NSX-T, you’ll need to configure Tier-0/Tier-1 gateways and define distributed firewall rules.
67+
68+
To get started with NSX-T in your HPC, refer to the [NSX first steps guide](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/nsx-01-first-steps).
69+
70+
### Step 6: Deploy core services
71+
72+
To reduce unnecessary traffic between your environments, deploy essential services directly inside the target Hosted Private Cloud:
73+
74+
- **NTP**: Use `ntp.ovh.net`
75+
- **DNS**: Deploy a Domain Controller if required
76+
- **Authentication**: Set up local or hybrid authentication services
77+
78+
### Step 7: Install Veeam B&R server in OVHcloud HPC
79+
80+
You must deploy a Veeam Backup & Replication (B&R) server directly in the OVHcloud Hosted Private Cloud.
81+
82+
In SNC environments, this must be ordered from a second OVHcloud NIC.
83+
84+
For step-by-step instructions on how to install and configure Veeam in the cloud, follow [this official guide](/pages/storage_and_backup/backup_and_disaster_recovery_solutions/veeam/veeam_veeam_backup_replication).
85+
86+
### Step 8: Set up secure connectivity
87+
88+
Set up a secure tunnel between your on-premises infrastructure and the OVHcloud HPC using one of the following options:
89+
90+
- [Configure IPsec VPN with NSX](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/nsx-12-configure-ipsec)
91+
- Use a compatible third-party solution like [Stormshield](https://documentation.stormshield.eu/SNS/v4/en/Content/User_Configuration_Manual_SNS_v4/IPSec_VPN/IPSEC_VPN.htm) or [OPNsense](https://docs.opnsense.org/manual/how-tos/ipsec-s2s.html)
92+
93+
If you need higher performance and lower latency, you can optionally use [OVHcloud Connect](https://www.ovhcloud.com/en-gb/network/ovhcloud-connect/).
94+
95+
> [!warning]
96+
> SNC environments require SPNs (Security Provider Names). Learn more in [this connectivity guide](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/snc-connectivity-concepts-vpn-spn).
97+
98+
### Step 9: Deploy the Veeam proxy server on-prem
99+
100+
On your on-premises infrastructure, configure a server to act as a **Veeam proxy**. This proxy is responsible for data transfer during replication.
101+
102+
To set it up, follow this [official Veeam proxy configuration guide](https://helpcenter.veeam.com/docs/backup/vsphere/add_vmware_proxy.html?ver=120).
103+
104+
### Step 10: Create replication jobs
105+
106+
Once the cloud and proxy infrastructure is ready, go to Veeam B&R and create the replication jobs targeting the Hosted Private Cloud.
107+
108+
For guidance, follow this [Veeam job creation guide](https://helpcenter.veeam.com/docs/backup/vsphere/replica_job.html?ver=120).
109+
110+
### Step 11: Start replication
111+
112+
You can now start your replication jobs and monitor their progress from the Veeam console.
113+
114+
To manage, pause or edit jobs, refer to [this section of the Veeam documentation](https://helpcenter.veeam.com/docs/backup/vsphere/managing_replication_jobs.html?ver=120).
115+
116+
### Step 12: Test replication
117+
118+
Once the jobs are complete, it’s a good idea to run a test failover.
119+
120+
You can do this using the `Failover Now` option. For instructions, check out:
121+
122+
- [Failover guide](https://helpcenter.veeam.com/docs/backup/vsphere/failover.html?ver=120)
123+
- [Undo Failover guide](https://helpcenter.veeam.com/docs/backup/vsphere/undo_failover.html?ver=120)
124+
125+
### Step 13: Perform the final migration
126+
127+
When you're ready to switch production to the cloud, initiate a `Planned Failover` in Veeam. This step gracefully shuts down on-prem VMs, performs a last sync, and boots the VMs in your HPC.
128+
129+
For the full procedure, see the [Planned Failover guide](https://helpcenter.veeam.com/docs/backup/vsphere/planned_failover.html?ver=120).
130+
131+
### Step 14: Validate applications
132+
133+
After the failover:
134+
135+
- Check that all VMs are online and reachable
136+
- Test AD, DNS, antivirus, databases, web services, and other business-critical applications
137+
138+
### Step 15: Confirm permanent failover
139+
140+
To finalise the migration, use the `Permanent Failover` feature in Veeam.
141+
142+
For a full walkthrough, consult the [Permanent Failover guide](https://helpcenter.veeam.com/docs/backup/vsphere/permanent_failover.html?ver=120).
143+
144+
### Step 16: Move VMs to target storage
145+
146+
Now that your workloads are running in the cloud, you can optimize storage placement using **Storage vMotion**. Move VMs to appropriate datastores (NFS or vSAN) depending on performance needs.
147+
148+
Learn more in the [Storage vMotion guide](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vmware_storage_vmotion).
149+
150+
### Step 17: Create backup jobs
151+
152+
To protect your VMs long-term, configure backup jobs in Veeam that use **OVHcloud Object Storage** (S3\*-compatible).
153+
154+
Follow the steps in our [dedicated backup guide](/pages/storage_and_backup/object_storage/s3_veeam).
155+
156+
\*: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc.
157+
158+
## Go further
159+
160+
If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
161+
162+
Ask questions, give your feedback and interact directly with the team building our Hosted Private Cloud services on the dedicated [Discord](https://discord.gg/ovhcloud) channel.
163+
164+
Join our [community of users](/links/community).

‎pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vmware_migration_veeam_secnumcloud/guide.en-asia.md

Lines changed: 164 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,164 @@
1+
---
2+
title: Move2Cloud - Migrating VMware Workloads to OVHcloud SecNumCloud with Veeam Replication
3+
excerpt: Learn how to migrate your on-prem VMware workloads to an OVHcloud Hosted Private Cloud SecNumCloud environment using Veeam Replication
4+
updated: 2025-04-09
5+
---
6+
7+
## Objective
8+
9+
This guide explains how to migrate your on-premises VMware workloads to an **OVHcloud Hosted Private Cloud (HPC) SecNumCloud environment** using **Veeam Replication**.
10+
11+
>[!primary]
12+
> **This guide applies to Hosted Private Cloud environments qualified for SecNumCloud (SNC).**
13+
> Some features such as OVHcloud IAM are not available in SNC environments.
14+
15+
## Requirements
16+
17+
Before getting started, make sure you have:
18+
19+
- An up-to-date inventory of VMs with FQDNs, IP addresses, OS versions, and dependencies.
20+
- A plan to group VMs into migration batches (per application stack).
21+
- A complete list of subnets and VLAN IDs for the target HPC.
22+
- Correctly sized compute and storage resources (hosts, datastores, vSAN).
23+
- A configured VPN or OVHcloud Connect link (non-NAT).
24+
- Access to [Veeam Backup & Replication](https://www.veeam.com/downloads.html?ad=top-sub-menu).
25+
- A second OVHcloud account (NIC) for ordering the Veeam Enterprise Service (required in SNC environments).
26+
27+
## Instructions
28+
29+
![migration](images/secnumcloud.png){.thumbnail}
30+
31+
### Step 1: Make an inventory of source VMs and network configuration
32+
33+
- List all source VMs with their FQDNs, IPs, and OS versions.
34+
- Group VMs by application dependency (web/app/db) to define migration batches.
35+
- List subnets and VLANs. OVHcloud vRack supports over 4000 VLANs, allowing you to keep your original IP plan.
36+
37+
### Step 2: Size your HPC resources
38+
39+
- Define your core, RAM, and storage needs based on your current consolidation ratio (e.g., vCPU/pCPU).
40+
- Choose between **NFS datastores** and **vSAN** depending on IOPS requirements.
41+
- If using NSX-T:
42+
- Plan segments and overlays.
43+
- Assess north/south traffic.
44+
- Decide on virtual firewalls (Stormshield, FortiVM, Palo Alto VM-Series).
45+
- For internet-facing services, request additional public IPs or use the [BYOIP feature](/links/network/byoip).
46+
47+
### Step 3: Authorize vCenter access via IP whitelisting
48+
49+
vCenter access is restricted by default in OVHcloud environments. To allow access:
50+
51+
- Follow the [dedicated guide](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/autoriser_des_ip_a_se_connecter_au_vcenter) to whitelist the IP addresses of your source infrastructure and Veeam components.
52+
- To enable access without triggering 2FA on Veeam components, refer to the *Application access permission* section of [this guide](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/utilisation_2FA).
53+
54+
### Step 4: Configure roles and permissions
55+
56+
As IAM is not available in SecNumCloud environments, you need to define and manage user access directly within vSphere.
57+
58+
To learn how to set up local users and activate two-factor authentication, follow [this documentation](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/interface-secure).
59+
60+
### Step 5: Build your target network
61+
62+
Plan your network architecture in advance:
63+
64+
- Create a **flow matrix** showing allowed traffic between VMs by VLAN and protocol.
65+
- Use the preconfigured **distributed vSwitches (dVS)** and VLANs provided by OVHcloud.
66+
- If you are using NSX-T, you’ll need to configure Tier-0/Tier-1 gateways and define distributed firewall rules.
67+
68+
To get started with NSX-T in your HPC, refer to the [NSX first steps guide](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/nsx-01-first-steps).
69+
70+
### Step 6: Deploy core services
71+
72+
To reduce unnecessary traffic between your environments, deploy essential services directly inside the target Hosted Private Cloud:
73+
74+
- **NTP**: Use `ntp.ovh.net`
75+
- **DNS**: Deploy a Domain Controller if required
76+
- **Authentication**: Set up local or hybrid authentication services
77+
78+
### Step 7: Install Veeam B&R server in OVHcloud HPC
79+
80+
You must deploy a Veeam Backup & Replication (B&R) server directly in the OVHcloud Hosted Private Cloud.
81+
82+
In SNC environments, this must be ordered from a second OVHcloud NIC.
83+
84+
For step-by-step instructions on how to install and configure Veeam in the cloud, follow [this official guide](/pages/storage_and_backup/backup_and_disaster_recovery_solutions/veeam/veeam_veeam_backup_replication).
85+
86+
### Step 8: Set up secure connectivity
87+
88+
Set up a secure tunnel between your on-premises infrastructure and the OVHcloud HPC using one of the following options:
89+
90+
- [Configure IPsec VPN with NSX](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/nsx-12-configure-ipsec)
91+
- Use a compatible third-party solution like [Stormshield](https://documentation.stormshield.eu/SNS/v4/en/Content/User_Configuration_Manual_SNS_v4/IPSec_VPN/IPSEC_VPN.htm) or [OPNsense](https://docs.opnsense.org/manual/how-tos/ipsec-s2s.html)
92+
93+
If you need higher performance and lower latency, you can optionally use [OVHcloud Connect](https://www.ovhcloud.com/en-gb/network/ovhcloud-connect/).
94+
95+
> [!warning]
96+
> SNC environments require SPNs (Security Provider Names). Learn more in [this connectivity guide](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/snc-connectivity-concepts-vpn-spn).
97+
98+
### Step 9: Deploy the Veeam proxy server on-prem
99+
100+
On your on-premises infrastructure, configure a server to act as a **Veeam proxy**. This proxy is responsible for data transfer during replication.
101+
102+
To set it up, follow this [official Veeam proxy configuration guide](https://helpcenter.veeam.com/docs/backup/vsphere/add_vmware_proxy.html?ver=120).
103+
104+
### Step 10: Create replication jobs
105+
106+
Once the cloud and proxy infrastructure is ready, go to Veeam B&R and create the replication jobs targeting the Hosted Private Cloud.
107+
108+
For guidance, follow this [Veeam job creation guide](https://helpcenter.veeam.com/docs/backup/vsphere/replica_job.html?ver=120).
109+
110+
### Step 11: Start replication
111+
112+
You can now start your replication jobs and monitor their progress from the Veeam console.
113+
114+
To manage, pause or edit jobs, refer to [this section of the Veeam documentation](https://helpcenter.veeam.com/docs/backup/vsphere/managing_replication_jobs.html?ver=120).
115+
116+
### Step 12: Test replication
117+
118+
Once the jobs are complete, it’s a good idea to run a test failover.
119+
120+
You can do this using the `Failover Now` option. For instructions, check out:
121+
122+
- [Failover guide](https://helpcenter.veeam.com/docs/backup/vsphere/failover.html?ver=120)
123+
- [Undo Failover guide](https://helpcenter.veeam.com/docs/backup/vsphere/undo_failover.html?ver=120)
124+
125+
### Step 13: Perform the final migration
126+
127+
When you're ready to switch production to the cloud, initiate a `Planned Failover` in Veeam. This step gracefully shuts down on-prem VMs, performs a last sync, and boots the VMs in your HPC.
128+
129+
For the full procedure, see the [Planned Failover guide](https://helpcenter.veeam.com/docs/backup/vsphere/planned_failover.html?ver=120).
130+
131+
### Step 14: Validate applications
132+
133+
After the failover:
134+
135+
- Check that all VMs are online and reachable
136+
- Test AD, DNS, antivirus, databases, web services, and other business-critical applications
137+
138+
### Step 15: Confirm permanent failover
139+
140+
To finalise the migration, use the `Permanent Failover` feature in Veeam.
141+
142+
For a full walkthrough, consult the [Permanent Failover guide](https://helpcenter.veeam.com/docs/backup/vsphere/permanent_failover.html?ver=120).
143+
144+
### Step 16: Move VMs to target storage
145+
146+
Now that your workloads are running in the cloud, you can optimize storage placement using **Storage vMotion**. Move VMs to appropriate datastores (NFS or vSAN) depending on performance needs.
147+
148+
Learn more in the [Storage vMotion guide](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vmware_storage_vmotion).
149+
150+
### Step 17: Create backup jobs
151+
152+
To protect your VMs long-term, configure backup jobs in Veeam that use **OVHcloud Object Storage** (S3\*-compatible).
153+
154+
Follow the steps in our [dedicated backup guide](/pages/storage_and_backup/object_storage/s3_veeam).
155+
156+
\*: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc.
157+
158+
## Go further
159+
160+
If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
161+
162+
Ask questions, give your feedback and interact directly with the team building our Hosted Private Cloud services on the dedicated [Discord](https://discord.gg/ovhcloud) channel.
163+
164+
Join our [community of users](/links/community).

0 commit comments

Comments
 (0)