Skip to content

Commit 8a99ad3

Browse files
dstagnoldstagnol
authored andcommitted
adding secnumcloud guide + proofread
1 parent a066341 commit 8a99ad3

File tree

6 files changed

+942
-81
lines changed

6 files changed

+942
-81
lines changed

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/vmware_migration_zerto/guide.en-gb.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Move2Cloud - Migrate VMware workloads to OVHcloud Hosted Private Cloud with Zerto
33
excerpt: "Learn how to migrate your on-premises VMware workloads to an OVHcloud Hosted Private Cloud environment using Zerto Virtual Replication."
4-
updated: 2025-07-07
4+
updated: 2025-07-08
55
---
66

77
## Objective
@@ -28,6 +28,7 @@ Before you begin, make sure you have:
2828
>[!warning]
2929
> As of May 2025, **Zerto does not support replication of virtual machines with VMEncrypt enabled**.
3030
> vSAN’s encryption at rest is supported. You can also encrypt your VMs after migration is complete.
31+
3132
## In practice
3233

3334
![Move2CloudZerto](images/Move2Cloud-Zerto.png){.thumbnail}
@@ -214,12 +215,10 @@ If your authentication is based on Active Directory, deploy a replica domain con
214215

215216
You can also establish secure communication between the on-prem AD and the tenant to avoid duplicating identities.
216217

217-
## Step 7: Install Zerto in the OVHcloud tenant
218+
## Step 7: Install and activate Zerto in the OVHcloud tenant
218219

219220
Zerto is installed and managed per site. On the OVHcloud side, the components are deployed automatically when you activate Zerto.
220221

221-
### Step 7.1: Activate Zerto on the tenant
222-
223222
In your `Hosted Private Cloud`{.action} interface:
224223

225224
1. Go to `Disaster Recovery`{.action}
@@ -245,7 +244,7 @@ The main components are:
245244
- ZVM: Installed on a Windows Server with vSphere access
246245
- ZVRAs: Deployed on each ESXi host hosting protected VMs
247246

248-
Ensure that:
247+
Make sure that:
249248

250249
- TCP ports 9071, 9081 are open between ZVMs
251250
- TCP ports 4007, 4008 are open between ZVRAs

0 commit comments

Comments
 (0)