Merge pull request #8298 from ovh/ds-zerto-2

Zerto guides updates -  SK-2245 & SK-2246

Author: Y0Coss

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/zerto-virtual-replication-customer-to-ovhcloud/guide.de-de.md

@@ -1,12 +1,13 @@
 ---
-title: 'Using Zerto between OVHcloud and a third party platform'
-excerpt: 'Learn how to setup Zerto between your OVHcloud Private Cloud and another platform'
-updated: 2025-06-25
+title: Using Zerto between OVHcloud and a third-party platform
+excerpt: Learn how to set up Zerto between your OVHcloud Private Cloud and another platform
+updated: 2025-08-25
 ---
 
 ## Objective
 
 This guide provides an outline of how to configure a virtual private network between an OVHcloud Hosted Private Cloud and a different platform.
+
 We will use the OPNsense open-source VPN Solution as an example, and explain the simplest way to set up a VPN tunnel to the Zerto network. 
 
 Check out [Zerto between two OVHcloud datacenters](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/zerto_virtual_replication_as_a_service) for the other scenario.
@@ -19,6 +20,7 @@ Check out [Zerto between two OVHcloud datacenters](/pages/hosted_private_cloud/h
 - A Zerto platform installed on the on-premises platform
 - VRAs (Virtual Replication Appliances) on both sides that are able to connect to the counterpart on TCP ports 4007 and 4008
 - Zerto administration consoles or ZVMs (Zerto Virtual Managers) that are able to connect to the counterpart on TCP port 9071
+- A **Read Write (RW)** vCenter account is required to access and operate the Zerto interface.
 
 > [!primary]
 >
@@ -109,7 +111,7 @@ If the default values are correct:
 
 The only required parameter is the OVHcloud IPSec endpoint IP address.
 
-##### 3.1.2 Phase 1: Authentification.
+##### 3.1.2 Phase 1: Authentication.
 
 Once the default values are valid, you only need to provide the shared secret for authentication.
 
@@ -119,7 +121,7 @@ Once the default values are valid, you only need to provide the shared secret fo
 
 ![](images/image-EN-12.png){.thumbnail}
 
-Supported values for each parameters:
+Supported values for each parameter:
 
 - Encryption algorithms: AES 256 bits
 - Hash algorithms: SHA256
@@ -175,7 +177,7 @@ On OVHcloud side, the ZVM network is always a /23 network (512 IPs).
 
 Supported values are:
 
-- Protocole: ESP
+- Protocol: ESP
 - Encryption algorithm: AES 256 bits
 - Hash algorithms: SHA256
 - PFS: Off
@@ -246,7 +248,7 @@ For "Source" and "Destination", select "Single host or Network" type. The source
 
 ![](images/image-EN-28.png){.thumbnail}
 
-Destination TCP port is 9071. Click `Save`{.action} and `Apply Change`{.action}.
+Destination TCP port is 9071. Click `Save`{.action} and `Apply Changes`{.action}.
 
 #### 4.2 vRAs opening.
 
@@ -256,14 +258,14 @@ To simplify this setup, we are going to use the alias feature of OPNsense. An al
 We will define three aliases:
 
 * one for vRA IPs on the customer side
-* one for vRA IPs on the OVHCloud side
+* one for vRA IPs on the OVHcloud side
 * one for the ports
 
 You can get the OVHcloud vRAs IP from the destination Private Cloud vCenter interface.  
 
 ![](images/image-EN-29.png){.thumbnail}
 
-Let's create the OVH_VRA alias for OVHCLoud vRAs:
+Let's create the OVH_VRA alias for OVHcloud vRAs:
 
 ![](images/image-EN-30.png){.thumbnail}
 
@@ -295,7 +297,7 @@ In the dashboard, you can see the pairing is ongoing:
 
 ![](images/image-EN-36.png){.thumbnail}
 
-You will be notified when the pairing is successfull:
+You will be notified when the pairing is successful:
 
 ![](images/image-EN-37.png){.thumbnail}
 
@@ -305,6 +307,12 @@ You can check that your OVHcloud PCC is visible in the `Sites`{.action} tab.
 
 At this point, your Zerto setup is functional and you can start to create your virtual protection groups (VPGs).
 
+> [!warning]
+>
+> When enabling Zerto, a `Z-VRAH` VM may appear in your inventory.
+> This deployment is **not systematic**; it depends notably on the data volume to process.
+> If present, it is essential to the service and **must not be modified or deleted**.
+
 #### Troubleshooting
 
 If the on-premises ZVM is not able to successfully contact the OVHcloud ZVM (due to an incorrect firewall setup, for example) you will get the following message:
@@ -319,4 +327,8 @@ The most probable cause is that the OVHcloud ZVM is not authorised to contact yo
 
 ## Go further
 
-Join our community of users on <https://community.ovh.com/en/>.
+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.
+
+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.
+
+Join our [community of users](/links/community).

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/zerto-virtual-replication-customer-to-ovhcloud/guide.en-asia.md

@@ -1,12 +1,13 @@
 ---
-title: 'Using Zerto between OVHcloud and a third party platform'
-excerpt: 'Learn how to setup Zerto between your OVHcloud Private Cloud and another platform'
-updated: 2025-06-25
+title: Using Zerto between OVHcloud and a third-party platform
+excerpt: Learn how to set up Zerto between your OVHcloud Private Cloud and another platform
+updated: 2025-08-25
 ---
 
 ## Objective
 
 This guide provides an outline of how to configure a virtual private network between an OVHcloud Hosted Private Cloud and a different platform.
+
 We will use the OPNsense open-source VPN Solution as an example, and explain the simplest way to set up a VPN tunnel to the Zerto network. 
 
 Check out [Zerto between two OVHcloud datacenters](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/zerto_virtual_replication_as_a_service) for the other scenario.
@@ -19,6 +20,7 @@ Check out [Zerto between two OVHcloud datacenters](/pages/hosted_private_cloud/h
 - A Zerto platform installed on the on-premises platform
 - VRAs (Virtual Replication Appliances) on both sides that are able to connect to the counterpart on TCP ports 4007 and 4008
 - Zerto administration consoles or ZVMs (Zerto Virtual Managers) that are able to connect to the counterpart on TCP port 9071
+- A **Read Write (RW)** vCenter account is required to access and operate the Zerto interface.
 
 > [!primary]
 >
@@ -109,7 +111,7 @@ If the default values are correct:
 
 The only required parameter is the OVHcloud IPSec endpoint IP address.
 
-##### 3.1.2 Phase 1: Authentification.
+##### 3.1.2 Phase 1: Authentication.
 
 Once the default values are valid, you only need to provide the shared secret for authentication.
 
@@ -119,7 +121,7 @@ Once the default values are valid, you only need to provide the shared secret fo
 
 ![](images/image-EN-12.png){.thumbnail}
 
-Supported values for each parameters:
+Supported values for each parameter:
 
 - Encryption algorithms: AES 256 bits
 - Hash algorithms: SHA256
@@ -175,7 +177,7 @@ On OVHcloud side, the ZVM network is always a /23 network (512 IPs).
 
 Supported values are:
 
-- Protocole: ESP
+- Protocol: ESP
 - Encryption algorithm: AES 256 bits
 - Hash algorithms: SHA256
 - PFS: Off
@@ -246,7 +248,7 @@ For "Source" and "Destination", select "Single host or Network" type. The source
 
 ![](images/image-EN-28.png){.thumbnail}
 
-Destination TCP port is 9071. Click `Save`{.action} and `Apply Change`{.action}.
+Destination TCP port is 9071. Click `Save`{.action} and `Apply Changes`{.action}.
 
 #### 4.2 vRAs opening.
 
@@ -256,14 +258,14 @@ To simplify this setup, we are going to use the alias feature of OPNsense. An al
 We will define three aliases:
 
 * one for vRA IPs on the customer side
-* one for vRA IPs on the OVHCloud side
+* one for vRA IPs on the OVHcloud side
 * one for the ports
 
 You can get the OVHcloud vRAs IP from the destination Private Cloud vCenter interface.  
 
 ![](images/image-EN-29.png){.thumbnail}
 
-Let's create the OVH_VRA alias for OVHCLoud vRAs:
+Let's create the OVH_VRA alias for OVHcloud vRAs:
 
 ![](images/image-EN-30.png){.thumbnail}
 
@@ -295,7 +297,7 @@ In the dashboard, you can see the pairing is ongoing:
 
 ![](images/image-EN-36.png){.thumbnail}
 
-You will be notified when the pairing is successfull:
+You will be notified when the pairing is successful:
 
 ![](images/image-EN-37.png){.thumbnail}
 
@@ -305,6 +307,12 @@ You can check that your OVHcloud PCC is visible in the `Sites`{.action} tab.
 
 At this point, your Zerto setup is functional and you can start to create your virtual protection groups (VPGs).
 
+> [!warning]
+>
+> When enabling Zerto, a `Z-VRAH` VM may appear in your inventory.
+> This deployment is **not systematic**; it depends notably on the data volume to process.
+> If present, it is essential to the service and **must not be modified or deleted**.
+
 #### Troubleshooting
 
 If the on-premises ZVM is not able to successfully contact the OVHcloud ZVM (due to an incorrect firewall setup, for example) you will get the following message:
@@ -319,4 +327,8 @@ The most probable cause is that the OVHcloud ZVM is not authorised to contact yo
 
 ## Go further
 
-Join our community of users on <https://community.ovh.com/en/>.
+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.
+
+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.
+
+Join our [community of users](/links/community).

pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/zerto-virtual-replication-customer-to-ovhcloud/guide.en-au.md

@@ -1,12 +1,13 @@
 ---
-title: 'Using Zerto between OVHcloud and a third party platform'
-excerpt: 'Learn how to setup Zerto between your OVHcloud Private Cloud and another platform'
-updated: 2025-06-25
+title: Using Zerto between OVHcloud and a third-party platform
+excerpt: Learn how to set up Zerto between your OVHcloud Private Cloud and another platform
+updated: 2025-08-25
 ---
 
 ## Objective
 
 This guide provides an outline of how to configure a virtual private network between an OVHcloud Hosted Private Cloud and a different platform.
+
 We will use the OPNsense open-source VPN Solution as an example, and explain the simplest way to set up a VPN tunnel to the Zerto network. 
 
 Check out [Zerto between two OVHcloud datacenters](/pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/zerto_virtual_replication_as_a_service) for the other scenario.
@@ -19,6 +20,7 @@ Check out [Zerto between two OVHcloud datacenters](/pages/hosted_private_cloud/h
 - A Zerto platform installed on the on-premises platform
 - VRAs (Virtual Replication Appliances) on both sides that are able to connect to the counterpart on TCP ports 4007 and 4008
 - Zerto administration consoles or ZVMs (Zerto Virtual Managers) that are able to connect to the counterpart on TCP port 9071
+- A **Read Write (RW)** vCenter account is required to access and operate the Zerto interface.
 
 > [!primary]
 >
@@ -109,7 +111,7 @@ If the default values are correct:
 
 The only required parameter is the OVHcloud IPSec endpoint IP address.
 
-##### 3.1.2 Phase 1: Authentification.
+##### 3.1.2 Phase 1: Authentication.
 
 Once the default values are valid, you only need to provide the shared secret for authentication.
 
@@ -119,7 +121,7 @@ Once the default values are valid, you only need to provide the shared secret fo
 
 ![](images/image-EN-12.png){.thumbnail}
 
-Supported values for each parameters:
+Supported values for each parameter:
 
 - Encryption algorithms: AES 256 bits
 - Hash algorithms: SHA256
@@ -175,7 +177,7 @@ On OVHcloud side, the ZVM network is always a /23 network (512 IPs).
 
 Supported values are:
 
-- Protocole: ESP
+- Protocol: ESP
 - Encryption algorithm: AES 256 bits
 - Hash algorithms: SHA256
 - PFS: Off
@@ -246,7 +248,7 @@ For "Source" and "Destination", select "Single host or Network" type. The source
 
 ![](images/image-EN-28.png){.thumbnail}
 
-Destination TCP port is 9071. Click `Save`{.action} and `Apply Change`{.action}.
+Destination TCP port is 9071. Click `Save`{.action} and `Apply Changes`{.action}.
 
 #### 4.2 vRAs opening.
 
@@ -256,14 +258,14 @@ To simplify this setup, we are going to use the alias feature of OPNsense. An al
 We will define three aliases:
 
 * one for vRA IPs on the customer side
-* one for vRA IPs on the OVHCloud side
+* one for vRA IPs on the OVHcloud side
 * one for the ports
 
 You can get the OVHcloud vRAs IP from the destination Private Cloud vCenter interface.  
 
 ![](images/image-EN-29.png){.thumbnail}
 
-Let's create the OVH_VRA alias for OVHCLoud vRAs:
+Let's create the OVH_VRA alias for OVHcloud vRAs:
 
 ![](images/image-EN-30.png){.thumbnail}
 
@@ -295,7 +297,7 @@ In the dashboard, you can see the pairing is ongoing:
 
 ![](images/image-EN-36.png){.thumbnail}
 
-You will be notified when the pairing is successfull:
+You will be notified when the pairing is successful:
 
 ![](images/image-EN-37.png){.thumbnail}
 
@@ -305,6 +307,12 @@ You can check that your OVHcloud PCC is visible in the `Sites`{.action} tab.
 
 At this point, your Zerto setup is functional and you can start to create your virtual protection groups (VPGs).
 
+> [!warning]
+>
+> When enabling Zerto, a `Z-VRAH` VM may appear in your inventory.
+> This deployment is **not systematic**; it depends notably on the data volume to process.
+> If present, it is essential to the service and **must not be modified or deleted**.
+
 #### Troubleshooting
 
 If the on-premises ZVM is not able to successfully contact the OVHcloud ZVM (due to an incorrect firewall setup, for example) you will get the following message:
@@ -319,4 +327,8 @@ The most probable cause is that the OVHcloud ZVM is not authorised to contact yo
 
 ## Go further
 
-Join our community of users on <https://community.ovh.com/en/>.
+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.
+
+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.
+
+Join our [community of users](/links/community).