diff --git a/links/bare-metal/vps-lz b/links/bare-metal/vps-lz
index e8f46ea8287..6a77e0f742c 100644
--- a/links/bare-metal/vps-lz
+++ b/links/bare-metal/vps-lz
@@ -1,16 +1,16 @@
-- [de-de](https://www.ovhcloud.com/de/vps/vps-lz/)
-- [en-asia](https://www.ovhcloud.com/asia/vps/vps-lz/)
-- [en-au](https://www.ovhcloud.com/en-au/vps/vps-lz/)
-- [en-ca](https://www.ovhcloud.com/en-ca/vps/vps-lz/)
-- [en-gb](https://www.ovhcloud.com/en-gb/vps/vps-lz/)
-- [en-ie](https://www.ovhcloud.com/en-ie/vps/vps-lz/)
-- [en-in](https://www.ovhcloud.com/en-in/vps/vps-lz/)
-- [en-sg](https://www.ovhcloud.com/en-sg/vps/vps-lz/)
-- [en-us](https://www.ovhcloud.com/en/vps/vps-lz/)
-- [es-es](https://www.ovhcloud.com/es-es/vps/vps-lz/)
-- [es-us](https://www.ovhcloud.com/es/vps/vps-lz/)
-- [fr-ca](https://www.ovhcloud.com/fr-ca/vps/vps-lz/)
-- [fr-fr](https://www.ovhcloud.com/fr/vps/vps-lz/)
-- [it-it](https://www.ovhcloud.com/it/vps/vps-lz/)
-- [pl-pl](https://www.ovhcloud.com/pl/vps/vps-lz/)
-- [pt-pt](https://www.ovhcloud.com/pt/vps/vps-lz/)
\ No newline at end of file
+- [de-de](https://www.ovhcloud.com/de/vps/)
+- [en-asia](https://www.ovhcloud.com/asia/vps/)
+- [en-au](https://www.ovhcloud.com/en-au/vps/)
+- [en-ca](https://www.ovhcloud.com/en-ca/vps/)
+- [en-gb](https://www.ovhcloud.com/en-gb/vps/)
+- [en-ie](https://www.ovhcloud.com/en-ie/vps/)
+- [en-in](https://www.ovhcloud.com/en-in/vps/)
+- [en-sg](https://www.ovhcloud.com/en-sg/vps/)
+- [en-us](https://www.ovhcloud.com/en/vps/)
+- [es-es](https://www.ovhcloud.com/es-es/vps/)
+- [es-us](https://www.ovhcloud.com/es/vps/)
+- [fr-ca](https://www.ovhcloud.com/fr-ca/vps/)
+- [fr-fr](https://www.ovhcloud.com/fr/vps/)
+- [it-it](https://www.ovhcloud.com/it/vps/)
+- [pl-pl](https://www.ovhcloud.com/pl/vps/)
+- [pt-pt](https://www.ovhcloud.com/pt/vps/)
diff --git a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.de-de.md b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.de-de.md
index bcf19f79c15..2bc2c691ad4 100755
--- a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.de-de.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.de-de.md
@@ -4,10 +4,6 @@ excerpt: Erfahren Sie hier, wie Sie auf Ihrem VPS vorinstallierte Anwendungen ei
updated: 2022-08-25
---
-> [!primary]
-> Diese Übersetzung wurde durch unseren Partner SYSTRAN automatisch erstellt. In manchen Fällen können ungenaue Formulierungen verwendet worden sein, z.B. bei der Beschriftung von Schaltflächen oder technischen Details. Bitte ziehen Sie im Zweifelsfall die englische oder französische Fassung der Anleitung zu Rate. Möchten Sie mithelfen, diese Übersetzung zu verbessern? Dann nutzen Sie dazu bitte den Button "Beitragen" auf dieser Seite.
->
-
## Ziel
OVHcloud bietet VPS-Nutzern vorinstallierte Images verschiedener Anwendungen für eine schnelle und einfache Inbetriebnahme mit nur wenigen Klicks.
@@ -26,6 +22,10 @@ Installieren Sie die [Anwendung Ihrer Wahl](/links/manager) über das OVHcloud K
#### cPanel
+> [!warning]
+> Diese Funktion ist derzeit nicht verfügbar für VPS in [Local Zones](/links/bare-metal/vps-lz).
+>
+
Nachfolgend finden Sie die ersten Schritte zur Inbetriebnahme des vorinstallierten cPanel. Auf die mit "\*" gekennzeichneten Schritte folgt eine FAQ.
1. Öffnen Sie die E-Mail mit den Login-Daten zur Anwendung.
@@ -57,6 +57,10 @@ Es ist kein weiterer Schritt erforderlich, um die erste Konfiguration dieser Anw
#### Plesk
+> [!warning]
+> Diese Funktion ist derzeit nicht verfügbar für VPS in [Local Zones](/links/bare-metal/vps-lz).
+>
+
Nachfolgend finden Sie die ersten Schritte zur Inbetriebnahme des vorinstallierten Plesk. Auf die mit "\*" gekennzeichneten Schritte folgt eine FAQ.
1. Öffnen Sie die E-Mail mit den Login-Daten zur Anwendung.
@@ -77,6 +81,10 @@ Es ist kein weiterer Schritt erforderlich, um die erste Konfiguration dieser Anw
#### Docker
+> [!warning]
+> Diese Funktion ist derzeit nicht verfügbar für VPS in [Local Zones](/links/bare-metal/vps-lz).
+>
+
Nachfolgend finden Sie die ersten Schritte zur Inbetriebnahme des vorinstallierten Docker.
1. Verbinden Sie sich via SSH mit dem Benutzernamen und dem Passwort aus der E-Mail mit dem Server.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-asia.md b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-asia.md
deleted file mode 100644
index 8cf83628fa5..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-asia.md
+++ /dev/null
@@ -1,146 +0,0 @@
----
-title: 'First steps with pre-installed applications'
-excerpt: Find out how to deploy pre-installed applications on your VPS
-updated: 2022-08-25
----
-
-## Objective
-
-OVHcloud offers VPS customers pre-installed application images for quick and easy deployment of applications with few clicks only.
-
-**This guide will provide the first steps for each and every pre-installed application image on our VPS.**
-
-## Requirements
-
-- A [VPS](/links/bare-metal/vps) in your OVHcloud account
-
-## Instructions
-
-### Install your chosen pre-installed application
-
-Using the [OVHcloud Control Panel](/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps) / API, install your chosen application on your VPS.
-
-#### cPanel
-
-This section will explain the first steps specifically for the cPanel pre-installed image. Steps marked with \* will have FAQ at the end of the steps.
-
-1. Open the email from us which contains your application login details.
-2. Click on the URL for cPanel in the email.
-
-> [!primary]
->
-> If the link has expired already, please connect to your VPS via SSH using the CentOS user and execute the "sudo whmlogin" command to generate a new link.
->
-
-
- - Read and accept the terms of cPanel.
- - Provide your email and nameservers you wish to set on the server *.
- - Set your root password which you will use the next time you log in to WHM *.
-
-
-{.thumbnail}
-
-No further steps are necessary to complete the first configuration of this application.
-
-> [!faq]
->
-> Can I use my own nameservers?
->> Yes, you can. But you need to make sure you create glue records with your domain registrar. For example if you want "ns1.mydomain.com" and "ns2.mydomain.com", you must set up glue records for both which must point to the IP of your server. If your domain is registered with OVHcloud, you can follow [this guide](/pages/web_cloud/domains/glue_registry#step-1-add-the-glue-records). Please note that this can take 24 hours to create.
-> Why set root password?
->> WHM by default uses the root user for authentication and the one time link allows access to complete first setup and change root password. Next time you log in to WHM you must use the root user and the password you have set.
-> Where is my licence for cPanel?
->> You can purchase a licence from OVHcloud for your VPS via the [OVHcloud Control Panel](https://ca.ovh.com/manager/dedicated/#/configuration/license/order).
-
-#### Plesk
-
-This section will explain the first steps specifically for the Plesk pre-installed image. Steps marked with \* will have FAQ at the end of the steps.
-
-1. Open the email from OVHcloud which contains your application login details.
-2. Click on the URL for Plesk in the email.
-3. Log in using the username and password provided in the email.
-4. Once logged in, Plesk will ask you to provide:
- a) Your contact information
- b) A new password for the "admin" user which you will use for login on the Plesk panel
- c) Licence information*
- d) Read and accept their end-user licence agreement
-
-No further steps are necessary to complete the first configuration of this application.
-
-> [!faq]
->
-> Where is my licence for Plesk?
->> You can purchase a licence from OVHcloud for your VPS via the [OVHcloud Control Panel](https://ca.ovh.com/manager/dedicated/#/configuration/license/order).
-
-#### Docker
-
-This section will explain the first steps specifically for the Docker pre-installed image.
-
-1. SSH into the server using the login details sent in the email to you.
-2. Check that Docker is working using the "docker run hello-world" command.
-
-No further steps are necessary to complete the first configuration of this application.
-
-### Let's Encrypt SSL
-
-This section only applies to WordPress, Drupal, Joomla! and PrestaShop installations. It will not work for other installations.
-
-1. You must create or edit two `A` records in the OVHcloud Control Panel which point to the IP address of your server. For example if your domain name is "personaldomain.ovh" then you need to create `A` records for:
- - personaldomain.ovh
- - www.personaldomain.ovh
-
-If your domain is registered with OVHcloud you can follow [this guide](/pages/web_cloud/domains/dns_zone_edit).
-
If your domain is registered with another company you will need to contact them for assistance to set up your `A` records.
-
-
-- You may need to wait 24 hours before the two records propagate fully. You can always check it with mxtoolbox. If the IP for your domain is showing on mxtoolbox the same as your server's IP address then you can proceed to the next step.
-- SSH into your server with the CentOS user and execute the following commands to install Certbot.
-
-
-> [!warning]
->
-> Replace personaldomain.ovh in the commands with your own domain name.
->
-
-```sh
-sudo -i
-dnf install -y epel-release
-dnf install -y certbot python3-certbot-apache mod_ssl
-echo "ServerName personaldomain.ovh;" >> /etc/httpd/conf/httpd.conf
-systemctl restart httpd
-```
-
-
-- Generate your SSL using Certbot (follow the on screen instructions).
-
-
-```sh
-certbot certonly -d personaldomain.ovh --webroot
-```
-
-When asked about "Input the webroot", you need to enter something like "/var/www/wordpress". If you are installing Joomla!, you need to replace "wordpress" with "joomla".
-
-Now you need to get Certbot to also place it into the ssl.conf file. To trigger this, enter:
-
-```sh
-certbot -d personaldomain.ovh --apache
-```
-
-When prompted, answer the first prompt with "1" and also the second prompt with "1".
-
-You should get the following output if your SSL has been generated:
-
-```sh
-IMPORTANT NOTES:
- - Congratulations! Your certificate and chain have been saved at:
- /etc/letsencrypt/live/personaldomain.ovh/fullchain.pem
- Your key file has been saved at:
- /etc/letsencrypt/live/personaldomain.ovh/privkey.pem
- Your cert will expire on 2020-11-12. To obtain a new or tweaked
- version of this certificate in the future, simply run certbot again
- with the "certonly" option. To non-interactively renew *all* of
- your certificates, run "certbot renew"
-```
-
-## Go further
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-au.md b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-au.md
deleted file mode 100644
index 8cf83628fa5..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-au.md
+++ /dev/null
@@ -1,146 +0,0 @@
----
-title: 'First steps with pre-installed applications'
-excerpt: Find out how to deploy pre-installed applications on your VPS
-updated: 2022-08-25
----
-
-## Objective
-
-OVHcloud offers VPS customers pre-installed application images for quick and easy deployment of applications with few clicks only.
-
-**This guide will provide the first steps for each and every pre-installed application image on our VPS.**
-
-## Requirements
-
-- A [VPS](/links/bare-metal/vps) in your OVHcloud account
-
-## Instructions
-
-### Install your chosen pre-installed application
-
-Using the [OVHcloud Control Panel](/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps) / API, install your chosen application on your VPS.
-
-#### cPanel
-
-This section will explain the first steps specifically for the cPanel pre-installed image. Steps marked with \* will have FAQ at the end of the steps.
-
-1. Open the email from us which contains your application login details.
-2. Click on the URL for cPanel in the email.
-
-> [!primary]
->
-> If the link has expired already, please connect to your VPS via SSH using the CentOS user and execute the "sudo whmlogin" command to generate a new link.
->
-
-
- - Read and accept the terms of cPanel.
- - Provide your email and nameservers you wish to set on the server *.
- - Set your root password which you will use the next time you log in to WHM *.
-
-
-{.thumbnail}
-
-No further steps are necessary to complete the first configuration of this application.
-
-> [!faq]
->
-> Can I use my own nameservers?
->> Yes, you can. But you need to make sure you create glue records with your domain registrar. For example if you want "ns1.mydomain.com" and "ns2.mydomain.com", you must set up glue records for both which must point to the IP of your server. If your domain is registered with OVHcloud, you can follow [this guide](/pages/web_cloud/domains/glue_registry#step-1-add-the-glue-records). Please note that this can take 24 hours to create.
-> Why set root password?
->> WHM by default uses the root user for authentication and the one time link allows access to complete first setup and change root password. Next time you log in to WHM you must use the root user and the password you have set.
-> Where is my licence for cPanel?
->> You can purchase a licence from OVHcloud for your VPS via the [OVHcloud Control Panel](https://ca.ovh.com/manager/dedicated/#/configuration/license/order).
-
-#### Plesk
-
-This section will explain the first steps specifically for the Plesk pre-installed image. Steps marked with \* will have FAQ at the end of the steps.
-
-1. Open the email from OVHcloud which contains your application login details.
-2. Click on the URL for Plesk in the email.
-3. Log in using the username and password provided in the email.
-4. Once logged in, Plesk will ask you to provide:
- a) Your contact information
- b) A new password for the "admin" user which you will use for login on the Plesk panel
- c) Licence information*
- d) Read and accept their end-user licence agreement
-
-No further steps are necessary to complete the first configuration of this application.
-
-> [!faq]
->
-> Where is my licence for Plesk?
->> You can purchase a licence from OVHcloud for your VPS via the [OVHcloud Control Panel](https://ca.ovh.com/manager/dedicated/#/configuration/license/order).
-
-#### Docker
-
-This section will explain the first steps specifically for the Docker pre-installed image.
-
-1. SSH into the server using the login details sent in the email to you.
-2. Check that Docker is working using the "docker run hello-world" command.
-
-No further steps are necessary to complete the first configuration of this application.
-
-### Let's Encrypt SSL
-
-This section only applies to WordPress, Drupal, Joomla! and PrestaShop installations. It will not work for other installations.
-
-1. You must create or edit two `A` records in the OVHcloud Control Panel which point to the IP address of your server. For example if your domain name is "personaldomain.ovh" then you need to create `A` records for:
- - personaldomain.ovh
- - www.personaldomain.ovh
-
-If your domain is registered with OVHcloud you can follow [this guide](/pages/web_cloud/domains/dns_zone_edit).
-
If your domain is registered with another company you will need to contact them for assistance to set up your `A` records.
-
-
-- You may need to wait 24 hours before the two records propagate fully. You can always check it with mxtoolbox. If the IP for your domain is showing on mxtoolbox the same as your server's IP address then you can proceed to the next step.
-- SSH into your server with the CentOS user and execute the following commands to install Certbot.
-
-
-> [!warning]
->
-> Replace personaldomain.ovh in the commands with your own domain name.
->
-
-```sh
-sudo -i
-dnf install -y epel-release
-dnf install -y certbot python3-certbot-apache mod_ssl
-echo "ServerName personaldomain.ovh;" >> /etc/httpd/conf/httpd.conf
-systemctl restart httpd
-```
-
-
-- Generate your SSL using Certbot (follow the on screen instructions).
-
-
-```sh
-certbot certonly -d personaldomain.ovh --webroot
-```
-
-When asked about "Input the webroot", you need to enter something like "/var/www/wordpress". If you are installing Joomla!, you need to replace "wordpress" with "joomla".
-
-Now you need to get Certbot to also place it into the ssl.conf file. To trigger this, enter:
-
-```sh
-certbot -d personaldomain.ovh --apache
-```
-
-When prompted, answer the first prompt with "1" and also the second prompt with "1".
-
-You should get the following output if your SSL has been generated:
-
-```sh
-IMPORTANT NOTES:
- - Congratulations! Your certificate and chain have been saved at:
- /etc/letsencrypt/live/personaldomain.ovh/fullchain.pem
- Your key file has been saved at:
- /etc/letsencrypt/live/personaldomain.ovh/privkey.pem
- Your cert will expire on 2020-11-12. To obtain a new or tweaked
- version of this certificate in the future, simply run certbot again
- with the "certonly" option. To non-interactively renew *all* of
- your certificates, run "certbot renew"
-```
-
-## Go further
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-ca.md b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-ca.md
deleted file mode 100644
index 00275e7b2e7..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-ca.md
+++ /dev/null
@@ -1,146 +0,0 @@
----
-title: 'First steps with pre-installed applications'
-excerpt: Find out how to deploy pre-installed applications on your VPS
-updated: 2022-08-25
----
-
-## Objective
-
-OVHcloud offers VPS customers pre-installed application images for quick and easy deployment of applications with few clicks only.
-
-**This guide will provide the first steps for each and every pre-installed application image on our VPS.**
-
-## Requirements
-
-- A [VPS](/links/bare-metal/vps) in your OVHcloud account
-
-## Instructions
-
-### Install your chosen pre-installed application
-
-Using the [OVHcloud Control Panel](/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps) / API, install your chosen application on your VPS.
-
-#### cPanel
-
-This section will explain the first steps specifically for the cPanel pre-installed image. Steps marked with \* will have FAQ at the end of the steps.
-
-1. Open the email from us which contains your application login details.
-2. Click on the URL for cPanel in the email.
-
-> [!primary]
->
-> If the link has expired already, please connect to your VPS via SSH using the CentOS user and execute the "sudo whmlogin" command to generate a new link.
->
-
-
- - Read and accept the terms of cPanel.
- - Provide your email and nameservers you wish to set on the server *.
- - Set your root password which you will use the next time you log in to WHM *.
-
-
-{.thumbnail}
-
-No further steps are necessary to complete the first configuration of this application.
-
-> [!faq]
->
-> Can I use my own nameservers?
->> Yes, you can. But you need to make sure you create glue records with your domain registrar. For example if you want "ns1.mydomain.com" and "ns2.mydomain.com", you must set up glue records for both which must point to the IP of your server. If your domain is registered with OVHcloud, you can follow [this guide](/pages/web_cloud/domains/glue_registry#step-1-add-the-glue-records). Please note that this can take 24 hours to create.
-> Why set root password?
->> WHM by default uses the root user for authentication and the one time link allows access to complete first setup and change root password. Next time you log in to WHM you must use the root user and the password you have set.
-> Where is my licence for cPanel?
->> You can purchase a licence from OVHcloud for your VPS via the [OVHcloud Control Panel](https://ca.ovh.com/manager/dedicated/#/configuration/license/order).
-
-#### Plesk
-
-This section will explain the first steps specifically for the Plesk pre-installed image. Steps marked with \* will have FAQ at the end of the steps.
-
-1. Open the email from OVHcloud which contains your application login details.
-2. Click on the URL for Plesk in the email.
-3. Log in using the username and password provided in the email.
-4. Once logged in, Plesk will ask you to provide:
- a) Your contact information
- b) A new password for the "admin" user which you will use for login on the Plesk panel
- c) Licence information*
- d) Read and accept their end-user licence agreement
-
-No further steps are necessary to complete the first configuration of this application.
-
-> [!faq]
->
-> Where is my licence for Plesk?
->> You can purchase a licence from OVHcloud for your VPS via the [OVHcloud Control Panel](https://ca.ovh.com/manager/dedicated/#/configuration/license/order).
-
-#### Docker
-
-This section will explain the first steps specifically for the Docker pre-installed image.
-
-1. SSH into the server using the login details sent in the email to you.
-2. Check that Docker is working using the "docker run hello-world" command.
-
-No further steps are necessary to complete the first configuration of this application.
-
-### Let's Encrypt SSL
-
-This section only applies to WordPress, Drupal, Joomla! and PrestaShop installations. It will not work for other installations.
-
-1. You must create or edit two `A` records in the OVHcloud Control Panel which point to the IP address of your server. For example if your domain name is "personaldomain.ovh" then you need to create `A` records for:
- - personaldomain.ovh
- - www.personaldomain.ovh
-
-If your domain is registered with OVHcloud you can follow [this guide](/pages/web_cloud/domains/dns_zone_edit).
-
If your domain is registered with another company you will need to contact them for assistance to set up your `A` records.
-
-
-- You may need to wait 24 hours before the two records propagate fully. You can always check it with mxtoolbox. If the IP for your domain is showing on mxtoolbox the same as your server's IP address then you can proceed to the next step.
-- SSH into your server with the CentOS user and execute the following commands to install Certbot.
-
-
-> [!warning]
->
-> Replace personaldomain.ovh in the commands with your own domain name.
->
-
-```sh
-sudo -i
-dnf install -y epel-release
-dnf install -y certbot python3-certbot-apache mod_ssl
-echo "ServerName personaldomain.ovh;" >> /etc/httpd/conf/httpd.conf
-systemctl restart httpd
-```
-
-
-- Generate your SSL using Certbot (follow the on screen instructions).
-
-
-```sh
-certbot certonly -d personaldomain.ovh --webroot
-```
-
-When asked about "Input the webroot", you need to enter something like "/var/www/wordpress". If you are installing Joomla!, you need to replace "wordpress" with "joomla".
-
-Now you need to get Certbot to also place it into the ssl.conf file. To trigger this, enter:
-
-```sh
-certbot -d personaldomain.ovh --apache
-```
-
-When prompted, answer the first prompt with "1" and also the second prompt with "1".
-
-You should get the following output if your SSL has been generated:
-
-```sh
-IMPORTANT NOTES:
- - Congratulations! Your certificate and chain have been saved at:
- /etc/letsencrypt/live/personaldomain.ovh/fullchain.pem
- Your key file has been saved at:
- /etc/letsencrypt/live/personaldomain.ovh/privkey.pem
- Your cert will expire on 2020-11-12. To obtain a new or tweaked
- version of this certificate in the future, simply run certbot again
- with the "certonly" option. To non-interactively renew *all* of
- your certificates, run "certbot renew"
-```
-
-## Go further
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-gb.md b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-gb.md
index c71477a1fd7..736406f048a 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-gb.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-gb.md
@@ -22,6 +22,11 @@ Using the [OVHcloud Control Panel](/pages/bare_metal_cloud/virtual_private_serve
#### cPanel
+
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
This section will explain the first steps specifically for the cPanel pre-installed image. Steps marked with \* will have FAQ at the end of the steps.
1. Open the email from us which contains your application login details.
@@ -53,6 +58,10 @@ No further steps are necessary to complete the first configuration of this appli
#### Plesk
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
This section will explain the first steps specifically for the Plesk pre-installed image. Steps marked with \* will have FAQ at the end of the steps.
1. Open the email from OVHcloud which contains your application login details.
@@ -73,6 +82,10 @@ No further steps are necessary to complete the first configuration of this appli
#### Docker
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
This section will explain the first steps specifically for the Docker pre-installed image.
1. SSH into the server using the login details sent in the email to you.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-ie.md b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-ie.md
deleted file mode 100644
index c71477a1fd7..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-ie.md
+++ /dev/null
@@ -1,146 +0,0 @@
----
-title: 'First steps with pre-installed applications'
-excerpt: Find out how to deploy pre-installed applications on your VPS
-updated: 2022-08-25
----
-
-## Objective
-
-OVHcloud offers VPS customers pre-installed application images for quick and easy deployment of applications with few clicks only.
-
-**This guide will provide the first steps for each and every pre-installed application image on our VPS.**
-
-## Requirements
-
-- A [VPS](/links/bare-metal/vps) in your OVHcloud account
-
-## Instructions
-
-### Install your chosen pre-installed application
-
-Using the [OVHcloud Control Panel](/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps) / API, install your chosen application on your VPS.
-
-#### cPanel
-
-This section will explain the first steps specifically for the cPanel pre-installed image. Steps marked with \* will have FAQ at the end of the steps.
-
-1. Open the email from us which contains your application login details.
-2. Click on the URL for cPanel in the email.
-
-> [!primary]
->
-> If the link has expired already, please connect to your VPS via SSH using the CentOS user and execute the "sudo whmlogin" command to generate a new link.
->
-
-
- - Read and accept the terms of cPanel.
- - Provide your email and nameservers you wish to set on the server *.
- - Set your root password which you will use the next time you log in to WHM *.
-
-
-{.thumbnail}
-
-No further steps are necessary to complete the first configuration of this application.
-
-> [!faq]
->
-> Can I use my own nameservers?
->> Yes, you can. But you need to make sure you create glue records with your domain registrar. For example if you want "ns1.mydomain.com" and "ns2.mydomain.com", you must set up glue records for both which must point to the IP of your server. If your domain is registered with OVHcloud, you can follow [this guide](/pages/web_cloud/domains/glue_registry#step-1-add-the-glue-records). Please note that this can take 24 hours to create.
-> Why set root password?
->> WHM by default uses the root user for authentication and the one time link allows access to complete first setup and change root password. Next time you log in to WHM you must use the root user and the password you have set.
-> Where is my licence for cPanel?
->> You can purchase a licence from OVHcloud for your VPS via the [OVHcloud Control Panel](https://www.ovh.com/manager/dedicated/#/configuration/license/order).
-
-#### Plesk
-
-This section will explain the first steps specifically for the Plesk pre-installed image. Steps marked with \* will have FAQ at the end of the steps.
-
-1. Open the email from OVHcloud which contains your application login details.
-2. Click on the URL for Plesk in the email.
-3. Log in using the username and password provided in the email.
-4. Once logged in, Plesk will ask you to provide:
- a) Your contact information
- b) A new password for the "admin" user which you will use for login on the Plesk panel
- c) Licence information*
- d) Read and accept their end-user licence agreement
-
-No further steps are necessary to complete the first configuration of this application.
-
-> [!faq]
->
-> Where is my licence for Plesk?
->> You can purchase a licence from OVHcloud for your VPS via the [OVHcloud Control Panel](https://www.ovh.com/manager/dedicated/#/configuration/license/order).
-
-#### Docker
-
-This section will explain the first steps specifically for the Docker pre-installed image.
-
-1. SSH into the server using the login details sent in the email to you.
-2. Check that Docker is working using the "docker run hello-world" command.
-
-No further steps are necessary to complete the first configuration of this application.
-
-### Let's Encrypt SSL
-
-This section only applies to WordPress, Drupal, Joomla! and PrestaShop installations. It will not work for other installations.
-
-1. You must create or edit two `A` records in the OVHcloud Control Panel which point to the IP address of your server. For example if your domain name is "personaldomain.ovh" then you need to create `A` records for:
- - personaldomain.ovh
- - www.personaldomain.ovh
-
-If your domain is registered with OVHcloud you can follow [this guide](/pages/web_cloud/domains/dns_zone_edit).
-
If your domain is registered with another company you will need to contact them for assistance to set up your `A` records.
-
-
-- You may need to wait 24 hours before the two records propagate fully. You can always check it with mxtoolbox. If the IP for your domain is showing on mxtoolbox the same as your server's IP address then you can proceed to the next step.
-- SSH into your server with the CentOS user and execute the following commands to install Certbot.
-
-
-> [!warning]
->
-> Replace personaldomain.ovh in the commands with your own domain name.
->
-
-```sh
-sudo -i
-dnf install -y epel-release
-dnf install -y certbot python3-certbot-apache mod_ssl
-echo "ServerName personaldomain.ovh;" >> /etc/httpd/conf/httpd.conf
-systemctl restart httpd
-```
-
-
-- Generate your SSL using Certbot (follow the on screen instructions).
-
-
-```sh
-certbot certonly -d personaldomain.ovh --webroot
-```
-
-When asked about "Input the webroot", you need to enter something like "/var/www/wordpress". If you are installing Joomla!, you need to replace "wordpress" with "joomla".
-
-Now you need to get Certbot to also place it into the ssl.conf file. To trigger this, enter:
-
-```sh
-certbot -d personaldomain.ovh --apache
-```
-
-When prompted, answer the first prompt with "1" and also the second prompt with "1".
-
-You should get the following output if your SSL has been generated:
-
-```sh
-IMPORTANT NOTES:
- - Congratulations! Your certificate and chain have been saved at:
- /etc/letsencrypt/live/personaldomain.ovh/fullchain.pem
- Your key file has been saved at:
- /etc/letsencrypt/live/personaldomain.ovh/privkey.pem
- Your cert will expire on 2020-11-12. To obtain a new or tweaked
- version of this certificate in the future, simply run certbot again
- with the "certonly" option. To non-interactively renew *all* of
- your certificates, run "certbot renew"
-```
-
-## Go further
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-sg.md b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-sg.md
deleted file mode 100644
index 8cf83628fa5..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-sg.md
+++ /dev/null
@@ -1,146 +0,0 @@
----
-title: 'First steps with pre-installed applications'
-excerpt: Find out how to deploy pre-installed applications on your VPS
-updated: 2022-08-25
----
-
-## Objective
-
-OVHcloud offers VPS customers pre-installed application images for quick and easy deployment of applications with few clicks only.
-
-**This guide will provide the first steps for each and every pre-installed application image on our VPS.**
-
-## Requirements
-
-- A [VPS](/links/bare-metal/vps) in your OVHcloud account
-
-## Instructions
-
-### Install your chosen pre-installed application
-
-Using the [OVHcloud Control Panel](/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps) / API, install your chosen application on your VPS.
-
-#### cPanel
-
-This section will explain the first steps specifically for the cPanel pre-installed image. Steps marked with \* will have FAQ at the end of the steps.
-
-1. Open the email from us which contains your application login details.
-2. Click on the URL for cPanel in the email.
-
-> [!primary]
->
-> If the link has expired already, please connect to your VPS via SSH using the CentOS user and execute the "sudo whmlogin" command to generate a new link.
->
-
-
- - Read and accept the terms of cPanel.
- - Provide your email and nameservers you wish to set on the server *.
- - Set your root password which you will use the next time you log in to WHM *.
-
-
-{.thumbnail}
-
-No further steps are necessary to complete the first configuration of this application.
-
-> [!faq]
->
-> Can I use my own nameservers?
->> Yes, you can. But you need to make sure you create glue records with your domain registrar. For example if you want "ns1.mydomain.com" and "ns2.mydomain.com", you must set up glue records for both which must point to the IP of your server. If your domain is registered with OVHcloud, you can follow [this guide](/pages/web_cloud/domains/glue_registry#step-1-add-the-glue-records). Please note that this can take 24 hours to create.
-> Why set root password?
->> WHM by default uses the root user for authentication and the one time link allows access to complete first setup and change root password. Next time you log in to WHM you must use the root user and the password you have set.
-> Where is my licence for cPanel?
->> You can purchase a licence from OVHcloud for your VPS via the [OVHcloud Control Panel](https://ca.ovh.com/manager/dedicated/#/configuration/license/order).
-
-#### Plesk
-
-This section will explain the first steps specifically for the Plesk pre-installed image. Steps marked with \* will have FAQ at the end of the steps.
-
-1. Open the email from OVHcloud which contains your application login details.
-2. Click on the URL for Plesk in the email.
-3. Log in using the username and password provided in the email.
-4. Once logged in, Plesk will ask you to provide:
- a) Your contact information
- b) A new password for the "admin" user which you will use for login on the Plesk panel
- c) Licence information*
- d) Read and accept their end-user licence agreement
-
-No further steps are necessary to complete the first configuration of this application.
-
-> [!faq]
->
-> Where is my licence for Plesk?
->> You can purchase a licence from OVHcloud for your VPS via the [OVHcloud Control Panel](https://ca.ovh.com/manager/dedicated/#/configuration/license/order).
-
-#### Docker
-
-This section will explain the first steps specifically for the Docker pre-installed image.
-
-1. SSH into the server using the login details sent in the email to you.
-2. Check that Docker is working using the "docker run hello-world" command.
-
-No further steps are necessary to complete the first configuration of this application.
-
-### Let's Encrypt SSL
-
-This section only applies to WordPress, Drupal, Joomla! and PrestaShop installations. It will not work for other installations.
-
-1. You must create or edit two `A` records in the OVHcloud Control Panel which point to the IP address of your server. For example if your domain name is "personaldomain.ovh" then you need to create `A` records for:
- - personaldomain.ovh
- - www.personaldomain.ovh
-
-If your domain is registered with OVHcloud you can follow [this guide](/pages/web_cloud/domains/dns_zone_edit).
-
If your domain is registered with another company you will need to contact them for assistance to set up your `A` records.
-
-
-- You may need to wait 24 hours before the two records propagate fully. You can always check it with mxtoolbox. If the IP for your domain is showing on mxtoolbox the same as your server's IP address then you can proceed to the next step.
-- SSH into your server with the CentOS user and execute the following commands to install Certbot.
-
-
-> [!warning]
->
-> Replace personaldomain.ovh in the commands with your own domain name.
->
-
-```sh
-sudo -i
-dnf install -y epel-release
-dnf install -y certbot python3-certbot-apache mod_ssl
-echo "ServerName personaldomain.ovh;" >> /etc/httpd/conf/httpd.conf
-systemctl restart httpd
-```
-
-
-- Generate your SSL using Certbot (follow the on screen instructions).
-
-
-```sh
-certbot certonly -d personaldomain.ovh --webroot
-```
-
-When asked about "Input the webroot", you need to enter something like "/var/www/wordpress". If you are installing Joomla!, you need to replace "wordpress" with "joomla".
-
-Now you need to get Certbot to also place it into the ssl.conf file. To trigger this, enter:
-
-```sh
-certbot -d personaldomain.ovh --apache
-```
-
-When prompted, answer the first prompt with "1" and also the second prompt with "1".
-
-You should get the following output if your SSL has been generated:
-
-```sh
-IMPORTANT NOTES:
- - Congratulations! Your certificate and chain have been saved at:
- /etc/letsencrypt/live/personaldomain.ovh/fullchain.pem
- Your key file has been saved at:
- /etc/letsencrypt/live/personaldomain.ovh/privkey.pem
- Your cert will expire on 2020-11-12. To obtain a new or tweaked
- version of this certificate in the future, simply run certbot again
- with the "certonly" option. To non-interactively renew *all* of
- your certificates, run "certbot renew"
-```
-
-## Go further
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-us.md b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-us.md
deleted file mode 100644
index 8cf83628fa5..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.en-us.md
+++ /dev/null
@@ -1,146 +0,0 @@
----
-title: 'First steps with pre-installed applications'
-excerpt: Find out how to deploy pre-installed applications on your VPS
-updated: 2022-08-25
----
-
-## Objective
-
-OVHcloud offers VPS customers pre-installed application images for quick and easy deployment of applications with few clicks only.
-
-**This guide will provide the first steps for each and every pre-installed application image on our VPS.**
-
-## Requirements
-
-- A [VPS](/links/bare-metal/vps) in your OVHcloud account
-
-## Instructions
-
-### Install your chosen pre-installed application
-
-Using the [OVHcloud Control Panel](/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps) / API, install your chosen application on your VPS.
-
-#### cPanel
-
-This section will explain the first steps specifically for the cPanel pre-installed image. Steps marked with \* will have FAQ at the end of the steps.
-
-1. Open the email from us which contains your application login details.
-2. Click on the URL for cPanel in the email.
-
-> [!primary]
->
-> If the link has expired already, please connect to your VPS via SSH using the CentOS user and execute the "sudo whmlogin" command to generate a new link.
->
-
-
- - Read and accept the terms of cPanel.
- - Provide your email and nameservers you wish to set on the server *.
- - Set your root password which you will use the next time you log in to WHM *.
-
-
-{.thumbnail}
-
-No further steps are necessary to complete the first configuration of this application.
-
-> [!faq]
->
-> Can I use my own nameservers?
->> Yes, you can. But you need to make sure you create glue records with your domain registrar. For example if you want "ns1.mydomain.com" and "ns2.mydomain.com", you must set up glue records for both which must point to the IP of your server. If your domain is registered with OVHcloud, you can follow [this guide](/pages/web_cloud/domains/glue_registry#step-1-add-the-glue-records). Please note that this can take 24 hours to create.
-> Why set root password?
->> WHM by default uses the root user for authentication and the one time link allows access to complete first setup and change root password. Next time you log in to WHM you must use the root user and the password you have set.
-> Where is my licence for cPanel?
->> You can purchase a licence from OVHcloud for your VPS via the [OVHcloud Control Panel](https://ca.ovh.com/manager/dedicated/#/configuration/license/order).
-
-#### Plesk
-
-This section will explain the first steps specifically for the Plesk pre-installed image. Steps marked with \* will have FAQ at the end of the steps.
-
-1. Open the email from OVHcloud which contains your application login details.
-2. Click on the URL for Plesk in the email.
-3. Log in using the username and password provided in the email.
-4. Once logged in, Plesk will ask you to provide:
- a) Your contact information
- b) A new password for the "admin" user which you will use for login on the Plesk panel
- c) Licence information*
- d) Read and accept their end-user licence agreement
-
-No further steps are necessary to complete the first configuration of this application.
-
-> [!faq]
->
-> Where is my licence for Plesk?
->> You can purchase a licence from OVHcloud for your VPS via the [OVHcloud Control Panel](https://ca.ovh.com/manager/dedicated/#/configuration/license/order).
-
-#### Docker
-
-This section will explain the first steps specifically for the Docker pre-installed image.
-
-1. SSH into the server using the login details sent in the email to you.
-2. Check that Docker is working using the "docker run hello-world" command.
-
-No further steps are necessary to complete the first configuration of this application.
-
-### Let's Encrypt SSL
-
-This section only applies to WordPress, Drupal, Joomla! and PrestaShop installations. It will not work for other installations.
-
-1. You must create or edit two `A` records in the OVHcloud Control Panel which point to the IP address of your server. For example if your domain name is "personaldomain.ovh" then you need to create `A` records for:
- - personaldomain.ovh
- - www.personaldomain.ovh
-
-If your domain is registered with OVHcloud you can follow [this guide](/pages/web_cloud/domains/dns_zone_edit).
-
If your domain is registered with another company you will need to contact them for assistance to set up your `A` records.
-
-
-- You may need to wait 24 hours before the two records propagate fully. You can always check it with mxtoolbox. If the IP for your domain is showing on mxtoolbox the same as your server's IP address then you can proceed to the next step.
-- SSH into your server with the CentOS user and execute the following commands to install Certbot.
-
-
-> [!warning]
->
-> Replace personaldomain.ovh in the commands with your own domain name.
->
-
-```sh
-sudo -i
-dnf install -y epel-release
-dnf install -y certbot python3-certbot-apache mod_ssl
-echo "ServerName personaldomain.ovh;" >> /etc/httpd/conf/httpd.conf
-systemctl restart httpd
-```
-
-
-- Generate your SSL using Certbot (follow the on screen instructions).
-
-
-```sh
-certbot certonly -d personaldomain.ovh --webroot
-```
-
-When asked about "Input the webroot", you need to enter something like "/var/www/wordpress". If you are installing Joomla!, you need to replace "wordpress" with "joomla".
-
-Now you need to get Certbot to also place it into the ssl.conf file. To trigger this, enter:
-
-```sh
-certbot -d personaldomain.ovh --apache
-```
-
-When prompted, answer the first prompt with "1" and also the second prompt with "1".
-
-You should get the following output if your SSL has been generated:
-
-```sh
-IMPORTANT NOTES:
- - Congratulations! Your certificate and chain have been saved at:
- /etc/letsencrypt/live/personaldomain.ovh/fullchain.pem
- Your key file has been saved at:
- /etc/letsencrypt/live/personaldomain.ovh/privkey.pem
- Your cert will expire on 2020-11-12. To obtain a new or tweaked
- version of this certificate in the future, simply run certbot again
- with the "certonly" option. To non-interactively renew *all* of
- your certificates, run "certbot renew"
-```
-
-## Go further
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.es-es.md b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.es-es.md
index d2885e4e2e9..6fcc5d1a6c6 100755
--- a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.es-es.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.es-es.md
@@ -4,10 +4,6 @@ excerpt: Cómo desplegar aplicaciones preinstaladas en un VPS
updated: 2022-08-25
---
-> [!primary]
-> Esta traducción ha sido generada de forma automática por nuestro partner SYSTRAN. En algunos casos puede contener términos imprecisos, como en las etiquetas de los botones o los detalles técnicos. En caso de duda, le recomendamos que consulte la versión inglesa o francesa de la guía. Si quiere ayudarnos a mejorar esta traducción, por favor, utilice el botón «Contribuir» de esta página.
->
-
## Objetivo
OVHcloud ofrece a los clientes VPS imágenes de aplicaciones preinstaladas para un despliegue rápido y fácil en pocos clics.
@@ -26,6 +22,10 @@ Instale [la aplicación que desee desde el área de cliente de OVHcloud](/links/
#### cPanel
+> [!warning]
+> Esta funcionalidad no está disponible actualmente para los servidores virtuales en las [Local Zones](/links/bare-metal/vps-lz).
+>
+
A continuación se indican los primeros pasos para poner en servicio la imagen preinstalada de cPanel. A las etapas marcadas con un "*", seguiremos una FAQ.
1. Abra el mensaje de correo electrónico que haya recibido con las claves de acceso a la aplicación.
@@ -57,6 +57,10 @@ No es necesario realizar ningún otro paso para finalizar la primera configuraci
#### Plesk
+> [!warning]
+> Esta funcionalidad no está disponible actualmente para los servidores virtuales en las [Local Zones](/links/bare-metal/vps-lz).
+>
+
A continuación se indican los primeros pasos para poner en servicio la imagen preinstalada de Plesk. A las etapas marcadas con un "\*", seguiremos una FAQ.
1. Abra el mensaje de correo electrónico que haya recibido con las claves de acceso a la aplicación.
@@ -77,6 +81,10 @@ No es necesario realizar ningún otro paso para finalizar la primera configuraci
#### Docker
+> [!warning]
+> Esta funcionalidad no está disponible actualmente para los servidores virtuales en las [Local Zones](/links/bare-metal/vps-lz).
+>
+
A continuación se indican los primeros pasos para poner en servicio la imagen preinstalada de Docker.
1. Conéctese al servidor por SSH utilizando el nombre de usuario y la contraseña del mensaje de correo electrónico.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.es-us.md b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.es-us.md
deleted file mode 100755
index 61ed80e8a1e..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.es-us.md
+++ /dev/null
@@ -1,152 +0,0 @@
----
-title: 'Primeros pasos con las aplicaciones preinstaladas'
-excerpt: Cómo desplegar aplicaciones preinstaladas en un VPS
-updated: 2022-08-25
----
-
-> [!primary]
-> Esta traducción ha sido generada de forma automática por nuestro partner SYSTRAN. En algunos casos puede contener términos imprecisos, como en las etiquetas de los botones o los detalles técnicos. En caso de duda, le recomendamos que consulte la versión inglesa o francesa de la guía. Si quiere ayudarnos a mejorar esta traducción, por favor, utilice el botón «Contribuir» de esta página.
->
-
-## Objetivo
-
-OVHcloud ofrece a los clientes VPS imágenes de aplicaciones preinstaladas para un despliegue rápido y fácil en pocos clics.
-
-**Esta guía explica cómo desplegar aplicaciones preinstaladas en un VPS.**
-
-## Requisitos
-
-- Tener un [VPS](/links/bare-metal/vps) en su cuenta de OVHcloud.
-
-## Procedimiento
-
-### Instalar la aplicación preinstalada que desee
-
-Instale la aplicación que desee desde el [área de cliente de OVHcloud](/links/manager) o las API de OVHcloud. También puede consultar nuestra guía [Primeros pasos con un VPS](/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps).
-
-#### cPanel
-
-A continuación se indican los primeros pasos para poner en servicio la imagen preinstalada de cPanel. A las etapas marcadas con un "\*", seguiremos una FAQ.
-
-1. Abra el mensaje de correo electrónico que haya recibido con las claves de acceso a la aplicación.
-2. Haga clic en la URL de cPanel en este email.
-
-> [!primary]
->
-> Si el enlace ya ha caducado, por favor conéctese a su VPS vía SSH usando el usuario CentOS y ejecute el comando « sudo whmlogin » para generar un nuevo enlace.
->
-
-
- - Lea y acepte las condiciones particulares de cPanel.
- - Introduzca sus servidores de correo y servidores DNS*.
- - Establezca la contraseña root que utilizará la próxima vez que se conecte a WHM *.
-
-
-{.thumbnail}
-
-No es necesario realizar ningún otro paso para finalizar la primera configuración de esta aplicación.
-
-> [!faq]
->
-> ¿Puedo utilizar mis propios servidores DNS?
->> Sí, puede. Asegúrese de crear los registros Glue con su agente registrador de dominios. Por ejemplo, si quiere "ns1.mydomain.com" y "ns2.mydomain.com", debe configurar los registros Glue para que ambos apunten a la dirección IP de su servidor. Si tiene su dominio registrado con OVHcloud, puede seguir [esta guía](/pages/web_cloud/domains/glue_registry#1-anadir-los-registros-glue) La creación puede tardar 24 horas.
-> ¿Por qué establecer la contraseña root?
->> WHM utiliza por defecto el usuario root para la autenticación. La URL de un solo uso permite acceder a la primera configuración y cambiar la contraseña root. La próxima vez que se conecte a WHM, deberá utilizar el usuario root y la contraseña que haya establecido.
-> ¿Dónde está mi licencia para cPanel?
->> Puede contratar su licencia cPanel para su VPS desde [el área de cliente de OVHcloud](/links/manager).
-
-#### Plesk
-
-A continuación se indican los primeros pasos para poner en servicio la imagen preinstalada de Plesk. A las etapas marcadas con un "\*", seguiremos una FAQ.
-
-1. Abra el mensaje de correo electrónico que haya recibido con las claves de acceso a la aplicación.
-2. Haga clic en la URL de Plesk en este email.
-3. Conéctese con el nombre de usuario y la contraseña del mensaje de correo electrónico.
-4. Una vez conectado, Plesk le preguntará:
- a) Sus datos.
- b) Una nueva contraseña para el usuario "admin" que utilizará para conectarse a la interfaz de Plesk.
- c) Información sobre la licencia.*
- d) Leer y aceptar los contratos de licencia de usuario.
-
-No es necesario realizar ningún otro paso para finalizar la primera configuración de esta aplicación.
-
-> [!faq]
->
-> ¿Dónde está mi licencia Plesk?
->> Puede contratar una licencia Plesk para su VPS desde [el área de cliente de OVHcloud](https://ca.ovh.com/manager/dedicated/#/configuration/license/order).
-
-#### Docker
-
-A continuación se indican los primeros pasos para poner en servicio la imagen preinstalada de Docker.
-
-1. Conéctese al servidor por SSH utilizando el nombre de usuario y la contraseña del mensaje de correo electrónico.
-2. Compruebe que Docker funciona con el comando "docker run hello-world".
-
-No es necesario realizar ningún otro paso para finalizar la primera configuración de esta aplicación.
-
-### Let's Encrypt SSL
-
-Esta sección solo se aplica a las instalaciones de WordPress, Drupal, Joomla! y PrestaShop. No se aplicará a las demás instalaciones.
-
-1. Es necesario crear o modificar dos registros `A` en el área de cliente de OVHcloud que apuntan a la dirección IP del servidor. Por ejemplo, si el dominio es "personaldomain.ovh", es necesario crear registros `A` para:
-
- personaldomain.ovh
- www.personaldomain.ovh
-
-Si su dominio está registrado en OVHcloud, puede seguir [esta guía.](/pages/web_cloud/domains/dns_zone_edit)
-
Si su dominio está registrado con otra empresa, deberá contactar con ella para solicitar ayuda sobre la configuración de sus registros `A`.
-
-
- - Tal vez tengan que esperar 24 horas antes de que ambos registros se propaguen por completo. Todavía puede comprobarlo con mxtoolbox. Si la dirección IP de su dominio aparece en mxtoolbox del mismo modo que la de su servidor, puede pasar a la siguiente etapa.
-
- - Conéctese al servidor por SSH con el usuario CentOS y ejecute los siguientes comandos para instalar Cura:
-
-
-> [!warning]
->
-> Sustituya a personaldomain.ovh por su propio dominio en los siguientes comandos.
->
-
-```sh
-sudo -i
-dnf install -y epel-release
-dnf install -y certbot python3-certbot-apache mod_ssl
-echo "ServerName personaldomain.ovh;" >> /etc/httpd/conf/httpd.conf
-systemctl restart httpd
-```
-
-
- - Genere su certificado SSL utilizando Cura (siga las indicaciones en pantalla).
-
-
-```sh
-certbot certonly -d personaldomain.ovh --webroot
-```
-
-Al introducir "Input the webroot", debe introducir una variable del tipo "/var/www/wordpress". Si instala Joomla!, debe sustituir "wordpress" por "joomla".
-
-Ahora debe asegurarse de que Cierbot también sitúe esta variable en el archivo ssl.conf. Para ello, introduzca:
-
-```sh
-certbot -d personaldomain.ovh —apache
-```
-
-Cuando usted esté invitado, responda a la primera pregunta por "1" y a la segunda también por "1".
-
-Si se ha generado el certificado SSL, obtendrá el siguiente resultado:
-
-```sh
-NOTAS IMPORTANTES:
- - Congratulaciones! Your certificate and chain have been saved at:
- /etc/letsencrypt/live/personaldomain.ovh/fullchain.pem
- Your key file has been saved at:
- /etc/letsencrypt/live/personaldomain.ovh/privkey.pem
- Your cert will expira on 2020-11-12. To obtain a new or tweaked
- version of this certificate in the future, simply run certbot again
- with the "certonly" option. To no interactively renew *all* of
- your certificates, run "certbot renew"
-```
-
-## Vaya más lejos
-
-Interactúe con nuestra comunidad de usuarios en .
diff --git a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.fr-ca.md b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.fr-ca.md
deleted file mode 100644
index 87b07f7aa85..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.fr-ca.md
+++ /dev/null
@@ -1,148 +0,0 @@
----
-title: 'Premiers pas avec les applications préinstallées'
-excerpt: Découvrez comment déployer des applications préinstallées sur votre VPS
-updated: 2022-08-25
----
-
-## Objectif
-
-OVHcloud offre aux clients VPS des images d'applications préinstallées pour un déploiement rapide et facile en quelques clics.
-
-**Découvrez comment déployer des applications préinstallées sur votre VPS.**
-
-## Prérequis
-
-- Disposer d'un [VPS](/links/bare-metal/vps) sur votre compte OVHcloud.
-
-## En pratique
-
-### Installer l'application préinstallée de votre choix
-
-Depuis [l'espace client OVHcloud](/links/manager) ou les API OVHcloud, installez l'application de votre choix. Vous pouvez également consulter notre guide [Débuter avec un VPS](/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps).
-
-#### cPanel
-
-Vous trouverez ci-dessous les premières étapes relatives à la mise en service de l'image préinstallée de cPanel. Les étapes marquées d'un « * » seront suivies d'une FAQ.
-
-1. Ouvrez l'e-mail que vous avez reçu contenant les identifiants de connexion à l'application.
-2. Cliquez sur l'URL de cPanel dans cet e-mail.
-
-> [!primary]
->
-> Si le lien a déjà expiré, connectez-vous en SSH au serveur à l'aide de l'utilisateur CentOS et exécutez la commande « sudo whmlogin » pour générer un nouveau lien.
->
-
-
- - Lisez et acceptez les conditions particulières de cPanel.
- - Saisissez vos serveurs de messagerie et serveurs DNS *.
- - Définissez le mot de passe root que vous utiliserez la prochaine fois que vous vous connecterez à WHM *.
-
-
-{.thumbnail}
-
-Aucune autre étape n'est nécessaire pour terminer la première configuration de cette application.
-
-> [!faq]
->
-> Puis-je utiliser mes propres serveurs DNS ?
->> Oui, vous le pouvez. Assurez-vous de créer des enregistrements « GLUE » avec votre bureau d'enregistrement de domaine. Par exemple, si vous voulez « ns1.mydomain.com » et « ns2.mydomain.com », vous devez configurer des enregistrements « GLUE » pour que les deux pointent sur l'adresse IP de votre serveur. Si votre domaine est enregistré avec OVHcloud, vous pouvez suivre [ce guide](/pages/web_cloud/domains/glue_registry#etape-1-ajouter-les-enregistrements-glue). Notez que la création peut prendre 24 heures.
-> Pourquoi définir le mot de passe root?
->> WHM utilise par défaut l'utilisateur root pour l'authentification. L'URL à usage unique permet d'accéder à la première configuration et de modifier le mot de passe root. La prochaine fois que vous vous connecterez à WHM, vous devrez utiliser l'utilisateur root et le mot de passe que vous avez défini.
-> Où est ma licence pour cPanel?
->> Vous pouvez commander votre licence cPanel pour votre VPS depuis [l'espace client OVHcloud](https://ca.ovh.com/manager/dedicated/#/configuration/license/order).
-
-#### Plesk
-
-Vous trouverez ci-dessous les premières étapes relatives à la mise en service de l'image préinstallée de Plesk. Les étapes marquées d'un « * » seront suivies d'une FAQ.
-
-1. Ouvrez l'e-mail que vous avez reçu contenant les identifiants de connexion à l'application.
-2. Cliquez sur l'URL de Plesk dans cet e-mail.
-3. Connectez-vous à l'aide du nom d'utilisateur et du mot de passe présents dans l'e-mail.
-4. Une fois connecté, Plesk vous demandera:
- a) Vos coordonnées.
- b) Un nouveau mot de passe pour l'utilisateur « admin » que vous utiliserez pour vous connecter à l'interface de Plesk.
- c) Des informations sur la licence.*
- d) De lire et accepter les contrats de licence utilisateur.
-
-Aucune autre étape n'est nécessaire pour terminer la première configuration de cette application.
-
-> [!faq]
->
-> Où est ma licence Plesk?
->> Vous pouvez commander votre licence Plesk pour votre VPS depuis [l'espace client OVHcloud](https://ca.ovh.com/manager/dedicated/#/configuration/license/order).
-
-#### Docker
-
-Vous trouverez ci-dessous les premières étapes relatives à la mise en service de l'image préinstallée de Docker.
-
-1. Connectez-vous en SSH sur le serveur à l'aide du nom d'utilisateur et du mot de passe présents dans l'e-mail.
-2. Vérifiez que Docker fonctionne à l'aide de la commande « docker run hello-world ».
-
-Aucune autre étape n'est nécessaire pour terminer la première configuration de cette application.
-
-### Let's Encrypt SSL
-
-Cette section s'applique uniquement aux installations de WordPress, Drupal, Joomla! et PrestaShop. Elle ne s'applique pas pour les autres installations.
-
-1. Vous devez créer ou modifier, dans l'espace client OVHcloud, deux enregistrements `A ` qui pointent vers l'adresse IP de votre serveur. Par exemple, si votre nom de domaine est « personaldomain.ovh », vous devez créer des enregistrements `A` pour :
-
- - personaldomain.ovh
- - www.personaldomain.ovh
-
-Si votre domaine est enregistré chez OVHcloud, vous pouvez suivre [ce guide](/pages/web_cloud/domains/dns_zone_edit).
-
Si votre domaine est enregistré auprès d'une autre société, vous devrez contacter celle-ci pour obtenir de l'aide sur la configuration de vos enregistrements `A`.
-
-
- - Vous devrez peut-être attendre 24 heures avant que les deux enregistrements ne se propagent complètement. Vous pouvez toujours le vérifier avec mxtoolbox. Si l'adresse IP de votre domaine s'affiche sur mxtoolbox de la même manière que celle de votre serveur, vous pouvez passer à l'étape suivante.
-
- - Connectez-vous en SSH sur votre serveur avec l'utilisateur CentOS et exécutez les commandes suivantes pour installer Certbot :
-
-
-> [!warning]
->
-> Remplacez personaldomain.ovh par votre propre nom de domaine dans les commandes suivantes.
->
-
-```sh
-sudo -i
-dnf install -y epel-release
-dnf install -y certbot python3-certbot-apache mod_ssl
-echo "ServerName personaldomain.ovh;" >> /etc/httpd/conf/httpd.conf
-systemctl restart httpd
-```
-
-
- - Générez votre certificat SSL en utilisant Certbot (suivez les instructions à l'écran).
-
-
-```sh
-certbot certonly -d personaldomain.ovh --webroot
-```
-
-Lorsque vous êtes invité à saisir « Input the webroot », vous devez saisir une variable du type « /var/www/wordpress ». Si vous installez Joomla!, vous devez remplacer « wordpress » par « joomla ».
-
-Vous devez maintenant faire en sorte que Certbot place également cette variable dans le fichier ssl.conf. Pour cela, entrez :
-
-```sh
-certbot -d personaldomain.ovh --apache
-```
-
-Lorsque vous y êtes invité, répondez à la première question par « 1 » et à la seconde aussi par « 1 ».
-
-Vous devriez obtenir le résultat suivant si votre certificat SSL a été généré :
-
-```sh
-IMPORTANT NOTES:
- - Congratulations! Your certificate and chain have been saved at:
- /etc/letsencrypt/live/personaldomain.ovh/fullchain.pem
- Your key file has been saved at:
- /etc/letsencrypt/live/personaldomain.ovh/privkey.pem
- Your cert will expire on 2020-11-12. To obtain a new or tweaked
- version of this certificate in the future, simply run certbot again
- with the "certonly" option. To non-interactively renew *all* of
- your certificates, run "certbot renew"
-```
-
-## Allez plus loin
-
-Échangez avec notre [communauté d'utilisateurs](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.fr-fr.md b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.fr-fr.md
index 8459172a2f1..6dfe2f1463f 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.fr-fr.md
@@ -22,6 +22,10 @@ Depuis [l'espace client OVHcloud](/links/manager) ou les API OVHcloud, installez
#### cPanel
+> [!warning]
+> Cette fonctionnalité est actuellement indisponible pour les serveurs privés virtuels dans les [Local Zones](/links/bare-metal/vps-lz).
+>
+
Vous trouverez ci-dessous les premières étapes relatives à la mise en service de l'image préinstallée de cPanel. Les étapes marquées d'un « * » seront suivies d'une FAQ.
1. Ouvrez l'e-mail que vous avez reçu contenant les identifiants de connexion à l'application.
@@ -53,6 +57,10 @@ Aucune autre étape n'est nécessaire pour terminer la première configuration d
#### Plesk
+> [!warning]
+> Cette fonctionnalité est actuellement indisponible pour les serveurs privés virtuels dans les [Local Zones](/links/bare-metal/vps-lz).
+>
+
Vous trouverez ci-dessous les premières étapes relatives à la mise en service de l'image préinstallée de Plesk. Les étapes marquées d'un « * » seront suivies d'une FAQ.
1. Ouvrez l'e-mail que vous avez reçu contenant les identifiants de connexion à l'application.
@@ -73,6 +81,10 @@ Aucune autre étape n'est nécessaire pour terminer la première configuration d
#### Docker
+> [!warning]
+> Cette fonctionnalité est actuellement indisponible pour les serveurs privés virtuels dans les [Local Zones](/links/bare-metal/vps-lz).
+>
+
Vous trouverez ci-dessous les premières étapes relatives à la mise en service de l'image préinstallée de Docker.
1. Connectez-vous en SSH sur le serveur à l'aide du nom d'utilisateur et du mot de passe présents dans l'e-mail.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.it-it.md b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.it-it.md
index 915c74fc905..138271cd916 100755
--- a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.it-it.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.it-it.md
@@ -4,10 +4,6 @@ excerpt: Come implementare applicazioni preinstallate sul tuo VPS
updated: 2022-08-25
---
-> [!primary]
-> Questa traduzione è stata generata automaticamente dal nostro partner SYSTRAN. I contenuti potrebbero presentare imprecisioni, ad esempio la nomenclatura dei pulsanti o alcuni dettagli tecnici. In caso di dubbi consigliamo di fare riferimento alla versione inglese o francese della guida. Per aiutarci a migliorare questa traduzione, utilizza il pulsante "Contribuisci" di questa pagina.
->
-
## Obiettivo
OVHcloud offre ai clienti VPS immagini di applicazioni preinstallate per un'implementazione rapida e semplice in pochi click.
@@ -26,6 +22,10 @@ Dallo [Spazio Cliente OVHcloud](/links/manager) o tramite le API OVHcloud è pos
#### cPanel
+> [!warning]
+> Questa funzionalità non è attualmente disponibile per i server privati virtuali nelle [Local Zones](/links/bare-metal/vps-lz).
+>
+
Di seguito trovi i primi step per la messa in servizio dell'immagine preinstallata di cPanel. Gli step contrassegnati con "\*" saranno seguiti da FAQ.
1. Apri l'email ricevuta con le credenziali di accesso all'applicazione.
@@ -57,6 +57,10 @@ Per completare la prima configurazione dell'applicazione non sono necessari ulte
#### Plesk
+> [!warning]
+> Questa funzionalità non è attualmente disponibile per i server privati virtuali nelle [Local Zones](/links/bare-metal/vps-lz).
+>
+
Di seguito trovi i primi step per la messa in servizio dell'immagine preinstallata di Plesk. Gli step contrassegnati con "\*" saranno seguiti da FAQ.
1. Apri l'email ricevuta con le credenziali di accesso all'applicazione.
@@ -77,6 +81,10 @@ Per completare la prima configurazione dell'applicazione non sono necessari ulte
#### Docker
+> [!warning]
+> Questa funzionalità non è attualmente disponibile per i server privati virtuali nelle [Local Zones](/links/bare-metal/vps-lz).
+>
+
Di seguito trovi i primi step per la messa in servizio dell'immagine preinstallata di Docker.
1. Accedi in SSH al server utilizzando il nome utente e la password presenti nell'email.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.pl-pl.md b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.pl-pl.md
index 737c2b15071..9c360d6bfc4 100755
--- a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.pl-pl.md
@@ -4,10 +4,6 @@ excerpt: Dowiedz się, jak wdrożyć aplikacje zainstalowane na serwerze VPS
updated: 2022-08-25
---
-> [!primary]
-> Tłumaczenie zostało wygenerowane automatycznie przez system naszego partnera SYSTRAN. W niektórych przypadkach mogą wystąpić nieprecyzyjne sformułowania, na przykład w tłumaczeniu nazw przycisków lub szczegółów technicznych. W przypadku jakichkolwiek wątpliwości zalecamy zapoznanie się z angielską/francuską wersją przewodnika. Jeśli chcesz przyczynić się do ulepszenia tłumaczenia, kliknij przycisk "Zgłóś propozycję modyfikacji" na tej stronie.
->
-
## Wprowadzenie
OVHcloud udostępnia klientom VPS obrazy wstępnie zainstalowanych aplikacji, które umożliwiają szybkie i łatwe wdrożenie.
@@ -26,6 +22,10 @@ W [Panelu klienta OVHcloud](/links/manager) lub w API OVHcloud zainstaluj wybran
#### cPanel
+> [!warning]
+> Funkcja ta nie jest aktualnie dostępna dla prywatnych serwerów wirtualnych w [Local Zones](/links/bare-metal/vps-lz).
+>
+
Poniżej znajdziesz pierwsze kroki związane z uruchomieniem wstępnie zainstalowanego obrazu cPanel. Po wszystkich etapach oznaczone "\*" pojawi się FAQ.
1. Otwórz otrzymany e-mail zawierający dane do logowania do aplikacji.
@@ -57,6 +57,10 @@ Nie musisz wykonywać żadnych innych kroków, aby zakończyć pierwszą konfigu
#### Plesk
+> [!warning]
+> Funkcja ta nie jest aktualnie dostępna dla prywatnych serwerów wirtualnych w [Local Zones](/links/bare-metal/vps-lz).
+>
+
Poniżej znajdziesz pierwsze kroki związane z uruchomieniem wstępnie zainstalowanego obrazu Pleska. Po wszystkich etapach oznaczone "\*" pojawi się FAQ.
1. Otwórz otrzymany e-mail zawierający dane do logowania do aplikacji.
@@ -77,6 +81,10 @@ Nie musisz wykonywać żadnych innych kroków, aby zakończyć pierwszą konfigu
#### Docker
+> [!warning]
+> Funkcja ta nie jest aktualnie dostępna dla prywatnych serwerów wirtualnych w [Local Zones](/links/bare-metal/vps-lz).
+>
+
Poniżej znajdziesz pierwsze kroki związane z uruchomieniem wstępnie zainstalowanego obrazu Docker.
1. Połącz się z serwerem za pomocą SSH za pomocą nazwy użytkownika i hasła dostępnych w wiadomości e-mail.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.pt-pt.md b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.pt-pt.md
index 35279e6d712..20c154afb1d 100755
--- a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/guide.pt-pt.md
@@ -4,10 +4,6 @@ excerpt: Saiba como implementar aplicações pré-instaladas no seu VPS
updated: 2022-08-25
---
-> [!primary]
-> Esta tradução foi automaticamente gerada pelo nosso parceiro SYSTRAN. Em certos casos, poderão ocorrer formulações imprecisas, como por exemplo nomes de botões ou detalhes técnicos. Recomendamos que consulte a versão inglesa ou francesa do manual, caso tenha alguma dúvida. Se nos quiser ajudar a melhorar esta tradução, clique em "Contribuir" nesta página.
->
-
## Objetivo
A OVHcloud oferece aos clientes VPS imagens de aplicações pré-instaladas para uma implementação rápida e fácil em apenas alguns cliques.
@@ -26,6 +22,10 @@ A partir da [Área de Cliente OVHcloud](/links/manager) ou das API OVHcloud, ins
#### cPanel
+> [!warning]
+> Esta funcionalidade está atualmente indisponível para os servidores privados virtuais nas [Local Zones](/links/bare-metal/vps-lz).
+>
+
Encontrará abaixo as primeiras etapas relativas à implementação da imagem pré-instalada do cPanel. Os passos assinalados com "\*" serão seguidos de uma FAQ.
1. Abra o e-mail que recebeu com os dados de acesso à aplicação.
@@ -57,6 +57,10 @@ Não é necessário mais nenhuma etapa para terminar a primeira configuração d
#### Plesk
+> [!warning]
+> Esta funcionalidade está atualmente indisponível para os servidores privados virtuais nas [Local Zones](/links/bare-metal/vps-lz).
+>
+
Encontrará abaixo os primeiros passos para a implementação da imagem pré-instalada do Plesk. Os passos assinalados com "\*" serão seguidos de uma FAQ.
1. Abra o e-mail que recebeu com os dados de acesso à aplicação.
@@ -77,6 +81,10 @@ Não é necessário mais nenhuma etapa para terminar a primeira configuração d
#### Docker
+> [!warning]
+> Esta funcionalidade está atualmente indisponível para os servidores privados virtuais nas [Local Zones](/links/bare-metal/vps-lz).
+>
+
Encontrará abaixo os primeiros passos para a implementação da imagem pré-instalada do Docker.
1. Aceda ao servidor com o nome de utilizador e a palavra-passe presentes no e-mail.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/meta.yaml b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/meta.yaml
index 5a8c6d5b691..0678dc6fa12 100755
--- a/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/meta.yaml
+++ b/pages/bare_metal_cloud/virtual_private_servers/apps_first_steps/meta.yaml
@@ -1,2 +1,3 @@
id: 2470451f-e99c-4a7f-a42d-96510d081567
-full_slug: vps-pre-installed-applications
\ No newline at end of file
+full_slug: vps-pre-installed-applications
+translation_banner: true
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.de-de.md b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.de-de.md
index 1964d99a062..c3dbe7f07c6 100755
--- a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.de-de.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.de-de.md
@@ -16,6 +16,10 @@ Bei den VPS von OVHcloud können Sie einen sicheren Speicherplatz als Dienstopti
- Sie haben Zugriff auf Ihr [OVHcloud Kundencenter](/links/manager).
- Administrativer Zugriff via SSH oder RDP auf Ihren VPS.
+> [!warning]
+> Diese Funktion ist derzeit nicht verfügbar für VPS in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## In der praktischen Anwendung
Loggen Sie sich in Ihr [OVHcloud Kundencenter](/links/manager) ein, gehen Sie in den Bereich `Bare Metal Cloud`{.action} und wählen Sie Ihren Server in `Virtual Private Server`{.action} aus.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-asia.md b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-asia.md
index f5941fca335..72ce3fcaab7 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-asia.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-asia.md
@@ -16,6 +16,10 @@ With OVHcloud Virtual Private Servers you have the possibility to add a secure s
- Access to the [OVHcloud Control Panel](/links/manager)
- Administrative access via SSH or RDP to your VPS
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instructions
Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from `Virtual Private Servers`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-au.md b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-au.md
index f5941fca335..72ce3fcaab7 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-au.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-au.md
@@ -16,6 +16,10 @@ With OVHcloud Virtual Private Servers you have the possibility to add a secure s
- Access to the [OVHcloud Control Panel](/links/manager)
- Administrative access via SSH or RDP to your VPS
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instructions
Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from `Virtual Private Servers`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-ca.md b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-ca.md
index f5941fca335..72ce3fcaab7 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-ca.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-ca.md
@@ -16,6 +16,10 @@ With OVHcloud Virtual Private Servers you have the possibility to add a secure s
- Access to the [OVHcloud Control Panel](/links/manager)
- Administrative access via SSH or RDP to your VPS
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instructions
Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from `Virtual Private Servers`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-gb.md b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-gb.md
index ac8693a0f7b..4aedbebf995 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-gb.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-gb.md
@@ -16,6 +16,10 @@ With OVHcloud Virtual Private Servers you have the possibility to add a secure s
- Access to the [OVHcloud Control Panel](/links/manager)
- Administrative access via SSH or RDP to your VPS
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instructions
Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from `Virtual Private Servers`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-ie.md b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-ie.md
index f5941fca335..c61f66c9a14 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-ie.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-ie.md
@@ -16,6 +16,9 @@ With OVHcloud Virtual Private Servers you have the possibility to add a secure s
- Access to the [OVHcloud Control Panel](/links/manager)
- Administrative access via SSH or RDP to your VPS
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
## Instructions
Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from `Virtual Private Servers`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-sg.md b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-sg.md
index f5941fca335..72ce3fcaab7 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-sg.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-sg.md
@@ -16,6 +16,10 @@ With OVHcloud Virtual Private Servers you have the possibility to add a secure s
- Access to the [OVHcloud Control Panel](/links/manager)
- Administrative access via SSH or RDP to your VPS
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instructions
Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from `Virtual Private Servers`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-us.md b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-us.md
deleted file mode 100644
index f5941fca335..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.en-us.md
+++ /dev/null
@@ -1,302 +0,0 @@
----
-title: "How to configure an additional disk"
-excerpt: "Find out how to add and configure additional storage space on a VPS"
-updated: 2025-07-24
----
-
-## Objective
-
-With OVHcloud Virtual Private Servers you have the possibility to add a secure storage space as a service option. This storage is separated from the internal storage capacity of the VPS solution which makes it a secure place for your backups or other static data. The additional disk will only be accessible from the server's IP address and data stored on it will remain unaffected, even if the VPS is reinstalled or should suffer data loss.
-
-**This guide explains how to enable the additional disk option and configure the storage space for use with the VPS.**
-
-## Requirements
-
-- A [VPS](/links/bare-metal/vps) in your OVHcloud account
-- Access to the [OVHcloud Control Panel](/links/manager)
-- Administrative access via SSH or RDP to your VPS
-
-## Instructions
-
-Log in to the [OVHcloud Control Panel](/links/manager), go to the `Bare Metal Cloud`{.action} section and select your server from `Virtual Private Servers`{.action}.
-
-### Subscribing to the additional disk option
-
-After selecting your VPS, click on the `Additional disk`{.action} tab in the horizontal menu. Click on `Order an additional disk`{.action} and choose a disk size from the selection that appears.
-
-{.thumbnail}
-
-Take note of the pricing information, then click on `Order`{.action}. You will be guided through the order process and receive a confirmation email as soon as the disk is installed.
-
-### Mounting the new storage space
-
-> [!warning]
-> OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
->
-> This guide is designed to assist you in common tasks as much as possible. Nevertheless, we recommend contacting a [specialist service provider](/links/partner) or reaching out to [our community of users](/links/community) if you experience any issues.
->
-
-#### On a Linux VPS
-
-If a GNU/Linux distribution is installed on your VPS, establish an SSH connection to your server from the command line terminal or by using a SSH client application.
-
-The examples below presume you are logged in as a user with elevated permissions.
-
-You can use the following command to verify the name of the new device:
-
-```bash
-$ lsblk
-
-sda 8:0 0 80G 0 disk
-├─sda1 8:1 0 79.9G 0 part /
-├─sda14 8:14 0 4M 0 part
-└─sda15 8:15 0 106M 0 part /boot/efi
-sdb 8:16 0 50G 0 disk
-```
-
-In this example, the additional disk is named `sdb`.
-
-Execute `fdisk` to create a partition on the disk; when prompted, enter `n` for a new partition and accept the subsequent defaults by pressing Enter. Finally, use the `w` command to write the changes to the disk.
-
-```bash
-$ sudo fdisk /dev/sdb
-
-Welcome to fdisk (util-linux 2.34).
-Changes will remain in memory only, until you decide to write them.
-Be careful before using the write command.
-```
-
-```bash
-Command (m for help): n
-
-Partition type
- p primary (0 primary, 0 extended, 4 free)
- e extended (container for logical partitions)
-
-Select (default p):
-```
-
-```bash
-Partition number (1-4, default 1):
-
-First sector (2048-104857599, default 2048):
-Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-104857599, default 104857599):
-
-Created a new partition 1 of type 'Linux' and of size 50 GiB.
-```
-
-```bash
-Command (m for help): w
-
-The partition table has been altered.
-Calling ioctl() to re-read partition table.
-Syncing disks.
-```
-
-Now that the partition `sdb1` is created, you can format it with ext4:
-
-```bash
-$ sudo mkfs.ext4 /dev/sdb1
-
-Creating filesystem with 13106944 4k blocks and 3276800 inodes
-Filesystem UUID: a667d351-cf36-49f2-94b4-daf03d7a86a6
-Superblock backups stored on blocks:
-32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
-4096000, 7962624, 11239424
-
-Allocating group tables: done
-Writing inode tables: done
-Creating journal (65536 blocks): done
-Writing superblocks and filesystem accounting information: done
-```
-
-The final step is to mount the disk:
-
-```bash
-$ sudo mkdir /mnt/disk
-$ sudo mount /dev/sdb1 /mnt/disk
-```
-
-You can see in the last line that the additional disk is now mounted at `/mnt/disk`:
-
-```bash
-$ df -h
-Filesystem Size Used Avail Use% Mounted on
-udev 1.9G 0 1.9G 0% /dev
-tmpfs 385M 1.1M 384M 1% /run
-/dev/sda1 78G 2.4G 75G 4% /
-tmpfs 1.9G 0 1.9G 0% /dev/shm
-tmpfs 5.0M 0 5.0M 0% /run/lock
-tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
-/dev/sda15 105M 3.9M 101M 4% /boot/efi
-/dev/loop1 68M 68M 0 100% /snap/lxd/18150
-/dev/loop3 32M 32M 0 100% /snap/snapd/10707
-/dev/loop4 56M 56M 0 100% /snap/core18/1944
-/dev/loop5 70M 70M 0 100% /snap/lxd/19188
-tmpfs 385M 0 385M 0% /run/user/0
-/dev/loop6 56M 56M 0 100% /snap/core18/1988
-/dev/loop2 32M 32M 0 100% /snap/snapd/11036
-tmpfs 385M 0 385M 0% /run/user/1000
-/dev/sdb1 49G 53M 47G 1% /mnt/disk
-```
-
-> [!primary]
->
-This previous step is not persistent because the disk will be detached if the VPS is restarted. In order to automate the mounting process, the `fstab` file needs to be edited.
->
-
-First, retrieve the UUID (block ID) of the device:
-
-```bash
-$ sudo blkid
-/dev/sda1: LABEL="cloudimg-rootfs" UUID="e616a2cd-3c02-4c79-9823-9b1bb5c13b26" TYPE="ext4" PARTUUID="a44089a3-f407-41e6-b7a5-1ed7672cef20"
-/dev/sda15: LABEL_FATBOOT="UEFI" LABEL="UEFI" UUID="4411-1580" TYPE="vfat" PARTUUID="e1746ac7-80c1-4859-9b4d-fa6ce11b3ae9"
-/dev/loop1: TYPE="squashfs"
-/dev/loop2: TYPE="squashfs"
-/dev/loop3: TYPE="squashfs"
-/dev/loop4: TYPE="squashfs"
-/dev/loop5: TYPE="squashfs"
-/dev/loop6: TYPE="squashfs"
-/dev/sda14: PARTUUID="7d19a2c9-75df-443e-8301-0bb85931df7d"
-/dev/sdb1: UUID="87571b68-30e1-498b-a64c-49ec5cd4f31c" TYPE="ext4" PARTUUID="c965cbdf-01"
-```
-
-Open `/etc/fstab` with a text editor:
-
-```bash
-$ sudo nano /etc/fstab
-```
-
-Add the line below to the file and replace the UUID with your own:
-
-```console
-UUID=87571b68-30e1-498b-a64c-49ec5cd4f31c /mnt/disk ext4 nofail 0 0
-```
-
-Save and exit the editor. The disk should be automatically mounted after every reboot from now on.
-
-#### On a Windows VPS
-
-If a Windows OS is installed on your VPS, establish a remote desktop (RDP) connection to your server.
-
-Once logged in, right-click on the `Start Menu`{.action} button and open `Disk Management`{.action}.
-
-{.thumbnail}
-
-The new disk will be displayed as an unknown volume with unallocated space.
-
-{.thumbnail}
-
-If the disk is marked as offline here, it needs to be initialised first. You can use the [Windows GUI](#initDiskManagement) or the [DISKPART utility](#initDiskpart) to achieve this. Otherwise, proceed with [formatting the disk in Disk Management](#formatDiskManagement).
-
-##### **Initialising the disk in Disk Management**
-
-Right-click on the disk and select `Online`{.action}.
-
-{.thumbnail}
-
-Then right-click on the disk again and this time select `Initialise Disk`{.action}.
-
-{.thumbnail}
-
-Select `MBR`{.action} in the new window and click `OK`{.action}.
-
-{.thumbnail}
-
-##### **Initialising the disk with DISKPART**
-
-Right-click on the `Start Menu`{.action} button and open `Run`{.action}.
-
-{.thumbnail}
-
-Type `cmd` and click `OK`{.action} to open the command line application.
-
-{.thumbnail}
-
-At the command prompt, open DISKPART:
-
-```console
-C:\> diskpart
-```
-
-Use the following series of DISKPART commands to set the disk to online:
-
-```console
-DISKPART> san
-
-SAN Policy : Offline Shared
-```
-
-```console
-DISKPART> san policy = OnlineAll
-
-DiskPart successfully changed the SAN policy for the current operating system.
-
-- Implementation of the strategy on the extra disk:
-[Code] DISKPART> list disk
-
-Disk ### Status Size Free Dyn Gpt
--------- ------------- ------- ------- --- ---
-Disk 0 Online 200 GB 0 B
-* Disk 1 Offline 10 GB 1024 KB
-```
-
-```console
-DISKPART> select disk 1
-
-Disk 1 is now the selected disk.
-```
-
-```console
-DISKPART> attributes disk clear readonly
-
-Disk attributes cleared successfully.
-```
-
-```console
-DISKPART> attributes disk
-
-Current Read-only State : No
-Read-only : No
-Boot Disk : No
-Pagefile Disk : No
-Hibernation File Disk : No
-Crashdump Disk : No
-Clustered Disk : No
-```
-
-```console
-DISKPART> online disk
-
-DiskPart successfully onlined the selected disk.
-```
-
-##### **Formatting the disk**
-
-In `Disk Management`{.action}, right-click on the new disk and select `New Simple Volume...`{.action}.
-
-{.thumbnail}
-
-In the wizard, click `Next`{.action} to specify the volume size. It should be set to maximum by default. Click `Next`{.action} to continue.
-
-{.thumbnail}
-
-Leave the new drive letter at default or select a different one, then click `Next`{.action}.
-
-{.thumbnail}
-
-Label the volume (optional) and confirm the formatting options by clicking `Next`{.action}.
-
-{.thumbnail}
-
-In the last window, click `Finish`{.action} to format the disk. It will be available as a drive in File Explorer after the operation.
-
-### Cancelling the additional disk option
-
-From the `Home`{.action} tab, scroll down to the box labelled **Summary of options**. Click on `...`{.action} next to the option "Additional disks" and in the context menu click on `Cancel`{.action}.
-
-{.thumbnail}
-
-## Go further
-
-Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.es-es.md b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.es-es.md
index dea7597b672..3edff58b639 100755
--- a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.es-es.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.es-es.md
@@ -16,6 +16,10 @@ Con los VPS de OVHcloud, puede añadir un espacio de almacenamiento seguro como
- Haber iniciado sesión en el [área de cliente de OVHcloud](/links/manager).
- Tener acceso administrativo a su VPS por SSH o RDP.
+> [!warning]
+> Esta funcionalidad no está disponible actualmente para los servidores virtuales en las [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Procedimiento
Conéctese al [Panel de configuración de OVHcloud](/links/manager), acceda a la sección `Bare Metal Cloud`{.action} y seleccione el servidor en la sección `Servidores Privados Virtuales`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.es-us.md b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.es-us.md
index 3b4f40bee61..6ac89f33655 100755
--- a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.es-us.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.es-us.md
@@ -16,6 +16,10 @@ Con los VPS de OVHcloud, puede añadir un espacio de almacenamiento seguro como
- Haber iniciado sesión en el [área de cliente de OVHcloud](/links/manager).
- Tener acceso administrativo a su VPS por SSH o RDP.
+> [!warning]
+> Esta funcionalidad no está disponible actualmente para los servidores virtuales en las [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Procedimiento
Conéctese al [Panel de configuración de OVHcloud](/links/manager), acceda a la sección `Bare Metal Cloud`{.action} y seleccione el servidor en la sección `Servidores Privados Virtuales`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.fr-ca.md b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.fr-ca.md
index f03f8b9930c..ccc4d19261d 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.fr-ca.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.fr-ca.md
@@ -16,6 +16,10 @@ Avec les VPS OVHcloud, vous avez la possibilité d'ajouter un espace de stockage
- Être connecté à votre [espace client OVHcloud](/links/manager)
- Disposer d'un accès administratif via SSH ou RDP à votre VPS
+> [!warning]
+> Cette fonctionnalité est actuellement indisponible pour les serveurs privés virtuels dans les [Local Zones](/links/bare-metal/vps-lz).
+>
+
## En pratique
Connectez-vous à votre [espace client OVHcloud](/links/manager), rendez-vous dans la section `Bare Metal Cloud`{.action} et sélectionnez votre serveur sous la partie `Serveur privés virtuels`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.fr-fr.md b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.fr-fr.md
index f03f8b9930c..ccc4d19261d 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.fr-fr.md
@@ -16,6 +16,10 @@ Avec les VPS OVHcloud, vous avez la possibilité d'ajouter un espace de stockage
- Être connecté à votre [espace client OVHcloud](/links/manager)
- Disposer d'un accès administratif via SSH ou RDP à votre VPS
+> [!warning]
+> Cette fonctionnalité est actuellement indisponible pour les serveurs privés virtuels dans les [Local Zones](/links/bare-metal/vps-lz).
+>
+
## En pratique
Connectez-vous à votre [espace client OVHcloud](/links/manager), rendez-vous dans la section `Bare Metal Cloud`{.action} et sélectionnez votre serveur sous la partie `Serveur privés virtuels`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.it-it.md b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.it-it.md
index 25fc328a2e0..a0b26fe2667 100755
--- a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.it-it.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.it-it.md
@@ -16,6 +16,10 @@ Con i VPS OVHcloud è possibile aggiungere spazio di storage sicuro come opzione
- Avere accesso allo [Spazio Cliente OVHcloud](/links/manager)
- Avere accesso amministrativo via SSH o RDP al VPS
+> [!warning]
+> Questa funzionalità non è attualmente disponibile per i server privati virtuali nelle [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Procedura
Accedi allo [Spazio Cliente OVHcloud](/links/manager), clicca su `Bare Metal Cloud`{.action} e seleziona il tuo server nella sezione `Server Privati Virtuali`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.pl-pl.md b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.pl-pl.md
index 7bf0dff7313..8b38f3748e3 100755
--- a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.pl-pl.md
@@ -16,6 +16,10 @@ Wraz z ofertą VPS OVHcloud możesz dodać bezpieczną przestrzeń dyskową jako
- Zalogowanie do [Panelu klienta OVHcloud](/links/manager)
- Dostęp administracyjny przez SSH lub RDP do serwera VPS
+> [!warning]
+> Funkcja ta nie jest aktualnie dostępna dla prywatnych serwerów wirtualnych w [Local Zones](/links/bare-metal/vps-lz).
+>
+
## W praktyce
Zaloguj się do [Panelu client OVHcloud](/links/manager), przejdź do sekcji `Bare Metal Cloud`{.action} i wybierz Twój serwer w części `Prywatny serwer wirtualny`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.pt-pt.md b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.pt-pt.md
index cd5feaf22d3..58d6cfb604e 100755
--- a/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk/guide.pt-pt.md
@@ -16,6 +16,10 @@ Com os VPS OVHcloud, tem a possibilidade de adicionar um espaço de armazenament
- Estar ligado à [Área de Cliente OVHcloud](/links/manager)
- Ter acesso administrativo via SSH ou RDP ao VPS
+> [!warning]
+> Esta funcionalidade está atualmente indisponível para os servidores privados virtuais nas [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instruções
Ligue-se à sua [Área de Cliente OVHcloud](/links/manager), vá à secção `Bare Metal Cloud`{.action} e selecione o seu servidor na secção `Servidor privado virtual`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.de-de.md b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.de-de.md
index b8b86e76d11..e6e9c5fa708 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.de-de.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.de-de.md
@@ -1,7 +1,7 @@
---
title: "IP-Adresse als Alias konfigurieren"
excerpt: "Erfahren Sie hier, wie Sie Additional IPs in Ihre VPS-Konfiguration einbinden"
-updated: 2024-11-05
+updated: 2025-09-11
---
## Ziel
@@ -23,6 +23,10 @@ Bei *IP Aliasing* handelt es sich um eine spezielle Netzwerkkonfiguration für b
- Sie haben administrativen Zugriff (sudo) auf Ihren VPS über SSH oder GUI.
- Sie haben Grundkenntnisse in Administration und Netzwerkkonfiguration.
+> [!warning]
+> Additional IP-Adressen sind derzeit nicht verfügbar für VPS in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## In der praktischen Anwendung
Die folgenden Abschnitte enthalten die Konfigurationen für die am häufigsten verwendeten Distributionen/Betriebssysteme. Der erste Schritt ist immer die Anmeldung an Ihrem Server über SSH oder einen GUI-Login (RDP für einen Windows-VPS). Die folgenden Beispiele setzen voraus, dass Sie als Benutzer mit erhöhten Berechtigungen (Administrator/sudo) angemeldet sind.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-asia.md b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-asia.md
deleted file mode 100644
index da952afc4f2..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-asia.md
+++ /dev/null
@@ -1,488 +0,0 @@
----
-title: Configuring IP aliasing
-excerpt: Find out how to add Additional IP addresses to your VPS configuration
-updated: 2024-11-05
----
-
-## Objective
-
-IP aliasing refers to a special network configuration for certain OVHcloud services. Additional IPs allow you to associate multiple IP addresses with a single network interface.
-
-**This guide explains how to add Additional IP addresses to your network configuration.**
-
-> [!warning]
-> OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
->
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialist service provider](/links/partner) or reaching out to the [OVHcloud community](/links/community) if you encounter any difficulties.
->
-
-## Requirements
-
-- A [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account
-- An [Additional IP address](/links/bare-metal/ip)
-- Administrative access (sudo) via SSH or GUI to your server
-- Basic networking and administration knowledge
-
-## Instructions
-
-The following sections contain the configurations for the most commonly used distributions/operating systems. The first step is always to log in to your server via SSH or a GUI login session (RDP for a Windows VPS). The examples below presume you are logged in as a user with elevated permissions (Administrator/sudo).
-
-> [!primary]
->
-Concerning different distribution releases, please note that the proper procedure to configure your network interface as well as the file names may have been subject to change. We recommend to consult the manuals and knowledge resources of the respective OS versions if you experience any issues.
->
-
-**Please take note of the following terminology that will be used in code examples and instructions of the guide sections below:**
-
-|Term|Description|Examples|
-|---|---|---|
-|ADDITIONAL_IP|An Additional IP address assigned to your service|203.0.113.0|
-|NETWORK_INTERFACE|The name of the network interface|*eth0*, *ens3*|
-|ID|ID of the IP alias, starting with *0* (depending on the number of additional IPs there are to configure)|*0*, *1*|
-
-### Debian 11
-
-#### Step 1: Disable automatic network configuration
-
-Open the following file path with a text editor, in our example, we are using `nano`.
-
-```bash
-sudo nano /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
-```
-Enter the following line, then save and exit the editor.
-
-```console
-network: {config: disabled}
-```
-Creating this configuration file will prevent changes to your network configuration from being made automatically.
-
-#### Step 2: Create a backup
-
-By default, the configuration file is located in the path `etc\network\interfaces.d`.
-
-In our example, our file is called `50-cloud-init`, so we make a copy of the `50-cloud-init` file using the following command:
-
-```bash
-sudo cp /etc/network/interfaces.d/50-cloud-init /etc/network/interfaces.d/50-cloud-init.bak
-```
-
-In case of a mistake, you will be able to revert the changes, using the commands below:
-
-```bash
-sudo rm -f /etc/network/interfaces.d/50-cloud-init
-sudo cp /etc/network/interfaces.d/50-cloud-init.bak /etc/network/interfaces.d/50-cloud-init
-```
-#### Step 3: Edit the configuration file
-
-The first step is to verify your network interface name with this command:
-
-```bash
-ip a
-```
-
-Next, open the network configuration file for editing with the following command:
-
-```bash
-sudo nano /etc/network/interfaces.d/50-cloud-init
-```
-
-To configure your Additional IP, you need to add a virtual interface or ethernet alias to your network interface. In our example, our interface is called `eth0`, so our first alias is `eth0:0`. Do this for each Additional IP you wish to configure.
-
-Do not modify the existing lines in the configuration file, simply add your Additional IP to the file as follows, replacing `NETWORK_INTERFACE`, `ID` and `ADDITIONAL_IP` wih your own values:
-
-
-```console
-auto NETWORK_INTERFACE:ID
-iface NETWORK_INTERFACE:ID inet static
-address ADDITIONAL_IP
-netmask 255.255.255.255
-```
-
-If you are configuring more than one Additional IP, your configuration file should look like this:
-
-```console
-auto NETWORK_INTERFACE:ID
-iface NETWORK_INTERFACE:ID inet static
-address ADDITIONAL_IP1
-address ADDITIONAL_IP2
-netmask 255.255.255.255
-```
-
-**Configuration example:**
-
-```console
-auto eth0:0
-iface eth0:0 inet static
-address 203.0.113.0
-netmask 255.255.255.255
-```
-
-#### Step 4: Restart the interface
-
-Apply the changes with the following command:
-
-```bash
-sudo systemctl restart networking
-```
-
-### Debian 12, Ubuntu 20.04 and following
-
-The configuration file for your Additional IP addresses is located in the folder `/etc/netplan/`. In this example it is called `50-cloud-init.yaml`.
-
-The best practice approach is to create a separate configuration file to set up Additional IP addresses. This way, you can easily revert the changes in case of an error.
-
-#### Step 1: Create the network configuration file
-
-In our example, our file is call `51-cloud-init.yaml`:
-
-```bash
-sudo touch /etc/netplan/51-cloud-init.yaml
-```
-
-#### Step 2: Edit the configuration file
-
-You can verify your network interface name with this command:
-
-```bash
-ip a
-```
-
-Next, open the network configuration file for editing with the following command:
-
-```bash
-sudo nano /etc/netplan/51-cloud-init.yaml
-```
-
-Edit the file with the content below, replacing `INTERFACE_NAME` and `ADDITIONAL_IP` with your own values:
-
-```yaml
-network:
- version: 2
- ethernets:
- INTERFACE_NAME:
- dhcp4: true
- addresses:
- - ADDITIONAL_IP/32
-```
-
-If you have more Additional IPs to configure, the configuration file should look like this:
-
-```yaml
-network:
- version: 2
- ethernets:
- INTERFACE_NAME:
- dhcp4: true
- addresses:
- - ADDITIONAL_IP1/32
- - ADDITIONAL_IP2/32
-```
-
-> [!warning]
->
-> It is important to respect the alignment of each element in this file as represented in the example above. Do not use the tab key to create your spacing.
->
-
-**Configuration example:**
-
-```yaml
-network:
- version: 2
- ethernets:
- eth0:
- dhcp4: true
- addresses:
- - 203.0.113.0/32
-```
-
-Save and close the file.
-
-#### Step 3: Apply the new network configuration
-
-You can test your configuration using this command:
-
-```bash
-sudo netplan try
-```
-
-If it is correct, apply it using the following command:
-
-```bash
-sudo netplan apply
-```
-
-### AlmaLinux (8 & 9), Rocky Linux (8 & 9)
-
-The main configuration file is located in `/etc/sysconfig/network-scripts/`. In this example it is called `ifcfg-eth0`. Before making changes, verify the actual file name in this folder.
-
-For each Additional IP to be configured, we create a seperate configuration file with the following parameters: `ifcfg-NETWORK_INTERFACE:ID`. Where `NETWORK_INTERFACE` is the physical interface and `ID` is the virtual network interface or ethernet alias starting with a value of 0. For example, for our interface named `eth0` the first alias is `eth0:0`, the second alias is `eth0:1`, etc...
-
-#### Step 1: Determine the interface
-
-```bash
-ip a
-```
-
-#### Step 2: Create the configuration file
-
-First, create the configuration file. Replace `NETWORK_INTERFACE:ID` with your own values.
-
-```bash
-sudo nano /etc/sysconfig/network-scripts/ifcfg-NETWORK_INTERFACE:ID
-```
-
-Next, edit the file with the content below, replacing `NETWORK_INTERFACE:ID`, and `ADDITIONAL_IP` with your own values:
-
-```console
-DEVICE=NETWORK_INTERFACE:ID
-ONBOOT=yes
-BOOTPROTO=none # For CentOS use "static"
-IPADDR=ADDITIONAL_IP
-NETMASK=255.255.255.255
-BROADCAST=ADDITIONAL_IP
-```
-
-**Configuration example:**
-
-```console
-DEVICE=eth0:0
-ONBOOT=yes
-BOOTPROTO=none # For CentOS use "static"
-IPADDR=203.0.113.0
-NETMASK=255.255.255.255
-BROADCAST=203.0.113.0
-```
-
-#### Step 3: Restart the interface
-
-```bash
-sudo systemctl restart network
-```
-
-#### For AlmaLinux and Rocky Linux
-
-```bash
-sudo systemctl restart NetworkManager
-```
-
-### Fedora 37 and following
-
-Fedora now uses keyfiles. NetworkManager previously stored network profiles in ifcfg format in this directory: `/etc/sysconfig/network-scripts/`. However, the ifcfg format is now deprecated. By default, NetworkManager no longer creates new profiles in this format. The configuration file is now found in `/etc/NetworkManager/system-connections/`.
-
-#### Step 1: Create a backup
-
-In our example, our file is called `cloud-init-eno1.nmconnection`, so we make a copy of the `cloud-init-eno1.nmconnection` file using the following command:
-
-```bash
-sudo cp -r /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak
-```
-
-In case of a mistake, you will be able to revert the changes, using the commands below:
-
-```bash
-sudo rm -f /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-sudo cp /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-```
-
-#### Step 2: Edit the config file
-
-> [!primary]
-> Please note that the name of the network file in our example may differ from yours. Please adapt the commands to your file name.
->
-
-```bash
-sudo nano /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-```
-
-Do not modify the existing lines in the configuration file, add your Additional IP to the file as follows, replacing `ADDITIONAL_IP/32` wih your own values:
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=ADDITIONAL_IP/32
-```
-
-If you have two Additional IPs to configure, the configuration should look like this:
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=ADDITIONAL_IP1/32
-address2=ADDITIONAL_IP2/32
-```
-
-**Configuration example:**
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=203.0.113.0/32
-```
-
-#### Step 3: Restart the interface
-
-You now need to restart your interface:
-
-```bash
-sudo systemctl restart NetworkManager
-```
-
-### cPanel
-
-#### Step 1: Access the WHM IP management section
-
-In the WHM control panel, click on `IP Functions`{.action} and select `Add a New IP Address`{.action} in the left-hand sidebar.
-
-{.thumbnail}
-
-#### Step 2: Add the Additional IP information
-
-Enter your Additional IP in the form `xxx.xxx.xxx.xxx` into the field “New IP or IP range to add”.
-
-Select `255.255.255.255` as your subnet mask, then click on `Submit`{.action}.
-
-{.thumbnail}
-
-> [!warning]
->
-> Please note that if you have more than one IP to configure on the same block and you add them all at once, the WHM system will force you to use the subnet mask `255.255.255.0`. We do not recommend using this configuration. Instead, you need to add each IP individually in order to use the proper subnet mask `255.255.255.255`.
->
-
-#### Step 3: Check the current IP configuration
-
-Back in the section `IP Functions`{.action}, click on `Show or Delete Current IP Addresses`{.action} to verify that the Additional IP address was added correctly.
-
-{.thumbnail}
-
-### Plesk
-
-#### Step 1: Access the Plesk IP management section
-
-In the Plesk control panel, choose `Tools & Settings`{.action} from the left-hand sidebar.
-
-{.thumbnail}
-
-Click on `IP Addresses`{.action} under **Tools & Resources**.
-
-#### Step 2: Add the additional IP information
-
-In this section, click on the button `Add IP Address`{.action}.
-
-{.thumbnail}
-
-Enter your Additional IP in the form `xxx.xxx.xxx.xxx/32` into the field "IP address and subnet mask", then click on `OK`{.action}.
-
-{.thumbnail}
-
-#### Step 3: Check the current IP configuration
-
-Back in the section "IP Addresses", verify that the Additional IP address was added correctly.
-
-{.thumbnail}
-
-### Windows Servers
-
-#### Step 1: Verify the network configuration
-
-Right-click on the `Start Menu`{.action} button and open `Run`{.action}.
-
-Type `cmd` and click `OK`{.action} to open the command line application.
-
-{.thumbnail}
-
-In order to retrieve the current IP configuration, enter `ipconfig` at the command prompt.
-
-```console
-C:\Users\Administrator>ipconfig
-
-Windows IP Configuration
-
-
-Ethernet adapter Ethernet:
-
- Connection-specific DNS Suffix . : openstacklocal
- Link-local IPv6 Address . . . . . : fe90::30gf:258a:84d6:abcf%5
- IPv4 Address. . . . . . . . . . . : 192.0.2.29
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- Default Gateway . . . . . . . . . : 192.0.2.1
-```
-
-#### Step 2: Change the IPv4 Properties
-
-Now you need to change the IP properties to a static configuration.
-
-1. Go to `Start`{.action}> `Control Panel`{.action}>` Network and Internet`{.action}> `Network and Sharing Centre`{.action}> `Change Adapter Settings`{.action}(in the left-hand menu).
-2. Right-click on `Ethernet`{.action}.
-3. Click on `Properties`{.action}.
-4. Select `Internet Protocol Version 4 (TCP/IPv4)`{.action}, then click on `Properties`{.action}.
-5. Click on `Use the following IP address`{.action} and type in your server’s primary IP, subnet mask and default gateway information obtained by using the `ipconfig`{.action} command above. In the "Preferred DNS Server" box, type `213.186.33.99`.
-
-
-{.thumbnail}
-
-> [!warning]
->
-> Be careful – the server will no longer be accessible if you enter incorrect information. You will then have to make the corrections in the KVM.
->
-
-Once done, click on `Advanced`{.action}.
-
-#### Step 3: Add the Additional IP in the "Advanced TCP/IP Settings"
-
-In the new window, click on `Add...`{.action} under "IP addresses". Enter your Additional IP address and the subnet mask (255.255.255.255).
-
-{.thumbnail}
-
-Confirm by clicking on `Add`{.action}.
-
-{.thumbnail}
-
-Once done, click on `OK`{.action} to apply the configuration.
-
-{.thumbnail}
-
-You will lose the connection to the server for a few seconds.
-
-#### Step 4: Check the new network configuration
-
-Open the command prompt (cmd) and enter `ipconfig`. The configuration should now include the new Additional IP address.
-
-```console
-C:\Users\Administrator>ipconfig
-
-Windows IP Configuration
-
-
-Ethernet adapter Ethernet:
-
- Connection-specific DNS Suffix . :
- Link-local IPv6 Address . . . . . : fe90::30gf:258a:84d6:abcf%5
- IPv4 Address. . . . . . . . . . . : 192.0.2.29
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- IPv4 Address. . . . . . . . . . . : 203.0.113.0
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- Default Gateway . . . . . . . . . : 192.0.2.1
-```
-
-### Troubleshooting
-
-First, restart your server from the command line or its GUI. If you are still unable to establish a connection from the public network to your alias IP and suspect a network problem, you need to reboot the server in [rescue mode](/pages/bare_metal_cloud/virtual_private_servers/rescue). Then you can set up the Additional IP address directly on the server.
-
-Once you are connected to your server via SSH, enter the following command:
-
-```bash
-ifconfig ens3:0 ADDITIONAL_IP netmask 255.255.255.255 broadcast ADDITIONAL_IP up
-```
-
-To test the connection, simply ping your Additional IP from the outside. If it responds in rescue mode, that probably means that there is a configuration error. If, however, the IP is still not working, please inform our support teams by creating a [support request](https://help.ovhcloud.com/csm?id=csm_get_help) for further investigations.
-
-## Go further
-
-[Activating Rescue Mode on VPS](/pages/bare_metal_cloud/virtual_private_servers/rescue)
-
-If you would like assistance using and configuring your OVHcloud solutions, please refer to our [support offers](/links/support).
-
-Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-au.md b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-au.md
deleted file mode 100644
index da952afc4f2..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-au.md
+++ /dev/null
@@ -1,488 +0,0 @@
----
-title: Configuring IP aliasing
-excerpt: Find out how to add Additional IP addresses to your VPS configuration
-updated: 2024-11-05
----
-
-## Objective
-
-IP aliasing refers to a special network configuration for certain OVHcloud services. Additional IPs allow you to associate multiple IP addresses with a single network interface.
-
-**This guide explains how to add Additional IP addresses to your network configuration.**
-
-> [!warning]
-> OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
->
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialist service provider](/links/partner) or reaching out to the [OVHcloud community](/links/community) if you encounter any difficulties.
->
-
-## Requirements
-
-- A [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account
-- An [Additional IP address](/links/bare-metal/ip)
-- Administrative access (sudo) via SSH or GUI to your server
-- Basic networking and administration knowledge
-
-## Instructions
-
-The following sections contain the configurations for the most commonly used distributions/operating systems. The first step is always to log in to your server via SSH or a GUI login session (RDP for a Windows VPS). The examples below presume you are logged in as a user with elevated permissions (Administrator/sudo).
-
-> [!primary]
->
-Concerning different distribution releases, please note that the proper procedure to configure your network interface as well as the file names may have been subject to change. We recommend to consult the manuals and knowledge resources of the respective OS versions if you experience any issues.
->
-
-**Please take note of the following terminology that will be used in code examples and instructions of the guide sections below:**
-
-|Term|Description|Examples|
-|---|---|---|
-|ADDITIONAL_IP|An Additional IP address assigned to your service|203.0.113.0|
-|NETWORK_INTERFACE|The name of the network interface|*eth0*, *ens3*|
-|ID|ID of the IP alias, starting with *0* (depending on the number of additional IPs there are to configure)|*0*, *1*|
-
-### Debian 11
-
-#### Step 1: Disable automatic network configuration
-
-Open the following file path with a text editor, in our example, we are using `nano`.
-
-```bash
-sudo nano /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
-```
-Enter the following line, then save and exit the editor.
-
-```console
-network: {config: disabled}
-```
-Creating this configuration file will prevent changes to your network configuration from being made automatically.
-
-#### Step 2: Create a backup
-
-By default, the configuration file is located in the path `etc\network\interfaces.d`.
-
-In our example, our file is called `50-cloud-init`, so we make a copy of the `50-cloud-init` file using the following command:
-
-```bash
-sudo cp /etc/network/interfaces.d/50-cloud-init /etc/network/interfaces.d/50-cloud-init.bak
-```
-
-In case of a mistake, you will be able to revert the changes, using the commands below:
-
-```bash
-sudo rm -f /etc/network/interfaces.d/50-cloud-init
-sudo cp /etc/network/interfaces.d/50-cloud-init.bak /etc/network/interfaces.d/50-cloud-init
-```
-#### Step 3: Edit the configuration file
-
-The first step is to verify your network interface name with this command:
-
-```bash
-ip a
-```
-
-Next, open the network configuration file for editing with the following command:
-
-```bash
-sudo nano /etc/network/interfaces.d/50-cloud-init
-```
-
-To configure your Additional IP, you need to add a virtual interface or ethernet alias to your network interface. In our example, our interface is called `eth0`, so our first alias is `eth0:0`. Do this for each Additional IP you wish to configure.
-
-Do not modify the existing lines in the configuration file, simply add your Additional IP to the file as follows, replacing `NETWORK_INTERFACE`, `ID` and `ADDITIONAL_IP` wih your own values:
-
-
-```console
-auto NETWORK_INTERFACE:ID
-iface NETWORK_INTERFACE:ID inet static
-address ADDITIONAL_IP
-netmask 255.255.255.255
-```
-
-If you are configuring more than one Additional IP, your configuration file should look like this:
-
-```console
-auto NETWORK_INTERFACE:ID
-iface NETWORK_INTERFACE:ID inet static
-address ADDITIONAL_IP1
-address ADDITIONAL_IP2
-netmask 255.255.255.255
-```
-
-**Configuration example:**
-
-```console
-auto eth0:0
-iface eth0:0 inet static
-address 203.0.113.0
-netmask 255.255.255.255
-```
-
-#### Step 4: Restart the interface
-
-Apply the changes with the following command:
-
-```bash
-sudo systemctl restart networking
-```
-
-### Debian 12, Ubuntu 20.04 and following
-
-The configuration file for your Additional IP addresses is located in the folder `/etc/netplan/`. In this example it is called `50-cloud-init.yaml`.
-
-The best practice approach is to create a separate configuration file to set up Additional IP addresses. This way, you can easily revert the changes in case of an error.
-
-#### Step 1: Create the network configuration file
-
-In our example, our file is call `51-cloud-init.yaml`:
-
-```bash
-sudo touch /etc/netplan/51-cloud-init.yaml
-```
-
-#### Step 2: Edit the configuration file
-
-You can verify your network interface name with this command:
-
-```bash
-ip a
-```
-
-Next, open the network configuration file for editing with the following command:
-
-```bash
-sudo nano /etc/netplan/51-cloud-init.yaml
-```
-
-Edit the file with the content below, replacing `INTERFACE_NAME` and `ADDITIONAL_IP` with your own values:
-
-```yaml
-network:
- version: 2
- ethernets:
- INTERFACE_NAME:
- dhcp4: true
- addresses:
- - ADDITIONAL_IP/32
-```
-
-If you have more Additional IPs to configure, the configuration file should look like this:
-
-```yaml
-network:
- version: 2
- ethernets:
- INTERFACE_NAME:
- dhcp4: true
- addresses:
- - ADDITIONAL_IP1/32
- - ADDITIONAL_IP2/32
-```
-
-> [!warning]
->
-> It is important to respect the alignment of each element in this file as represented in the example above. Do not use the tab key to create your spacing.
->
-
-**Configuration example:**
-
-```yaml
-network:
- version: 2
- ethernets:
- eth0:
- dhcp4: true
- addresses:
- - 203.0.113.0/32
-```
-
-Save and close the file.
-
-#### Step 3: Apply the new network configuration
-
-You can test your configuration using this command:
-
-```bash
-sudo netplan try
-```
-
-If it is correct, apply it using the following command:
-
-```bash
-sudo netplan apply
-```
-
-### AlmaLinux (8 & 9), Rocky Linux (8 & 9)
-
-The main configuration file is located in `/etc/sysconfig/network-scripts/`. In this example it is called `ifcfg-eth0`. Before making changes, verify the actual file name in this folder.
-
-For each Additional IP to be configured, we create a seperate configuration file with the following parameters: `ifcfg-NETWORK_INTERFACE:ID`. Where `NETWORK_INTERFACE` is the physical interface and `ID` is the virtual network interface or ethernet alias starting with a value of 0. For example, for our interface named `eth0` the first alias is `eth0:0`, the second alias is `eth0:1`, etc...
-
-#### Step 1: Determine the interface
-
-```bash
-ip a
-```
-
-#### Step 2: Create the configuration file
-
-First, create the configuration file. Replace `NETWORK_INTERFACE:ID` with your own values.
-
-```bash
-sudo nano /etc/sysconfig/network-scripts/ifcfg-NETWORK_INTERFACE:ID
-```
-
-Next, edit the file with the content below, replacing `NETWORK_INTERFACE:ID`, and `ADDITIONAL_IP` with your own values:
-
-```console
-DEVICE=NETWORK_INTERFACE:ID
-ONBOOT=yes
-BOOTPROTO=none # For CentOS use "static"
-IPADDR=ADDITIONAL_IP
-NETMASK=255.255.255.255
-BROADCAST=ADDITIONAL_IP
-```
-
-**Configuration example:**
-
-```console
-DEVICE=eth0:0
-ONBOOT=yes
-BOOTPROTO=none # For CentOS use "static"
-IPADDR=203.0.113.0
-NETMASK=255.255.255.255
-BROADCAST=203.0.113.0
-```
-
-#### Step 3: Restart the interface
-
-```bash
-sudo systemctl restart network
-```
-
-#### For AlmaLinux and Rocky Linux
-
-```bash
-sudo systemctl restart NetworkManager
-```
-
-### Fedora 37 and following
-
-Fedora now uses keyfiles. NetworkManager previously stored network profiles in ifcfg format in this directory: `/etc/sysconfig/network-scripts/`. However, the ifcfg format is now deprecated. By default, NetworkManager no longer creates new profiles in this format. The configuration file is now found in `/etc/NetworkManager/system-connections/`.
-
-#### Step 1: Create a backup
-
-In our example, our file is called `cloud-init-eno1.nmconnection`, so we make a copy of the `cloud-init-eno1.nmconnection` file using the following command:
-
-```bash
-sudo cp -r /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak
-```
-
-In case of a mistake, you will be able to revert the changes, using the commands below:
-
-```bash
-sudo rm -f /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-sudo cp /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-```
-
-#### Step 2: Edit the config file
-
-> [!primary]
-> Please note that the name of the network file in our example may differ from yours. Please adapt the commands to your file name.
->
-
-```bash
-sudo nano /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-```
-
-Do not modify the existing lines in the configuration file, add your Additional IP to the file as follows, replacing `ADDITIONAL_IP/32` wih your own values:
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=ADDITIONAL_IP/32
-```
-
-If you have two Additional IPs to configure, the configuration should look like this:
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=ADDITIONAL_IP1/32
-address2=ADDITIONAL_IP2/32
-```
-
-**Configuration example:**
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=203.0.113.0/32
-```
-
-#### Step 3: Restart the interface
-
-You now need to restart your interface:
-
-```bash
-sudo systemctl restart NetworkManager
-```
-
-### cPanel
-
-#### Step 1: Access the WHM IP management section
-
-In the WHM control panel, click on `IP Functions`{.action} and select `Add a New IP Address`{.action} in the left-hand sidebar.
-
-{.thumbnail}
-
-#### Step 2: Add the Additional IP information
-
-Enter your Additional IP in the form `xxx.xxx.xxx.xxx` into the field “New IP or IP range to add”.
-
-Select `255.255.255.255` as your subnet mask, then click on `Submit`{.action}.
-
-{.thumbnail}
-
-> [!warning]
->
-> Please note that if you have more than one IP to configure on the same block and you add them all at once, the WHM system will force you to use the subnet mask `255.255.255.0`. We do not recommend using this configuration. Instead, you need to add each IP individually in order to use the proper subnet mask `255.255.255.255`.
->
-
-#### Step 3: Check the current IP configuration
-
-Back in the section `IP Functions`{.action}, click on `Show or Delete Current IP Addresses`{.action} to verify that the Additional IP address was added correctly.
-
-{.thumbnail}
-
-### Plesk
-
-#### Step 1: Access the Plesk IP management section
-
-In the Plesk control panel, choose `Tools & Settings`{.action} from the left-hand sidebar.
-
-{.thumbnail}
-
-Click on `IP Addresses`{.action} under **Tools & Resources**.
-
-#### Step 2: Add the additional IP information
-
-In this section, click on the button `Add IP Address`{.action}.
-
-{.thumbnail}
-
-Enter your Additional IP in the form `xxx.xxx.xxx.xxx/32` into the field "IP address and subnet mask", then click on `OK`{.action}.
-
-{.thumbnail}
-
-#### Step 3: Check the current IP configuration
-
-Back in the section "IP Addresses", verify that the Additional IP address was added correctly.
-
-{.thumbnail}
-
-### Windows Servers
-
-#### Step 1: Verify the network configuration
-
-Right-click on the `Start Menu`{.action} button and open `Run`{.action}.
-
-Type `cmd` and click `OK`{.action} to open the command line application.
-
-{.thumbnail}
-
-In order to retrieve the current IP configuration, enter `ipconfig` at the command prompt.
-
-```console
-C:\Users\Administrator>ipconfig
-
-Windows IP Configuration
-
-
-Ethernet adapter Ethernet:
-
- Connection-specific DNS Suffix . : openstacklocal
- Link-local IPv6 Address . . . . . : fe90::30gf:258a:84d6:abcf%5
- IPv4 Address. . . . . . . . . . . : 192.0.2.29
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- Default Gateway . . . . . . . . . : 192.0.2.1
-```
-
-#### Step 2: Change the IPv4 Properties
-
-Now you need to change the IP properties to a static configuration.
-
-1. Go to `Start`{.action}> `Control Panel`{.action}>` Network and Internet`{.action}> `Network and Sharing Centre`{.action}> `Change Adapter Settings`{.action}(in the left-hand menu).
-2. Right-click on `Ethernet`{.action}.
-3. Click on `Properties`{.action}.
-4. Select `Internet Protocol Version 4 (TCP/IPv4)`{.action}, then click on `Properties`{.action}.
-5. Click on `Use the following IP address`{.action} and type in your server’s primary IP, subnet mask and default gateway information obtained by using the `ipconfig`{.action} command above. In the "Preferred DNS Server" box, type `213.186.33.99`.
-
-
-{.thumbnail}
-
-> [!warning]
->
-> Be careful – the server will no longer be accessible if you enter incorrect information. You will then have to make the corrections in the KVM.
->
-
-Once done, click on `Advanced`{.action}.
-
-#### Step 3: Add the Additional IP in the "Advanced TCP/IP Settings"
-
-In the new window, click on `Add...`{.action} under "IP addresses". Enter your Additional IP address and the subnet mask (255.255.255.255).
-
-{.thumbnail}
-
-Confirm by clicking on `Add`{.action}.
-
-{.thumbnail}
-
-Once done, click on `OK`{.action} to apply the configuration.
-
-{.thumbnail}
-
-You will lose the connection to the server for a few seconds.
-
-#### Step 4: Check the new network configuration
-
-Open the command prompt (cmd) and enter `ipconfig`. The configuration should now include the new Additional IP address.
-
-```console
-C:\Users\Administrator>ipconfig
-
-Windows IP Configuration
-
-
-Ethernet adapter Ethernet:
-
- Connection-specific DNS Suffix . :
- Link-local IPv6 Address . . . . . : fe90::30gf:258a:84d6:abcf%5
- IPv4 Address. . . . . . . . . . . : 192.0.2.29
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- IPv4 Address. . . . . . . . . . . : 203.0.113.0
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- Default Gateway . . . . . . . . . : 192.0.2.1
-```
-
-### Troubleshooting
-
-First, restart your server from the command line or its GUI. If you are still unable to establish a connection from the public network to your alias IP and suspect a network problem, you need to reboot the server in [rescue mode](/pages/bare_metal_cloud/virtual_private_servers/rescue). Then you can set up the Additional IP address directly on the server.
-
-Once you are connected to your server via SSH, enter the following command:
-
-```bash
-ifconfig ens3:0 ADDITIONAL_IP netmask 255.255.255.255 broadcast ADDITIONAL_IP up
-```
-
-To test the connection, simply ping your Additional IP from the outside. If it responds in rescue mode, that probably means that there is a configuration error. If, however, the IP is still not working, please inform our support teams by creating a [support request](https://help.ovhcloud.com/csm?id=csm_get_help) for further investigations.
-
-## Go further
-
-[Activating Rescue Mode on VPS](/pages/bare_metal_cloud/virtual_private_servers/rescue)
-
-If you would like assistance using and configuring your OVHcloud solutions, please refer to our [support offers](/links/support).
-
-Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-ca.md b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-ca.md
deleted file mode 100644
index da952afc4f2..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-ca.md
+++ /dev/null
@@ -1,488 +0,0 @@
----
-title: Configuring IP aliasing
-excerpt: Find out how to add Additional IP addresses to your VPS configuration
-updated: 2024-11-05
----
-
-## Objective
-
-IP aliasing refers to a special network configuration for certain OVHcloud services. Additional IPs allow you to associate multiple IP addresses with a single network interface.
-
-**This guide explains how to add Additional IP addresses to your network configuration.**
-
-> [!warning]
-> OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
->
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialist service provider](/links/partner) or reaching out to the [OVHcloud community](/links/community) if you encounter any difficulties.
->
-
-## Requirements
-
-- A [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account
-- An [Additional IP address](/links/bare-metal/ip)
-- Administrative access (sudo) via SSH or GUI to your server
-- Basic networking and administration knowledge
-
-## Instructions
-
-The following sections contain the configurations for the most commonly used distributions/operating systems. The first step is always to log in to your server via SSH or a GUI login session (RDP for a Windows VPS). The examples below presume you are logged in as a user with elevated permissions (Administrator/sudo).
-
-> [!primary]
->
-Concerning different distribution releases, please note that the proper procedure to configure your network interface as well as the file names may have been subject to change. We recommend to consult the manuals and knowledge resources of the respective OS versions if you experience any issues.
->
-
-**Please take note of the following terminology that will be used in code examples and instructions of the guide sections below:**
-
-|Term|Description|Examples|
-|---|---|---|
-|ADDITIONAL_IP|An Additional IP address assigned to your service|203.0.113.0|
-|NETWORK_INTERFACE|The name of the network interface|*eth0*, *ens3*|
-|ID|ID of the IP alias, starting with *0* (depending on the number of additional IPs there are to configure)|*0*, *1*|
-
-### Debian 11
-
-#### Step 1: Disable automatic network configuration
-
-Open the following file path with a text editor, in our example, we are using `nano`.
-
-```bash
-sudo nano /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
-```
-Enter the following line, then save and exit the editor.
-
-```console
-network: {config: disabled}
-```
-Creating this configuration file will prevent changes to your network configuration from being made automatically.
-
-#### Step 2: Create a backup
-
-By default, the configuration file is located in the path `etc\network\interfaces.d`.
-
-In our example, our file is called `50-cloud-init`, so we make a copy of the `50-cloud-init` file using the following command:
-
-```bash
-sudo cp /etc/network/interfaces.d/50-cloud-init /etc/network/interfaces.d/50-cloud-init.bak
-```
-
-In case of a mistake, you will be able to revert the changes, using the commands below:
-
-```bash
-sudo rm -f /etc/network/interfaces.d/50-cloud-init
-sudo cp /etc/network/interfaces.d/50-cloud-init.bak /etc/network/interfaces.d/50-cloud-init
-```
-#### Step 3: Edit the configuration file
-
-The first step is to verify your network interface name with this command:
-
-```bash
-ip a
-```
-
-Next, open the network configuration file for editing with the following command:
-
-```bash
-sudo nano /etc/network/interfaces.d/50-cloud-init
-```
-
-To configure your Additional IP, you need to add a virtual interface or ethernet alias to your network interface. In our example, our interface is called `eth0`, so our first alias is `eth0:0`. Do this for each Additional IP you wish to configure.
-
-Do not modify the existing lines in the configuration file, simply add your Additional IP to the file as follows, replacing `NETWORK_INTERFACE`, `ID` and `ADDITIONAL_IP` wih your own values:
-
-
-```console
-auto NETWORK_INTERFACE:ID
-iface NETWORK_INTERFACE:ID inet static
-address ADDITIONAL_IP
-netmask 255.255.255.255
-```
-
-If you are configuring more than one Additional IP, your configuration file should look like this:
-
-```console
-auto NETWORK_INTERFACE:ID
-iface NETWORK_INTERFACE:ID inet static
-address ADDITIONAL_IP1
-address ADDITIONAL_IP2
-netmask 255.255.255.255
-```
-
-**Configuration example:**
-
-```console
-auto eth0:0
-iface eth0:0 inet static
-address 203.0.113.0
-netmask 255.255.255.255
-```
-
-#### Step 4: Restart the interface
-
-Apply the changes with the following command:
-
-```bash
-sudo systemctl restart networking
-```
-
-### Debian 12, Ubuntu 20.04 and following
-
-The configuration file for your Additional IP addresses is located in the folder `/etc/netplan/`. In this example it is called `50-cloud-init.yaml`.
-
-The best practice approach is to create a separate configuration file to set up Additional IP addresses. This way, you can easily revert the changes in case of an error.
-
-#### Step 1: Create the network configuration file
-
-In our example, our file is call `51-cloud-init.yaml`:
-
-```bash
-sudo touch /etc/netplan/51-cloud-init.yaml
-```
-
-#### Step 2: Edit the configuration file
-
-You can verify your network interface name with this command:
-
-```bash
-ip a
-```
-
-Next, open the network configuration file for editing with the following command:
-
-```bash
-sudo nano /etc/netplan/51-cloud-init.yaml
-```
-
-Edit the file with the content below, replacing `INTERFACE_NAME` and `ADDITIONAL_IP` with your own values:
-
-```yaml
-network:
- version: 2
- ethernets:
- INTERFACE_NAME:
- dhcp4: true
- addresses:
- - ADDITIONAL_IP/32
-```
-
-If you have more Additional IPs to configure, the configuration file should look like this:
-
-```yaml
-network:
- version: 2
- ethernets:
- INTERFACE_NAME:
- dhcp4: true
- addresses:
- - ADDITIONAL_IP1/32
- - ADDITIONAL_IP2/32
-```
-
-> [!warning]
->
-> It is important to respect the alignment of each element in this file as represented in the example above. Do not use the tab key to create your spacing.
->
-
-**Configuration example:**
-
-```yaml
-network:
- version: 2
- ethernets:
- eth0:
- dhcp4: true
- addresses:
- - 203.0.113.0/32
-```
-
-Save and close the file.
-
-#### Step 3: Apply the new network configuration
-
-You can test your configuration using this command:
-
-```bash
-sudo netplan try
-```
-
-If it is correct, apply it using the following command:
-
-```bash
-sudo netplan apply
-```
-
-### AlmaLinux (8 & 9), Rocky Linux (8 & 9)
-
-The main configuration file is located in `/etc/sysconfig/network-scripts/`. In this example it is called `ifcfg-eth0`. Before making changes, verify the actual file name in this folder.
-
-For each Additional IP to be configured, we create a seperate configuration file with the following parameters: `ifcfg-NETWORK_INTERFACE:ID`. Where `NETWORK_INTERFACE` is the physical interface and `ID` is the virtual network interface or ethernet alias starting with a value of 0. For example, for our interface named `eth0` the first alias is `eth0:0`, the second alias is `eth0:1`, etc...
-
-#### Step 1: Determine the interface
-
-```bash
-ip a
-```
-
-#### Step 2: Create the configuration file
-
-First, create the configuration file. Replace `NETWORK_INTERFACE:ID` with your own values.
-
-```bash
-sudo nano /etc/sysconfig/network-scripts/ifcfg-NETWORK_INTERFACE:ID
-```
-
-Next, edit the file with the content below, replacing `NETWORK_INTERFACE:ID`, and `ADDITIONAL_IP` with your own values:
-
-```console
-DEVICE=NETWORK_INTERFACE:ID
-ONBOOT=yes
-BOOTPROTO=none # For CentOS use "static"
-IPADDR=ADDITIONAL_IP
-NETMASK=255.255.255.255
-BROADCAST=ADDITIONAL_IP
-```
-
-**Configuration example:**
-
-```console
-DEVICE=eth0:0
-ONBOOT=yes
-BOOTPROTO=none # For CentOS use "static"
-IPADDR=203.0.113.0
-NETMASK=255.255.255.255
-BROADCAST=203.0.113.0
-```
-
-#### Step 3: Restart the interface
-
-```bash
-sudo systemctl restart network
-```
-
-#### For AlmaLinux and Rocky Linux
-
-```bash
-sudo systemctl restart NetworkManager
-```
-
-### Fedora 37 and following
-
-Fedora now uses keyfiles. NetworkManager previously stored network profiles in ifcfg format in this directory: `/etc/sysconfig/network-scripts/`. However, the ifcfg format is now deprecated. By default, NetworkManager no longer creates new profiles in this format. The configuration file is now found in `/etc/NetworkManager/system-connections/`.
-
-#### Step 1: Create a backup
-
-In our example, our file is called `cloud-init-eno1.nmconnection`, so we make a copy of the `cloud-init-eno1.nmconnection` file using the following command:
-
-```bash
-sudo cp -r /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak
-```
-
-In case of a mistake, you will be able to revert the changes, using the commands below:
-
-```bash
-sudo rm -f /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-sudo cp /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-```
-
-#### Step 2: Edit the config file
-
-> [!primary]
-> Please note that the name of the network file in our example may differ from yours. Please adapt the commands to your file name.
->
-
-```bash
-sudo nano /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-```
-
-Do not modify the existing lines in the configuration file, add your Additional IP to the file as follows, replacing `ADDITIONAL_IP/32` wih your own values:
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=ADDITIONAL_IP/32
-```
-
-If you have two Additional IPs to configure, the configuration should look like this:
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=ADDITIONAL_IP1/32
-address2=ADDITIONAL_IP2/32
-```
-
-**Configuration example:**
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=203.0.113.0/32
-```
-
-#### Step 3: Restart the interface
-
-You now need to restart your interface:
-
-```bash
-sudo systemctl restart NetworkManager
-```
-
-### cPanel
-
-#### Step 1: Access the WHM IP management section
-
-In the WHM control panel, click on `IP Functions`{.action} and select `Add a New IP Address`{.action} in the left-hand sidebar.
-
-{.thumbnail}
-
-#### Step 2: Add the Additional IP information
-
-Enter your Additional IP in the form `xxx.xxx.xxx.xxx` into the field “New IP or IP range to add”.
-
-Select `255.255.255.255` as your subnet mask, then click on `Submit`{.action}.
-
-{.thumbnail}
-
-> [!warning]
->
-> Please note that if you have more than one IP to configure on the same block and you add them all at once, the WHM system will force you to use the subnet mask `255.255.255.0`. We do not recommend using this configuration. Instead, you need to add each IP individually in order to use the proper subnet mask `255.255.255.255`.
->
-
-#### Step 3: Check the current IP configuration
-
-Back in the section `IP Functions`{.action}, click on `Show or Delete Current IP Addresses`{.action} to verify that the Additional IP address was added correctly.
-
-{.thumbnail}
-
-### Plesk
-
-#### Step 1: Access the Plesk IP management section
-
-In the Plesk control panel, choose `Tools & Settings`{.action} from the left-hand sidebar.
-
-{.thumbnail}
-
-Click on `IP Addresses`{.action} under **Tools & Resources**.
-
-#### Step 2: Add the additional IP information
-
-In this section, click on the button `Add IP Address`{.action}.
-
-{.thumbnail}
-
-Enter your Additional IP in the form `xxx.xxx.xxx.xxx/32` into the field "IP address and subnet mask", then click on `OK`{.action}.
-
-{.thumbnail}
-
-#### Step 3: Check the current IP configuration
-
-Back in the section "IP Addresses", verify that the Additional IP address was added correctly.
-
-{.thumbnail}
-
-### Windows Servers
-
-#### Step 1: Verify the network configuration
-
-Right-click on the `Start Menu`{.action} button and open `Run`{.action}.
-
-Type `cmd` and click `OK`{.action} to open the command line application.
-
-{.thumbnail}
-
-In order to retrieve the current IP configuration, enter `ipconfig` at the command prompt.
-
-```console
-C:\Users\Administrator>ipconfig
-
-Windows IP Configuration
-
-
-Ethernet adapter Ethernet:
-
- Connection-specific DNS Suffix . : openstacklocal
- Link-local IPv6 Address . . . . . : fe90::30gf:258a:84d6:abcf%5
- IPv4 Address. . . . . . . . . . . : 192.0.2.29
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- Default Gateway . . . . . . . . . : 192.0.2.1
-```
-
-#### Step 2: Change the IPv4 Properties
-
-Now you need to change the IP properties to a static configuration.
-
-1. Go to `Start`{.action}> `Control Panel`{.action}>` Network and Internet`{.action}> `Network and Sharing Centre`{.action}> `Change Adapter Settings`{.action}(in the left-hand menu).
-2. Right-click on `Ethernet`{.action}.
-3. Click on `Properties`{.action}.
-4. Select `Internet Protocol Version 4 (TCP/IPv4)`{.action}, then click on `Properties`{.action}.
-5. Click on `Use the following IP address`{.action} and type in your server’s primary IP, subnet mask and default gateway information obtained by using the `ipconfig`{.action} command above. In the "Preferred DNS Server" box, type `213.186.33.99`.
-
-
-{.thumbnail}
-
-> [!warning]
->
-> Be careful – the server will no longer be accessible if you enter incorrect information. You will then have to make the corrections in the KVM.
->
-
-Once done, click on `Advanced`{.action}.
-
-#### Step 3: Add the Additional IP in the "Advanced TCP/IP Settings"
-
-In the new window, click on `Add...`{.action} under "IP addresses". Enter your Additional IP address and the subnet mask (255.255.255.255).
-
-{.thumbnail}
-
-Confirm by clicking on `Add`{.action}.
-
-{.thumbnail}
-
-Once done, click on `OK`{.action} to apply the configuration.
-
-{.thumbnail}
-
-You will lose the connection to the server for a few seconds.
-
-#### Step 4: Check the new network configuration
-
-Open the command prompt (cmd) and enter `ipconfig`. The configuration should now include the new Additional IP address.
-
-```console
-C:\Users\Administrator>ipconfig
-
-Windows IP Configuration
-
-
-Ethernet adapter Ethernet:
-
- Connection-specific DNS Suffix . :
- Link-local IPv6 Address . . . . . : fe90::30gf:258a:84d6:abcf%5
- IPv4 Address. . . . . . . . . . . : 192.0.2.29
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- IPv4 Address. . . . . . . . . . . : 203.0.113.0
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- Default Gateway . . . . . . . . . : 192.0.2.1
-```
-
-### Troubleshooting
-
-First, restart your server from the command line or its GUI. If you are still unable to establish a connection from the public network to your alias IP and suspect a network problem, you need to reboot the server in [rescue mode](/pages/bare_metal_cloud/virtual_private_servers/rescue). Then you can set up the Additional IP address directly on the server.
-
-Once you are connected to your server via SSH, enter the following command:
-
-```bash
-ifconfig ens3:0 ADDITIONAL_IP netmask 255.255.255.255 broadcast ADDITIONAL_IP up
-```
-
-To test the connection, simply ping your Additional IP from the outside. If it responds in rescue mode, that probably means that there is a configuration error. If, however, the IP is still not working, please inform our support teams by creating a [support request](https://help.ovhcloud.com/csm?id=csm_get_help) for further investigations.
-
-## Go further
-
-[Activating Rescue Mode on VPS](/pages/bare_metal_cloud/virtual_private_servers/rescue)
-
-If you would like assistance using and configuring your OVHcloud solutions, please refer to our [support offers](/links/support).
-
-Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-gb.md b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-gb.md
index da952afc4f2..f801884c19d 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-gb.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-gb.md
@@ -1,7 +1,7 @@
---
-title: Configuring IP aliasing
+title: How to configure IP aliasing
excerpt: Find out how to add Additional IP addresses to your VPS configuration
-updated: 2024-11-05
+updated: 2025-09-11
---
## Objective
@@ -23,6 +23,10 @@ IP aliasing refers to a special network configuration for certain OVHcloud servi
- Administrative access (sudo) via SSH or GUI to your server
- Basic networking and administration knowledge
+> [!warning]
+> Additional IP addresses are currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instructions
The following sections contain the configurations for the most commonly used distributions/operating systems. The first step is always to log in to your server via SSH or a GUI login session (RDP for a Windows VPS). The examples below presume you are logged in as a user with elevated permissions (Administrator/sudo).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-ie.md b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-ie.md
deleted file mode 100644
index da952afc4f2..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-ie.md
+++ /dev/null
@@ -1,488 +0,0 @@
----
-title: Configuring IP aliasing
-excerpt: Find out how to add Additional IP addresses to your VPS configuration
-updated: 2024-11-05
----
-
-## Objective
-
-IP aliasing refers to a special network configuration for certain OVHcloud services. Additional IPs allow you to associate multiple IP addresses with a single network interface.
-
-**This guide explains how to add Additional IP addresses to your network configuration.**
-
-> [!warning]
-> OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
->
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialist service provider](/links/partner) or reaching out to the [OVHcloud community](/links/community) if you encounter any difficulties.
->
-
-## Requirements
-
-- A [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account
-- An [Additional IP address](/links/bare-metal/ip)
-- Administrative access (sudo) via SSH or GUI to your server
-- Basic networking and administration knowledge
-
-## Instructions
-
-The following sections contain the configurations for the most commonly used distributions/operating systems. The first step is always to log in to your server via SSH or a GUI login session (RDP for a Windows VPS). The examples below presume you are logged in as a user with elevated permissions (Administrator/sudo).
-
-> [!primary]
->
-Concerning different distribution releases, please note that the proper procedure to configure your network interface as well as the file names may have been subject to change. We recommend to consult the manuals and knowledge resources of the respective OS versions if you experience any issues.
->
-
-**Please take note of the following terminology that will be used in code examples and instructions of the guide sections below:**
-
-|Term|Description|Examples|
-|---|---|---|
-|ADDITIONAL_IP|An Additional IP address assigned to your service|203.0.113.0|
-|NETWORK_INTERFACE|The name of the network interface|*eth0*, *ens3*|
-|ID|ID of the IP alias, starting with *0* (depending on the number of additional IPs there are to configure)|*0*, *1*|
-
-### Debian 11
-
-#### Step 1: Disable automatic network configuration
-
-Open the following file path with a text editor, in our example, we are using `nano`.
-
-```bash
-sudo nano /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
-```
-Enter the following line, then save and exit the editor.
-
-```console
-network: {config: disabled}
-```
-Creating this configuration file will prevent changes to your network configuration from being made automatically.
-
-#### Step 2: Create a backup
-
-By default, the configuration file is located in the path `etc\network\interfaces.d`.
-
-In our example, our file is called `50-cloud-init`, so we make a copy of the `50-cloud-init` file using the following command:
-
-```bash
-sudo cp /etc/network/interfaces.d/50-cloud-init /etc/network/interfaces.d/50-cloud-init.bak
-```
-
-In case of a mistake, you will be able to revert the changes, using the commands below:
-
-```bash
-sudo rm -f /etc/network/interfaces.d/50-cloud-init
-sudo cp /etc/network/interfaces.d/50-cloud-init.bak /etc/network/interfaces.d/50-cloud-init
-```
-#### Step 3: Edit the configuration file
-
-The first step is to verify your network interface name with this command:
-
-```bash
-ip a
-```
-
-Next, open the network configuration file for editing with the following command:
-
-```bash
-sudo nano /etc/network/interfaces.d/50-cloud-init
-```
-
-To configure your Additional IP, you need to add a virtual interface or ethernet alias to your network interface. In our example, our interface is called `eth0`, so our first alias is `eth0:0`. Do this for each Additional IP you wish to configure.
-
-Do not modify the existing lines in the configuration file, simply add your Additional IP to the file as follows, replacing `NETWORK_INTERFACE`, `ID` and `ADDITIONAL_IP` wih your own values:
-
-
-```console
-auto NETWORK_INTERFACE:ID
-iface NETWORK_INTERFACE:ID inet static
-address ADDITIONAL_IP
-netmask 255.255.255.255
-```
-
-If you are configuring more than one Additional IP, your configuration file should look like this:
-
-```console
-auto NETWORK_INTERFACE:ID
-iface NETWORK_INTERFACE:ID inet static
-address ADDITIONAL_IP1
-address ADDITIONAL_IP2
-netmask 255.255.255.255
-```
-
-**Configuration example:**
-
-```console
-auto eth0:0
-iface eth0:0 inet static
-address 203.0.113.0
-netmask 255.255.255.255
-```
-
-#### Step 4: Restart the interface
-
-Apply the changes with the following command:
-
-```bash
-sudo systemctl restart networking
-```
-
-### Debian 12, Ubuntu 20.04 and following
-
-The configuration file for your Additional IP addresses is located in the folder `/etc/netplan/`. In this example it is called `50-cloud-init.yaml`.
-
-The best practice approach is to create a separate configuration file to set up Additional IP addresses. This way, you can easily revert the changes in case of an error.
-
-#### Step 1: Create the network configuration file
-
-In our example, our file is call `51-cloud-init.yaml`:
-
-```bash
-sudo touch /etc/netplan/51-cloud-init.yaml
-```
-
-#### Step 2: Edit the configuration file
-
-You can verify your network interface name with this command:
-
-```bash
-ip a
-```
-
-Next, open the network configuration file for editing with the following command:
-
-```bash
-sudo nano /etc/netplan/51-cloud-init.yaml
-```
-
-Edit the file with the content below, replacing `INTERFACE_NAME` and `ADDITIONAL_IP` with your own values:
-
-```yaml
-network:
- version: 2
- ethernets:
- INTERFACE_NAME:
- dhcp4: true
- addresses:
- - ADDITIONAL_IP/32
-```
-
-If you have more Additional IPs to configure, the configuration file should look like this:
-
-```yaml
-network:
- version: 2
- ethernets:
- INTERFACE_NAME:
- dhcp4: true
- addresses:
- - ADDITIONAL_IP1/32
- - ADDITIONAL_IP2/32
-```
-
-> [!warning]
->
-> It is important to respect the alignment of each element in this file as represented in the example above. Do not use the tab key to create your spacing.
->
-
-**Configuration example:**
-
-```yaml
-network:
- version: 2
- ethernets:
- eth0:
- dhcp4: true
- addresses:
- - 203.0.113.0/32
-```
-
-Save and close the file.
-
-#### Step 3: Apply the new network configuration
-
-You can test your configuration using this command:
-
-```bash
-sudo netplan try
-```
-
-If it is correct, apply it using the following command:
-
-```bash
-sudo netplan apply
-```
-
-### AlmaLinux (8 & 9), Rocky Linux (8 & 9)
-
-The main configuration file is located in `/etc/sysconfig/network-scripts/`. In this example it is called `ifcfg-eth0`. Before making changes, verify the actual file name in this folder.
-
-For each Additional IP to be configured, we create a seperate configuration file with the following parameters: `ifcfg-NETWORK_INTERFACE:ID`. Where `NETWORK_INTERFACE` is the physical interface and `ID` is the virtual network interface or ethernet alias starting with a value of 0. For example, for our interface named `eth0` the first alias is `eth0:0`, the second alias is `eth0:1`, etc...
-
-#### Step 1: Determine the interface
-
-```bash
-ip a
-```
-
-#### Step 2: Create the configuration file
-
-First, create the configuration file. Replace `NETWORK_INTERFACE:ID` with your own values.
-
-```bash
-sudo nano /etc/sysconfig/network-scripts/ifcfg-NETWORK_INTERFACE:ID
-```
-
-Next, edit the file with the content below, replacing `NETWORK_INTERFACE:ID`, and `ADDITIONAL_IP` with your own values:
-
-```console
-DEVICE=NETWORK_INTERFACE:ID
-ONBOOT=yes
-BOOTPROTO=none # For CentOS use "static"
-IPADDR=ADDITIONAL_IP
-NETMASK=255.255.255.255
-BROADCAST=ADDITIONAL_IP
-```
-
-**Configuration example:**
-
-```console
-DEVICE=eth0:0
-ONBOOT=yes
-BOOTPROTO=none # For CentOS use "static"
-IPADDR=203.0.113.0
-NETMASK=255.255.255.255
-BROADCAST=203.0.113.0
-```
-
-#### Step 3: Restart the interface
-
-```bash
-sudo systemctl restart network
-```
-
-#### For AlmaLinux and Rocky Linux
-
-```bash
-sudo systemctl restart NetworkManager
-```
-
-### Fedora 37 and following
-
-Fedora now uses keyfiles. NetworkManager previously stored network profiles in ifcfg format in this directory: `/etc/sysconfig/network-scripts/`. However, the ifcfg format is now deprecated. By default, NetworkManager no longer creates new profiles in this format. The configuration file is now found in `/etc/NetworkManager/system-connections/`.
-
-#### Step 1: Create a backup
-
-In our example, our file is called `cloud-init-eno1.nmconnection`, so we make a copy of the `cloud-init-eno1.nmconnection` file using the following command:
-
-```bash
-sudo cp -r /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak
-```
-
-In case of a mistake, you will be able to revert the changes, using the commands below:
-
-```bash
-sudo rm -f /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-sudo cp /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-```
-
-#### Step 2: Edit the config file
-
-> [!primary]
-> Please note that the name of the network file in our example may differ from yours. Please adapt the commands to your file name.
->
-
-```bash
-sudo nano /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-```
-
-Do not modify the existing lines in the configuration file, add your Additional IP to the file as follows, replacing `ADDITIONAL_IP/32` wih your own values:
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=ADDITIONAL_IP/32
-```
-
-If you have two Additional IPs to configure, the configuration should look like this:
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=ADDITIONAL_IP1/32
-address2=ADDITIONAL_IP2/32
-```
-
-**Configuration example:**
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=203.0.113.0/32
-```
-
-#### Step 3: Restart the interface
-
-You now need to restart your interface:
-
-```bash
-sudo systemctl restart NetworkManager
-```
-
-### cPanel
-
-#### Step 1: Access the WHM IP management section
-
-In the WHM control panel, click on `IP Functions`{.action} and select `Add a New IP Address`{.action} in the left-hand sidebar.
-
-{.thumbnail}
-
-#### Step 2: Add the Additional IP information
-
-Enter your Additional IP in the form `xxx.xxx.xxx.xxx` into the field “New IP or IP range to add”.
-
-Select `255.255.255.255` as your subnet mask, then click on `Submit`{.action}.
-
-{.thumbnail}
-
-> [!warning]
->
-> Please note that if you have more than one IP to configure on the same block and you add them all at once, the WHM system will force you to use the subnet mask `255.255.255.0`. We do not recommend using this configuration. Instead, you need to add each IP individually in order to use the proper subnet mask `255.255.255.255`.
->
-
-#### Step 3: Check the current IP configuration
-
-Back in the section `IP Functions`{.action}, click on `Show or Delete Current IP Addresses`{.action} to verify that the Additional IP address was added correctly.
-
-{.thumbnail}
-
-### Plesk
-
-#### Step 1: Access the Plesk IP management section
-
-In the Plesk control panel, choose `Tools & Settings`{.action} from the left-hand sidebar.
-
-{.thumbnail}
-
-Click on `IP Addresses`{.action} under **Tools & Resources**.
-
-#### Step 2: Add the additional IP information
-
-In this section, click on the button `Add IP Address`{.action}.
-
-{.thumbnail}
-
-Enter your Additional IP in the form `xxx.xxx.xxx.xxx/32` into the field "IP address and subnet mask", then click on `OK`{.action}.
-
-{.thumbnail}
-
-#### Step 3: Check the current IP configuration
-
-Back in the section "IP Addresses", verify that the Additional IP address was added correctly.
-
-{.thumbnail}
-
-### Windows Servers
-
-#### Step 1: Verify the network configuration
-
-Right-click on the `Start Menu`{.action} button and open `Run`{.action}.
-
-Type `cmd` and click `OK`{.action} to open the command line application.
-
-{.thumbnail}
-
-In order to retrieve the current IP configuration, enter `ipconfig` at the command prompt.
-
-```console
-C:\Users\Administrator>ipconfig
-
-Windows IP Configuration
-
-
-Ethernet adapter Ethernet:
-
- Connection-specific DNS Suffix . : openstacklocal
- Link-local IPv6 Address . . . . . : fe90::30gf:258a:84d6:abcf%5
- IPv4 Address. . . . . . . . . . . : 192.0.2.29
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- Default Gateway . . . . . . . . . : 192.0.2.1
-```
-
-#### Step 2: Change the IPv4 Properties
-
-Now you need to change the IP properties to a static configuration.
-
-1. Go to `Start`{.action}> `Control Panel`{.action}>` Network and Internet`{.action}> `Network and Sharing Centre`{.action}> `Change Adapter Settings`{.action}(in the left-hand menu).
-2. Right-click on `Ethernet`{.action}.
-3. Click on `Properties`{.action}.
-4. Select `Internet Protocol Version 4 (TCP/IPv4)`{.action}, then click on `Properties`{.action}.
-5. Click on `Use the following IP address`{.action} and type in your server’s primary IP, subnet mask and default gateway information obtained by using the `ipconfig`{.action} command above. In the "Preferred DNS Server" box, type `213.186.33.99`.
-
-
-{.thumbnail}
-
-> [!warning]
->
-> Be careful – the server will no longer be accessible if you enter incorrect information. You will then have to make the corrections in the KVM.
->
-
-Once done, click on `Advanced`{.action}.
-
-#### Step 3: Add the Additional IP in the "Advanced TCP/IP Settings"
-
-In the new window, click on `Add...`{.action} under "IP addresses". Enter your Additional IP address and the subnet mask (255.255.255.255).
-
-{.thumbnail}
-
-Confirm by clicking on `Add`{.action}.
-
-{.thumbnail}
-
-Once done, click on `OK`{.action} to apply the configuration.
-
-{.thumbnail}
-
-You will lose the connection to the server for a few seconds.
-
-#### Step 4: Check the new network configuration
-
-Open the command prompt (cmd) and enter `ipconfig`. The configuration should now include the new Additional IP address.
-
-```console
-C:\Users\Administrator>ipconfig
-
-Windows IP Configuration
-
-
-Ethernet adapter Ethernet:
-
- Connection-specific DNS Suffix . :
- Link-local IPv6 Address . . . . . : fe90::30gf:258a:84d6:abcf%5
- IPv4 Address. . . . . . . . . . . : 192.0.2.29
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- IPv4 Address. . . . . . . . . . . : 203.0.113.0
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- Default Gateway . . . . . . . . . : 192.0.2.1
-```
-
-### Troubleshooting
-
-First, restart your server from the command line or its GUI. If you are still unable to establish a connection from the public network to your alias IP and suspect a network problem, you need to reboot the server in [rescue mode](/pages/bare_metal_cloud/virtual_private_servers/rescue). Then you can set up the Additional IP address directly on the server.
-
-Once you are connected to your server via SSH, enter the following command:
-
-```bash
-ifconfig ens3:0 ADDITIONAL_IP netmask 255.255.255.255 broadcast ADDITIONAL_IP up
-```
-
-To test the connection, simply ping your Additional IP from the outside. If it responds in rescue mode, that probably means that there is a configuration error. If, however, the IP is still not working, please inform our support teams by creating a [support request](https://help.ovhcloud.com/csm?id=csm_get_help) for further investigations.
-
-## Go further
-
-[Activating Rescue Mode on VPS](/pages/bare_metal_cloud/virtual_private_servers/rescue)
-
-If you would like assistance using and configuring your OVHcloud solutions, please refer to our [support offers](/links/support).
-
-Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-sg.md b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-sg.md
deleted file mode 100644
index da952afc4f2..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-sg.md
+++ /dev/null
@@ -1,488 +0,0 @@
----
-title: Configuring IP aliasing
-excerpt: Find out how to add Additional IP addresses to your VPS configuration
-updated: 2024-11-05
----
-
-## Objective
-
-IP aliasing refers to a special network configuration for certain OVHcloud services. Additional IPs allow you to associate multiple IP addresses with a single network interface.
-
-**This guide explains how to add Additional IP addresses to your network configuration.**
-
-> [!warning]
-> OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
->
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialist service provider](/links/partner) or reaching out to the [OVHcloud community](/links/community) if you encounter any difficulties.
->
-
-## Requirements
-
-- A [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account
-- An [Additional IP address](/links/bare-metal/ip)
-- Administrative access (sudo) via SSH or GUI to your server
-- Basic networking and administration knowledge
-
-## Instructions
-
-The following sections contain the configurations for the most commonly used distributions/operating systems. The first step is always to log in to your server via SSH or a GUI login session (RDP for a Windows VPS). The examples below presume you are logged in as a user with elevated permissions (Administrator/sudo).
-
-> [!primary]
->
-Concerning different distribution releases, please note that the proper procedure to configure your network interface as well as the file names may have been subject to change. We recommend to consult the manuals and knowledge resources of the respective OS versions if you experience any issues.
->
-
-**Please take note of the following terminology that will be used in code examples and instructions of the guide sections below:**
-
-|Term|Description|Examples|
-|---|---|---|
-|ADDITIONAL_IP|An Additional IP address assigned to your service|203.0.113.0|
-|NETWORK_INTERFACE|The name of the network interface|*eth0*, *ens3*|
-|ID|ID of the IP alias, starting with *0* (depending on the number of additional IPs there are to configure)|*0*, *1*|
-
-### Debian 11
-
-#### Step 1: Disable automatic network configuration
-
-Open the following file path with a text editor, in our example, we are using `nano`.
-
-```bash
-sudo nano /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
-```
-Enter the following line, then save and exit the editor.
-
-```console
-network: {config: disabled}
-```
-Creating this configuration file will prevent changes to your network configuration from being made automatically.
-
-#### Step 2: Create a backup
-
-By default, the configuration file is located in the path `etc\network\interfaces.d`.
-
-In our example, our file is called `50-cloud-init`, so we make a copy of the `50-cloud-init` file using the following command:
-
-```bash
-sudo cp /etc/network/interfaces.d/50-cloud-init /etc/network/interfaces.d/50-cloud-init.bak
-```
-
-In case of a mistake, you will be able to revert the changes, using the commands below:
-
-```bash
-sudo rm -f /etc/network/interfaces.d/50-cloud-init
-sudo cp /etc/network/interfaces.d/50-cloud-init.bak /etc/network/interfaces.d/50-cloud-init
-```
-#### Step 3: Edit the configuration file
-
-The first step is to verify your network interface name with this command:
-
-```bash
-ip a
-```
-
-Next, open the network configuration file for editing with the following command:
-
-```bash
-sudo nano /etc/network/interfaces.d/50-cloud-init
-```
-
-To configure your Additional IP, you need to add a virtual interface or ethernet alias to your network interface. In our example, our interface is called `eth0`, so our first alias is `eth0:0`. Do this for each Additional IP you wish to configure.
-
-Do not modify the existing lines in the configuration file, simply add your Additional IP to the file as follows, replacing `NETWORK_INTERFACE`, `ID` and `ADDITIONAL_IP` wih your own values:
-
-
-```console
-auto NETWORK_INTERFACE:ID
-iface NETWORK_INTERFACE:ID inet static
-address ADDITIONAL_IP
-netmask 255.255.255.255
-```
-
-If you are configuring more than one Additional IP, your configuration file should look like this:
-
-```console
-auto NETWORK_INTERFACE:ID
-iface NETWORK_INTERFACE:ID inet static
-address ADDITIONAL_IP1
-address ADDITIONAL_IP2
-netmask 255.255.255.255
-```
-
-**Configuration example:**
-
-```console
-auto eth0:0
-iface eth0:0 inet static
-address 203.0.113.0
-netmask 255.255.255.255
-```
-
-#### Step 4: Restart the interface
-
-Apply the changes with the following command:
-
-```bash
-sudo systemctl restart networking
-```
-
-### Debian 12, Ubuntu 20.04 and following
-
-The configuration file for your Additional IP addresses is located in the folder `/etc/netplan/`. In this example it is called `50-cloud-init.yaml`.
-
-The best practice approach is to create a separate configuration file to set up Additional IP addresses. This way, you can easily revert the changes in case of an error.
-
-#### Step 1: Create the network configuration file
-
-In our example, our file is call `51-cloud-init.yaml`:
-
-```bash
-sudo touch /etc/netplan/51-cloud-init.yaml
-```
-
-#### Step 2: Edit the configuration file
-
-You can verify your network interface name with this command:
-
-```bash
-ip a
-```
-
-Next, open the network configuration file for editing with the following command:
-
-```bash
-sudo nano /etc/netplan/51-cloud-init.yaml
-```
-
-Edit the file with the content below, replacing `INTERFACE_NAME` and `ADDITIONAL_IP` with your own values:
-
-```yaml
-network:
- version: 2
- ethernets:
- INTERFACE_NAME:
- dhcp4: true
- addresses:
- - ADDITIONAL_IP/32
-```
-
-If you have more Additional IPs to configure, the configuration file should look like this:
-
-```yaml
-network:
- version: 2
- ethernets:
- INTERFACE_NAME:
- dhcp4: true
- addresses:
- - ADDITIONAL_IP1/32
- - ADDITIONAL_IP2/32
-```
-
-> [!warning]
->
-> It is important to respect the alignment of each element in this file as represented in the example above. Do not use the tab key to create your spacing.
->
-
-**Configuration example:**
-
-```yaml
-network:
- version: 2
- ethernets:
- eth0:
- dhcp4: true
- addresses:
- - 203.0.113.0/32
-```
-
-Save and close the file.
-
-#### Step 3: Apply the new network configuration
-
-You can test your configuration using this command:
-
-```bash
-sudo netplan try
-```
-
-If it is correct, apply it using the following command:
-
-```bash
-sudo netplan apply
-```
-
-### AlmaLinux (8 & 9), Rocky Linux (8 & 9)
-
-The main configuration file is located in `/etc/sysconfig/network-scripts/`. In this example it is called `ifcfg-eth0`. Before making changes, verify the actual file name in this folder.
-
-For each Additional IP to be configured, we create a seperate configuration file with the following parameters: `ifcfg-NETWORK_INTERFACE:ID`. Where `NETWORK_INTERFACE` is the physical interface and `ID` is the virtual network interface or ethernet alias starting with a value of 0. For example, for our interface named `eth0` the first alias is `eth0:0`, the second alias is `eth0:1`, etc...
-
-#### Step 1: Determine the interface
-
-```bash
-ip a
-```
-
-#### Step 2: Create the configuration file
-
-First, create the configuration file. Replace `NETWORK_INTERFACE:ID` with your own values.
-
-```bash
-sudo nano /etc/sysconfig/network-scripts/ifcfg-NETWORK_INTERFACE:ID
-```
-
-Next, edit the file with the content below, replacing `NETWORK_INTERFACE:ID`, and `ADDITIONAL_IP` with your own values:
-
-```console
-DEVICE=NETWORK_INTERFACE:ID
-ONBOOT=yes
-BOOTPROTO=none # For CentOS use "static"
-IPADDR=ADDITIONAL_IP
-NETMASK=255.255.255.255
-BROADCAST=ADDITIONAL_IP
-```
-
-**Configuration example:**
-
-```console
-DEVICE=eth0:0
-ONBOOT=yes
-BOOTPROTO=none # For CentOS use "static"
-IPADDR=203.0.113.0
-NETMASK=255.255.255.255
-BROADCAST=203.0.113.0
-```
-
-#### Step 3: Restart the interface
-
-```bash
-sudo systemctl restart network
-```
-
-#### For AlmaLinux and Rocky Linux
-
-```bash
-sudo systemctl restart NetworkManager
-```
-
-### Fedora 37 and following
-
-Fedora now uses keyfiles. NetworkManager previously stored network profiles in ifcfg format in this directory: `/etc/sysconfig/network-scripts/`. However, the ifcfg format is now deprecated. By default, NetworkManager no longer creates new profiles in this format. The configuration file is now found in `/etc/NetworkManager/system-connections/`.
-
-#### Step 1: Create a backup
-
-In our example, our file is called `cloud-init-eno1.nmconnection`, so we make a copy of the `cloud-init-eno1.nmconnection` file using the following command:
-
-```bash
-sudo cp -r /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak
-```
-
-In case of a mistake, you will be able to revert the changes, using the commands below:
-
-```bash
-sudo rm -f /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-sudo cp /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-```
-
-#### Step 2: Edit the config file
-
-> [!primary]
-> Please note that the name of the network file in our example may differ from yours. Please adapt the commands to your file name.
->
-
-```bash
-sudo nano /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-```
-
-Do not modify the existing lines in the configuration file, add your Additional IP to the file as follows, replacing `ADDITIONAL_IP/32` wih your own values:
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=ADDITIONAL_IP/32
-```
-
-If you have two Additional IPs to configure, the configuration should look like this:
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=ADDITIONAL_IP1/32
-address2=ADDITIONAL_IP2/32
-```
-
-**Configuration example:**
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=203.0.113.0/32
-```
-
-#### Step 3: Restart the interface
-
-You now need to restart your interface:
-
-```bash
-sudo systemctl restart NetworkManager
-```
-
-### cPanel
-
-#### Step 1: Access the WHM IP management section
-
-In the WHM control panel, click on `IP Functions`{.action} and select `Add a New IP Address`{.action} in the left-hand sidebar.
-
-{.thumbnail}
-
-#### Step 2: Add the Additional IP information
-
-Enter your Additional IP in the form `xxx.xxx.xxx.xxx` into the field “New IP or IP range to add”.
-
-Select `255.255.255.255` as your subnet mask, then click on `Submit`{.action}.
-
-{.thumbnail}
-
-> [!warning]
->
-> Please note that if you have more than one IP to configure on the same block and you add them all at once, the WHM system will force you to use the subnet mask `255.255.255.0`. We do not recommend using this configuration. Instead, you need to add each IP individually in order to use the proper subnet mask `255.255.255.255`.
->
-
-#### Step 3: Check the current IP configuration
-
-Back in the section `IP Functions`{.action}, click on `Show or Delete Current IP Addresses`{.action} to verify that the Additional IP address was added correctly.
-
-{.thumbnail}
-
-### Plesk
-
-#### Step 1: Access the Plesk IP management section
-
-In the Plesk control panel, choose `Tools & Settings`{.action} from the left-hand sidebar.
-
-{.thumbnail}
-
-Click on `IP Addresses`{.action} under **Tools & Resources**.
-
-#### Step 2: Add the additional IP information
-
-In this section, click on the button `Add IP Address`{.action}.
-
-{.thumbnail}
-
-Enter your Additional IP in the form `xxx.xxx.xxx.xxx/32` into the field "IP address and subnet mask", then click on `OK`{.action}.
-
-{.thumbnail}
-
-#### Step 3: Check the current IP configuration
-
-Back in the section "IP Addresses", verify that the Additional IP address was added correctly.
-
-{.thumbnail}
-
-### Windows Servers
-
-#### Step 1: Verify the network configuration
-
-Right-click on the `Start Menu`{.action} button and open `Run`{.action}.
-
-Type `cmd` and click `OK`{.action} to open the command line application.
-
-{.thumbnail}
-
-In order to retrieve the current IP configuration, enter `ipconfig` at the command prompt.
-
-```console
-C:\Users\Administrator>ipconfig
-
-Windows IP Configuration
-
-
-Ethernet adapter Ethernet:
-
- Connection-specific DNS Suffix . : openstacklocal
- Link-local IPv6 Address . . . . . : fe90::30gf:258a:84d6:abcf%5
- IPv4 Address. . . . . . . . . . . : 192.0.2.29
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- Default Gateway . . . . . . . . . : 192.0.2.1
-```
-
-#### Step 2: Change the IPv4 Properties
-
-Now you need to change the IP properties to a static configuration.
-
-1. Go to `Start`{.action}> `Control Panel`{.action}>` Network and Internet`{.action}> `Network and Sharing Centre`{.action}> `Change Adapter Settings`{.action}(in the left-hand menu).
-2. Right-click on `Ethernet`{.action}.
-3. Click on `Properties`{.action}.
-4. Select `Internet Protocol Version 4 (TCP/IPv4)`{.action}, then click on `Properties`{.action}.
-5. Click on `Use the following IP address`{.action} and type in your server’s primary IP, subnet mask and default gateway information obtained by using the `ipconfig`{.action} command above. In the "Preferred DNS Server" box, type `213.186.33.99`.
-
-
-{.thumbnail}
-
-> [!warning]
->
-> Be careful – the server will no longer be accessible if you enter incorrect information. You will then have to make the corrections in the KVM.
->
-
-Once done, click on `Advanced`{.action}.
-
-#### Step 3: Add the Additional IP in the "Advanced TCP/IP Settings"
-
-In the new window, click on `Add...`{.action} under "IP addresses". Enter your Additional IP address and the subnet mask (255.255.255.255).
-
-{.thumbnail}
-
-Confirm by clicking on `Add`{.action}.
-
-{.thumbnail}
-
-Once done, click on `OK`{.action} to apply the configuration.
-
-{.thumbnail}
-
-You will lose the connection to the server for a few seconds.
-
-#### Step 4: Check the new network configuration
-
-Open the command prompt (cmd) and enter `ipconfig`. The configuration should now include the new Additional IP address.
-
-```console
-C:\Users\Administrator>ipconfig
-
-Windows IP Configuration
-
-
-Ethernet adapter Ethernet:
-
- Connection-specific DNS Suffix . :
- Link-local IPv6 Address . . . . . : fe90::30gf:258a:84d6:abcf%5
- IPv4 Address. . . . . . . . . . . : 192.0.2.29
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- IPv4 Address. . . . . . . . . . . : 203.0.113.0
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- Default Gateway . . . . . . . . . : 192.0.2.1
-```
-
-### Troubleshooting
-
-First, restart your server from the command line or its GUI. If you are still unable to establish a connection from the public network to your alias IP and suspect a network problem, you need to reboot the server in [rescue mode](/pages/bare_metal_cloud/virtual_private_servers/rescue). Then you can set up the Additional IP address directly on the server.
-
-Once you are connected to your server via SSH, enter the following command:
-
-```bash
-ifconfig ens3:0 ADDITIONAL_IP netmask 255.255.255.255 broadcast ADDITIONAL_IP up
-```
-
-To test the connection, simply ping your Additional IP from the outside. If it responds in rescue mode, that probably means that there is a configuration error. If, however, the IP is still not working, please inform our support teams by creating a [support request](https://help.ovhcloud.com/csm?id=csm_get_help) for further investigations.
-
-## Go further
-
-[Activating Rescue Mode on VPS](/pages/bare_metal_cloud/virtual_private_servers/rescue)
-
-If you would like assistance using and configuring your OVHcloud solutions, please refer to our [support offers](/links/support).
-
-Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-us.md b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-us.md
deleted file mode 100644
index da952afc4f2..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.en-us.md
+++ /dev/null
@@ -1,488 +0,0 @@
----
-title: Configuring IP aliasing
-excerpt: Find out how to add Additional IP addresses to your VPS configuration
-updated: 2024-11-05
----
-
-## Objective
-
-IP aliasing refers to a special network configuration for certain OVHcloud services. Additional IPs allow you to associate multiple IP addresses with a single network interface.
-
-**This guide explains how to add Additional IP addresses to your network configuration.**
-
-> [!warning]
-> OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
->
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialist service provider](/links/partner) or reaching out to the [OVHcloud community](/links/community) if you encounter any difficulties.
->
-
-## Requirements
-
-- A [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account
-- An [Additional IP address](/links/bare-metal/ip)
-- Administrative access (sudo) via SSH or GUI to your server
-- Basic networking and administration knowledge
-
-## Instructions
-
-The following sections contain the configurations for the most commonly used distributions/operating systems. The first step is always to log in to your server via SSH or a GUI login session (RDP for a Windows VPS). The examples below presume you are logged in as a user with elevated permissions (Administrator/sudo).
-
-> [!primary]
->
-Concerning different distribution releases, please note that the proper procedure to configure your network interface as well as the file names may have been subject to change. We recommend to consult the manuals and knowledge resources of the respective OS versions if you experience any issues.
->
-
-**Please take note of the following terminology that will be used in code examples and instructions of the guide sections below:**
-
-|Term|Description|Examples|
-|---|---|---|
-|ADDITIONAL_IP|An Additional IP address assigned to your service|203.0.113.0|
-|NETWORK_INTERFACE|The name of the network interface|*eth0*, *ens3*|
-|ID|ID of the IP alias, starting with *0* (depending on the number of additional IPs there are to configure)|*0*, *1*|
-
-### Debian 11
-
-#### Step 1: Disable automatic network configuration
-
-Open the following file path with a text editor, in our example, we are using `nano`.
-
-```bash
-sudo nano /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
-```
-Enter the following line, then save and exit the editor.
-
-```console
-network: {config: disabled}
-```
-Creating this configuration file will prevent changes to your network configuration from being made automatically.
-
-#### Step 2: Create a backup
-
-By default, the configuration file is located in the path `etc\network\interfaces.d`.
-
-In our example, our file is called `50-cloud-init`, so we make a copy of the `50-cloud-init` file using the following command:
-
-```bash
-sudo cp /etc/network/interfaces.d/50-cloud-init /etc/network/interfaces.d/50-cloud-init.bak
-```
-
-In case of a mistake, you will be able to revert the changes, using the commands below:
-
-```bash
-sudo rm -f /etc/network/interfaces.d/50-cloud-init
-sudo cp /etc/network/interfaces.d/50-cloud-init.bak /etc/network/interfaces.d/50-cloud-init
-```
-#### Step 3: Edit the configuration file
-
-The first step is to verify your network interface name with this command:
-
-```bash
-ip a
-```
-
-Next, open the network configuration file for editing with the following command:
-
-```bash
-sudo nano /etc/network/interfaces.d/50-cloud-init
-```
-
-To configure your Additional IP, you need to add a virtual interface or ethernet alias to your network interface. In our example, our interface is called `eth0`, so our first alias is `eth0:0`. Do this for each Additional IP you wish to configure.
-
-Do not modify the existing lines in the configuration file, simply add your Additional IP to the file as follows, replacing `NETWORK_INTERFACE`, `ID` and `ADDITIONAL_IP` wih your own values:
-
-
-```console
-auto NETWORK_INTERFACE:ID
-iface NETWORK_INTERFACE:ID inet static
-address ADDITIONAL_IP
-netmask 255.255.255.255
-```
-
-If you are configuring more than one Additional IP, your configuration file should look like this:
-
-```console
-auto NETWORK_INTERFACE:ID
-iface NETWORK_INTERFACE:ID inet static
-address ADDITIONAL_IP1
-address ADDITIONAL_IP2
-netmask 255.255.255.255
-```
-
-**Configuration example:**
-
-```console
-auto eth0:0
-iface eth0:0 inet static
-address 203.0.113.0
-netmask 255.255.255.255
-```
-
-#### Step 4: Restart the interface
-
-Apply the changes with the following command:
-
-```bash
-sudo systemctl restart networking
-```
-
-### Debian 12, Ubuntu 20.04 and following
-
-The configuration file for your Additional IP addresses is located in the folder `/etc/netplan/`. In this example it is called `50-cloud-init.yaml`.
-
-The best practice approach is to create a separate configuration file to set up Additional IP addresses. This way, you can easily revert the changes in case of an error.
-
-#### Step 1: Create the network configuration file
-
-In our example, our file is call `51-cloud-init.yaml`:
-
-```bash
-sudo touch /etc/netplan/51-cloud-init.yaml
-```
-
-#### Step 2: Edit the configuration file
-
-You can verify your network interface name with this command:
-
-```bash
-ip a
-```
-
-Next, open the network configuration file for editing with the following command:
-
-```bash
-sudo nano /etc/netplan/51-cloud-init.yaml
-```
-
-Edit the file with the content below, replacing `INTERFACE_NAME` and `ADDITIONAL_IP` with your own values:
-
-```yaml
-network:
- version: 2
- ethernets:
- INTERFACE_NAME:
- dhcp4: true
- addresses:
- - ADDITIONAL_IP/32
-```
-
-If you have more Additional IPs to configure, the configuration file should look like this:
-
-```yaml
-network:
- version: 2
- ethernets:
- INTERFACE_NAME:
- dhcp4: true
- addresses:
- - ADDITIONAL_IP1/32
- - ADDITIONAL_IP2/32
-```
-
-> [!warning]
->
-> It is important to respect the alignment of each element in this file as represented in the example above. Do not use the tab key to create your spacing.
->
-
-**Configuration example:**
-
-```yaml
-network:
- version: 2
- ethernets:
- eth0:
- dhcp4: true
- addresses:
- - 203.0.113.0/32
-```
-
-Save and close the file.
-
-#### Step 3: Apply the new network configuration
-
-You can test your configuration using this command:
-
-```bash
-sudo netplan try
-```
-
-If it is correct, apply it using the following command:
-
-```bash
-sudo netplan apply
-```
-
-### AlmaLinux (8 & 9), Rocky Linux (8 & 9)
-
-The main configuration file is located in `/etc/sysconfig/network-scripts/`. In this example it is called `ifcfg-eth0`. Before making changes, verify the actual file name in this folder.
-
-For each Additional IP to be configured, we create a seperate configuration file with the following parameters: `ifcfg-NETWORK_INTERFACE:ID`. Where `NETWORK_INTERFACE` is the physical interface and `ID` is the virtual network interface or ethernet alias starting with a value of 0. For example, for our interface named `eth0` the first alias is `eth0:0`, the second alias is `eth0:1`, etc...
-
-#### Step 1: Determine the interface
-
-```bash
-ip a
-```
-
-#### Step 2: Create the configuration file
-
-First, create the configuration file. Replace `NETWORK_INTERFACE:ID` with your own values.
-
-```bash
-sudo nano /etc/sysconfig/network-scripts/ifcfg-NETWORK_INTERFACE:ID
-```
-
-Next, edit the file with the content below, replacing `NETWORK_INTERFACE:ID`, and `ADDITIONAL_IP` with your own values:
-
-```console
-DEVICE=NETWORK_INTERFACE:ID
-ONBOOT=yes
-BOOTPROTO=none # For CentOS use "static"
-IPADDR=ADDITIONAL_IP
-NETMASK=255.255.255.255
-BROADCAST=ADDITIONAL_IP
-```
-
-**Configuration example:**
-
-```console
-DEVICE=eth0:0
-ONBOOT=yes
-BOOTPROTO=none # For CentOS use "static"
-IPADDR=203.0.113.0
-NETMASK=255.255.255.255
-BROADCAST=203.0.113.0
-```
-
-#### Step 3: Restart the interface
-
-```bash
-sudo systemctl restart network
-```
-
-#### For AlmaLinux and Rocky Linux
-
-```bash
-sudo systemctl restart NetworkManager
-```
-
-### Fedora 37 and following
-
-Fedora now uses keyfiles. NetworkManager previously stored network profiles in ifcfg format in this directory: `/etc/sysconfig/network-scripts/`. However, the ifcfg format is now deprecated. By default, NetworkManager no longer creates new profiles in this format. The configuration file is now found in `/etc/NetworkManager/system-connections/`.
-
-#### Step 1: Create a backup
-
-In our example, our file is called `cloud-init-eno1.nmconnection`, so we make a copy of the `cloud-init-eno1.nmconnection` file using the following command:
-
-```bash
-sudo cp -r /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak
-```
-
-In case of a mistake, you will be able to revert the changes, using the commands below:
-
-```bash
-sudo rm -f /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-sudo cp /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-```
-
-#### Step 2: Edit the config file
-
-> [!primary]
-> Please note that the name of the network file in our example may differ from yours. Please adapt the commands to your file name.
->
-
-```bash
-sudo nano /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-```
-
-Do not modify the existing lines in the configuration file, add your Additional IP to the file as follows, replacing `ADDITIONAL_IP/32` wih your own values:
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=ADDITIONAL_IP/32
-```
-
-If you have two Additional IPs to configure, the configuration should look like this:
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=ADDITIONAL_IP1/32
-address2=ADDITIONAL_IP2/32
-```
-
-**Configuration example:**
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=203.0.113.0/32
-```
-
-#### Step 3: Restart the interface
-
-You now need to restart your interface:
-
-```bash
-sudo systemctl restart NetworkManager
-```
-
-### cPanel
-
-#### Step 1: Access the WHM IP management section
-
-In the WHM control panel, click on `IP Functions`{.action} and select `Add a New IP Address`{.action} in the left-hand sidebar.
-
-{.thumbnail}
-
-#### Step 2: Add the Additional IP information
-
-Enter your Additional IP in the form `xxx.xxx.xxx.xxx` into the field “New IP or IP range to add”.
-
-Select `255.255.255.255` as your subnet mask, then click on `Submit`{.action}.
-
-{.thumbnail}
-
-> [!warning]
->
-> Please note that if you have more than one IP to configure on the same block and you add them all at once, the WHM system will force you to use the subnet mask `255.255.255.0`. We do not recommend using this configuration. Instead, you need to add each IP individually in order to use the proper subnet mask `255.255.255.255`.
->
-
-#### Step 3: Check the current IP configuration
-
-Back in the section `IP Functions`{.action}, click on `Show or Delete Current IP Addresses`{.action} to verify that the Additional IP address was added correctly.
-
-{.thumbnail}
-
-### Plesk
-
-#### Step 1: Access the Plesk IP management section
-
-In the Plesk control panel, choose `Tools & Settings`{.action} from the left-hand sidebar.
-
-{.thumbnail}
-
-Click on `IP Addresses`{.action} under **Tools & Resources**.
-
-#### Step 2: Add the additional IP information
-
-In this section, click on the button `Add IP Address`{.action}.
-
-{.thumbnail}
-
-Enter your Additional IP in the form `xxx.xxx.xxx.xxx/32` into the field "IP address and subnet mask", then click on `OK`{.action}.
-
-{.thumbnail}
-
-#### Step 3: Check the current IP configuration
-
-Back in the section "IP Addresses", verify that the Additional IP address was added correctly.
-
-{.thumbnail}
-
-### Windows Servers
-
-#### Step 1: Verify the network configuration
-
-Right-click on the `Start Menu`{.action} button and open `Run`{.action}.
-
-Type `cmd` and click `OK`{.action} to open the command line application.
-
-{.thumbnail}
-
-In order to retrieve the current IP configuration, enter `ipconfig` at the command prompt.
-
-```console
-C:\Users\Administrator>ipconfig
-
-Windows IP Configuration
-
-
-Ethernet adapter Ethernet:
-
- Connection-specific DNS Suffix . : openstacklocal
- Link-local IPv6 Address . . . . . : fe90::30gf:258a:84d6:abcf%5
- IPv4 Address. . . . . . . . . . . : 192.0.2.29
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- Default Gateway . . . . . . . . . : 192.0.2.1
-```
-
-#### Step 2: Change the IPv4 Properties
-
-Now you need to change the IP properties to a static configuration.
-
-1. Go to `Start`{.action}> `Control Panel`{.action}>` Network and Internet`{.action}> `Network and Sharing Centre`{.action}> `Change Adapter Settings`{.action}(in the left-hand menu).
-2. Right-click on `Ethernet`{.action}.
-3. Click on `Properties`{.action}.
-4. Select `Internet Protocol Version 4 (TCP/IPv4)`{.action}, then click on `Properties`{.action}.
-5. Click on `Use the following IP address`{.action} and type in your server’s primary IP, subnet mask and default gateway information obtained by using the `ipconfig`{.action} command above. In the "Preferred DNS Server" box, type `213.186.33.99`.
-
-
-{.thumbnail}
-
-> [!warning]
->
-> Be careful – the server will no longer be accessible if you enter incorrect information. You will then have to make the corrections in the KVM.
->
-
-Once done, click on `Advanced`{.action}.
-
-#### Step 3: Add the Additional IP in the "Advanced TCP/IP Settings"
-
-In the new window, click on `Add...`{.action} under "IP addresses". Enter your Additional IP address and the subnet mask (255.255.255.255).
-
-{.thumbnail}
-
-Confirm by clicking on `Add`{.action}.
-
-{.thumbnail}
-
-Once done, click on `OK`{.action} to apply the configuration.
-
-{.thumbnail}
-
-You will lose the connection to the server for a few seconds.
-
-#### Step 4: Check the new network configuration
-
-Open the command prompt (cmd) and enter `ipconfig`. The configuration should now include the new Additional IP address.
-
-```console
-C:\Users\Administrator>ipconfig
-
-Windows IP Configuration
-
-
-Ethernet adapter Ethernet:
-
- Connection-specific DNS Suffix . :
- Link-local IPv6 Address . . . . . : fe90::30gf:258a:84d6:abcf%5
- IPv4 Address. . . . . . . . . . . : 192.0.2.29
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- IPv4 Address. . . . . . . . . . . : 203.0.113.0
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- Default Gateway . . . . . . . . . : 192.0.2.1
-```
-
-### Troubleshooting
-
-First, restart your server from the command line or its GUI. If you are still unable to establish a connection from the public network to your alias IP and suspect a network problem, you need to reboot the server in [rescue mode](/pages/bare_metal_cloud/virtual_private_servers/rescue). Then you can set up the Additional IP address directly on the server.
-
-Once you are connected to your server via SSH, enter the following command:
-
-```bash
-ifconfig ens3:0 ADDITIONAL_IP netmask 255.255.255.255 broadcast ADDITIONAL_IP up
-```
-
-To test the connection, simply ping your Additional IP from the outside. If it responds in rescue mode, that probably means that there is a configuration error. If, however, the IP is still not working, please inform our support teams by creating a [support request](https://help.ovhcloud.com/csm?id=csm_get_help) for further investigations.
-
-## Go further
-
-[Activating Rescue Mode on VPS](/pages/bare_metal_cloud/virtual_private_servers/rescue)
-
-If you would like assistance using and configuring your OVHcloud solutions, please refer to our [support offers](/links/support).
-
-Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.es-es.md b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.es-es.md
index 15cd0048048..44a5ca8088e 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.es-es.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.es-es.md
@@ -1,7 +1,7 @@
---
title: 'Configurar una dirección IP como alias'
excerpt: 'Cómo añadir direcciones Additional IP a su configuración VPS'
-updated: 2024-11-05
+updated: 2025-09-11
---
## Objetivo
@@ -24,6 +24,10 @@ El alias de IP (*IP aliasing* en inglés) es una configuración especial de red
- Tener acceso de administrador (sudo) a través de SSH o GUI en su servidor
- Tener conocimientos básicos de redes y administración
+> [!warning]
+> Las direcciones Additional IP no están disponibles actualmente para los servidores virtuales en las [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Procedimiento
Esta guía explica las configuraciones de las distribuciones y sistemas operativos más habituales. En primer lugar, conéctese al servidor por SSH o a través de una sesión de conexión a la interfaz gráfica de usuario (RDP para un VPS Windows). Los siguientes ejemplos suponen que está conectado como usuario con permisos muy exigentes (administrador/sudo).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.es-us.md b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.es-us.md
deleted file mode 100644
index 4dcded37eee..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.es-us.md
+++ /dev/null
@@ -1,486 +0,0 @@
----
-title: 'Configurar una dirección IP como alias'
-excerpt: 'Cómo añadir direcciones Additional IP a su configuración VPS'
-updated: 2024-11-05
----
-
-## Objetivo
-
-El alias de IP (*IP aliasing* en inglés) es una configuración especial de red para los servidores de OVHcloud, que permite asociar varias direcciones IP a una única interfaz de red.
-
-**Esta guía explica cómo añadir direcciones Additional IP a su configuración de red.**
-
-> [!warning]
->
-> OVHcloud pone a su disposición servicios cuya configuración, gestión y responsabilidad recaen sobre usted. No tenemos acceso a estas máquinas, por lo que no somos los administradores de las mismas y no podremos asistirle. Por lo tanto, usted es responsable de la gestión del software y de la seguridad diaria.
->
-> Esta guía le ayudará a realizar las tareas más habituales. No obstante, le recomendamos que, si tiene problemas o dudas sobre la administración, la utilización o la seguridad de un servidor, contacte con un [proveedor especializado](/links/partner). Para más información, consulte el apartado "Más información" de esta guía.
->
-
-## Requisitos
-
-- Tener un [VPS](/links/bare-metal/vps) en su cuenta OVHcloud
-- Tener una [dirección Additional IP](/links/bare-metal/ip)
-- Tener acceso de administrador (sudo) a través de SSH o GUI en su servidor
-- Tener conocimientos básicos de redes y administración
-
-## Procedimiento
-
-Esta guía explica las configuraciones de las distribuciones y sistemas operativos más habituales. En primer lugar, conéctese al servidor por SSH o a través de una sesión de conexión a la interfaz gráfica de usuario (RDP para un VPS Windows). Los siguientes ejemplos suponen que está conectado como usuario con permisos muy exigentes (administrador/sudo).
-
-> [!primary]
->
-En cuanto a las distintas versiones de distribuciones, tenga en cuenta que puede haber cambiado el procedimiento adecuado para configurar la interfaz de red y los nombres de archivos. Si necesita ayuda, le recomendamos que consulte la documentación relativa a su sistema operativo.
->
-
-**Tome nota de la siguiente terminología que se utilizará en los ejemplos de código y en las instrucciones que se explican en esta guía:**
-
-|Valor|Descripción|Ejemplos|
-|---|---|---|
-|ADDITIONAL_IP|Dirección Additional IP atribuida a su servicio|203.0.113.0|
-|NETWORK_INTERFACE|Nombre de la interfaz de red|*eth0*, *ens3*|
-|ID|ID del alias IP, comenzando por *0* (en función del número de direcciones IP adicionales a configurar)|*0*, *1*|
-
-### Debian 11
-
-#### 1\. desactivar la configuración automática de red
-
-Abra la ruta al siguiente archivo con un editor de texto, en nuestro ejemplo utilizamos `nano` :
-
-```bash
-sudo nano /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
-```
-
-Introduzca la siguiente línea y, a continuación, guarde y cierre el editor.
-
-```console
-network: {config: disabled}
-```
-
-La creación de este archivo de configuración impide la ejecución automática de los cambios realizados en la configuración de su red.
-
-#### 2\. crear una copia de seguridad
-
-Por defecto, el fichero de configuración se encuentra en la ruta `/etc/network/interfaces.d`.
-
-En nuestro ejemplo, nuestro archivo se llama `50-cloud-init`, por lo que hacemos una copia del archivo `50-cloud-init` utilizando el siguiente comando:
-
-```bash
-sudo cp /etc/network/interfaces.d/50-cloud-init /etc/network/interfaces.d/50-cloud-init.bak
-```
-
-Si comete algún error, puede revertir los cambios utilizando los siguientes comandos:
-
-```bash
-sudo rm -f /etc/network/interfaces.d/50-cloud-init
-sudo cp /etc/network/interfaces.d/50-cloud-init.bak /etc/network/interfaces.d/50-cloud-init
-```
-
-#### 3\. editar el archivo de configuración de red
-
-Para comprobar el nombre de la interfaz de red, utilice el siguiente comando:
-
-```bash
-ip a
-```
-
-Abra el archivo de configuración de red para modificarlo con el siguiente comando:
-
-```bash
-sudo nano /etc/network/interfaces.d/50-cloud-init
-```
-
-Para configurar su dirección Additional IP, añada una interfaz virtual o un alias Ethernet a su interfaz de red. En nuestro ejemplo, nuestra interfaz se llama `eth0`, por lo que nuestro primer alias es `eth0:0`. Haga esto para cada dirección Additional IP que quiera configurar.
-
-No modifique las líneas existentes en el fichero de configuración, añada únicamente su dirección Additional IP al fichero, sustituyendo `NETWORK_INTERFACE`, `ID` y `ADDITIONAL_IP` por sus propios valores:
-
-
-```console
-auto NETWORK_INTERFACE:ID
-iface NETWORK_INTERFACE:ID inet static
-address ADDITIONAL_IP
-netmask 255.255.255.255
-```
-
-Si configura más de una dirección Additional IP, su archivo de configuración debería tener el siguiente aspecto:
-
-```console
-auto NETWORK_INTERFACE:ID
-iface NETWORK_INTERFACE:ID inet static
-address ADDITIONAL_IP1
-address ADDITIONAL_IP2
-netmask 255.255.255.255
-```
-
-**Ejemplo**
-
-```console
-auto eth0:0
-iface eth0:0 inet static
-address 203.0.113.0
-netmask 255.255.255.255
-```
-
-#### 4\. reiniciar la interfaz
-
-Aplique los cambios con el siguiente comando:
-
-```bash
-sudo systemctl restart networking
-```
-
-### Debian 12, Ubuntu 20.04 y posteriores
-
-El archivo de configuración de las direcciones Additional IP se encuentra en `/etc/netplan/`. En este ejemplo, se llama `50-cloud-init.yaml`.
-
-La práctica recomendada es crear un archivo de configuración independiente para definir las direcciones Additional IP. De este modo, podrá volver a revisar fácilmente los cambios en caso de que se produzca un error.
-
-
-#### 1\. crear el archivo de configuración de red
-
-En nuestro ejemplo, nuestro archivo se llama `51-cloud-init.yaml`:
-
-```bash
-sudo touch /etc/netplan/51-cloud-init.yaml
-```
-
-#### 2\. editar el archivo de configuración
-
-Para comprobar el nombre de la interfaz de red, utilice el siguiente comando:
-
-```bash
-ip a
-```
-
-Abra el archivo de configuración de red para modificarlo con el siguiente comando:
-
-```bash
-sudo nano /etc/netplan/51-cloud-init.yaml
-```
-
-Edite el fichero con el siguiente contenido, sustituyendo `INTERFACE_NAME` y `ADDITIONAL_IP` por sus propios valores:
-
-```yaml
-network:
- version: 2
- ethernets:
- INTERFACE_NAME:
- dhcp4: true
- addresses:
- - ADDITIONAL_IP/32
-```
-
-Si tiene que configurar más de una dirección Additional IP, el archivo de configuración debería tener el siguiente aspecto:
-
-```yaml
-network:
- version: 2
- ethernets:
- INTERFACE_NAME:
- dhcp4: true
- addresses:
- - ADDITIONAL_IP1/32
- - ADDITIONAL_IP2/32
-```
-
-> [!warning]
->
-> Es importante mantener la alineación de cada elemento del archivo, tal y como se muestra en el ejemplo anterior. No use la tecla de tabulación para crear el espacio.
->
-
-**Ejemplo**
-
-```yaml
-network:
- version: 2
- ethernets:
- eth0:
- dhcp4: true
- addresses:
- - 203.0.113.0/32
-```
-
-Guarde y cierre el archivo.
-
-#### 3\. aplicar la nueva configuración de red
-
-Para probar su configuración, utilice el siguiente comando:
-
-```bash
-sudo netplan try
-```
-
-Si es correcta, puede aplicarla con el siguiente comando:
-
-```bash
-sudo netplan apply
-```
-
-Repita este procedimiento para cada dirección Additional IP.
-
-### AlmaLinux (8 y 9), Rocky Linux (8 y 9)
-
-El archivo de configuración principal se encuentra en la carpeta `/etc/sysconfig/network-scripts/`. En este ejemplo, se denomina `ifcfg-eth0`. Antes de realizar cualquier cambio, compruebe el nombre real del archivo en esta carpeta.
-
-Para cada dirección Additional IP que desee configurar, cree un archivo de configuración independiente con los siguientes parámetros: `ifcfg-NETWORK_INTERFACE:ID`. Donde `NETWORK_INTERFACE` representa la interfaz física y `ID` representa la interfaz de red virtual o el alias ethernet que empieza por un valor de 0. Por ejemplo, para nuestra interfaz llamada `eth0` el primer alias es `eth0:0`, el segundo alias es `eth0:1`, etc.
-
-#### 1\. determinar la interfaz
-
-Para comprobar el nombre de la interfaz de red, utilice el siguiente comando:
-
-```bash
-ip a
-```
-
-#### 2\. crear el archivo de configuración
-
-En primer lugar, cree el archivo de configuración. Sustituya `NETWORK_INTERFACE:ID` por sus propios valores.
-
-```bash
-sudo nano /etc/sysconfig/network-scripts/ifcfg-NETWORK_INTERFACE:ID
-```
-
-A continuación, edite el archivo con el siguiente contenido, sustituyendo `NETWORK_INTERFACE:ID` y `ADDITIONAL_IP` por sus propios valores:
-
-```console
-DEVICE=NETWORK_INTERFACE:ID
-BOOTPROTO=static
-IPADDR=ADDITIONAL_IP
-NETMASK=255.255.255.255
-BROADCAST=ADDITIONAL_IP
-ONBOOT=yes
-```
-
-**Ejemplo**
-
-```console
-DEVICE=NETWORK_INTERFACE:ID
-BOOTPROTO=static
-IPADDR=203.0.113.0
-NETMASK=255.255.255.255
-BROADCAST=203.0.113.0
-ONBOOT=yes
-```
-
-#### 3\. reiniciar la interfaz
-
-Aplique los cambios con el siguiente comando:
-
-```bash
-sudo systemctl restart network
-```
-
-#### Para AlmaLinux y Rocky Linux
-
-```bash
-sudo systemctl restart NetworkManager
-```
-
-### Fedora 37 y versiones posteriores
-
-Fedora ahora utiliza archivos clave. NetworkManager almacenaba previamente los perfiles de red en formato ifcfg en este directorio: `/etc/sysconfig/network-scripts/`. Sin embargo, el formato ifcfg está obsoleto. De forma predeterminada, NetworkManager ya no crea nuevos perfiles en este formato. El archivo de configuración se encuentra ahora en `/etc/NetworkManager/system-connections/`.
-
-#### 1\. crear una copia de seguridad
-
-En nuestro ejemplo, nuestro archivo se llama `cloud-init-eno1.nmconnection`, por lo que hacemos una copia del archivo `cloud-init-eno1.nmconnection` utilizando el siguiente comando:
-
-```bash
-sudo cp -r /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak
-```
-
-Si comete algún error, puede revertir los cambios utilizando los siguientes comandos:
-
-```bash
-sudo rm -f /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-sudo cp /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-```
-
-#### 2\. modificar el archivo de configuración
-
-> [!primary]
-> Tenga en cuenta que el nombre del archivo de red en nuestro ejemplo puede ser diferente del suyo. Adapte los comandos a su nombre de archivo.
->
-
-```bash
-sudo nano /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-```
-
-No modifique las líneas existentes en el fichero de configuración, añada su Additional IP al fichero como sigue, sustituyendo `ADDITIONAL_IP/32` por sus propios valores:
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=ADDITIONAL_IP/32
-```
-
-Si tiene dos direcciones Additional IP que configurar, la configuración debería ser similar a la siguiente:
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=ADDITIONAL_IP1/32
-address2=ADDITIONAL_IP2/32
-```
-
-**Ejemplo**
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=203.0.113.0/32
-```
-
-#### 3\. reiniciar la interfaz
-
-```bash
-sudo systemctl restart NetworkManager
-```
-
-### cPanel
-
-#### 1\. acceder a la sección de gestión de las IP del WHM
-
-En el área de cliente de WHM, haga clic en `IP Functions`{.action} y seleccione `Add a New IP Address`{.action} en el menú de la izquierda.
-
-{.thumbnail}
-
-#### 2\. añadir la información de las direcciones Additional IP
-
-Introduzca su dirección Additional IP con el formato `xxx.xxx.xxx.xxx` en el campo `New IP or IP range to add`.
-
-Seleccione `255.255.255.255` como máscara de subred y haga clic en `Submit`{.action}.
-
-{.thumbnail}
-
-> [!warning]
->
-> Atención, si tiene varias IP que configurar en un mismo bloque y las añade todas al mismo tiempo, el sistema WHM le obligará a utilizar la máscara de subred `255.255.255.0`. No se recomienda utilizar esta configuración, es necesario añadir cada IP individualmente para poder utilizar la máscara de subred adecuada `255.255.255.255`.
->
-
-#### 3\. comprobar la configuración IP actual
-
-Vuelva a la sección `IP Functions`{.action} y haga clic en `Show or Delete Current IP Addresses`{.action} para comprobar que la dirección Additional IP se ha añadido correctamente.
-
-{.thumbnail}
-
-
-### Plesk
-
-#### 1\. acceder a la gestión de IP de Plesk
-
-En el panel de configuración de Plesk, seleccione `Tools & Settings`{.action} en la columna izquierda.
-
-{.thumbnail}
-
-Haga clic en `IP Addresses`{.action} bajo **Tools & Settings**.
-
-#### 2\. añadir la información IP adicional
-
-En esta sección, haga clic en el botón `Add IP Address`{.action}.
-
-{.thumbnail}
-
-Introduzca su dirección Additional IP como `xxx.xxx.xxx.xxx/32` en el campo "IP address and subnet mask" y haga clic en `OK`{.action}.
-
-{.thumbnail}
-
-#### 3\. comprobar la configuración IP actual
-
-En la sección "IP Addresses", compruebe que la dirección Additional IP se haya añadido correctamente.
-
-{.thumbnail}
-
-
-### Windows Server
-
-#### 1\. comprobar la configuración de red
-
-Haga clic derecho en el botón `Start`{.action} y abra `Run`{.action}.
-
-Pulse `cmd` y haga clic en `OK`{.action} para abrir la aplicación de línea de órdenes.
-
-{.thumbnail}
-
-Para obtener la configuración de IP actual, introduzca `ipconfig` en la consola de comandos.
-
-```console
-C:\Users\Administrator>ipconfig
-Windows IP Configuration
-Ethernet adapter Ethernet:
- Connection-specific DNS Suffix . : openstacklocal
- Link-local IPv6 Address . . . . . : fe90::30gf:258a:84d6:abcf%5
- IPv4 Address. . . . . . . . . . . : 192.0.2.29
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- Default Gateway . . . . . . . . . : 192.0.2.1
-```
-
-#### 2\. modificar las propiedades IPv4
-
-1. Vaya al menú `Start`{.action}, luego `Control Panel`{.action}, `Network and Internet`{.action}, `Network and Sharing Centre`{.action} y `Change Adapter Settings`{.action} en la barra de la izquierda.
-2. Haga clic derecho en `Ethernet`{.action};
-3. Haga clic en `Properties`{.action};
-4. Seleccione `Internet Protocol Version 4 (TCP/IPv4)`{.action} y haga clic en `Properties`{.action};
-5. Haga clic en `Use the following IP address`{.action} e introduzca la IP principal del servidor, la máscara de subred y la puerta de enlace por defecto obtenidas con el comando `ipconfig`{.action} anterior. En el cuadro "Preferred DNS Server", escriba "213.186.33.99".
-
-{.thumbnail}
-
-> [!warning]
->
-> Atención: si introduce información incorrecta, no podrá acceder al servidor. En ese caso, deberá realizar las correcciones oportunas a través del KVM.
->
-
-#### 3\. añadir la dirección Additional IP en los Parámetros TCP/IP avanzados
-
-En la nueva ventana, haga clic en `Add...`{.action} en "IP addresses". Introduzca su dirección Additional IP y la máscara de subred (255.255.255.255).
-
-{.thumbnail}
-
-Confirme haciendo clic en `Add`{.action}.
-
-{.thumbnail}
-
-A continuación, haga clic en `OK`{.action} para aplicar la configuración.
-
-{.thumbnail}
-
-Perderá la conexión con su servidor durante unos segundos.
-
-#### 4\. comprobar la configuración IP actual
-
-Abra el símbolo del sistema (cmd) e introduzca `ipconfig`. La configuración debe incluir ahora la nueva dirección Additional IP.
-
-```console
-C:\Users\Administrator>ipconfig
-Windows IP Configuration
-Ethernet adapter Ethernet:
- Connection-specific DNS Suffix . :
- Link-local IPv6 Address . . . . . : fe90::30gf:258a:84d6:abcf%5
- IPv4 Address. . . . . . . . . . . : 192.0.2.29
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- IPv4 Address. . . . . . . . . . . : 203.0.113.0
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- Default Gateway . . . . . . . . . : 192.0.2.1
-```
-
-### Diagnóstico
-
-En primer lugar, reinicie el servidor a través de la línea de comandos o la interfaz de usuario. Si todavía no consigue establecer una conexión entre la red pública y su dirección IP de alias y si sospecha que existe algún problema de red, deberá reiniciar el servidor en [modo de rescate](/pages/bare_metal_cloud/virtual_private_servers/rescue). A continuación, podrá configurar la dirección Additional IP directamente en el servidor.
-
-Una vez que se haya conectado al servidor por SSH, introduzca el siguiente comando:
-
-```bash
-ifconfig ens3:0 ADDITIONAL_IP netmask 255.255.255.255 broadcast ADDITIONAL_IP up
-```
-
-Para probar la conexión, solo tiene que enviar un ping a su dirección Additional IP desde el exterior. Si responde en modo de rescate, probablemente significa que se ha producido un error de configuración. No obstante, si la IP todavía no funciona, informe a nuestro equipo del soporte creando un [tíquet de soporte](https://help.ovhcloud.com/csm?id=csm_get_help).
-
-## Más información
-
-[Activar el modo de rescate en un VPS](/pages/bare_metal_cloud/virtual_private_servers/rescue)
-
-Si quiere disfrutar de ayuda para utilizar y configurar sus soluciones de OVHcloud, puede consultar nuestras distintas soluciones [pestañas de soporte](/links/support).
-
-Interactúe con nuestra comunidad de usuarios en .
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.fr-ca.md b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.fr-ca.md
deleted file mode 100644
index a42a3aa9516..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.fr-ca.md
+++ /dev/null
@@ -1,483 +0,0 @@
----
-title: 'Configurer une adresse IP en alias'
-excerpt: 'Découvrez comment ajouter des adresses Additional IP à votre configuration VPS'
-updated: 2024-11-05
----
-
-## Objectif
-
-L'alias d'IP (*IP aliasing* en anglais) est une configuration spéciale du réseau pour vos serveurs OVHcloud. Elle vous permet d'associer plusieurs adresses IP sur une seule interface réseau.
-
-**Découvrez comment ajouter des adresses Additional IP à votre configuration réseau.**
-
-> [!warning]
->
-> OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. En effet, n’ayant aucun accès à ces machines, nous n’en sommes pas les administrateurs et nous ne pourrons pas vous fournir d'assistance. Il vous appartient de ce fait d’en assurer la gestion logicielle et la sécurisation au quotidien.
->
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [prestataire spécialisé](https://marketplace.ovhcloud.com/) si vous éprouvez des difficultés ou des doutes concernant l’administration, l’utilisation ou la sécurisation d’un serveur. Plus d’informations dans la section « Aller plus loin » de ce guide.
->
-
-## Prérequis
-
-- Disposer d'une offre [VPS](/links/bare-metal/vps) dans votre compte OVHcloud
-- Disposer d'une [adresse Additional IP](/links/bare-metal/ip)
-- Avoir un accès administrateur (sudo) via SSH ou GUI sur votre serveur
-- Avoir les connaissances de base sur les réseaux et leur administration
-
-## En pratique
-
-Ce guide contient les configurations des distributions/systèmes d'exploitation les plus couramment utilisés. La première étape consiste toujours à se connecter à votre serveur via SSH ou via une session de connexion à l'interface graphique utilisateur (RDP pour un VPS Windows). Les exemples ci-dessous supposent que vous êtes connecté en tant qu'utilisateur avec des autorisations élevées (Administrateur/sudo).
-
-> [!primary]
->
-En ce qui concerne les différentes versions de distributions, veuillez noter que la procédure appropriée pour configurer votre interface réseau ainsi que les noms de fichiers peuvent avoir été modifiés. Si vous rencontrez des difficultés, nous vous recommandons de consulter la documentation relative à votre système d’exploitation.
->
-
-**Veuillez prendre note de la terminologie suivante qui sera utilisée dans les exemples de code et les instructions détaillées dans ce guide :**
-
-|Terme|Description|Exemples|
-|---|---|---|
-|ADDITIONAL_IP|Adresse Additional IP attribuée à votre service|203.0.113.0|
-|NETWORK_INTERFACE|Nom de l'interface réseau|*eth0*, *ens3*|
-|ID|ID de l'alias IP, commençant par *0* (en fonction du nombre d'adresses IP supplémentaires à configurer)|*0*, *1*|
-
-### Debian 11
-
-#### Étape 1 : désactiver la configuration automatique du réseau
-
-Ouvrez le chemin d'accès au fichier suivant avec un éditeur de texte, dans notre exemple nous utilisons `nano`. :
-
-```bash
-sudo nano /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
-```
-
-Entrez la ligne suivante, puis enregistrez et quittez l'éditeur.
-
-```console
-network: {config: disabled}
-```
-
-La création de ce fichier de configuration empêche l'exécution automatique des modifications apportées à la configuration de votre réseau.
-
-#### Étape 2 : créer une sauvegarde
-
-Par défaut, le fichier de configuration est situé dans le chemin `etc/network/interfaces.d`.
-
-Dans notre exemple, notre fichier s'appelle `50-cloud-init`, donc nous faisons une copie du fichier `50-cloud-init` en utilisant la commande suivante :
-
-```bash
-sudo cp /etc/network/interfaces.d/50-cloud-init /etc/network/interfaces.d/50-cloud-init.bak
-```
-
-En cas d'erreur, vous pourrez revenir sur les modifications en utilisant les commandes ci-dessous :
-
-```bash
-sudo rm -f /etc/network/interfaces.d/50-cloud-init
-sudo cp /etc/network/interfaces.d/50-cloud-init.bak /etc/network/interfaces.d/50-cloud-init
-```
-
-#### Étape 3 : éditer le fichier de configuration
-
-Vérifiez le nom de votre interface réseau à l'aide de la commande suivante :
-
-```bash
-ip a
-```
-
-Ouvrez le fichier de configuration réseau pour le modifier à l'aide de la commande suivante :
-
-```bash
-sudo nano /etc/network/interfaces.d/50-cloud-init
-```
-
-Pour configurer votre adresse Additional IP, ajoutez une interface virtuelle ou un alias Ethernet à votre interface réseau. Dans notre exemple, notre interface s'appelle `eth0`, donc notre premier alias est `eth0:0`. Faites ceci pour chaque adresse Additional IP que vous souhaitez configurer.
-
-Ne modifiez pas les lignes existantes dans le fichier de configuration, ajoutez uniquement votre adresse Additional IP au fichier comme suit, en remplaçant `NETWORK_INTERFACE`, `ID` et `ADDITIONAL_IP` par vos propres valeurs :
-
-```console
-auto NETWORK_INTERFACE:ID
-iface NETWORK_INTERFACE:ID inet static
-address ADDITIONAL_IP
-netmask 255.255.255.255
-```
-
-Si vous configurez plus d'une adresse Additional IP, votre fichier de configuration devrait ressembler à ceci :
-
-```console
-auto NETWORK_INTERFACE:ID
-iface NETWORK_INTERFACE:ID inet static
-address ADDITIONAL_IP1
-address ADDITIONAL_IP2
-netmask 255.255.255.255
-```
-
-**Exemple**
-
-```console
-auto eth0:0
-iface eth0:0 inet static
-address 203.0.113.0
-netmask 255.255.255.255
-```
-
-#### Étape 4 : redémarrer l'interface
-
-Appliquez les modifications à l'aide de la commande suivante :
-
-```bash
-sudo systemctl restart networking
-```
-
-### Debian 12, Ubuntu 20.04 et versions ultérieures
-
-Le fichier de configuration de vos adresses Additional IP se trouve dans le fichier `/etc/netplan/`. Dans cet exemple, il s'appelle `50-cloud-init.yaml`.
-
-La meilleure pratique consiste à créer un fichier de configuration distinct pour définir les adresses Additional IP. De cette manière, vous pouvez facilement revenir sur les modifications en cas d'erreur.
-
-#### Étape 1 : créer le fichier de configuration du réseau
-
-Dans notre exemple, notre fichier s'appelle `51-cloud-init.yaml` :
-
-```bash
-sudo touch /etc/netplan/51-cloud-init.yaml
-```
-
-#### Étape 2 : modifier le fichier de configuration
-
-Vérifiez le nom de votre interface réseau à l'aide de la commande suivante :
-
-```bash
-ip a
-```
-
-Ouvrez le fichier de configuration réseau pour le modifier à l'aide de la commande suivante :
-
-```bash
-sudo nano /etc/netplan/51-cloud-init.yaml
-```
-
-Editez le fichier avec le contenu ci-dessous, en remplaçant `INTERFACE_NAME` et `ADDITIONAL_IP` par vos propres valeurs :
-
-```yaml
-network:
- version: 2
- ethernets:
- INTERFACE_NAME:
- dhcp4: true
- addresses:
- - ADDITIONAL_IP1/32
-```
-
-Si vous avez plus d'une adresse Additional IP à configurer, le fichier de configuration devrait ressembler à ceci :
-
-```yaml
-network:
- version: 2
- ethernets:
- INTERFACE_NAME:
- dhcp4: true
- addresses:
- - ADDITIONAL_IP1/32
- - ADDITIONAL_IP2/32
-```
-
-
-> [!warning]
->
-> Il est important de respecter l'alignement de chaque élément de ce fichier tel que représenté dans l'exemple ci-dessus. N'utilisez pas la touche de tabulation pour créer votre espacement.
->
-
-**Exemple**
-
-```yaml
-network:
- version: 2
- ethernets:
- eth0:
- dhcp4: true
- addresses:
- - 203.0.113.0/32
-```
-
-Enregistrez et fermez le fichier.
-
-#### Étape 3 : appliquer la nouvelle configuration réseau
-
-Testez votre configuration à l'aide de la commande suivante :
-
-```bash
-sudo netplan try
-```
-
-Si elle est correcte, appliquez-la à l'aide de la commande suivante :
-
-```bash
-sudo netplan apply
-```
-
-Répétez cette procédure pour chaque adresse Additional IP.
-
-### AlmaLinux (8 & 9), Rocky Linux (8 & 9)
-
-Le fichier de configuration principal est situé dans le dossier `/etc/sysconfig/network-scripts/`. Dans cet exemple, il est appelé `ifcfg-eth0`. Avant de faire des changements, vérifiez le nom réel du fichier dans ce dossier.
-
-Pour chaque adresse Additional IP à configurer, créez un fichier de configuration séparé avec les paramètres suivants : `ifcfg-NETWORK_INTERFACE:ID`. Où `NETWORK_INTERFACE` représente l'interface physique et `ID` représente l'interface réseau virtuelle ou l'alias ethernet commençant par une valeur de 0. Par exemple, pour notre interface nommée `eth0` le premier alias est `eth0:0`, le second alias est `eth0:1`, etc.
-
-#### Étape 1 : déterminer l'interface
-
-Vérifiez le nom de votre interface réseau à l'aide de la commande suivante :
-
-```bash
-ip a
-```
-
-#### Étape 2 : créer le fichier de configuration
-
-Tout d'abord, créez le fichier de configuration. Remplacez `NETWORK_INTERFACE:ID` par vos propres valeurs.
-
-```bash
-sudo nano /etc/sysconfig/network-scripts/ifcfg-NETWORK_INTERFACE:ID
-```
-
-Ensuite, éditez le fichier avec le contenu ci-dessous, en remplaçant `NETWORK_INTERFACE:ID`, et `ADDITIONAL_IP` par vos propres valeurs :
-
-```console
-DEVICE=NETWORK_INTERFACE:ID
-ONBOOT=yes
-BOOTPROTO=none # For CentOS use "static"
-IPADDR=ADDITIONAL_IP
-NETMASK=255.255.255.255
-BROADCAST=ADDITIONAL_IP
-```
-
-**Exemple**
-
-```console
-DEVICE=eth0:0
-ONBOOT=yes
-BOOTPROTO=none # For CentOS use "static"
-IPADDR=203.0.113.0
-NETMASK=255.255.255.255
-BROADCAST=203.0.113.0
-```
-
-#### Étape 3 : redémarrer l'interface
-
-```bash
-sudo systemctl restart network
-```
-
-#### Pour AlmaLinux et Rocky Linux
-
-```bash
-sudo systemctl restart NetworkManager
-```
-
-### Fedora 37 et versions ultérieures
-
-Fedora utilise maintenant des fichiers clés. NetworkManager stockait auparavant les profils réseau au format ifcfg dans ce répertoire : `/etc/sysconfig/network-scripts/`. Cependant, le format ifcfg est maintenant obsolète. Par défaut, NetworkManager ne crée plus de nouveaux profils dans ce format. Le fichier de configuration se trouve maintenant dans `/etc/NetworkManager/system-connections/`.
-
-#### Étape 1 : créer une sauvegarde
-
-Dans notre exemple, notre fichier s'appelle `cloud-init-eno1.nmconnection`, donc nous faisons une copie du fichier `cloud-init-eno1.nmconnection` en utilisant la commande suivante :
-
-```bash
-sudo cp -r /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak
-```
-
-En cas d'erreur, vous pourrez revenir sur les modifications en utilisant les commandes ci-dessous :
-
-```bash
-sudo rm -f /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-sudo cp /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection.bak /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-```
-
-#### Étape 2 : modifier le fichier de configuration
-
-> [!primary]
-> Veuillez noter que le nom du fichier réseau dans notre exemple peut être différent du vôtre. Veuillez adapter les commandes à votre nom de fichier.
->
-
-```bash
-sudo nano /etc/NetworkManager/system-connections/cloud-init-eno1.nmconnection
-```
-
-Ne modifiez pas les lignes existantes dans le fichier de configuration, ajoutez votre Additional IP au fichier comme suit, en remplaçant `ADDITIONAL_IP/32` par vos propres valeurs :
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=ADDITIONAL_IP/32
-```
-
-Si vous avez deux adresses Additional IP à configurer, la configuration devrait ressembler à ceci :
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=ADDITIONAL_IP1/32
-address2=ADDITIONAL_IP2/32
-```
-
-**Exemple**
-
-```console
-[ipv4]
-method=auto
-may-fail=false
-address1=203.0.113.0/32
-```
-
-#### Étape 3 : redémarrer l'interface
-
-Redémarrez votre interface :
-
-```bash
-sudo systemctl restart NetworkManager
-```
-
-### cPanel
-
-#### Étape 1 : accéder à la section de gestion des IP du WHM
-
-Dans l'espace client WHM, cliquez sur `IP Functions`{.action} et sélectionnez `Add a New IP Address`{.action} dans le menu de gauche.
-
-{.thumbnail}
-
-#### Étape 2 : ajouter les informations des Additional IP
-
-Renseignez votre adresse Additional IP sous la forme « xxx.xxx.xxx.xxx » dans le champ « New IP or IP range to add ».
-
-Sélectionnez `255.255.255.255` comme masque de sous-réseau puis cliquez sur `Submit`{.action}.
-
-{.thumbnail}
-
-> [!warning]
->
-> Attention, si vous avez plusieurs IP à configurer sur un même bloc et que vous les ajoutez toutes en même temps, le système WHM vous forcera à utiliser le masque de sous-réseau `255.255.255.0`. Il n'est pas recommandé d'utiliser cette configuration, il faut ajouter chaque IP individuellement pour pouvoir utiliser le masque de sous-réseau approprié `255.255.255.255`.
->
-
-#### Étape 3 : vérifier la configuration IP actuelle
-
-De retour dans la section `IP Functions`{.action}, cliquez sur `Show or Delete Current IP Addresses`{.action} pour vérifier que l'adresse Additional IP a été correctement ajoutée.
-
-{.thumbnail}
-
-### Plesk
-
-#### Étape 1 : accéder à la gestion d'IP de Plesk
-
-Dans le panneau de configuration Plesk, choisissez `Tools & Settings`{.action} dans la barre latérale gauche.
-
-{.thumbnail}
-
-Cliquez sur `IP Addresses`{.action} sous **Tools & Settings**.
-
-#### Étape 2 : ajouter les informations des Additional IP
-
-Dans cette section, cliquez sur le bouton `Add IP Address`{.action}.
-
-{.thumbnail}
-
-Entrez votre adresse Additional IP sous la forme `xxx.xxx.xxx.xxx/32` dans le champ « IP address and subnet mask », puis cliquez sur `OK`{.action}.
-
-{.thumbnail}
-
-#### Étape 3 : vérifier la configuration IP actuelle
-
-Dans la section « IP Addresses », vérifiez que l'adresse Additional IP a été correctement ajoutée.
-
-{.thumbnail}
-
-### Windows Server
-
-#### Étape 1 : vérifier la configuration réseau
-
-Faites un clic droit sur le bouton `Menu Démarrer`{.action} et ouvrez `Exécuter`{.action}.
-
-Tapez `cmd` et cliquez sur `OK`{.action} pour ouvrir l'application de ligne de commande.
-
-{.thumbnail}
-
-Pour récupérer la configuration IP actuelle, entrez `ipconfig` dans l'invite de commande.
-
-```console
-C:\Users\Administrator>ipconfig
-Windows IP Configuration
-Ethernet adapter Ethernet:
- Connection-specific DNS Suffix . : openstacklocal
- Link-local IPv6 Address . . . . . : fe90::30gf:258a:84d6:abcf%5
- IPv4 Address. . . . . . . . . . . : 192.0.2.29
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- Default Gateway . . . . . . . . . : 192.0.2.1
-```
-
-#### Étape 2 : modifier les propriétés IPv4
-
-1. Allez dans le menu `Démarrer`{.action}, puis `Panneau de gestion`{.action}, `Réseau et Internet`{.action}, `Centre de réseau et Partage`{.action} et `Modifier les paramètres de la carte`{.action} dans la barre de gauche ;
-2. Effectuez un clic droit sur `Connexion au réseau local`{.action} ;
-3. Cliquez sur `Propriétés`{.action} ;
-4. Sélectionnez `Protocole Internet Version 4 (TCP/IPv4)`{.action}, puis cliquez sur `Propriétés`{.action} ;
-5. Cliquez sur `Utiliser l’adresse IP suivante`{.action} et renseignez l’IP principale de votre serveur, le masque sous-réseau et la passerelle par défaut obtenus grâce à la commande `ipconfig`{.action} ci-dessus. Dans la case « Serveur DNS Préféré », tapez « 213.186.33.99 ».
-
-{.thumbnail}
-
-> [!warning]
->
-> Attention, le serveur ne sera plus accessible si vous entrez des informations incorrectes. Vous serez alors obligé d’effectuer les corrections via le KVM.
->
-
-#### Étape 3 : ajouter l'adresse Additional IP dans les Paramètres TCP/IP avancés
-
-Dans la nouvelle fenêtre, cliquez sur `Ajouter...`{.action} sous « Adresses IP ». Entrez votre adresse Additional IP et le masque de sous-réseau (255.255.255.255).
-
-{.thumbnail}
-
-Confirmez en cliquant sur `Ajouter`{.action}.
-
-{.thumbnail}
-
-Cliquez ensuite sur `OK`{.action} pour appliquer la configuration.
-
-{.thumbnail}
-
-Vous perdrez la connexion à votre serveur pendant quelques secondes.
-
-#### Étape 4 : vérifier la nouvelle configuration réseau
-
-Ouvrez l'invite de commandes (cmd) et entrez `ipconfig`. La configuration doit maintenant inclure la nouvelle adresse Additional IP.
-
-```console
-C:\Users\Administrator>ipconfig
-Windows IP Configuration
-Ethernet adapter Ethernet:
- Connection-specific DNS Suffix . :
- Link-local IPv6 Address . . . . . : fe90::30gf:258a:84d6:abcf%5
- IPv4 Address. . . . . . . . . . . : 192.0.2.29
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- IPv4 Address. . . . . . . . . . . : 203.0.113.0
- Subnet Mask . . . . . . . . . . . : 255.255.255.255
- Default Gateway . . . . . . . . . : 192.0.2.1
-```
-
-### Diagnostic
-
-Tout d'abord, redémarrez votre serveur via la ligne de commande ou son interface utilisateur. Si vous ne parvenez toujours pas à établir une connexion entre le réseau public et votre adresse IP d'alias et que vous suspectez un problème réseau, redémarrez le serveur en [mode rescue](/pages/bare_metal_cloud/virtual_private_servers/rescue). Vous pouvez ensuite configurer l'adresse Additional IP directement sur le serveur.
-
-Une fois que vous êtes connecté à votre serveur via SSH, entrez la commande suivante :
-
-```bash
-ifconfig ens3:0 ADDITIONAL_IP netmask 255.255.255.255 broadcast ADDITIONAL_IP up
-```
-
-Pour tester la connexion, envoyez un ping à votre adresse Additional IP depuis l'extérieur. S'il répond en mode rescue, cela signifie probablement qu'il y a une erreur de configuration. Toutefois, si l'IP ne fonctionne toujours pas, veuillez en informer nos équipes du support en créant un [ticket d'assistance](https://help.ovhcloud.com/csm?id=csm_get_help).
-
-## Aller plus loin
-
-[Activer le mode rescue sur un VPS](/pages/bare_metal_cloud/virtual_private_servers/rescue)
-
-Si vous souhaitez bénéficier d'une assistance à l'usage et à la configuration de vos solutions OVHcloud, nous vous proposons de consulter nos différentes [offres de support](/links/support).
-
-Échangez avec notre [communauté d'utilisateurs](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.fr-fr.md b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.fr-fr.md
index 714c5bf91eb..61bf4916112 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.fr-fr.md
@@ -1,7 +1,7 @@
---
title: 'Configurer une adresse IP en alias'
excerpt: 'Découvrez comment ajouter des adresses Additional IP à votre configuration VPS'
-updated: 2024-11-05
+updated: 2025-09-11
---
## Objectif
@@ -24,6 +24,10 @@ L'alias d'IP (*IP aliasing* en anglais) est une configuration spéciale du rése
- Avoir un accès administrateur (sudo) via SSH ou GUI sur votre serveur
- Avoir les connaissances de base sur les réseaux et leur administration
+> [!warning]
+> Les adresses Additional IP actuellement indisponible pour les serveurs privés virtuels dans les [Local Zones](/links/bare-metal/vps-lz).
+>
+
## En pratique
Ce guide contient les configurations des distributions/systèmes d'exploitation les plus couramment utilisés. La première étape consiste toujours à se connecter à votre serveur via SSH ou via une session de connexion à l'interface graphique utilisateur (RDP pour un VPS Windows). Les exemples ci-dessous supposent que vous êtes connecté en tant qu'utilisateur avec des autorisations élevées (Administrateur/sudo).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.it-it.md b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.it-it.md
index 3135365a87c..2cc95fb8167 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.it-it.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.it-it.md
@@ -1,7 +1,7 @@
---
title: Configurare un indirizzo IP in alias
excerpt: Come aggiungere indirizzi Additional IP alla tua configurazione VPS
-updated: 2024-11-05
+updated: 2025-09-11
---
## Obiettivo
@@ -24,6 +24,10 @@ L'alias IP (*IP aliasing* in inglese) è una configurazione di rete speciale per
- Avere un accesso amministrator (sudo) via SSH o GUI sul tuo server
- Possedere conoscenze di base sulle reti e la loro amministrazione
+> [!warning]
+> Gli indirizzi Additional IP non sono attualmente disponibili per i server privati virtuali nelle [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Procedura
Questa guida ti mostra le configurazioni delle distribuzioni/dei sistemi operativi più comunemente utilizzati. Il primo step consiste sempre nell'connettersi al tuo server tramite SSH o tramite una sessione di connessione all'interfaccia grafica utente (RDP per un VPS Windows). Gli esempi che seguono presuppongono che tu sia connesso come utente con elevate autorizzazioni (Administratore/Sudo).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.pl-pl.md b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.pl-pl.md
index a805352359a..5b46ce8741b 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.pl-pl.md
@@ -1,7 +1,7 @@
---
title: 'Skonfiguruj adres IP jako alias'
excerpt: 'Dowiedz się, jak dodać adresy Additional IP do konfiguracji VPS'
-updated: 2024-11-05
+updated: 2025-09-11
---
## Wprowadzenie
@@ -24,6 +24,10 @@ Alias IP (*IP aliasing* w języku angielskim) to specjalna konfiguracja sieci dl
- Dostęp administratora (sudo) przez SSH lub GUI do serwera
- Posiadanie podstawowej wiedzy na temat sieci i zarządzania nimi
+> [!warning]
+> Adresy Additional IP aktualnie niedostępne dla prywatnych serwerów wirtualnych w [Local Zones](/links/bare-metal/vps-lz).
+>
+
## W praktyce
Niniejszy przewodnik zawiera najpopularniejsze konfiguracje dystrybucji/systemów operacyjnych. Pierwszy etap polega zawsze na logowaniu się do serwera przez SSH lub przez sesję logowania do interfejsu graficznego użytkownika (RDP dla serwera VPS Windows). Poniższe przykłady zakładają, że jesteś zalogowany jako użytkownik z dużymi uprawnieniami (Administrator/sudo).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.pt-pt.md b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.pt-pt.md
index 77723761c8f..8f24932979f 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing/guide.pt-pt.md
@@ -1,7 +1,7 @@
---
title: 'Configurar um endereço de IP alias'
excerpt: 'Saiba como adicionar endereços Additional IP à sua configuração VPS'
-updated: 2024-11-05
+updated: 2025-09-11
---
## Objetivo
@@ -24,6 +24,10 @@ O alias de IP (*IP aliasing* em inglês) é uma configuração especial da rede
- Ter um acesso administrador (sudo) via SSH ou GUI no seu servidor
- Ter conhecimentos básicos sobre as redes e a sua administração
+> [!warning]
+> Os endereços Additional IP atualmente indisponíveis para os servidores privados virtuais nas [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instruções
Este guia contém as configurações das distribuições/sistemas operativos mais frequentemente utilizados. A primeira etapa consiste sempre em ligar-se ao seu servidor através de SSH ou através de uma sessão de ligação à interface gráfica de utilizador (RDP para um VPS Windows). Os exemplos abaixo pressupõem que está ligado enquanto utilizador com autorizações elevadas (Administrador/Sudo).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.de-de.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.de-de.md
index a293e6fba3b..a8a9fb62b57 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.de-de.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.de-de.md
@@ -1,7 +1,7 @@
---
title: "cPanel auf einem VPS installieren"
excerpt: "Erfahren Sie hier, wie Sie einen VPS mit cPanel-Template einrichten"
-updated: 2025-07-14
+updated: 2025-09-11
---
## Ziel
@@ -23,6 +23,10 @@ Dank einer grafischen Oberfläche, die die Automatisierung von Einstellungen erl
- Sie haben einen [VPS](/links/bare-metal/vps) mit einer [kompatiblen Distribution](/links/bare-metal/vps-os).
- Sie haben Zugriff auf Ihr [OVHcloud Kundencenter](/links/manager).
+> [!warning]
+> Diese Funktion ist derzeit nicht verfügbar für VPS in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## In der praktischen Anwendung
Wenn Sie schon über einen VPS verfügen und cPanel darauf installieren möchten, wählen Sie die Option "VPS reinstallieren" in Ihrem [OVHcloud Kundencenter](/links/manager) und dann ein [Betriebssystem, das mit cPanel kompatibel ist](/links/bare-metal/vps-os).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-asia.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-asia.md
deleted file mode 100644
index c2ddb12c82a..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-asia.md
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: "How to deploy cPanel on a VPS"
-excerpt: "Find out how to instantiate a VPS with the preinstalled cPanel application"
-updated: 2025-07-14
----
-
-## Objective
-
-cPanel is a control panel that facilitates the management of web hosting. It makes complex tasks more accessible, especially to new users. It offers a wide range of features, such as:
-
-- Emails
-- Domain names
-- Databases
-- Security
-- etc.
-
-This simplifies website hosting, thanks to a graphical interface for automating settings.
-
-**This guide explains how to deploy cPanel with preinstalled applications on a VPS.**
-
-## Requirements
-
-- A [VPS](/links/bare-metal/vps) solution with a [compatible distribution](/links/bare-metal/vps-os)
-- Access to the [OVHcloud Control Panel](/links/manager)
-
-## Instructions
-
-If you already have a VPS and want to have cPanel on it, you can reinstall the VPS from your [OVHcloud Control Panel](/links/manager) via a [cPanel-compatible OS](/links/bare-metal/vps-os).
-
-> [!warning]
->
-> If you reinstall a VPS, all data stored on the VPS will be lost.
->
-
-To install your cPanel server, order a VPS with the cPanel distribution.
-
-{.thumbnail}
-
-When your VPS is ready, you will receive an email providing the information to connect to your cPanel server:
-
-```
- | Your application(s):
- | Application: cpanel
- | You can connect to cPanel from https://:2087/
-```
-
-### First login
-
-Once you have received the email containing the unique link, click on this link to perform the initial configuration. If the link has already expired, connect to the server [via SSH](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction) and run the command `sudo whmlogin` to generate a new link.
-
-The URL generated by the command `sudo whmlogin` allows you to log in to your WHM interface without any credentials (user and password). WHM is a server managemement tool used with cPanel. You will be able to access cPanel after completing the following steps.
-
-#### Step 1: Read and accept the cPanel Terms of Use
-
-Read and accept the cPanel Terms of Use.
-
-{.thumbnail}
-
-#### Step 2: Provide your email and nameservers you wish to set on the VPS
-
-{.thumbnail}
-
-#### Step 3: Set the root password
-
-{.thumbnail}
-
-You can now log in to your server via SSH, using the root user password you have just set.
-
-### Create a cPanel account from the WHM interface
-
-Once you have logged in to your WHM interface, click `Create a New Account`{.action} to create a cPanel account.
-
-{.thumbnail}
-
-Fill in the form, then confirm to create your cPanel account.
-
-{.thumbnail}
-
-On the new screen that pops up, click the `Go to cPanel`{.action} button to the right of the screen.
-
-{.thumbnail}
-
-You are redirected to your cPanel interface.
-
-{.thumbnail}
-
-You can now use cPanel. For more information about cPanel, see the [official documentation](https://docs.cpanel.net/).
-
-> [!primary]
->
-> In your browser's navigation bar, enter the following URLs to connect:
->
-> - To cPanel: https://<IP_V4>:2083/ (use the credentials that have just been created in the WHM interface)
-> - To WHM: https://<IP_V4>:2087/ (use the root username and password received in the service purchase email or the SSH password that has been changed in the WHM interface)
->
-> Find your IPv4 address in the email you received when ordering your VPS with the cPanel distribution.
->
-
-### Securing your service
-
-We recommend taking all the necessary measures to secure your WHM and VPS by following the [cPanel recommendations](https://docs.cpanel.net/knowledge-base/security/tips-to-make-your-server-more-secure/).
-
-We also recommend reading our guide to [securing a VPS](/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps), using [our backup solutions](/products/bare-metal-cloud-virtual-private-servers) and configuring the [Edge Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network).
-
-## Go further
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-au.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-au.md
deleted file mode 100644
index c2ddb12c82a..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-au.md
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: "How to deploy cPanel on a VPS"
-excerpt: "Find out how to instantiate a VPS with the preinstalled cPanel application"
-updated: 2025-07-14
----
-
-## Objective
-
-cPanel is a control panel that facilitates the management of web hosting. It makes complex tasks more accessible, especially to new users. It offers a wide range of features, such as:
-
-- Emails
-- Domain names
-- Databases
-- Security
-- etc.
-
-This simplifies website hosting, thanks to a graphical interface for automating settings.
-
-**This guide explains how to deploy cPanel with preinstalled applications on a VPS.**
-
-## Requirements
-
-- A [VPS](/links/bare-metal/vps) solution with a [compatible distribution](/links/bare-metal/vps-os)
-- Access to the [OVHcloud Control Panel](/links/manager)
-
-## Instructions
-
-If you already have a VPS and want to have cPanel on it, you can reinstall the VPS from your [OVHcloud Control Panel](/links/manager) via a [cPanel-compatible OS](/links/bare-metal/vps-os).
-
-> [!warning]
->
-> If you reinstall a VPS, all data stored on the VPS will be lost.
->
-
-To install your cPanel server, order a VPS with the cPanel distribution.
-
-{.thumbnail}
-
-When your VPS is ready, you will receive an email providing the information to connect to your cPanel server:
-
-```
- | Your application(s):
- | Application: cpanel
- | You can connect to cPanel from https://:2087/
-```
-
-### First login
-
-Once you have received the email containing the unique link, click on this link to perform the initial configuration. If the link has already expired, connect to the server [via SSH](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction) and run the command `sudo whmlogin` to generate a new link.
-
-The URL generated by the command `sudo whmlogin` allows you to log in to your WHM interface without any credentials (user and password). WHM is a server managemement tool used with cPanel. You will be able to access cPanel after completing the following steps.
-
-#### Step 1: Read and accept the cPanel Terms of Use
-
-Read and accept the cPanel Terms of Use.
-
-{.thumbnail}
-
-#### Step 2: Provide your email and nameservers you wish to set on the VPS
-
-{.thumbnail}
-
-#### Step 3: Set the root password
-
-{.thumbnail}
-
-You can now log in to your server via SSH, using the root user password you have just set.
-
-### Create a cPanel account from the WHM interface
-
-Once you have logged in to your WHM interface, click `Create a New Account`{.action} to create a cPanel account.
-
-{.thumbnail}
-
-Fill in the form, then confirm to create your cPanel account.
-
-{.thumbnail}
-
-On the new screen that pops up, click the `Go to cPanel`{.action} button to the right of the screen.
-
-{.thumbnail}
-
-You are redirected to your cPanel interface.
-
-{.thumbnail}
-
-You can now use cPanel. For more information about cPanel, see the [official documentation](https://docs.cpanel.net/).
-
-> [!primary]
->
-> In your browser's navigation bar, enter the following URLs to connect:
->
-> - To cPanel: https://<IP_V4>:2083/ (use the credentials that have just been created in the WHM interface)
-> - To WHM: https://<IP_V4>:2087/ (use the root username and password received in the service purchase email or the SSH password that has been changed in the WHM interface)
->
-> Find your IPv4 address in the email you received when ordering your VPS with the cPanel distribution.
->
-
-### Securing your service
-
-We recommend taking all the necessary measures to secure your WHM and VPS by following the [cPanel recommendations](https://docs.cpanel.net/knowledge-base/security/tips-to-make-your-server-more-secure/).
-
-We also recommend reading our guide to [securing a VPS](/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps), using [our backup solutions](/products/bare-metal-cloud-virtual-private-servers) and configuring the [Edge Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network).
-
-## Go further
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-ca.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-ca.md
deleted file mode 100644
index c2ddb12c82a..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-ca.md
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: "How to deploy cPanel on a VPS"
-excerpt: "Find out how to instantiate a VPS with the preinstalled cPanel application"
-updated: 2025-07-14
----
-
-## Objective
-
-cPanel is a control panel that facilitates the management of web hosting. It makes complex tasks more accessible, especially to new users. It offers a wide range of features, such as:
-
-- Emails
-- Domain names
-- Databases
-- Security
-- etc.
-
-This simplifies website hosting, thanks to a graphical interface for automating settings.
-
-**This guide explains how to deploy cPanel with preinstalled applications on a VPS.**
-
-## Requirements
-
-- A [VPS](/links/bare-metal/vps) solution with a [compatible distribution](/links/bare-metal/vps-os)
-- Access to the [OVHcloud Control Panel](/links/manager)
-
-## Instructions
-
-If you already have a VPS and want to have cPanel on it, you can reinstall the VPS from your [OVHcloud Control Panel](/links/manager) via a [cPanel-compatible OS](/links/bare-metal/vps-os).
-
-> [!warning]
->
-> If you reinstall a VPS, all data stored on the VPS will be lost.
->
-
-To install your cPanel server, order a VPS with the cPanel distribution.
-
-{.thumbnail}
-
-When your VPS is ready, you will receive an email providing the information to connect to your cPanel server:
-
-```
- | Your application(s):
- | Application: cpanel
- | You can connect to cPanel from https://:2087/
-```
-
-### First login
-
-Once you have received the email containing the unique link, click on this link to perform the initial configuration. If the link has already expired, connect to the server [via SSH](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction) and run the command `sudo whmlogin` to generate a new link.
-
-The URL generated by the command `sudo whmlogin` allows you to log in to your WHM interface without any credentials (user and password). WHM is a server managemement tool used with cPanel. You will be able to access cPanel after completing the following steps.
-
-#### Step 1: Read and accept the cPanel Terms of Use
-
-Read and accept the cPanel Terms of Use.
-
-{.thumbnail}
-
-#### Step 2: Provide your email and nameservers you wish to set on the VPS
-
-{.thumbnail}
-
-#### Step 3: Set the root password
-
-{.thumbnail}
-
-You can now log in to your server via SSH, using the root user password you have just set.
-
-### Create a cPanel account from the WHM interface
-
-Once you have logged in to your WHM interface, click `Create a New Account`{.action} to create a cPanel account.
-
-{.thumbnail}
-
-Fill in the form, then confirm to create your cPanel account.
-
-{.thumbnail}
-
-On the new screen that pops up, click the `Go to cPanel`{.action} button to the right of the screen.
-
-{.thumbnail}
-
-You are redirected to your cPanel interface.
-
-{.thumbnail}
-
-You can now use cPanel. For more information about cPanel, see the [official documentation](https://docs.cpanel.net/).
-
-> [!primary]
->
-> In your browser's navigation bar, enter the following URLs to connect:
->
-> - To cPanel: https://<IP_V4>:2083/ (use the credentials that have just been created in the WHM interface)
-> - To WHM: https://<IP_V4>:2087/ (use the root username and password received in the service purchase email or the SSH password that has been changed in the WHM interface)
->
-> Find your IPv4 address in the email you received when ordering your VPS with the cPanel distribution.
->
-
-### Securing your service
-
-We recommend taking all the necessary measures to secure your WHM and VPS by following the [cPanel recommendations](https://docs.cpanel.net/knowledge-base/security/tips-to-make-your-server-more-secure/).
-
-We also recommend reading our guide to [securing a VPS](/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps), using [our backup solutions](/products/bare-metal-cloud-virtual-private-servers) and configuring the [Edge Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network).
-
-## Go further
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-gb.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-gb.md
index c2ddb12c82a..194870526f0 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-gb.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-gb.md
@@ -1,7 +1,7 @@
---
title: "How to deploy cPanel on a VPS"
excerpt: "Find out how to instantiate a VPS with the preinstalled cPanel application"
-updated: 2025-07-14
+updated: 2025-09-11
---
## Objective
@@ -23,6 +23,9 @@ This simplifies website hosting, thanks to a graphical interface for automating
- A [VPS](/links/bare-metal/vps) solution with a [compatible distribution](/links/bare-metal/vps-os)
- Access to the [OVHcloud Control Panel](/links/manager)
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+
## Instructions
If you already have a VPS and want to have cPanel on it, you can reinstall the VPS from your [OVHcloud Control Panel](/links/manager) via a [cPanel-compatible OS](/links/bare-metal/vps-os).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-ie.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-ie.md
deleted file mode 100644
index c2ddb12c82a..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-ie.md
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: "How to deploy cPanel on a VPS"
-excerpt: "Find out how to instantiate a VPS with the preinstalled cPanel application"
-updated: 2025-07-14
----
-
-## Objective
-
-cPanel is a control panel that facilitates the management of web hosting. It makes complex tasks more accessible, especially to new users. It offers a wide range of features, such as:
-
-- Emails
-- Domain names
-- Databases
-- Security
-- etc.
-
-This simplifies website hosting, thanks to a graphical interface for automating settings.
-
-**This guide explains how to deploy cPanel with preinstalled applications on a VPS.**
-
-## Requirements
-
-- A [VPS](/links/bare-metal/vps) solution with a [compatible distribution](/links/bare-metal/vps-os)
-- Access to the [OVHcloud Control Panel](/links/manager)
-
-## Instructions
-
-If you already have a VPS and want to have cPanel on it, you can reinstall the VPS from your [OVHcloud Control Panel](/links/manager) via a [cPanel-compatible OS](/links/bare-metal/vps-os).
-
-> [!warning]
->
-> If you reinstall a VPS, all data stored on the VPS will be lost.
->
-
-To install your cPanel server, order a VPS with the cPanel distribution.
-
-{.thumbnail}
-
-When your VPS is ready, you will receive an email providing the information to connect to your cPanel server:
-
-```
- | Your application(s):
- | Application: cpanel
- | You can connect to cPanel from https://:2087/
-```
-
-### First login
-
-Once you have received the email containing the unique link, click on this link to perform the initial configuration. If the link has already expired, connect to the server [via SSH](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction) and run the command `sudo whmlogin` to generate a new link.
-
-The URL generated by the command `sudo whmlogin` allows you to log in to your WHM interface without any credentials (user and password). WHM is a server managemement tool used with cPanel. You will be able to access cPanel after completing the following steps.
-
-#### Step 1: Read and accept the cPanel Terms of Use
-
-Read and accept the cPanel Terms of Use.
-
-{.thumbnail}
-
-#### Step 2: Provide your email and nameservers you wish to set on the VPS
-
-{.thumbnail}
-
-#### Step 3: Set the root password
-
-{.thumbnail}
-
-You can now log in to your server via SSH, using the root user password you have just set.
-
-### Create a cPanel account from the WHM interface
-
-Once you have logged in to your WHM interface, click `Create a New Account`{.action} to create a cPanel account.
-
-{.thumbnail}
-
-Fill in the form, then confirm to create your cPanel account.
-
-{.thumbnail}
-
-On the new screen that pops up, click the `Go to cPanel`{.action} button to the right of the screen.
-
-{.thumbnail}
-
-You are redirected to your cPanel interface.
-
-{.thumbnail}
-
-You can now use cPanel. For more information about cPanel, see the [official documentation](https://docs.cpanel.net/).
-
-> [!primary]
->
-> In your browser's navigation bar, enter the following URLs to connect:
->
-> - To cPanel: https://<IP_V4>:2083/ (use the credentials that have just been created in the WHM interface)
-> - To WHM: https://<IP_V4>:2087/ (use the root username and password received in the service purchase email or the SSH password that has been changed in the WHM interface)
->
-> Find your IPv4 address in the email you received when ordering your VPS with the cPanel distribution.
->
-
-### Securing your service
-
-We recommend taking all the necessary measures to secure your WHM and VPS by following the [cPanel recommendations](https://docs.cpanel.net/knowledge-base/security/tips-to-make-your-server-more-secure/).
-
-We also recommend reading our guide to [securing a VPS](/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps), using [our backup solutions](/products/bare-metal-cloud-virtual-private-servers) and configuring the [Edge Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network).
-
-## Go further
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-sg.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-sg.md
deleted file mode 100644
index c2ddb12c82a..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-sg.md
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: "How to deploy cPanel on a VPS"
-excerpt: "Find out how to instantiate a VPS with the preinstalled cPanel application"
-updated: 2025-07-14
----
-
-## Objective
-
-cPanel is a control panel that facilitates the management of web hosting. It makes complex tasks more accessible, especially to new users. It offers a wide range of features, such as:
-
-- Emails
-- Domain names
-- Databases
-- Security
-- etc.
-
-This simplifies website hosting, thanks to a graphical interface for automating settings.
-
-**This guide explains how to deploy cPanel with preinstalled applications on a VPS.**
-
-## Requirements
-
-- A [VPS](/links/bare-metal/vps) solution with a [compatible distribution](/links/bare-metal/vps-os)
-- Access to the [OVHcloud Control Panel](/links/manager)
-
-## Instructions
-
-If you already have a VPS and want to have cPanel on it, you can reinstall the VPS from your [OVHcloud Control Panel](/links/manager) via a [cPanel-compatible OS](/links/bare-metal/vps-os).
-
-> [!warning]
->
-> If you reinstall a VPS, all data stored on the VPS will be lost.
->
-
-To install your cPanel server, order a VPS with the cPanel distribution.
-
-{.thumbnail}
-
-When your VPS is ready, you will receive an email providing the information to connect to your cPanel server:
-
-```
- | Your application(s):
- | Application: cpanel
- | You can connect to cPanel from https://:2087/
-```
-
-### First login
-
-Once you have received the email containing the unique link, click on this link to perform the initial configuration. If the link has already expired, connect to the server [via SSH](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction) and run the command `sudo whmlogin` to generate a new link.
-
-The URL generated by the command `sudo whmlogin` allows you to log in to your WHM interface without any credentials (user and password). WHM is a server managemement tool used with cPanel. You will be able to access cPanel after completing the following steps.
-
-#### Step 1: Read and accept the cPanel Terms of Use
-
-Read and accept the cPanel Terms of Use.
-
-{.thumbnail}
-
-#### Step 2: Provide your email and nameservers you wish to set on the VPS
-
-{.thumbnail}
-
-#### Step 3: Set the root password
-
-{.thumbnail}
-
-You can now log in to your server via SSH, using the root user password you have just set.
-
-### Create a cPanel account from the WHM interface
-
-Once you have logged in to your WHM interface, click `Create a New Account`{.action} to create a cPanel account.
-
-{.thumbnail}
-
-Fill in the form, then confirm to create your cPanel account.
-
-{.thumbnail}
-
-On the new screen that pops up, click the `Go to cPanel`{.action} button to the right of the screen.
-
-{.thumbnail}
-
-You are redirected to your cPanel interface.
-
-{.thumbnail}
-
-You can now use cPanel. For more information about cPanel, see the [official documentation](https://docs.cpanel.net/).
-
-> [!primary]
->
-> In your browser's navigation bar, enter the following URLs to connect:
->
-> - To cPanel: https://<IP_V4>:2083/ (use the credentials that have just been created in the WHM interface)
-> - To WHM: https://<IP_V4>:2087/ (use the root username and password received in the service purchase email or the SSH password that has been changed in the WHM interface)
->
-> Find your IPv4 address in the email you received when ordering your VPS with the cPanel distribution.
->
-
-### Securing your service
-
-We recommend taking all the necessary measures to secure your WHM and VPS by following the [cPanel recommendations](https://docs.cpanel.net/knowledge-base/security/tips-to-make-your-server-more-secure/).
-
-We also recommend reading our guide to [securing a VPS](/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps), using [our backup solutions](/products/bare-metal-cloud-virtual-private-servers) and configuring the [Edge Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network).
-
-## Go further
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-us.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-us.md
deleted file mode 100644
index c2ddb12c82a..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.en-us.md
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: "How to deploy cPanel on a VPS"
-excerpt: "Find out how to instantiate a VPS with the preinstalled cPanel application"
-updated: 2025-07-14
----
-
-## Objective
-
-cPanel is a control panel that facilitates the management of web hosting. It makes complex tasks more accessible, especially to new users. It offers a wide range of features, such as:
-
-- Emails
-- Domain names
-- Databases
-- Security
-- etc.
-
-This simplifies website hosting, thanks to a graphical interface for automating settings.
-
-**This guide explains how to deploy cPanel with preinstalled applications on a VPS.**
-
-## Requirements
-
-- A [VPS](/links/bare-metal/vps) solution with a [compatible distribution](/links/bare-metal/vps-os)
-- Access to the [OVHcloud Control Panel](/links/manager)
-
-## Instructions
-
-If you already have a VPS and want to have cPanel on it, you can reinstall the VPS from your [OVHcloud Control Panel](/links/manager) via a [cPanel-compatible OS](/links/bare-metal/vps-os).
-
-> [!warning]
->
-> If you reinstall a VPS, all data stored on the VPS will be lost.
->
-
-To install your cPanel server, order a VPS with the cPanel distribution.
-
-{.thumbnail}
-
-When your VPS is ready, you will receive an email providing the information to connect to your cPanel server:
-
-```
- | Your application(s):
- | Application: cpanel
- | You can connect to cPanel from https://:2087/
-```
-
-### First login
-
-Once you have received the email containing the unique link, click on this link to perform the initial configuration. If the link has already expired, connect to the server [via SSH](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction) and run the command `sudo whmlogin` to generate a new link.
-
-The URL generated by the command `sudo whmlogin` allows you to log in to your WHM interface without any credentials (user and password). WHM is a server managemement tool used with cPanel. You will be able to access cPanel after completing the following steps.
-
-#### Step 1: Read and accept the cPanel Terms of Use
-
-Read and accept the cPanel Terms of Use.
-
-{.thumbnail}
-
-#### Step 2: Provide your email and nameservers you wish to set on the VPS
-
-{.thumbnail}
-
-#### Step 3: Set the root password
-
-{.thumbnail}
-
-You can now log in to your server via SSH, using the root user password you have just set.
-
-### Create a cPanel account from the WHM interface
-
-Once you have logged in to your WHM interface, click `Create a New Account`{.action} to create a cPanel account.
-
-{.thumbnail}
-
-Fill in the form, then confirm to create your cPanel account.
-
-{.thumbnail}
-
-On the new screen that pops up, click the `Go to cPanel`{.action} button to the right of the screen.
-
-{.thumbnail}
-
-You are redirected to your cPanel interface.
-
-{.thumbnail}
-
-You can now use cPanel. For more information about cPanel, see the [official documentation](https://docs.cpanel.net/).
-
-> [!primary]
->
-> In your browser's navigation bar, enter the following URLs to connect:
->
-> - To cPanel: https://<IP_V4>:2083/ (use the credentials that have just been created in the WHM interface)
-> - To WHM: https://<IP_V4>:2087/ (use the root username and password received in the service purchase email or the SSH password that has been changed in the WHM interface)
->
-> Find your IPv4 address in the email you received when ordering your VPS with the cPanel distribution.
->
-
-### Securing your service
-
-We recommend taking all the necessary measures to secure your WHM and VPS by following the [cPanel recommendations](https://docs.cpanel.net/knowledge-base/security/tips-to-make-your-server-more-secure/).
-
-We also recommend reading our guide to [securing a VPS](/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps), using [our backup solutions](/products/bare-metal-cloud-virtual-private-servers) and configuring the [Edge Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network).
-
-## Go further
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.es-es.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.es-es.md
index 82ad590c533..c4197cefa84 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.es-es.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.es-es.md
@@ -1,7 +1,7 @@
---
title: "Desplegar cPanel en un VPS"
excerpt: "Descubra cómo instanciar un VPS con la aplicación cPanel preinstalada"
-updated: 2025-07-14
+updated: 2025-09-11
---
## Objetivo
@@ -16,8 +16,6 @@ cPanel es un panel de control que facilita la gestión de los alojamientos web.
Gracias a una interfaz gráfica que permite automatizar los parámetros, el alojamiento de sitios web se simplifica.
-**Descubra cómo desplegar cPanel con las aplicaciones preinstaladas en un VPS.**
-
**Esta guía explica cómo desplegar cPanel con aplicaciones preinstaladas en un VPS.**
## Requisitos
@@ -25,6 +23,10 @@ Gracias a una interfaz gráfica que permite automatizar los parámetros, el aloj
- Tener contratado un servicio [VPS reciente](/links/bare-metal/vps) con un [OS compatible con cPanel](/links/bare-metal/vps-os).
- Haber iniciado sesión en el [área de cliente de OVHcloud](/links/manager).
+> [!warning]
+> Esta funcionalidad no está disponible actualmente para los servidores virtuales en las [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Procedimiento
Si ya tiene un VPS y desea instalar cPanel, puede reinstalar el VPS desde su [área de cliente de OVHcloud](/links/manager) a través de un [OS compatible con cPanel](/links/bare-metal/vps-os).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.es-us.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.es-us.md
deleted file mode 100644
index 82ad590c533..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.es-us.md
+++ /dev/null
@@ -1,111 +0,0 @@
----
-title: "Desplegar cPanel en un VPS"
-excerpt: "Descubra cómo instanciar un VPS con la aplicación cPanel preinstalada"
-updated: 2025-07-14
----
-
-## Objetivo
-
-cPanel es un panel de control que facilita la gestión de los alojamientos web. Hace que las tareas complejas sean más accesibles, incluso para los nuevos usuarios. Ofrece una amplia gama de funcionalidades como, por ejemplo, para la gestión:
-
-- mensajes de correo
-- dominios
-- bases de datos
-- de la seguridad
-- etc.
-
-Gracias a una interfaz gráfica que permite automatizar los parámetros, el alojamiento de sitios web se simplifica.
-
-**Descubra cómo desplegar cPanel con las aplicaciones preinstaladas en un VPS.**
-
-**Esta guía explica cómo desplegar cPanel con aplicaciones preinstaladas en un VPS.**
-
-## Requisitos
-
-- Tener contratado un servicio [VPS reciente](/links/bare-metal/vps) con un [OS compatible con cPanel](/links/bare-metal/vps-os).
-- Haber iniciado sesión en el [área de cliente de OVHcloud](/links/manager).
-
-## Procedimiento
-
-Si ya tiene un VPS y desea instalar cPanel, puede reinstalar el VPS desde su [área de cliente de OVHcloud](/links/manager) a través de un [OS compatible con cPanel](/links/bare-metal/vps-os).
-
-> [!warning]
->
-> Si reinstala un VPS, todos los datos almacenados en el VPS se perderán.
->
-
-Para instalar su servidor cPanel, contrate un VPS con la distribución cPanel.
-
-{.thumbnail}
-
-Cuando su VPS esté listo, recibirá un correo electrónico con los datos de acceso para conectarse a su servidor cPanel:
-
-```
- | Sus aplicaciones:
- | Application: cpanel
- | Puede conectarse a cpanel desde https://:2087/
-```
-
-### Primera conexión
-
-Una vez que haya recibido el mensaje de correo electrónico con el enlace único, haga clic en este enlace para realizar la configuración inicial. Si el enlace ya ha expirado, conéctese al servidor por [SSH](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction) y ejecute el comando `sudo whmlogin` para generar un nuevo enlace.
-
-La URL generada por el comando `sudo whmlogin` le permite conectarse sin credenciales (usuario y contraseña) a su interfaz WHM. WHM es una capa de cPanel. Puede acceder a cPanel después de realizar los siguientes pasos.
-
-#### Etapa 1: leer y aceptar las condiciones de uso de cPanel
-
-Lea y acepte las condiciones de uso de cPanel.
-
-{.thumbnail}
-
-#### Etapa 2: Completar los campos obligatorios
-
-Indique los servidores de correo y de nombres (nameservers) que quiera configurar en el servidor VPS.
-
-{.thumbnail}
-
-#### Etapa 3: Establecer la contraseña root
-
-{.thumbnail}
-
-A partir de ahora, puede conectarse a su servidor por SSH utilizando el usuario root con la contraseña que acaba de establecer.
-
-### Crear una cuenta cPanel desde la interfaz WHM
-
-Una vez conectado a su interfaz WHM, haga clic en `Create a New Account`{.action} para crear una cuenta cPanel.
-
-{.thumbnail}
-
-Rellene el formulario y confirme la creación de su cuenta cPanel.
-
-{.thumbnail}
-
-En la nueva pantalla, haga clic en el botón `Go to cPanel`{.action} a la derecha de la pantalla.
-
-{.thumbnail}
-
-Será redirigido a su interfaz cPanel.
-
-{.thumbnail}
-
-Ya puede utilizar cPanel. Para más información sobre cPanel, consulte la [documentación oficial](https://docs.cpanel.net/).
-
-> [!primary]
->
-> En la barra de navegación de su navegador, introduzca las siguientes URL para conectarse a:
->
-> - cPanel: https://<IP_V4>:2083/ (utilice las claves recién creadas en la interfaz WHM)
-> - WHM: https://<IP_V4>:2087/ (utilice el nombre de usuario "root" y la contraseña recibida en el email de compra del servicio o la contraseña SSH que haya cambiado en la interfaz WHM)
->
-> Encuentre su dirección IPv4 en el mensaje de correo electrónico que recibió al contratar su VPS con la distribución cPanel.
->
-
-### Proteger el servicio
-
-Le recomendamos que tome todas las medidas necesarias para proteger su WHM y su VPS. Para ello, le recomendamos que lea [las recomendaciones de cPanel](https://docs.cpanel.net/knowledge-base/security/tips-to-make-your-server-more-secure/).
-
-Asimismo, le recomendamos que consulte nuestra guía para [proteger un VPS](/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps), utilice [nuestras soluciones de backup](/products/bare-metal-cloud-virtual-private-servers) y configure el [Edge Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network).
-
-## Más información
-
-Interactúe con nuestra [comunidad de usuarios](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.fr-ca.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.fr-ca.md
deleted file mode 100644
index 3aa773f0306..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.fr-ca.md
+++ /dev/null
@@ -1,109 +0,0 @@
----
-title: "Déployer cPanel sur un VPS"
-excerpt: "Découvrez comment instancier un VPS avec l’application cPanel pré-installée."
-updated: 2025-07-14
----
-
-## Objectif
-
-cPanel est un panneau de configuration qui facilite la gestion d'hébergements web. Il rend les tâches complexes plus accessibles, y compris pour les nouveaux utilisateurs. Il offre une vaste gamme de fonctionnalités comme, par exemple, pour la gestion :
-
-- des e-mails
-- des domaines
-- des bases de données
-- de la sécurité
-- etc.
-
-Grâce à une interface graphique permettant l'automatisation des paramètres, l'hébergement de sites web est ainsi simplifié.
-
-**Découvrez comment déployer cPanel avec les applications pré-installées sur un VPS.**
-
-## Prérequis
-
-- Disposer d'une offre [VPS](/links/bare-metal/vps) avec une distribution [compatible](/links/bare-metal/vps-os).
-- Être connecté à votre [espace client OVHcloud](/links/manager).
-
-## En pratique
-
-Si vous disposez déjà d'un VPS et que vous souhaitez y installer cPanel, vous pouvez réinstaller le VPS à partir de votre [espace client OVHcloud](/links/manager) via un [OS compatible avec cPanel](/links/bare-metal/vps-os).
-
-> [!warning]
->
-> Si vous réinstallez un VPS, toutes les données stockées sur le VPS seront perdues.
->
-
-Afin d'installer votre serveur cPanel, commandez un VPS avec la distribution cPanel.
-
-{.thumbnail}
-
-Quand votre VPS est prêt, vous recevez un e-mail vous donnant les accès pour vous connecter à votre serveur cPanel :
-
-```
- | Vos application(s):
- | Application: cpanel
- | Vous pouvez vous connecter à cpanel depuis https://:2087/
-```
-
-### Première connexion
-
-Une fois que vous avez reçu l'e-mail contenant le lien unique, cliquez sur ce lien pour effectuer la configuration initiale. Si le lien a déjà expiré, connectez-vous en [SSH](/pages/bare_metal_cloud/dedicated_servers/ssh_introduction) au serveur et exécutez la commande `sudo whmlogin` pour générer un nouveau lien.
-
-L'URL générée par la commande `sudo whmlogin` vous permet de vous connecter sans informations d'identification (utilisateur et mot de passe) à votre interface WHM. WHM est une surcouche de cPanel. Vous pourrez accéder à cPanel après avoir effectué les étapes suivantes.
-
-#### Étape 1 : lire et accepter les conditions d'utilisation de cPanel
-
-Lisez et acceptez les conditions d'utilisation de cPanel.
-
-{.thumbnail}
-
-#### Étape 2 : compléter les champs requis
-
-Indiquez les serveurs de messagerie et de noms (nameservers) que vous souhaitez définir sur le serveur VPS.
-
-{.thumbnail}
-
-#### Étape 3 : définir le mot de passe root
-
-{.thumbnail}
-
-Désormais, vous pouvez vous connecter à votre serveur en SSH en utilisant l'utilisateur root avec le mot de passe que vous venez de définir.
-
-### Créer un compte cPanel depuis l’interface WHM
-
-Une fois connecté à votre interface WHM, cliquez sur `Create a New Account`{.action} pour créer un compte cPanel.
-
-{.thumbnail}
-
-Remplissez le formulaire puis validez pour confirmer la création de votre compte cPanel.
-
-{.thumbnail}
-
-Sur le nouvel écran qui s'affiche, cliquez sur le boutton `Go to cPanel`{.action} à droite de l'écran.
-
-{.thumbnail}
-
-Vous êtes redirigé vers votre interface cPanel.
-
-{.thumbnail}
-
-Vous pouvez désormais utiliser cPanel. Pour toute information complémentaire concernant cPanel, consultez la [documentation officielle](https://docs.cpanel.net/).
-
-> [!primary]
->
-> Dans la barre de navigation de votre navigateur, entrez les URLs suivantes pour vous connecter à :
->
-> - cPanel : https://<IP_V4>:2083/ (utilisez les identifiants qui viennent d'être créés dans l'interface WHM)
-> - WHM : https://<IP_V4>:2087/ (utilisez le nom d'utilisateur « root » ainsi que le mot de passe reçu dans l’e-mail d’achat du service ou le mot de passe SSH qui a été modifié dans l’interface WHM)
->
-> Retrouvez votre adresse IPv4 dans l'e-mail que vous avez reçu suite à la commande de votre VPS avec la distribution cPanel.
->
-
-### Sécurisation de votre service
-
-Nous vous recommandons de prendre toutes les mesures nécessaires pour sécuriser votre WHM et votre VPS. Pour cela, nous vous recommandons de lire [les recommandations de cPanel](https://docs.cpanel.net/knowledge-base/security/tips-to-make-your-server-more-secure/).
-
-Nous vous recommandons également de consulter notre guide pour [sécuriser un VPS](/pages/bare_metal_cloud/virtual_private_servers/secure_your_vps), d'utiliser [nos solutions de sauvegarde](/products/bare-metal-cloud-virtual-private-servers) et de configurer le [Edge Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network).
-
-## Aller plus loin
-
-Échangez avec notre [communauté d'utilisateurs](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.fr-fr.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.fr-fr.md
index 8f17375fd33..098c956e64c 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.fr-fr.md
@@ -1,7 +1,7 @@
---
title: "Déployer cPanel sur un VPS"
excerpt: "Découvrez comment instancier un VPS avec l’application cPanel pré-installée."
-updated: 2025-07-14
+updated: 2025-09-11
---
## Objectif
@@ -23,6 +23,10 @@ Grâce à une interface graphique permettant l'automatisation des paramètres, l
- Disposer d'une offre [VPS](/links/bare-metal/vps) avec une distribution [compatible](/links/bare-metal/vps-os).
- Être connecté à votre [espace client OVHcloud](/links/manager).
+> [!warning]
+> Cette fonctionnalité est actuellement indisponible pour les serveurs privés virtuels dans les [Local Zones](/links/bare-metal/vps-lz).
+>
+
## En pratique
Si vous disposez déjà d'un VPS et que vous souhaitez y installer cPanel, vous pouvez réinstaller le VPS à partir de votre [espace client OVHcloud](/links/manager) via un [OS compatible avec cPanel](/links/bare-metal/vps-os).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.it-it.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.it-it.md
index 97ff402c80e..7f024d05fb0 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.it-it.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.it-it.md
@@ -1,7 +1,7 @@
---
title: "Deploy di cPanel su un VPS"
excerpt: "Come installare un VPS con l'applicazione cPanel preinstallata"
-updated: 2025-07-14
+updated: 2025-09-11
---
## Obiettivo
@@ -23,6 +23,10 @@ Grazie a un’interfaccia grafica che permette di automatizzare i parametri, l
- Disporre di una soluzione [VPS recente](/links/bare-metal/vps) con un [OS compatibile con cPanel](/links/bare-metal/vps-os).
- Avere accesso allo [Spazio Cliente OVHcloud](/links/manager).
+> [!warning]
+> Questa funzionalità non è attualmente disponibile per i server privati virtuali nelle [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Procedura
Se hai già un VPS e vuoi installarlo, puoi reinstallarlo dal tuo [Spazio Cliente OVHcloud](/links/manager) tramite un [OS compatibile con cPanel](/links/bare-metal/vps-os).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.pl-pl.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.pl-pl.md
index d7cab2915ec..34093c2b83d 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.pl-pl.md
@@ -1,7 +1,7 @@
---
title: "Instalacja cPanel na serwerze VPS"
excerpt: "Dowiedz się, jak utworzyć instancję VPS przy użyciu wstępnie zainstalowanej aplikacji cPanel"
-updated: 2025-07-14
+updated: 2025-09-11
---
## Wprowadzenie
@@ -23,6 +23,10 @@ Dzięki interfejsowi graficznemu umożliwiającemu automatyzację parametrów, h
- Wykupienie usługi [VPS](/links/bare-metal/vps) z dystrybucją [kompatybilną](/links/bare-metal/vps-os).
- zalogowanie do [Panelu client OVHcloud](/links/manager).
+> [!warning]
+> Funkcja ta nie jest aktualnie dostępna dla prywatnych serwerów wirtualnych w [Local Zones](/links/bare-metal/vps-lz).
+>
+
## W praktyce
Jeśli posiadasz już serwer VPS i chcesz na nim zainstalować cPanel, możesz wykonać reinstalację serwera VPS z poziomu [Panelu klienta OVHcloud](/links/manager) przez [OS kompatybilny z cPanelem](/links/bare-metal/vps-os).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.pt-pt.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.pt-pt.md
index aa6e277819b..05f517f2e66 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/cpanel/guide.pt-pt.md
@@ -1,7 +1,7 @@
---
title: "Implementar o cPanel num VPS"
excerpt: "Saiba como instanciar um VPS com a aplicação cPanel pré-instalada"
-updated: 2025-07-14
+updated: 2025-09-11
---
## Objetivo
@@ -23,6 +23,10 @@ Graças a uma interface gráfica que permite a automatização dos parâmetros,
- Ter uma oferta [VPS recente](/links/bare-metal/vps) com uma distribuição [compatível com cPanel](/links/bare-metal/vps-os).
- Estar ligado à [Área de Cliente OVHcloud](/links/manager).
+> [!warning]
+> Esta funcionalidade está atualmente indisponível para os servidores privados virtuais nas [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instruções
Se já dispõe de um VPS e deseja instalar o cPanel, pode reinstalar o VPS a partir da sua [Área de Cliente OVHcloud](/links/manager) através de um [OS compatível com cPanel](/links/bare-metal/vps-os).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel_snapshot/guide.en-gb.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel_snapshot/guide.en-gb.md
index 2e205b0c5b7..56801fc49e8 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel_snapshot/guide.en-gb.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/cpanel_snapshot/guide.en-gb.md
@@ -18,9 +18,13 @@ However, if Jailed Shell access is enabled, cPanel creates a *virtfs* which cann
## Requirements
-- A [VPS](https://www.ovhcloud.com/en-gb/vps) solution with a [compatible distribution](https://www.ovhcloud.com/en-gb/vps/os/)
+- A [VPS](/links/bare-metal/vps) solution with a [compatible distribution](/links/bare-metal/vps-os)
- cPanel installed on your server
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instructions
Decide on which of the 3 options above you would wish to proceed with and follow the section of the guide that corresponds to your choice. You only have to do one of the three options.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/cpanel_snapshot/guide.en-ie.md b/pages/bare_metal_cloud/virtual_private_servers/cpanel_snapshot/guide.en-ie.md
deleted file mode 100644
index b6d3be17585..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/cpanel_snapshot/guide.en-ie.md
+++ /dev/null
@@ -1,76 +0,0 @@
----
-title: 'Automated Backup - Kernel panic (cPanel)'
-excerpt: 'Find out how to fix issues with cPanel servers getting stuck during OVHcloud automated backup'
-updated: 2024-01-31
----
-
-## Objective
-
-When using the automated backup feature on a VPS which is running cPanel, you may experience cases when your VPS is stuck in backup status for a long time and may not be accessible. The root cause of this issue is when cPanel users use Jailed Shell access which creates a *virtfs* on your filesystem.
-
-When we create backups of your VPS (when you are subscribed to automated backups or snapshots), the hypervisor communicates to your VPS through the QEMU Guest Agent to freeze the filesystem on the VPS before we take the backup. This mechanism is there to ensure no writes happen to your disk while the backup is running and therefore ensures the consistency of the backup.
-
-However, if Jailed Shell access is enabled, cPanel creates a *virtfs* which cannot be frozen in this way. It will therefore lock up and cause a kernel panic as soon as the hypervisor initiates a freeze on the VPS. There are three ways to avoid this from happening and we explore them below.
-
-1. Disable QEMU Guest Agent
-2. Do not allow Jailed Shell
-3. Disable /tmp partition security (not recommended by cPanel, but it is an option available)
-
-## Requirements
-
-- A [VPS](https://www.ovhcloud.com/en-ie/vps) solution with a [compatible distribution](https://www.ovhcloud.com/en-ie/vps/os/)
-- cPanel installed on your server
-
-## Instructions
-
-Decide on which of the 3 options above you would wish to proceed with and follow the section of the guide that corresponds to your choice. You only have to do one of the three options.
-
-Please choose carefully as they each have their pros and cons.
-
-### Disable QEMU Guest Agent
-
-Firstly, you need to check if QEMU Guest Agent is running on your server. You can check this with the following command:
-
-```bash
-systemctl status qemu-guest-agent
-```
-
-The status of the service is indicated next to "Active:". If it is active/running then we need to stop the service and disable it from starting again in the future. You can do this with the following commands:
-
-```bash
-systemctl stop qemu-guest-agent
-systemctl disable qemu-guest-agent
-```
-
-### Switch from Jailed Shell to Normal Shell
-
-You can read about what is Jailed and Normal Shell [here](https://support.cpanel.net/hc/en-us/articles/360051992634-Differences-Between-Normal-and-Jailed-Shell).
-
-To disable a jailed shell environment for all new and modified users, you will need to disable the jailshell by default option in WHM’s Tweak Settings interface (WHM >> Home >> Server Configuration >> Tweak Settings).
-
-This option allows you to enable/disable the use of a jailed shell for new accounts and accounts that you subsequently edit in the following interfaces:
-
-1. WHM’s Modify An Account interface (WHM >> Home >> Account Functions >> Modify An Account)
-2. WHM’s Upgrade/Downgrade An Account interface (WHM >> Home >> Account Functions >> Upgrade/Downgrade An Account)
-
-This option does not affect accounts that already exist on the server but that you have not edited in these interfaces.
-
-To disable a jailed shell environment for a specific user, use WHM’s Manage Shell Access interface (WHM >> Home >> Account Functions >> Manage Shell Access).
-
-You can find all this information in the [cPanel official documentation](https://docs.cpanel.net/knowledge-base/accounts/virtfs-jailed-shell/#disable-or-remove-a-jailed-shell-environment).
-
-> [!warning]
->
-> As indicated by cPanel, some features can continue to use folders created by the Jailed Shell. As a consequence, even if the Jailed Shell environment is disabled, you may continue to experience difficulties in managing your backups.
->
-> If you still want to disable the Jailed Shell feature and delete the *virtfs* folders created, be careful as deleting the *virtfs* directory may result in loss of user data.
->
-> Make sure that you have made all the necessary backups in advance.
-
-### Disable cPanel /tmp partition security
-
-Please note this is not recommended by cPanel and at your own risk. Should you wish to continue with this option, you can find the exact steps on [this cPanel page](https://docs.cpanel.net/knowledge-base/security/tips-to-make-your-server-more-secure/#harden-your-tmp-partition).
-
-## Go further
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.de-de.md b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.de-de.md
index 4f0e89754cb..4c25463c5f8 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.de-de.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.de-de.md
@@ -17,6 +17,10 @@ Wenn Sie die maximale Kapazität Ihrer zusätzlichen Disk erreicht haben, könne
- Sie haben Zugriff auf Ihr [OVHcloud Kundencenter](/links/manager).
- Sie haben administrativen Zugriff auf Ihren VPS über SSH (Linux) oder RDP (Windows).
+> [!warning]
+> Diese Funktion ist derzeit nicht verfügbar für VPS in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## In der praktischen Anwendung
In den folgenden Schritten wird vorausgesetzt, dass Sie bereits eine zusätzliche Disk erstellt haben, wie [in unserer Anleitung beschrieben](/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-asia.md b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-asia.md
index 028eda20d8a..b5ace7ad6e1 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-asia.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-asia.md
@@ -17,6 +17,10 @@ If you have reached the maximum capacity on your additional disk, you can add mo
- Access to the [OVHcloud Control Panel](/links/manager)
- Administrative access via SSH or RDP to your VPS
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instructions
The following steps presume that you have configured an additional disk according to [our guide](/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-au.md b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-au.md
index 028eda20d8a..b5ace7ad6e1 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-au.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-au.md
@@ -17,6 +17,10 @@ If you have reached the maximum capacity on your additional disk, you can add mo
- Access to the [OVHcloud Control Panel](/links/manager)
- Administrative access via SSH or RDP to your VPS
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instructions
The following steps presume that you have configured an additional disk according to [our guide](/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-ca.md b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-ca.md
index 028eda20d8a..b5ace7ad6e1 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-ca.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-ca.md
@@ -17,6 +17,10 @@ If you have reached the maximum capacity on your additional disk, you can add mo
- Access to the [OVHcloud Control Panel](/links/manager)
- Administrative access via SSH or RDP to your VPS
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instructions
The following steps presume that you have configured an additional disk according to [our guide](/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-gb.md b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-gb.md
index 028eda20d8a..b5ace7ad6e1 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-gb.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-gb.md
@@ -17,6 +17,10 @@ If you have reached the maximum capacity on your additional disk, you can add mo
- Access to the [OVHcloud Control Panel](/links/manager)
- Administrative access via SSH or RDP to your VPS
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instructions
The following steps presume that you have configured an additional disk according to [our guide](/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-ie.md b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-ie.md
index 028eda20d8a..b5ace7ad6e1 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-ie.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-ie.md
@@ -17,6 +17,10 @@ If you have reached the maximum capacity on your additional disk, you can add mo
- Access to the [OVHcloud Control Panel](/links/manager)
- Administrative access via SSH or RDP to your VPS
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instructions
The following steps presume that you have configured an additional disk according to [our guide](/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-sg.md b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-sg.md
index 028eda20d8a..b5ace7ad6e1 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-sg.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-sg.md
@@ -17,6 +17,10 @@ If you have reached the maximum capacity on your additional disk, you can add mo
- Access to the [OVHcloud Control Panel](/links/manager)
- Administrative access via SSH or RDP to your VPS
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instructions
The following steps presume that you have configured an additional disk according to [our guide](/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-us.md b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-us.md
index 028eda20d8a..b5ace7ad6e1 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-us.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.en-us.md
@@ -17,6 +17,10 @@ If you have reached the maximum capacity on your additional disk, you can add mo
- Access to the [OVHcloud Control Panel](/links/manager)
- Administrative access via SSH or RDP to your VPS
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instructions
The following steps presume that you have configured an additional disk according to [our guide](/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.es-es.md b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.es-es.md
index a265760ae7d..84dc3c5047a 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.es-es.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.es-es.md
@@ -17,6 +17,10 @@ Si ha alcanzado la capacidad máxima de su disco adicional, puede añadir almace
- Tienes acceso a tu [Panel de configuración de OVHcloud](/links/manager).
- Tener acceso al VPS por SSH o RDP para la administración.
+> [!warning]
+> Esta funcionalidad no está disponible actualmente para los servidores virtuales en las [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Procedimiento
Los pasos que se indican a continuación suponen que ha configurado un disco adicional siguiendo las instrucciones de [esta guía](/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.es-us.md b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.es-us.md
index a265760ae7d..84dc3c5047a 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.es-us.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.es-us.md
@@ -17,6 +17,10 @@ Si ha alcanzado la capacidad máxima de su disco adicional, puede añadir almace
- Tienes acceso a tu [Panel de configuración de OVHcloud](/links/manager).
- Tener acceso al VPS por SSH o RDP para la administración.
+> [!warning]
+> Esta funcionalidad no está disponible actualmente para los servidores virtuales en las [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Procedimiento
Los pasos que se indican a continuación suponen que ha configurado un disco adicional siguiendo las instrucciones de [esta guía](/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.fr-ca.md b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.fr-ca.md
index 904e57cfad9..3c690be8183 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.fr-ca.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.fr-ca.md
@@ -17,6 +17,10 @@ Si vous avez atteint la capacité maximale de votre disque additionnel, vous pou
- Être connecté à votre [espace client OVHcloud](/links/manager).
- Avoir accès à votre VPS en SSH ou en RDP pour l'administration.
+> [!warning]
+> Cette fonctionnalité est actuellement indisponible pour les serveurs privés virtuels dans les [Local Zones](/links/bare-metal/vps-lz).
+>
+
## En pratique
Les étapes ci-dessous supposent que vous avez configuré un disque additionnel en suivant les instructions de [ce guide](/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.fr-fr.md b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.fr-fr.md
index 904e57cfad9..3c690be8183 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.fr-fr.md
@@ -17,6 +17,10 @@ Si vous avez atteint la capacité maximale de votre disque additionnel, vous pou
- Être connecté à votre [espace client OVHcloud](/links/manager).
- Avoir accès à votre VPS en SSH ou en RDP pour l'administration.
+> [!warning]
+> Cette fonctionnalité est actuellement indisponible pour les serveurs privés virtuels dans les [Local Zones](/links/bare-metal/vps-lz).
+>
+
## En pratique
Les étapes ci-dessous supposent que vous avez configuré un disque additionnel en suivant les instructions de [ce guide](/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.it-it.md b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.it-it.md
index a84002145dd..8f621f2cb36 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.it-it.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.it-it.md
@@ -17,6 +17,10 @@ Se hai raggiunto la capacità massima del tuo disco aggiuntivo, puoi aggiungere
- Avere accesso allo [Spazio Cliente OVHcloud](/links/manager).
- Avere accesso al VPS in SSH o in RDP per l'amministrazione.
+> [!warning]
+> Questa funzionalità non è attualmente disponibile per i server privati virtuali nelle [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Procedura
Negli step successivi è necessario aver configurato un disco aggiuntivo seguendo le indicazioni di [questa guida](/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.pl-pl.md b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.pl-pl.md
index 5e0c9931699..785f0554087 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.pl-pl.md
@@ -17,6 +17,10 @@ Jeśli osiągnąłeś maksymalną pojemność dodatkowego dysku, możesz zwięks
- Dostęp do [Panelu client OVHcloud](/links/manager).
- Dostęp do serwera VPS przez SSH lub RDP.
+> [!warning]
+> Funkcja ta nie jest aktualnie dostępna dla prywatnych serwerów wirtualnych w [Local Zones](/links/bare-metal/vps-lz).
+>
+
## W praktyce
Poniższe etapy zakładają, że skonfigurowałeś dodatkowy dysk zgodnie z instrukcjami zawartymi w [tym przewodniku](/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.pt-pt.md b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.pt-pt.md
index b3b341086c1..718be198e59 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/increase_additional_disk/guide.pt-pt.md
@@ -17,6 +17,10 @@ Se atingiu a capacidade máxima do seu disco adicional, pode adicionar armazenam
- Ter acesso à [Área de Cliente OVHcloud](/links/manager).
- Ter acesso ao VPS por SSH ou RDP para a administração.
+> [!warning]
+> Esta funcionalidade está atualmente indisponível para os servidores privados virtuais nas [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instruções
Os passos abaixo sugerem que configurou um disco adicional seguindo as instruções [deste manual](/pages/bare_metal_cloud/virtual_private_servers/config_additional_disk).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.de-de.md b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.de-de.md
index 35416e958dd..57a147fe6be 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.de-de.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.de-de.md
@@ -1,7 +1,7 @@
---
title: Erste Schritte mit einem VPS
excerpt: Erfahren Sie hier, wie Sie einen VPS in Ihrem Kundencenter verwalten sowie die ersten Schritte zum Start, inklusive Remote-Verbindungen und Sicherheitsmaßnahmen
-updated: 2025-09-05
+updated: 2025-09-11
---
## Ziel
@@ -15,6 +15,11 @@ Ein Virtual Private Server (VPS) ist ein virtualisierter Dedicated Server, der I
- Sie haben einen [VPS](/links/bare-metal/vps) in Ihrem OVHcloud Kundencenter.
- Sie haben Zugriff auf Ihr [OVHcloud Kundencenter](/links/manager).
+> [!warning]
+> Nicht alle auf dieser Seite erwähnten VPS-Funktionen sind in OVHcloud Local Zones verfügbar.
+>
+> Beachten Sie dazu die Informationen auf unserer [Local Zones Webseite](/links/bare-metal/vps-lz).
+
## In der praktischen Anwendung
### Inhaltsübersicht
diff --git a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-asia.md b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-asia.md
index 11314a6b3e4..ba361252da4 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-asia.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-asia.md
@@ -1,7 +1,7 @@
---
title: How to get started with a VPS
excerpt: Find out how to manage a VPS in the OVHcloud Control Panel and the first steps of using a VPS, including remote connections and security measures
-updated: 2025-09-05
+updated: 2025-09-11
---
## Objective
@@ -15,6 +15,11 @@ A **V**irtual **P**rivate **S**erver is a virtualized dedicated server that give
- An active [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account
- Access to the [OVHcloud Control Panel](/links/manager)
+> [!warning]
+> Not all VPS features mentioned on this page are available in OVHcloud Local Zones.
+>
+> Please visit our [Local Zones web page](/links/bare-metal/vps-lz) for more information.
+
## Instructions
### Content overview
diff --git a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-au.md b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-au.md
index 9a0ca2d264b..183c5861f3d 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-au.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-au.md
@@ -1,7 +1,7 @@
---
title: How to get started with a VPS
excerpt: Find out how to manage a VPS in the OVHcloud Control Panel and the first steps of using a VPS, including remote connections and security measures
-updated: 2025-09-05
+updated: 2025-09-11
---
## Objective
@@ -15,6 +15,11 @@ A **V**irtual **P**rivate **S**erver is a virtualized dedicated server that give
- An active [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account
- Access to the [OVHcloud Control Panel](/links/manager)
+> [!warning]
+> Not all VPS features mentioned on this page are available in OVHcloud Local Zones.
+>
+> Please visit our [Local Zones web page](/links/bare-metal/vps-lz) for more information.
+
## Instructions
### Content overview
diff --git a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-ca.md b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-ca.md
index 9a0ca2d264b..183c5861f3d 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-ca.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-ca.md
@@ -1,7 +1,7 @@
---
title: How to get started with a VPS
excerpt: Find out how to manage a VPS in the OVHcloud Control Panel and the first steps of using a VPS, including remote connections and security measures
-updated: 2025-09-05
+updated: 2025-09-11
---
## Objective
@@ -15,6 +15,11 @@ A **V**irtual **P**rivate **S**erver is a virtualized dedicated server that give
- An active [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account
- Access to the [OVHcloud Control Panel](/links/manager)
+> [!warning]
+> Not all VPS features mentioned on this page are available in OVHcloud Local Zones.
+>
+> Please visit our [Local Zones web page](/links/bare-metal/vps-lz) for more information.
+
## Instructions
### Content overview
diff --git a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-gb.md b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-gb.md
index 9a0ca2d264b..183c5861f3d 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-gb.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-gb.md
@@ -1,7 +1,7 @@
---
title: How to get started with a VPS
excerpt: Find out how to manage a VPS in the OVHcloud Control Panel and the first steps of using a VPS, including remote connections and security measures
-updated: 2025-09-05
+updated: 2025-09-11
---
## Objective
@@ -15,6 +15,11 @@ A **V**irtual **P**rivate **S**erver is a virtualized dedicated server that give
- An active [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account
- Access to the [OVHcloud Control Panel](/links/manager)
+> [!warning]
+> Not all VPS features mentioned on this page are available in OVHcloud Local Zones.
+>
+> Please visit our [Local Zones web page](/links/bare-metal/vps-lz) for more information.
+
## Instructions
### Content overview
diff --git a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-ie.md b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-ie.md
index 9a0ca2d264b..183c5861f3d 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-ie.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-ie.md
@@ -1,7 +1,7 @@
---
title: How to get started with a VPS
excerpt: Find out how to manage a VPS in the OVHcloud Control Panel and the first steps of using a VPS, including remote connections and security measures
-updated: 2025-09-05
+updated: 2025-09-11
---
## Objective
@@ -15,6 +15,11 @@ A **V**irtual **P**rivate **S**erver is a virtualized dedicated server that give
- An active [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account
- Access to the [OVHcloud Control Panel](/links/manager)
+> [!warning]
+> Not all VPS features mentioned on this page are available in OVHcloud Local Zones.
+>
+> Please visit our [Local Zones web page](/links/bare-metal/vps-lz) for more information.
+
## Instructions
### Content overview
diff --git a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-sg.md b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-sg.md
index 11314a6b3e4..ba361252da4 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-sg.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-sg.md
@@ -1,7 +1,7 @@
---
title: How to get started with a VPS
excerpt: Find out how to manage a VPS in the OVHcloud Control Panel and the first steps of using a VPS, including remote connections and security measures
-updated: 2025-09-05
+updated: 2025-09-11
---
## Objective
@@ -15,6 +15,11 @@ A **V**irtual **P**rivate **S**erver is a virtualized dedicated server that give
- An active [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account
- Access to the [OVHcloud Control Panel](/links/manager)
+> [!warning]
+> Not all VPS features mentioned on this page are available in OVHcloud Local Zones.
+>
+> Please visit our [Local Zones web page](/links/bare-metal/vps-lz) for more information.
+
## Instructions
### Content overview
diff --git a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-us.md b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-us.md
index 9a0ca2d264b..183c5861f3d 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-us.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.en-us.md
@@ -1,7 +1,7 @@
---
title: How to get started with a VPS
excerpt: Find out how to manage a VPS in the OVHcloud Control Panel and the first steps of using a VPS, including remote connections and security measures
-updated: 2025-09-05
+updated: 2025-09-11
---
## Objective
@@ -15,6 +15,11 @@ A **V**irtual **P**rivate **S**erver is a virtualized dedicated server that give
- An active [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account
- Access to the [OVHcloud Control Panel](/links/manager)
+> [!warning]
+> Not all VPS features mentioned on this page are available in OVHcloud Local Zones.
+>
+> Please visit our [Local Zones web page](/links/bare-metal/vps-lz) for more information.
+
## Instructions
### Content overview
diff --git a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.es-es.md b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.es-es.md
index 2c8fcb02baf..3b886944c6f 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.es-es.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.es-es.md
@@ -1,7 +1,7 @@
---
title: Primeros pasos con un VPS
excerpt: Aprenda a gestionar un VPS en su área de cliente y descubra las primeras etapas de su uso, incluyendo las conexiones a distancia y las medidas de seguridad
-updated: 2025-09-05
+updated: 2025-09-11
---
## Objetivo
@@ -15,6 +15,11 @@ Un servidor privado virtual o VPS (del inglés «virtual private server») es un
- Tener un [VPS](/links/bare-metal/vps) en el área de cliente de OVHcloud
- Tienes acceso a tu [área de cliente de OVHcloud](/links/manager).
+> [!warning]
+> No todas las funciones de VPS mencionadas en esta página están disponibles en las Local Zones de OVHcloud.
+>
+> Para más información, consulte la [página web de las Local Zones](/links/bare-metal/vps-lz).
+
## Procedimiento
### Contenido
diff --git a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.es-us.md b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.es-us.md
index 2c8fcb02baf..3b886944c6f 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.es-us.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.es-us.md
@@ -1,7 +1,7 @@
---
title: Primeros pasos con un VPS
excerpt: Aprenda a gestionar un VPS en su área de cliente y descubra las primeras etapas de su uso, incluyendo las conexiones a distancia y las medidas de seguridad
-updated: 2025-09-05
+updated: 2025-09-11
---
## Objetivo
@@ -15,6 +15,11 @@ Un servidor privado virtual o VPS (del inglés «virtual private server») es un
- Tener un [VPS](/links/bare-metal/vps) en el área de cliente de OVHcloud
- Tienes acceso a tu [área de cliente de OVHcloud](/links/manager).
+> [!warning]
+> No todas las funciones de VPS mencionadas en esta página están disponibles en las Local Zones de OVHcloud.
+>
+> Para más información, consulte la [página web de las Local Zones](/links/bare-metal/vps-lz).
+
## Procedimiento
### Contenido
diff --git a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.fr-ca.md b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.fr-ca.md
index b91adbbf499..ed561e8ea5c 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.fr-ca.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.fr-ca.md
@@ -1,7 +1,7 @@
---
title: Premiers pas avec un VPS
excerpt: "Apprenez à gérer un VPS dans votre espace client et découvrez les premières étapes de son utilisation, notamment les connexions à distance et les mesures de sécurité"
-updated: 2025-09-05
+updated: 2025-09-11
---
## Objectif
@@ -17,6 +17,11 @@ Un serveur privé virtuel (VPS) est un serveur dédié virtualisé qui vous offr
- Disposer d'une offre [VPS](/links/bare-metal/vps) active dans votre espace client OVHcloud
- Être connecté à votre [espace client OVHcloud](/links/manager)
+> [!warning]
+> Certaines fonctionnalités VPS mentionnées sur cette page ne sont pas disponibles dans les Local Zones OVHcloud.
+>
+> Veuillez visiter notre [page Web des Local Zones](/links/bare-metal/vps-lz) pour obtenir plus d'informations.
+
## En pratique
### Sommaire
diff --git a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.fr-fr.md b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.fr-fr.md
index b91adbbf499..ed561e8ea5c 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.fr-fr.md
@@ -1,7 +1,7 @@
---
title: Premiers pas avec un VPS
excerpt: "Apprenez à gérer un VPS dans votre espace client et découvrez les premières étapes de son utilisation, notamment les connexions à distance et les mesures de sécurité"
-updated: 2025-09-05
+updated: 2025-09-11
---
## Objectif
@@ -17,6 +17,11 @@ Un serveur privé virtuel (VPS) est un serveur dédié virtualisé qui vous offr
- Disposer d'une offre [VPS](/links/bare-metal/vps) active dans votre espace client OVHcloud
- Être connecté à votre [espace client OVHcloud](/links/manager)
+> [!warning]
+> Certaines fonctionnalités VPS mentionnées sur cette page ne sont pas disponibles dans les Local Zones OVHcloud.
+>
+> Veuillez visiter notre [page Web des Local Zones](/links/bare-metal/vps-lz) pour obtenir plus d'informations.
+
## En pratique
### Sommaire
diff --git a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.it-it.md b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.it-it.md
index 3d73b7f8c66..86eff6109e2 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.it-it.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.it-it.md
@@ -1,7 +1,7 @@
---
title: Iniziare a utilizzare un VPS
excerpt: Come gestire un VPS dallo Spazio Cliente OVHcloud e scopri gli step iniziali del suo utilizzo, incluse le connessioni remote e le misure di sicurezza
-updated: 2025-09-05
+updated: 2025-09-11
---
## Obiettivo
@@ -15,6 +15,11 @@ Un server privato virtuale (VPS) è un server dedicato virtualizzato che offre g
- Disporre di un [VPS](/links/bare-metal/vps) nello Spazio Cliente OVHcloud
- Avere accesso allo [Spazio Cliente OVHcloud](/links/manager)
+> [!warning]
+> Non tutte le funzionalità dei VPS citate in questa pagina sono disponibili nelle Local Zones di OVHcloud.
+>
+> Per maggiori informazioni, consulta la [pagina Web des Local Zones](/links/bare-metal/vps-lz).
+
## Procedura
### Sommario
diff --git a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.pl-pl.md b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.pl-pl.md
index 34dd56ed5e0..b260d8cc911 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.pl-pl.md
@@ -1,7 +1,7 @@
---
title: Pierwsze kroki z serwerem VPS
excerpt: Dowiedz się, jak zarządzać serwerem VPS w Panelu klienta i poznaj pierwsze kroki korzystania z niego, w tym zdalne połączenia i środki bezpieczeństwa
-updated: 2025-09-05
+updated: 2025-09-11
---
## Wprowadzenie
@@ -15,6 +15,11 @@ Prywatny serwer wirtualny (VPS) to zwirtualizowany serwer dedykowany, który zap
- Posiadanie serwera [VPS](/links/bare-metal/vps) w Panelu klienta OVHcloud
- Dostęp do [Panelu klienta OVHcloud](/links/manager)
+> [!warning]
+> Nie wszystkie funkcje VPS wymienione na tej stronie są dostępne w Local Zones OVHcloud.
+>
+> Aby uzyskać więcej informacji, zobacz [stronie WWW Local Zones](/links/bare-metal/vps-lz).
+
## W praktyce
### Podsumowanie
diff --git a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.pt-pt.md b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.pt-pt.md
index 8fd7e3c5d4b..556359de747 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/starting_with_a_vps/guide.pt-pt.md
@@ -1,7 +1,7 @@
---
title: Primeiros passos com um VPS
excerpt: Aprenda a gerir um VPS na sua Área de Cliente e descubra as primeiras etapas da sua utilização, nomeadamente as ligações remotas e as medidas de segurança
-updated: 2025-09-05
+updated: 2025-09-11
---
## Objetivo
@@ -15,6 +15,11 @@ Um servidor privado virtual (VPS) é um servidor dedicado virtualizado que lhe o
- Ter um [VPS](/links/bare-metal/vps) na Área de Cliente OVHcloud
- Ter acesso à [Área de Cliente OVHcloud](/links/manager)
+> [!warning]
+> Nem todas as funcionalidades VPS mencionadas nesta página estão disponíveis nas Zonas Locais da OVHcloud.
+>
+> Para mais informações, visite a nossa [página Web das Local Zones](/links/bare-metal/vps-lz).
+
## Instruções
### Índice
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.de-de.md b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.de-de.md
index d44bb2c2bbc..bb2e2e6d965 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.de-de.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.de-de.md
@@ -1,7 +1,7 @@
---
title: "Automatische Backups auf einem VPS verwenden"
excerpt: "Erfahren Sie, wie Sie im OVHcloud Kundencenter die Backup-Option verwenden, um Ihre Daten zu sichern"
-updated: 2025-08-07
+updated: 2025-09-11
---
## Ziel
@@ -21,6 +21,10 @@ Bevor Sie Backup-Optionen anwenden, empfehlen wir, die [Produktseiten und FAQ](/
- Sie haben einen [VPS](/links/bare-metal/vps) in Ihrem Kunden-Account.
- Administratorzugang (sudo) über SSH auf Ihren VPS (optional)
+> [!warning]
+> Diese Funktion ist derzeit nicht verfügbar für VPS in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## In der praktischen Anwendung
### Inhaltsübersicht
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-asia.md b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-asia.md
deleted file mode 100644
index f44b6b23153..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-asia.md
+++ /dev/null
@@ -1,298 +0,0 @@
----
-title: "How to use automated backups on a VPS"
-excerpt: "Find out how to use the Automated backup option in the OVHcloud Control Panel to secure your data"
-updated: 2025-08-07
----
-
-## Objective
-
-The Automated backup option for VPS offers a convenient way to have complete system backups available from your OVHcloud Control Panel without having to connect to the server to create and restore them manually. Another advantage is that you can also choose to mount a backup and then access its files remotely.
-
-**This guide explains the Automated backup option for your OVHcloud VPS.**
-
-> [!primary]
-> Before applying a backup strategy, we recommend to consult the [product pages and FAQ](/links/bare-metal/vps-options) for pricing comparisons and further details.
->
-
-## Requirements
-
-- Access to the [OVHcloud Control Panel](/links/manager).
-- A [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account.
-- Administrative access (sudo) via SSH to your VPS (optional).
-
-## Instructions
-
-### Content overview
-
-- [How to upgrade to Premium Automated Backup](#premium)
-- [How to configure the backup time](#time)
-- [How to restore a backup from the OVHcloud Control Panel](#restore)
-- [How to mount and access a backup](#mount)
- - [Using Secure Shell](#shell)
- - [Using Windows](#windows)
-- [Best practice for using Automated backups](#bestpractice)
- - [Configuring the QEMU agent on a VPS](#qemu)
- - [Debian-based distributions](#deb)
- - [Redhat-based distributions](#red)
- - [Windows](#win)
-
-Log in to your [OVHcloud Control Panel](/links/manager), open the `Bare Metal Cloud`{.action} section, and select your server under `Virtual Private Servers`{.action}.
-
-When you order a VPS, a single daily Automated backup is included as a free service option. This standard backup option allows you to:
-
-- Mount and restore the daily backup.
-- Set the time of day this backup will be created.
-
-For more flexiblity with your backups, you can activate the Premium Automated Backup option.
-
-
-
-### How to upgrade to Premium Automated Backup
-
-Upgrading to Premium Automated Backup enhances your Automated backup option to a 7-day rolling daily backup. This allows you to revert to older backup versions compared to the 24-hour rotation of the standard option.
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-
-Click the link `Order a premium backup`{.action}.
-
-{.thumbnail}
-
-In the next step, please take note of the pricing information, then click on `Order`{.action}. You will be guided through the order process and receive a confirmation email.
-
-
-
-### How to configure the backup time
-
-You can change the time of day at which the backup will take place.
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-
-Click on `...`{.action} above the table and then on `Edit`{.action}.
-
-{.thumbnail}
-
-In the window that appears, edit the time of day (24-hour UTC time standard). Click on `Confirm`{.action}.
-
-{.thumbnail}
-
-> [!primary]
->
-Once confirmed in the Control Panel, the change will come into effect after 24 to 48 hours.
->
-
-
-
-### How to restore a backup from the OVHcloud Control Panel
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-Click the button `...`{.action} next to the backup you would like to restore and select `Restoration`{.action}.
-
-{.thumbnail}
-
-If you recently changed your root password, make sure to tick the option "Modify the root password on restoration" in the popup window to preserve your current root password and click on `Confirm`{.action}. You will receive an email as soon as the task is complete. The restoration might take a while, depending on the disk space used.
-
-> [!alert]
->
-> Please note that the automated backups will not include your additional disks.
->
-
-
-
-### How to mount and access a backup
-
-It is not necessary to completely overwrite your existing service with a restoration. The "Mounting" option allows you to access the backup data to retrieve your files.
-
-> [!warning]
->
-> OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
->
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialist service provider](/links/partner) or reaching out to the [OVHcloud community](/links/community) if you encounter any difficulties. You can find more information in the [Go further](#go-further) section of this guide.
->
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-Click on `...`{.action} next to the backup you need to access and select `Mounting`{.action}.
-
-{.thumbnail}
-
-When you use this option, a read-write copy of the backup is created and mounted. The original backup will remain available unchanged for future restorations.
-
-After the process is completed, you will receive an email. You can now connect to your VPS and access the partition where your backup is located.
-
-
-
-#### Using Secure Shell
-
-First, connect to your VPS via SSH.
-
-You can use the following command to verify the name of the newly attached device:
-
-```bash
-lsblk
-```
-
-Here is a sample output of this command:
-
-```console
-NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
-sda 8:0 0 25G 0 disk
-├─sda1 8:1 0 24.9G 0 part /
-├─sda14 8:14 0 4M 0 part
-└─sda15 8:15 0 106M 0 part
-sdb 8:16 0 25G 0 disk
-├─sdb1 8:17 0 24.9G 0 part
-├─sdb14 8:30 0 4M 0 part
-└─sdb15 8:31 0 106M 0 part /boot/efi
-```
-
-In this example, the partition containing your backup filesystem is named "sdb1".
-Next, create a directory for this partition and define it as the mountpoint:
-
-```bash
-sudo mkdir -p /mnt/restore
-sudo mount /dev/sdb1 /mnt/restore
-```
-
-You can now switch to this folder and access your backup data.
-
-Remember to unmount the backup once you have finished using it. Click on the button `Unmount the backup`{.action} in the `Automated backup`{.action} tab, then confirm in the popup window.
-
-{.thumbnail}
-
-
-
-#### Using Windows
-
-Establish an RDP connection to your server.
-
-Once logged in, right-click on the `Start Menu`{.action} button, and then click `Disk Management`{.action}.
-
-{.thumbnail}
-
-When the disk management tool opens, your mounted backup will appear as a basic disk with the same storage space as your main disk.
-
-{.thumbnail}
-
-The disk will appear as `Offline`, right-click on the disk and select `Online`{.action}.
-
-{.thumbnail}
-
-Once done, your mounted backup will be accessible in the `File Explorer`.
-
-{.thumbnail}
-
-Remember to unmount the backup once you have finished using it. Click on the button `Unmount the backup`{.action} in the `Automated backup`{.action} tab, then confirm in the popup window.
-
-{.thumbnail}
-
-> [!warning]
->
-> Please note that a server reboot will occur when the backup is unmounted.
->
-
-
-
-### Best practice for using Automated backups
-
-The Automated Backup functionality is based on VPS snapshots. We recommend to follow the steps below to prevent any issues before using this option.
-
-
-
-#### Configuring the QEMU agent on a VPS
-
-Snapshots are instantaneous images of your running system ("live snapshot"). To ensure the availability of your system when the snapshot is created, the QEMU agent is used to prepare the filesystem for the process.
-
-The "**qemu-guest-agent**" agent is not installed by default on most distributions. Moreover, licensing restrictions may prevent OVHcloud from including it in the available OS images. Therefore, it is best practice to verify and install the agent in case it is not activated on your VPS. Connect to your VPS via SSH and follow the instructions below, according to your operating system.
-
-
-
-##### **Debian-based distributions (Debian, Ubuntu)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-```
-
-The expected output is:
-
-```console
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different, for example "No such file or directory", install the latest version of the package:
-
-```bash
-sudo apt-get update
-sudo apt-get install qemu-guest-agent
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Start the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent start
-```
-
-
-
-##### **Redhat-based distributions (Centos, Fedora)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-```
-
-The expected output is:
-
-```console
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different, for example "No such file or directory", install and enable the agent:
-
-```bash
-sudo yum install qemu-guest-agent
-sudo chkconfig qemu-guest-agent on
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Start the agent and verify that it is running:
-
-```bash
-sudo service qemu-guest-agent start
-sudo service qemu-guest-agent status
-```
-
-
-
-##### **Windows**
-
-You can install the agent via MSI file, available from the Fedora project website: .
-
-Verify that the service is running by using this powershell command:
-
-```console
-PS C:\Users\Administrator> Get-Service QEMU-GA
-Status Name DisplayName
------- ---- -----------
-Running QEMU-GA QEMU Guest Agent
-```
-
-
-
-## Go further
-
-[Using snapshots on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps)
-
-Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-au.md b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-au.md
deleted file mode 100644
index f44b6b23153..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-au.md
+++ /dev/null
@@ -1,298 +0,0 @@
----
-title: "How to use automated backups on a VPS"
-excerpt: "Find out how to use the Automated backup option in the OVHcloud Control Panel to secure your data"
-updated: 2025-08-07
----
-
-## Objective
-
-The Automated backup option for VPS offers a convenient way to have complete system backups available from your OVHcloud Control Panel without having to connect to the server to create and restore them manually. Another advantage is that you can also choose to mount a backup and then access its files remotely.
-
-**This guide explains the Automated backup option for your OVHcloud VPS.**
-
-> [!primary]
-> Before applying a backup strategy, we recommend to consult the [product pages and FAQ](/links/bare-metal/vps-options) for pricing comparisons and further details.
->
-
-## Requirements
-
-- Access to the [OVHcloud Control Panel](/links/manager).
-- A [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account.
-- Administrative access (sudo) via SSH to your VPS (optional).
-
-## Instructions
-
-### Content overview
-
-- [How to upgrade to Premium Automated Backup](#premium)
-- [How to configure the backup time](#time)
-- [How to restore a backup from the OVHcloud Control Panel](#restore)
-- [How to mount and access a backup](#mount)
- - [Using Secure Shell](#shell)
- - [Using Windows](#windows)
-- [Best practice for using Automated backups](#bestpractice)
- - [Configuring the QEMU agent on a VPS](#qemu)
- - [Debian-based distributions](#deb)
- - [Redhat-based distributions](#red)
- - [Windows](#win)
-
-Log in to your [OVHcloud Control Panel](/links/manager), open the `Bare Metal Cloud`{.action} section, and select your server under `Virtual Private Servers`{.action}.
-
-When you order a VPS, a single daily Automated backup is included as a free service option. This standard backup option allows you to:
-
-- Mount and restore the daily backup.
-- Set the time of day this backup will be created.
-
-For more flexiblity with your backups, you can activate the Premium Automated Backup option.
-
-
-
-### How to upgrade to Premium Automated Backup
-
-Upgrading to Premium Automated Backup enhances your Automated backup option to a 7-day rolling daily backup. This allows you to revert to older backup versions compared to the 24-hour rotation of the standard option.
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-
-Click the link `Order a premium backup`{.action}.
-
-{.thumbnail}
-
-In the next step, please take note of the pricing information, then click on `Order`{.action}. You will be guided through the order process and receive a confirmation email.
-
-
-
-### How to configure the backup time
-
-You can change the time of day at which the backup will take place.
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-
-Click on `...`{.action} above the table and then on `Edit`{.action}.
-
-{.thumbnail}
-
-In the window that appears, edit the time of day (24-hour UTC time standard). Click on `Confirm`{.action}.
-
-{.thumbnail}
-
-> [!primary]
->
-Once confirmed in the Control Panel, the change will come into effect after 24 to 48 hours.
->
-
-
-
-### How to restore a backup from the OVHcloud Control Panel
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-Click the button `...`{.action} next to the backup you would like to restore and select `Restoration`{.action}.
-
-{.thumbnail}
-
-If you recently changed your root password, make sure to tick the option "Modify the root password on restoration" in the popup window to preserve your current root password and click on `Confirm`{.action}. You will receive an email as soon as the task is complete. The restoration might take a while, depending on the disk space used.
-
-> [!alert]
->
-> Please note that the automated backups will not include your additional disks.
->
-
-
-
-### How to mount and access a backup
-
-It is not necessary to completely overwrite your existing service with a restoration. The "Mounting" option allows you to access the backup data to retrieve your files.
-
-> [!warning]
->
-> OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
->
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialist service provider](/links/partner) or reaching out to the [OVHcloud community](/links/community) if you encounter any difficulties. You can find more information in the [Go further](#go-further) section of this guide.
->
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-Click on `...`{.action} next to the backup you need to access and select `Mounting`{.action}.
-
-{.thumbnail}
-
-When you use this option, a read-write copy of the backup is created and mounted. The original backup will remain available unchanged for future restorations.
-
-After the process is completed, you will receive an email. You can now connect to your VPS and access the partition where your backup is located.
-
-
-
-#### Using Secure Shell
-
-First, connect to your VPS via SSH.
-
-You can use the following command to verify the name of the newly attached device:
-
-```bash
-lsblk
-```
-
-Here is a sample output of this command:
-
-```console
-NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
-sda 8:0 0 25G 0 disk
-├─sda1 8:1 0 24.9G 0 part /
-├─sda14 8:14 0 4M 0 part
-└─sda15 8:15 0 106M 0 part
-sdb 8:16 0 25G 0 disk
-├─sdb1 8:17 0 24.9G 0 part
-├─sdb14 8:30 0 4M 0 part
-└─sdb15 8:31 0 106M 0 part /boot/efi
-```
-
-In this example, the partition containing your backup filesystem is named "sdb1".
-Next, create a directory for this partition and define it as the mountpoint:
-
-```bash
-sudo mkdir -p /mnt/restore
-sudo mount /dev/sdb1 /mnt/restore
-```
-
-You can now switch to this folder and access your backup data.
-
-Remember to unmount the backup once you have finished using it. Click on the button `Unmount the backup`{.action} in the `Automated backup`{.action} tab, then confirm in the popup window.
-
-{.thumbnail}
-
-
-
-#### Using Windows
-
-Establish an RDP connection to your server.
-
-Once logged in, right-click on the `Start Menu`{.action} button, and then click `Disk Management`{.action}.
-
-{.thumbnail}
-
-When the disk management tool opens, your mounted backup will appear as a basic disk with the same storage space as your main disk.
-
-{.thumbnail}
-
-The disk will appear as `Offline`, right-click on the disk and select `Online`{.action}.
-
-{.thumbnail}
-
-Once done, your mounted backup will be accessible in the `File Explorer`.
-
-{.thumbnail}
-
-Remember to unmount the backup once you have finished using it. Click on the button `Unmount the backup`{.action} in the `Automated backup`{.action} tab, then confirm in the popup window.
-
-{.thumbnail}
-
-> [!warning]
->
-> Please note that a server reboot will occur when the backup is unmounted.
->
-
-
-
-### Best practice for using Automated backups
-
-The Automated Backup functionality is based on VPS snapshots. We recommend to follow the steps below to prevent any issues before using this option.
-
-
-
-#### Configuring the QEMU agent on a VPS
-
-Snapshots are instantaneous images of your running system ("live snapshot"). To ensure the availability of your system when the snapshot is created, the QEMU agent is used to prepare the filesystem for the process.
-
-The "**qemu-guest-agent**" agent is not installed by default on most distributions. Moreover, licensing restrictions may prevent OVHcloud from including it in the available OS images. Therefore, it is best practice to verify and install the agent in case it is not activated on your VPS. Connect to your VPS via SSH and follow the instructions below, according to your operating system.
-
-
-
-##### **Debian-based distributions (Debian, Ubuntu)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-```
-
-The expected output is:
-
-```console
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different, for example "No such file or directory", install the latest version of the package:
-
-```bash
-sudo apt-get update
-sudo apt-get install qemu-guest-agent
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Start the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent start
-```
-
-
-
-##### **Redhat-based distributions (Centos, Fedora)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-```
-
-The expected output is:
-
-```console
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different, for example "No such file or directory", install and enable the agent:
-
-```bash
-sudo yum install qemu-guest-agent
-sudo chkconfig qemu-guest-agent on
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Start the agent and verify that it is running:
-
-```bash
-sudo service qemu-guest-agent start
-sudo service qemu-guest-agent status
-```
-
-
-
-##### **Windows**
-
-You can install the agent via MSI file, available from the Fedora project website: .
-
-Verify that the service is running by using this powershell command:
-
-```console
-PS C:\Users\Administrator> Get-Service QEMU-GA
-Status Name DisplayName
------- ---- -----------
-Running QEMU-GA QEMU Guest Agent
-```
-
-
-
-## Go further
-
-[Using snapshots on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps)
-
-Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-ca.md b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-ca.md
deleted file mode 100644
index f44b6b23153..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-ca.md
+++ /dev/null
@@ -1,298 +0,0 @@
----
-title: "How to use automated backups on a VPS"
-excerpt: "Find out how to use the Automated backup option in the OVHcloud Control Panel to secure your data"
-updated: 2025-08-07
----
-
-## Objective
-
-The Automated backup option for VPS offers a convenient way to have complete system backups available from your OVHcloud Control Panel without having to connect to the server to create and restore them manually. Another advantage is that you can also choose to mount a backup and then access its files remotely.
-
-**This guide explains the Automated backup option for your OVHcloud VPS.**
-
-> [!primary]
-> Before applying a backup strategy, we recommend to consult the [product pages and FAQ](/links/bare-metal/vps-options) for pricing comparisons and further details.
->
-
-## Requirements
-
-- Access to the [OVHcloud Control Panel](/links/manager).
-- A [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account.
-- Administrative access (sudo) via SSH to your VPS (optional).
-
-## Instructions
-
-### Content overview
-
-- [How to upgrade to Premium Automated Backup](#premium)
-- [How to configure the backup time](#time)
-- [How to restore a backup from the OVHcloud Control Panel](#restore)
-- [How to mount and access a backup](#mount)
- - [Using Secure Shell](#shell)
- - [Using Windows](#windows)
-- [Best practice for using Automated backups](#bestpractice)
- - [Configuring the QEMU agent on a VPS](#qemu)
- - [Debian-based distributions](#deb)
- - [Redhat-based distributions](#red)
- - [Windows](#win)
-
-Log in to your [OVHcloud Control Panel](/links/manager), open the `Bare Metal Cloud`{.action} section, and select your server under `Virtual Private Servers`{.action}.
-
-When you order a VPS, a single daily Automated backup is included as a free service option. This standard backup option allows you to:
-
-- Mount and restore the daily backup.
-- Set the time of day this backup will be created.
-
-For more flexiblity with your backups, you can activate the Premium Automated Backup option.
-
-
-
-### How to upgrade to Premium Automated Backup
-
-Upgrading to Premium Automated Backup enhances your Automated backup option to a 7-day rolling daily backup. This allows you to revert to older backup versions compared to the 24-hour rotation of the standard option.
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-
-Click the link `Order a premium backup`{.action}.
-
-{.thumbnail}
-
-In the next step, please take note of the pricing information, then click on `Order`{.action}. You will be guided through the order process and receive a confirmation email.
-
-
-
-### How to configure the backup time
-
-You can change the time of day at which the backup will take place.
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-
-Click on `...`{.action} above the table and then on `Edit`{.action}.
-
-{.thumbnail}
-
-In the window that appears, edit the time of day (24-hour UTC time standard). Click on `Confirm`{.action}.
-
-{.thumbnail}
-
-> [!primary]
->
-Once confirmed in the Control Panel, the change will come into effect after 24 to 48 hours.
->
-
-
-
-### How to restore a backup from the OVHcloud Control Panel
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-Click the button `...`{.action} next to the backup you would like to restore and select `Restoration`{.action}.
-
-{.thumbnail}
-
-If you recently changed your root password, make sure to tick the option "Modify the root password on restoration" in the popup window to preserve your current root password and click on `Confirm`{.action}. You will receive an email as soon as the task is complete. The restoration might take a while, depending on the disk space used.
-
-> [!alert]
->
-> Please note that the automated backups will not include your additional disks.
->
-
-
-
-### How to mount and access a backup
-
-It is not necessary to completely overwrite your existing service with a restoration. The "Mounting" option allows you to access the backup data to retrieve your files.
-
-> [!warning]
->
-> OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
->
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialist service provider](/links/partner) or reaching out to the [OVHcloud community](/links/community) if you encounter any difficulties. You can find more information in the [Go further](#go-further) section of this guide.
->
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-Click on `...`{.action} next to the backup you need to access and select `Mounting`{.action}.
-
-{.thumbnail}
-
-When you use this option, a read-write copy of the backup is created and mounted. The original backup will remain available unchanged for future restorations.
-
-After the process is completed, you will receive an email. You can now connect to your VPS and access the partition where your backup is located.
-
-
-
-#### Using Secure Shell
-
-First, connect to your VPS via SSH.
-
-You can use the following command to verify the name of the newly attached device:
-
-```bash
-lsblk
-```
-
-Here is a sample output of this command:
-
-```console
-NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
-sda 8:0 0 25G 0 disk
-├─sda1 8:1 0 24.9G 0 part /
-├─sda14 8:14 0 4M 0 part
-└─sda15 8:15 0 106M 0 part
-sdb 8:16 0 25G 0 disk
-├─sdb1 8:17 0 24.9G 0 part
-├─sdb14 8:30 0 4M 0 part
-└─sdb15 8:31 0 106M 0 part /boot/efi
-```
-
-In this example, the partition containing your backup filesystem is named "sdb1".
-Next, create a directory for this partition and define it as the mountpoint:
-
-```bash
-sudo mkdir -p /mnt/restore
-sudo mount /dev/sdb1 /mnt/restore
-```
-
-You can now switch to this folder and access your backup data.
-
-Remember to unmount the backup once you have finished using it. Click on the button `Unmount the backup`{.action} in the `Automated backup`{.action} tab, then confirm in the popup window.
-
-{.thumbnail}
-
-
-
-#### Using Windows
-
-Establish an RDP connection to your server.
-
-Once logged in, right-click on the `Start Menu`{.action} button, and then click `Disk Management`{.action}.
-
-{.thumbnail}
-
-When the disk management tool opens, your mounted backup will appear as a basic disk with the same storage space as your main disk.
-
-{.thumbnail}
-
-The disk will appear as `Offline`, right-click on the disk and select `Online`{.action}.
-
-{.thumbnail}
-
-Once done, your mounted backup will be accessible in the `File Explorer`.
-
-{.thumbnail}
-
-Remember to unmount the backup once you have finished using it. Click on the button `Unmount the backup`{.action} in the `Automated backup`{.action} tab, then confirm in the popup window.
-
-{.thumbnail}
-
-> [!warning]
->
-> Please note that a server reboot will occur when the backup is unmounted.
->
-
-
-
-### Best practice for using Automated backups
-
-The Automated Backup functionality is based on VPS snapshots. We recommend to follow the steps below to prevent any issues before using this option.
-
-
-
-#### Configuring the QEMU agent on a VPS
-
-Snapshots are instantaneous images of your running system ("live snapshot"). To ensure the availability of your system when the snapshot is created, the QEMU agent is used to prepare the filesystem for the process.
-
-The "**qemu-guest-agent**" agent is not installed by default on most distributions. Moreover, licensing restrictions may prevent OVHcloud from including it in the available OS images. Therefore, it is best practice to verify and install the agent in case it is not activated on your VPS. Connect to your VPS via SSH and follow the instructions below, according to your operating system.
-
-
-
-##### **Debian-based distributions (Debian, Ubuntu)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-```
-
-The expected output is:
-
-```console
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different, for example "No such file or directory", install the latest version of the package:
-
-```bash
-sudo apt-get update
-sudo apt-get install qemu-guest-agent
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Start the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent start
-```
-
-
-
-##### **Redhat-based distributions (Centos, Fedora)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-```
-
-The expected output is:
-
-```console
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different, for example "No such file or directory", install and enable the agent:
-
-```bash
-sudo yum install qemu-guest-agent
-sudo chkconfig qemu-guest-agent on
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Start the agent and verify that it is running:
-
-```bash
-sudo service qemu-guest-agent start
-sudo service qemu-guest-agent status
-```
-
-
-
-##### **Windows**
-
-You can install the agent via MSI file, available from the Fedora project website: .
-
-Verify that the service is running by using this powershell command:
-
-```console
-PS C:\Users\Administrator> Get-Service QEMU-GA
-Status Name DisplayName
------- ---- -----------
-Running QEMU-GA QEMU Guest Agent
-```
-
-
-
-## Go further
-
-[Using snapshots on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps)
-
-Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-gb.md b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-gb.md
index f44b6b23153..72938b69ae0 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-gb.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-gb.md
@@ -1,7 +1,7 @@
---
title: "How to use automated backups on a VPS"
excerpt: "Find out how to use the Automated backup option in the OVHcloud Control Panel to secure your data"
-updated: 2025-08-07
+updated: 2025-09-11
---
## Objective
@@ -17,9 +17,13 @@ The Automated backup option for VPS offers a convenient way to have complete sys
## Requirements
- Access to the [OVHcloud Control Panel](/links/manager).
-- A [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account.
+- An active [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account
- Administrative access (sudo) via SSH to your VPS (optional).
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instructions
### Content overview
@@ -293,6 +297,6 @@ Running QEMU-GA QEMU Guest Agent
## Go further
-[Using snapshots on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps)
+[How to use snapshots on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps)
Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-ie.md b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-ie.md
deleted file mode 100644
index f44b6b23153..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-ie.md
+++ /dev/null
@@ -1,298 +0,0 @@
----
-title: "How to use automated backups on a VPS"
-excerpt: "Find out how to use the Automated backup option in the OVHcloud Control Panel to secure your data"
-updated: 2025-08-07
----
-
-## Objective
-
-The Automated backup option for VPS offers a convenient way to have complete system backups available from your OVHcloud Control Panel without having to connect to the server to create and restore them manually. Another advantage is that you can also choose to mount a backup and then access its files remotely.
-
-**This guide explains the Automated backup option for your OVHcloud VPS.**
-
-> [!primary]
-> Before applying a backup strategy, we recommend to consult the [product pages and FAQ](/links/bare-metal/vps-options) for pricing comparisons and further details.
->
-
-## Requirements
-
-- Access to the [OVHcloud Control Panel](/links/manager).
-- A [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account.
-- Administrative access (sudo) via SSH to your VPS (optional).
-
-## Instructions
-
-### Content overview
-
-- [How to upgrade to Premium Automated Backup](#premium)
-- [How to configure the backup time](#time)
-- [How to restore a backup from the OVHcloud Control Panel](#restore)
-- [How to mount and access a backup](#mount)
- - [Using Secure Shell](#shell)
- - [Using Windows](#windows)
-- [Best practice for using Automated backups](#bestpractice)
- - [Configuring the QEMU agent on a VPS](#qemu)
- - [Debian-based distributions](#deb)
- - [Redhat-based distributions](#red)
- - [Windows](#win)
-
-Log in to your [OVHcloud Control Panel](/links/manager), open the `Bare Metal Cloud`{.action} section, and select your server under `Virtual Private Servers`{.action}.
-
-When you order a VPS, a single daily Automated backup is included as a free service option. This standard backup option allows you to:
-
-- Mount and restore the daily backup.
-- Set the time of day this backup will be created.
-
-For more flexiblity with your backups, you can activate the Premium Automated Backup option.
-
-
-
-### How to upgrade to Premium Automated Backup
-
-Upgrading to Premium Automated Backup enhances your Automated backup option to a 7-day rolling daily backup. This allows you to revert to older backup versions compared to the 24-hour rotation of the standard option.
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-
-Click the link `Order a premium backup`{.action}.
-
-{.thumbnail}
-
-In the next step, please take note of the pricing information, then click on `Order`{.action}. You will be guided through the order process and receive a confirmation email.
-
-
-
-### How to configure the backup time
-
-You can change the time of day at which the backup will take place.
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-
-Click on `...`{.action} above the table and then on `Edit`{.action}.
-
-{.thumbnail}
-
-In the window that appears, edit the time of day (24-hour UTC time standard). Click on `Confirm`{.action}.
-
-{.thumbnail}
-
-> [!primary]
->
-Once confirmed in the Control Panel, the change will come into effect after 24 to 48 hours.
->
-
-
-
-### How to restore a backup from the OVHcloud Control Panel
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-Click the button `...`{.action} next to the backup you would like to restore and select `Restoration`{.action}.
-
-{.thumbnail}
-
-If you recently changed your root password, make sure to tick the option "Modify the root password on restoration" in the popup window to preserve your current root password and click on `Confirm`{.action}. You will receive an email as soon as the task is complete. The restoration might take a while, depending on the disk space used.
-
-> [!alert]
->
-> Please note that the automated backups will not include your additional disks.
->
-
-
-
-### How to mount and access a backup
-
-It is not necessary to completely overwrite your existing service with a restoration. The "Mounting" option allows you to access the backup data to retrieve your files.
-
-> [!warning]
->
-> OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
->
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialist service provider](/links/partner) or reaching out to the [OVHcloud community](/links/community) if you encounter any difficulties. You can find more information in the [Go further](#go-further) section of this guide.
->
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-Click on `...`{.action} next to the backup you need to access and select `Mounting`{.action}.
-
-{.thumbnail}
-
-When you use this option, a read-write copy of the backup is created and mounted. The original backup will remain available unchanged for future restorations.
-
-After the process is completed, you will receive an email. You can now connect to your VPS and access the partition where your backup is located.
-
-
-
-#### Using Secure Shell
-
-First, connect to your VPS via SSH.
-
-You can use the following command to verify the name of the newly attached device:
-
-```bash
-lsblk
-```
-
-Here is a sample output of this command:
-
-```console
-NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
-sda 8:0 0 25G 0 disk
-├─sda1 8:1 0 24.9G 0 part /
-├─sda14 8:14 0 4M 0 part
-└─sda15 8:15 0 106M 0 part
-sdb 8:16 0 25G 0 disk
-├─sdb1 8:17 0 24.9G 0 part
-├─sdb14 8:30 0 4M 0 part
-└─sdb15 8:31 0 106M 0 part /boot/efi
-```
-
-In this example, the partition containing your backup filesystem is named "sdb1".
-Next, create a directory for this partition and define it as the mountpoint:
-
-```bash
-sudo mkdir -p /mnt/restore
-sudo mount /dev/sdb1 /mnt/restore
-```
-
-You can now switch to this folder and access your backup data.
-
-Remember to unmount the backup once you have finished using it. Click on the button `Unmount the backup`{.action} in the `Automated backup`{.action} tab, then confirm in the popup window.
-
-{.thumbnail}
-
-
-
-#### Using Windows
-
-Establish an RDP connection to your server.
-
-Once logged in, right-click on the `Start Menu`{.action} button, and then click `Disk Management`{.action}.
-
-{.thumbnail}
-
-When the disk management tool opens, your mounted backup will appear as a basic disk with the same storage space as your main disk.
-
-{.thumbnail}
-
-The disk will appear as `Offline`, right-click on the disk and select `Online`{.action}.
-
-{.thumbnail}
-
-Once done, your mounted backup will be accessible in the `File Explorer`.
-
-{.thumbnail}
-
-Remember to unmount the backup once you have finished using it. Click on the button `Unmount the backup`{.action} in the `Automated backup`{.action} tab, then confirm in the popup window.
-
-{.thumbnail}
-
-> [!warning]
->
-> Please note that a server reboot will occur when the backup is unmounted.
->
-
-
-
-### Best practice for using Automated backups
-
-The Automated Backup functionality is based on VPS snapshots. We recommend to follow the steps below to prevent any issues before using this option.
-
-
-
-#### Configuring the QEMU agent on a VPS
-
-Snapshots are instantaneous images of your running system ("live snapshot"). To ensure the availability of your system when the snapshot is created, the QEMU agent is used to prepare the filesystem for the process.
-
-The "**qemu-guest-agent**" agent is not installed by default on most distributions. Moreover, licensing restrictions may prevent OVHcloud from including it in the available OS images. Therefore, it is best practice to verify and install the agent in case it is not activated on your VPS. Connect to your VPS via SSH and follow the instructions below, according to your operating system.
-
-
-
-##### **Debian-based distributions (Debian, Ubuntu)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-```
-
-The expected output is:
-
-```console
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different, for example "No such file or directory", install the latest version of the package:
-
-```bash
-sudo apt-get update
-sudo apt-get install qemu-guest-agent
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Start the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent start
-```
-
-
-
-##### **Redhat-based distributions (Centos, Fedora)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-```
-
-The expected output is:
-
-```console
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different, for example "No such file or directory", install and enable the agent:
-
-```bash
-sudo yum install qemu-guest-agent
-sudo chkconfig qemu-guest-agent on
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Start the agent and verify that it is running:
-
-```bash
-sudo service qemu-guest-agent start
-sudo service qemu-guest-agent status
-```
-
-
-
-##### **Windows**
-
-You can install the agent via MSI file, available from the Fedora project website: .
-
-Verify that the service is running by using this powershell command:
-
-```console
-PS C:\Users\Administrator> Get-Service QEMU-GA
-Status Name DisplayName
------- ---- -----------
-Running QEMU-GA QEMU Guest Agent
-```
-
-
-
-## Go further
-
-[Using snapshots on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps)
-
-Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-sg.md b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-sg.md
deleted file mode 100644
index f44b6b23153..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-sg.md
+++ /dev/null
@@ -1,298 +0,0 @@
----
-title: "How to use automated backups on a VPS"
-excerpt: "Find out how to use the Automated backup option in the OVHcloud Control Panel to secure your data"
-updated: 2025-08-07
----
-
-## Objective
-
-The Automated backup option for VPS offers a convenient way to have complete system backups available from your OVHcloud Control Panel without having to connect to the server to create and restore them manually. Another advantage is that you can also choose to mount a backup and then access its files remotely.
-
-**This guide explains the Automated backup option for your OVHcloud VPS.**
-
-> [!primary]
-> Before applying a backup strategy, we recommend to consult the [product pages and FAQ](/links/bare-metal/vps-options) for pricing comparisons and further details.
->
-
-## Requirements
-
-- Access to the [OVHcloud Control Panel](/links/manager).
-- A [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account.
-- Administrative access (sudo) via SSH to your VPS (optional).
-
-## Instructions
-
-### Content overview
-
-- [How to upgrade to Premium Automated Backup](#premium)
-- [How to configure the backup time](#time)
-- [How to restore a backup from the OVHcloud Control Panel](#restore)
-- [How to mount and access a backup](#mount)
- - [Using Secure Shell](#shell)
- - [Using Windows](#windows)
-- [Best practice for using Automated backups](#bestpractice)
- - [Configuring the QEMU agent on a VPS](#qemu)
- - [Debian-based distributions](#deb)
- - [Redhat-based distributions](#red)
- - [Windows](#win)
-
-Log in to your [OVHcloud Control Panel](/links/manager), open the `Bare Metal Cloud`{.action} section, and select your server under `Virtual Private Servers`{.action}.
-
-When you order a VPS, a single daily Automated backup is included as a free service option. This standard backup option allows you to:
-
-- Mount and restore the daily backup.
-- Set the time of day this backup will be created.
-
-For more flexiblity with your backups, you can activate the Premium Automated Backup option.
-
-
-
-### How to upgrade to Premium Automated Backup
-
-Upgrading to Premium Automated Backup enhances your Automated backup option to a 7-day rolling daily backup. This allows you to revert to older backup versions compared to the 24-hour rotation of the standard option.
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-
-Click the link `Order a premium backup`{.action}.
-
-{.thumbnail}
-
-In the next step, please take note of the pricing information, then click on `Order`{.action}. You will be guided through the order process and receive a confirmation email.
-
-
-
-### How to configure the backup time
-
-You can change the time of day at which the backup will take place.
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-
-Click on `...`{.action} above the table and then on `Edit`{.action}.
-
-{.thumbnail}
-
-In the window that appears, edit the time of day (24-hour UTC time standard). Click on `Confirm`{.action}.
-
-{.thumbnail}
-
-> [!primary]
->
-Once confirmed in the Control Panel, the change will come into effect after 24 to 48 hours.
->
-
-
-
-### How to restore a backup from the OVHcloud Control Panel
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-Click the button `...`{.action} next to the backup you would like to restore and select `Restoration`{.action}.
-
-{.thumbnail}
-
-If you recently changed your root password, make sure to tick the option "Modify the root password on restoration" in the popup window to preserve your current root password and click on `Confirm`{.action}. You will receive an email as soon as the task is complete. The restoration might take a while, depending on the disk space used.
-
-> [!alert]
->
-> Please note that the automated backups will not include your additional disks.
->
-
-
-
-### How to mount and access a backup
-
-It is not necessary to completely overwrite your existing service with a restoration. The "Mounting" option allows you to access the backup data to retrieve your files.
-
-> [!warning]
->
-> OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
->
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialist service provider](/links/partner) or reaching out to the [OVHcloud community](/links/community) if you encounter any difficulties. You can find more information in the [Go further](#go-further) section of this guide.
->
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-Click on `...`{.action} next to the backup you need to access and select `Mounting`{.action}.
-
-{.thumbnail}
-
-When you use this option, a read-write copy of the backup is created and mounted. The original backup will remain available unchanged for future restorations.
-
-After the process is completed, you will receive an email. You can now connect to your VPS and access the partition where your backup is located.
-
-
-
-#### Using Secure Shell
-
-First, connect to your VPS via SSH.
-
-You can use the following command to verify the name of the newly attached device:
-
-```bash
-lsblk
-```
-
-Here is a sample output of this command:
-
-```console
-NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
-sda 8:0 0 25G 0 disk
-├─sda1 8:1 0 24.9G 0 part /
-├─sda14 8:14 0 4M 0 part
-└─sda15 8:15 0 106M 0 part
-sdb 8:16 0 25G 0 disk
-├─sdb1 8:17 0 24.9G 0 part
-├─sdb14 8:30 0 4M 0 part
-└─sdb15 8:31 0 106M 0 part /boot/efi
-```
-
-In this example, the partition containing your backup filesystem is named "sdb1".
-Next, create a directory for this partition and define it as the mountpoint:
-
-```bash
-sudo mkdir -p /mnt/restore
-sudo mount /dev/sdb1 /mnt/restore
-```
-
-You can now switch to this folder and access your backup data.
-
-Remember to unmount the backup once you have finished using it. Click on the button `Unmount the backup`{.action} in the `Automated backup`{.action} tab, then confirm in the popup window.
-
-{.thumbnail}
-
-
-
-#### Using Windows
-
-Establish an RDP connection to your server.
-
-Once logged in, right-click on the `Start Menu`{.action} button, and then click `Disk Management`{.action}.
-
-{.thumbnail}
-
-When the disk management tool opens, your mounted backup will appear as a basic disk with the same storage space as your main disk.
-
-{.thumbnail}
-
-The disk will appear as `Offline`, right-click on the disk and select `Online`{.action}.
-
-{.thumbnail}
-
-Once done, your mounted backup will be accessible in the `File Explorer`.
-
-{.thumbnail}
-
-Remember to unmount the backup once you have finished using it. Click on the button `Unmount the backup`{.action} in the `Automated backup`{.action} tab, then confirm in the popup window.
-
-{.thumbnail}
-
-> [!warning]
->
-> Please note that a server reboot will occur when the backup is unmounted.
->
-
-
-
-### Best practice for using Automated backups
-
-The Automated Backup functionality is based on VPS snapshots. We recommend to follow the steps below to prevent any issues before using this option.
-
-
-
-#### Configuring the QEMU agent on a VPS
-
-Snapshots are instantaneous images of your running system ("live snapshot"). To ensure the availability of your system when the snapshot is created, the QEMU agent is used to prepare the filesystem for the process.
-
-The "**qemu-guest-agent**" agent is not installed by default on most distributions. Moreover, licensing restrictions may prevent OVHcloud from including it in the available OS images. Therefore, it is best practice to verify and install the agent in case it is not activated on your VPS. Connect to your VPS via SSH and follow the instructions below, according to your operating system.
-
-
-
-##### **Debian-based distributions (Debian, Ubuntu)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-```
-
-The expected output is:
-
-```console
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different, for example "No such file or directory", install the latest version of the package:
-
-```bash
-sudo apt-get update
-sudo apt-get install qemu-guest-agent
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Start the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent start
-```
-
-
-
-##### **Redhat-based distributions (Centos, Fedora)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-```
-
-The expected output is:
-
-```console
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different, for example "No such file or directory", install and enable the agent:
-
-```bash
-sudo yum install qemu-guest-agent
-sudo chkconfig qemu-guest-agent on
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Start the agent and verify that it is running:
-
-```bash
-sudo service qemu-guest-agent start
-sudo service qemu-guest-agent status
-```
-
-
-
-##### **Windows**
-
-You can install the agent via MSI file, available from the Fedora project website: .
-
-Verify that the service is running by using this powershell command:
-
-```console
-PS C:\Users\Administrator> Get-Service QEMU-GA
-Status Name DisplayName
------- ---- -----------
-Running QEMU-GA QEMU Guest Agent
-```
-
-
-
-## Go further
-
-[Using snapshots on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps)
-
-Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-us.md b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-us.md
deleted file mode 100644
index f44b6b23153..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.en-us.md
+++ /dev/null
@@ -1,298 +0,0 @@
----
-title: "How to use automated backups on a VPS"
-excerpt: "Find out how to use the Automated backup option in the OVHcloud Control Panel to secure your data"
-updated: 2025-08-07
----
-
-## Objective
-
-The Automated backup option for VPS offers a convenient way to have complete system backups available from your OVHcloud Control Panel without having to connect to the server to create and restore them manually. Another advantage is that you can also choose to mount a backup and then access its files remotely.
-
-**This guide explains the Automated backup option for your OVHcloud VPS.**
-
-> [!primary]
-> Before applying a backup strategy, we recommend to consult the [product pages and FAQ](/links/bare-metal/vps-options) for pricing comparisons and further details.
->
-
-## Requirements
-
-- Access to the [OVHcloud Control Panel](/links/manager).
-- A [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account.
-- Administrative access (sudo) via SSH to your VPS (optional).
-
-## Instructions
-
-### Content overview
-
-- [How to upgrade to Premium Automated Backup](#premium)
-- [How to configure the backup time](#time)
-- [How to restore a backup from the OVHcloud Control Panel](#restore)
-- [How to mount and access a backup](#mount)
- - [Using Secure Shell](#shell)
- - [Using Windows](#windows)
-- [Best practice for using Automated backups](#bestpractice)
- - [Configuring the QEMU agent on a VPS](#qemu)
- - [Debian-based distributions](#deb)
- - [Redhat-based distributions](#red)
- - [Windows](#win)
-
-Log in to your [OVHcloud Control Panel](/links/manager), open the `Bare Metal Cloud`{.action} section, and select your server under `Virtual Private Servers`{.action}.
-
-When you order a VPS, a single daily Automated backup is included as a free service option. This standard backup option allows you to:
-
-- Mount and restore the daily backup.
-- Set the time of day this backup will be created.
-
-For more flexiblity with your backups, you can activate the Premium Automated Backup option.
-
-
-
-### How to upgrade to Premium Automated Backup
-
-Upgrading to Premium Automated Backup enhances your Automated backup option to a 7-day rolling daily backup. This allows you to revert to older backup versions compared to the 24-hour rotation of the standard option.
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-
-Click the link `Order a premium backup`{.action}.
-
-{.thumbnail}
-
-In the next step, please take note of the pricing information, then click on `Order`{.action}. You will be guided through the order process and receive a confirmation email.
-
-
-
-### How to configure the backup time
-
-You can change the time of day at which the backup will take place.
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-
-Click on `...`{.action} above the table and then on `Edit`{.action}.
-
-{.thumbnail}
-
-In the window that appears, edit the time of day (24-hour UTC time standard). Click on `Confirm`{.action}.
-
-{.thumbnail}
-
-> [!primary]
->
-Once confirmed in the Control Panel, the change will come into effect after 24 to 48 hours.
->
-
-
-
-### How to restore a backup from the OVHcloud Control Panel
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-Click the button `...`{.action} next to the backup you would like to restore and select `Restoration`{.action}.
-
-{.thumbnail}
-
-If you recently changed your root password, make sure to tick the option "Modify the root password on restoration" in the popup window to preserve your current root password and click on `Confirm`{.action}. You will receive an email as soon as the task is complete. The restoration might take a while, depending on the disk space used.
-
-> [!alert]
->
-> Please note that the automated backups will not include your additional disks.
->
-
-
-
-### How to mount and access a backup
-
-It is not necessary to completely overwrite your existing service with a restoration. The "Mounting" option allows you to access the backup data to retrieve your files.
-
-> [!warning]
->
-> OVHcloud provides services for which you are responsible with regard to their configuration and management. It is therefore your responsibility to ensure that they function correctly.
->
-> This guide is designed to help you with common tasks. Nevertheless, we recommend contacting a [specialist service provider](/links/partner) or reaching out to the [OVHcloud community](/links/community) if you encounter any difficulties. You can find more information in the [Go further](#go-further) section of this guide.
->
-
-After selecting your VPS, click on the `Automated backup`{.action} tab in the horizontal menu.
-Click on `...`{.action} next to the backup you need to access and select `Mounting`{.action}.
-
-{.thumbnail}
-
-When you use this option, a read-write copy of the backup is created and mounted. The original backup will remain available unchanged for future restorations.
-
-After the process is completed, you will receive an email. You can now connect to your VPS and access the partition where your backup is located.
-
-
-
-#### Using Secure Shell
-
-First, connect to your VPS via SSH.
-
-You can use the following command to verify the name of the newly attached device:
-
-```bash
-lsblk
-```
-
-Here is a sample output of this command:
-
-```console
-NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
-sda 8:0 0 25G 0 disk
-├─sda1 8:1 0 24.9G 0 part /
-├─sda14 8:14 0 4M 0 part
-└─sda15 8:15 0 106M 0 part
-sdb 8:16 0 25G 0 disk
-├─sdb1 8:17 0 24.9G 0 part
-├─sdb14 8:30 0 4M 0 part
-└─sdb15 8:31 0 106M 0 part /boot/efi
-```
-
-In this example, the partition containing your backup filesystem is named "sdb1".
-Next, create a directory for this partition and define it as the mountpoint:
-
-```bash
-sudo mkdir -p /mnt/restore
-sudo mount /dev/sdb1 /mnt/restore
-```
-
-You can now switch to this folder and access your backup data.
-
-Remember to unmount the backup once you have finished using it. Click on the button `Unmount the backup`{.action} in the `Automated backup`{.action} tab, then confirm in the popup window.
-
-{.thumbnail}
-
-
-
-#### Using Windows
-
-Establish an RDP connection to your server.
-
-Once logged in, right-click on the `Start Menu`{.action} button, and then click `Disk Management`{.action}.
-
-{.thumbnail}
-
-When the disk management tool opens, your mounted backup will appear as a basic disk with the same storage space as your main disk.
-
-{.thumbnail}
-
-The disk will appear as `Offline`, right-click on the disk and select `Online`{.action}.
-
-{.thumbnail}
-
-Once done, your mounted backup will be accessible in the `File Explorer`.
-
-{.thumbnail}
-
-Remember to unmount the backup once you have finished using it. Click on the button `Unmount the backup`{.action} in the `Automated backup`{.action} tab, then confirm in the popup window.
-
-{.thumbnail}
-
-> [!warning]
->
-> Please note that a server reboot will occur when the backup is unmounted.
->
-
-
-
-### Best practice for using Automated backups
-
-The Automated Backup functionality is based on VPS snapshots. We recommend to follow the steps below to prevent any issues before using this option.
-
-
-
-#### Configuring the QEMU agent on a VPS
-
-Snapshots are instantaneous images of your running system ("live snapshot"). To ensure the availability of your system when the snapshot is created, the QEMU agent is used to prepare the filesystem for the process.
-
-The "**qemu-guest-agent**" agent is not installed by default on most distributions. Moreover, licensing restrictions may prevent OVHcloud from including it in the available OS images. Therefore, it is best practice to verify and install the agent in case it is not activated on your VPS. Connect to your VPS via SSH and follow the instructions below, according to your operating system.
-
-
-
-##### **Debian-based distributions (Debian, Ubuntu)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-```
-
-The expected output is:
-
-```console
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different, for example "No such file or directory", install the latest version of the package:
-
-```bash
-sudo apt-get update
-sudo apt-get install qemu-guest-agent
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Start the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent start
-```
-
-
-
-##### **Redhat-based distributions (Centos, Fedora)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-```
-
-The expected output is:
-
-```console
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different, for example "No such file or directory", install and enable the agent:
-
-```bash
-sudo yum install qemu-guest-agent
-sudo chkconfig qemu-guest-agent on
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Start the agent and verify that it is running:
-
-```bash
-sudo service qemu-guest-agent start
-sudo service qemu-guest-agent status
-```
-
-
-
-##### **Windows**
-
-You can install the agent via MSI file, available from the Fedora project website: .
-
-Verify that the service is running by using this powershell command:
-
-```console
-PS C:\Users\Administrator> Get-Service QEMU-GA
-Status Name DisplayName
------- ---- -----------
-Running QEMU-GA QEMU Guest Agent
-```
-
-
-
-## Go further
-
-[Using snapshots on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps)
-
-Join our [community of users](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.es-es.md b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.es-es.md
index 55543febe3f..be6847c2853 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.es-es.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.es-es.md
@@ -1,7 +1,7 @@
---
title: "Cómo utilizar los backups automatizados en un VPS"
excerpt: "Descubra cómo utilizar la opción de backup automatizado desde el área de cliente de OVHcloud para proteger los datos"
-updated: 2025-08-07
+updated: 2025-09-11
---
## Objetivo
@@ -20,6 +20,11 @@ La opción backup automatizado para VPS es una forma cómoda de tener copias de
- Tener un [servidor privado virtual (VPS)](/links/bare-metal/vps) de OVHcloud ya configurado.
- Tener acceso de administrador (sudo) a su servidor virtual privado (VPS) a través del protocolo/programa SSH (opcional).
+
+> [!warning]
+> Esta funcionalidad no está disponible actualmente para los servidores virtuales en las [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Procedimiento
### Introducción al contenido
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.es-us.md b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.es-us.md
deleted file mode 100644
index 55543febe3f..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.es-us.md
+++ /dev/null
@@ -1,295 +0,0 @@
----
-title: "Cómo utilizar los backups automatizados en un VPS"
-excerpt: "Descubra cómo utilizar la opción de backup automatizado desde el área de cliente de OVHcloud para proteger los datos"
-updated: 2025-08-07
----
-
-## Objetivo
-
-La opción backup automatizado para VPS es una forma cómoda de tener copias de seguridad completas del sistema disponibles desde el área de cliente de OVHcloud sin tener que conectarse al servidor para crearlas y restaurarlas manualmente. Otra ventaja es que también puede optar por montar una copia de seguridad y acceder a sus archivos de forma remota.
-
-**Esta guía explica la opción de backup automatizado para su VPS OVHcloud.**
-
-> [!primary]
-> Antes de aplicar las opciones de copia de seguridad, le recomendamos que consulte las [preguntas frecuentes y demás páginas del producto](/links/bare-metal/vps-options) para acceder a una comparativa de los precios y otras informaciones.
->
-
-## Requisitos
-
-- Tener acceso al [área de cliente de OVHcloud](/links/manager).
-- Tener un [servidor privado virtual (VPS)](/links/bare-metal/vps) de OVHcloud ya configurado.
-- Tener acceso de administrador (sudo) a su servidor virtual privado (VPS) a través del protocolo/programa SSH (opcional).
-
-## Procedimiento
-
-### Introducción al contenido
-
-- [Cómo actualizar a backup automatizado Premium](#premium)
-- [Configurar la hora del backup](#time)
-- [Restaurar una copia de seguridad desde el área de cliente de OVHcloud](#restore)
-- [Cómo montar y acceder a un backup](#mount)
- - [En Secure Shell](#shell)
- - [En Windows](#windows)
-- [Buenas prácticas para utilizar el backup automatizado](#bestpractice)
- - [Configuración del agente QEMU en un VPS](#qemu)
- - [Distribuciones Debian](#deb)
- - [Distribuciones Redhat](#red)
- - [Windows](#win)
-
-
-Conéctese al [área de cliente de OVHcloud](/links/manager), acceda a la sección `Bare Metal Cloud`{.action} y seleccione el servidor en la sección `Servidores Privados Virtuales`{.action}.
-
-Al contratar un VPS, la opción de servicio gratuito incluye una única copia de seguridad automática diaria. Esta opción de backup estándar le permite:
-
-- Montar y restaurar la copia de seguridad diaria.
-- Establecer la hora de creación de esta copia de seguridad.
-
-Para mayor flexibilidad en sus backups, puede activar la opción backup automatizado Premium.
-
-
-
-### Cómo actualizar a backup automatizado Premium
-
-La actualización a backup automatizado Premium mejora su opción de backup automático a un backup diario continuo de 7 días. Esto le permite volver a versiones de backup más antiguas en comparación con la rotación de 24 horas de la opción estándar.
-
-Una vez seleccionado el VPS, haga clic en la pestaña `Backup automatizado`{.action} del menú horizontal.
-
-Haga clic en el enlace `Contratar un backup automatizado premium`{.action}.
-
-{.thumbnail}
-
-
-
-### Configurar la hora del backup
-
-Puede cambiar la hora en la que se realizará la copia de seguridad.
-
-Una vez seleccionado el VPS, haga clic en la pestaña `Backup automatizado`{.action} del menú horizontal.
-
-Haga clic en `...`{.action} encima de la tabla y, seguidamente, en `Editar`{.action}.
-
-{.thumbnail}
-
-Se abrirá una ventana en la que podrá cambiar la hora del día (UTC 24 horas). Haga clic en `Confirmar`{.action}.
-
-{.thumbnail}
-
-> [!primary]
->
-> Una vez validado en el área de cliente, el cambio será efectivo en un plazo de 24 a 48 horas.
->
-
-
-
-### Restaurar una copia de seguridad desde el área de cliente de OVHcloud
-
-Después de seleccionar su servidor virtual privado (VPS), haga clic en la pestaña `Backup automatizado`{.action} en el menú horizontal.
-Haga clic en `...`{.action} junto a la copia de seguridad que quiera restaurar y seleccione `Restauración`{.action}.
-
-{.thumbnail}
-
-Si recientemente ha cambiado su contraseña raíz, asegúrese de marcar la opción «Modificar la contraseña raíz al restaurar» en la ventana emergente para conservar su contraseña raíz actual y, seguidamente, haga clic en `Confirmar`{.action}. Recibirá un mensaje de correo electrónico tan pronto como se complete la tarea. En función del espacio en disco utilizado, la restauración puede tardar un rato en completarse.
-
-> [!alert]
-> Tenga en cuenta que las copias de seguridad automatizadas no incluirán sus discos adicionales.
->
-
-
-
-### Cómo montar y acceder a un backup
-
-No es necesario sobrescribir íntegramente el servicio existente con una restauración. La opción «Montaje» le permite acceder a los datos de la copia de seguridad para recuperar sus archivos.
-
-> [!warning]
->
-> La configuración y la gestión de la serie de servicios que OVHcloud le ofrece recae sobre usted. Por lo tanto, es su responsabilidad asegurarse de que estos servicios funcionen correctamente.
->
-> El propósito de esta guía es ayudarle, en la medida de lo posible, con las tareas generales. No obstante, póngase en contacto con un [proveedor especializado](/links/partner) y/o el editor del software del servicio si tiene alguna dificultad. Nosotros no podremos ayudarle al respecto. Puede encontrar información adicional en la sección [Más información](#go-further) de esta guía.
->
-
-Haga clic en `...`{.action} junto a la copia de seguridad a la que necesite acceder y seleccione `Montaje`{.action}.
-
-{.thumbnail}
-
-Cuando se usa esta opción, se crea y monta una copia de seguridad de lectura y escritura. La copia de seguridad original seguirá estando disponible para futuras restauraciones.
-
-Una vez completado el proceso, recibirá un mensaje de correo electrónico. Ahora, puede conectarse a su servidor virtual privado (VPS) y añadir la partición donde se encuentra su copia de seguridad.
-
-
-
-#### En Secure Shell
-
-Primero, conéctese a su servidor virtual privado (VPS) a través del protocolo/programa Secure Shell (SSH).
-
-Puede utilizar el comando siguiente para verificar el nombre del nuevo dispositivo conectado:
-
-```bash
-lsblk
-```
-
-A continuación, un resultado de muestra de este comando:
-
-```console
-NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
-sda 8:0 0 25G 0 disk
-├─sda1 8:1 0 24.9G 0 part /
-├─sda14 8:14 0 4M 0 part
-└─sda15 8:15 0 106M 0 part
-sdb 8:16 0 25G 0 disk
-├─sdb1 8:17 0 24.9G 0 part
-├─sdb14 8:30 0 4M 0 part
-└─sdb15 8:31 0 106M 0 part /boot/efi
-```
-
-En este ejemplo, la partición que contiene el sistema de archivos de la copia de seguridad se denomina «sdb1».
-A continuación, cree un directorio para esta partición y defínalo como el punto de montaje:
-
-```bash
-sudo mkdir -p /mnt/restore
-sudo mount /dev/sdb1 /mnt/restore
-```
-
-Ahora, puede cambiar a esta carpeta y acceder a los datos de su copia de seguridad.
-
-Recuerde desmontar la copia de seguridad automática una vez que haya finalizado su uso. Haga clic en el botón `Desmontar el backup`{.action} en la pestaña `Backup automatizado`{.action} y acepte en la ventana que se abre.
-
-{.thumbnail}
-
-
-
-#### En Windows
-
-Establezca una conexión RDP (Remote Desktop) con su VPS.
-
-Una vez que se haya conectado, haga clic derecho en el botón `Inicio`{.action} y abra el menú `Administración de discos`{.action}.
-
-{.thumbnail}
-
-La copia de seguridad montada aparecerá como un disco básico con el mismo espacio de almacenamiento que el disco principal.
-
-{.thumbnail}
-
-El disco aparecerá como `Desactivada`, haga clic derecho en el disco y seleccione `En línea`{.action}.
-
-{.thumbnail}
-
-Más adelante podrá acceder a la copia de seguridad montada en `Explorador de archivos`.
-
-{.thumbnail}
-
-Recuerde desmontar la copia de seguridad automática una vez que haya finalizado su uso. Haga clic en el botón `Desmontar el backup`{.action} en la pestaña `Backup automatizado`{.action} y acepte en la ventana que se abre.
-
-{.thumbnail}
-
-> [!warning]
->
-> Tenga en cuenta que se reiniciará el servidor al desmontar la copia de seguridad.
->
-
-
-
-### Buenas prácticas para utilizar la copia de seguridad automática
-
-La función de backup automatizado está basada en los snapshots VPS. Le recomendamos que siga los pasos que se indican a continuación para evitar cualquier anomalía antes de utilizar esta opción.
-
-
-
-#### Configuración del agente QEMU en un VPS
-
-Los snapshots son imágenes instantáneas de su sistema en ejecución («live snapshots»). Para garantizar la disponibilidad de su sistema durante la creación del snapshot, el software QEMU permite preparar el sistema de archivos para este proceso.
-
-El agente "**qemu-guest-agent**" no è installato di default sulla maggior parte delle distribuzioni. Además, las restricciones de licencia pueden impedir que OVHcloud lo incluya en las imágenes de los SO disponibles. Por lo tanto, le recomendamos que compruebe si este agente está activado en su VPS y, en caso negativo, que lo instale. Para ello, conéctese a su VPS por SSH y siga las instrucciones que se indican en función de su sistema operativo.
-
-
-
-##### **Distribuciones Debian (Debian, Ubuntu)**
-
-Utilice el siguiente comando para comprobar si el sistema está configurado correctamente para los snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-```
-
-El resultado esperado es el siguiente:
-
-```console
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-Si el resultado es diferente, como «No such file or directory», instale la última versión del paquete:
-
-```bash
-sudo apt-get update
-sudo apt-get install qemu-guest-agent
-```
-
-Reinicie el VPS:
-
-```bash
-sudo reboot
-```
-
-Inicie el servicio para garantizar que está en ejecución:
-
-```bash
-sudo service qemu-guest-agent start
-```
-
-
-
-##### **Distribuciones Redhat (CentOS, Fedora)**
-
-Utilice el siguiente comando para comprobar si el sistema está configurado correctamente para los snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-```
-
-El resultado esperado es el siguiente:
-
-```console
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-Si el resultado es diferente, como «No such file or directory», instale y active el software:
-
-```bash
-sudo yum install qemu-guest-agent
-sudo chkconfig qemu-guest-agent on
-```
-
-Reinicie el VPS:
-
-```bash
-sudo reboot
-```
-
-Inicie el software y compruebe que está en ejecución:
-
-```bash
-sudo service qemu-guest-agent start
-sudo service qemu-guest-agent status
-```
-
-
-
-##### **Windows**
-
-Puede instalar el agente a través de un archivo MSI, disponible en el sitio web del proyecto Fedora:
-
-Compruebe que el servicio está en ejecución con el siguiente comando PowerShell:
-
-```console
-PS C:\Users\Administrator> Get-Service QEMU-GA
-Status Name DisplayName
------- ---- -----------
-Running QEMU-GA QEMU Guest Agent
-```
-
-
-
-## Más información
-
-[Usar instantáneas en un servidor virtual privado (VPS)](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps)
-
-Interactúe con nuestra [comunidad de usuarios](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.fr-ca.md b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.fr-ca.md
deleted file mode 100644
index e3a73232d4e..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.fr-ca.md
+++ /dev/null
@@ -1,300 +0,0 @@
----
-title: "Comment utiliser les sauvegardes automatisées sur un VPS"
-excerpt: "Découvrez comment utiliser l'option Backup automatisé depuis l'espace client OVHcloud pour sécuriser vos données"
-updated: 2025-08-07
----
-
-## Objectif
-
-L'option Backup Automatisé pour les VPS offre un moyen pratique de disposer de sauvegardes complètes du système depuis votre espace client OVHcloud sans avoir à vous connecter au serveur pour créer et restaurer manuellement vos sauvegardes. Un autre avantage est que vous pouvez également choisir de monter une sauvegarde et accéder ensuite à ses fichiers à distance.
-
-**Ce guide vous présente en détail l'option Backup automatisé pour votre VPS OVHcloud.**
-
-
-
-> [!primary]
-> Avant d'appliquer une option de sauvegarde, nous vous recommandons de consulter les [options VPS disponibles](/links/bare-metal/vps-options) afin de comparer les détails et tarifs de chaque option.
->
-
-## Prérequis
-
-- Être connecté à [l'espace client OVHcloud](/links/manager).
-- Posséder un [VPS OVHcloud](/links/bare-metal/vps) déjà configuré.
-- Disposer d'un accès administrateur (sudo) en SSH à votre VPS (facultatif).
-
-## En pratique
-
-### Présentation du contenu
-
-- [Comment passer au Backup automatisé Premium](#premium)
-- [Configurer l’heure du backup](#time)
-- [Comment restaurer une sauvegarde depuis l’espace client OVHcloud](#restore)
-- [Monter et accéder à une image de sauvegarde](#mount)
- - [Sous Linux](#shell)
- - [Sous Windows](#windows)
-- [Bonnes pratiques pour l'utilisation du Backup automatisé](#bestpractice)
- - [Configuration de l'agent QEMU sur un VPS](#qemu)
- - [Distributions Redhat](#deb)
- - [Distributions Debian](#red)
- - [Windows](#win)
-
-Connectez-vous à votre [espace client OVHcloud](/links/manager), rendez-vous dans la section `Bare Metal Cloud`{.action} et sélectionnez votre serveur sous la partie `Serveurs privés virtuels`{.action}.
-
-Lorsque vous commandez un VPS, une seule sauvegarde automatique quotidienne est incluse en option de service gratuite. Cette option de sauvegarde standard vous permet de :
-
-- Monter et restaurer la sauvegarde quotidienne.
-- Définir l'heure de création de cette sauvegarde.
-
-Pour plus de flexibilité avec vos sauvegardes, vous pouvez activer l'option Backup automatisé Premium.
-
-
-
-### Comment passer au Backup automatisé Premium
-
-La mise à niveau vers le Backup automatisé Premium améliore votre option de sauvegarde automatique vers une sauvegarde quotidienne sur 7 jours glissants. Cela vous permet de revenir à des versions de sauvegardes plus anciennes par rapport à la rotation sur 24 heures de l'option standard.
-
-Après avoir sélectionné votre VPS, cliquez sur l'onglet `Backup automatisé`{.action} dans le menu horizontal.
-
-Cliquez sur le lien `Commander un backup premium`{.action}.
-
-{.thumbnail}
-
-Lors de l'étape suivante, veuillez prendre note des informations de tarification, puis cliquez sur `Commander`{.action}. Vous serez guidé tout au long du processus de commande et recevrez un e-mail de confirmation.
-
-
-
-### Configurer l’heure du backup
-
-Vous pouvez modifier l'heure à laquelle la sauvegarde aura lieu.
-
-Après avoir sélectionné votre VPS, cliquez sur l'onglet `Backup automatisé`{.action} dans le menu horizontal.
-
-Cliquez sur `...`{.action} au-dessus du tableau puis sur `Éditer`{.action}.
-
-{.thumbnail}
-
-Dans la fenêtre qui s'affiche, modifiez l'heure de la journée (norme de temps UTC 24 heures). Cliquez sur `Confirmer`{.action}.
-
-{.thumbnail}
-
-> [!primary]
->
-> Une fois la validation effectuée dans l’espace client, le changement sera effectif dans un délai de 24 à 48 heures.
->
-
-
-
-### Comment restaurer une sauvegarde depuis l’espace client OVHcloud
-
-Sélectionnez votre VPS puis cliquez sur l'onglet `Backup automatisé`{.action} dans le menu horizontal.
-Cliquez sur `...`{.action} à droite de la sauvegarde à restaurer et sélectionnez `Restauration`{.action}.
-
-{.thumbnail}
-
-Si vous avez récemment modifié votre mot de passe root, assurez-vous de cocher l'option « Modifier le mot de passe root lors de la restauration » dans la fenêtre contextuelle pour conserver votre mot de passe root actuel et cliquez sur `Confirmer`{.action}. Vous recevrez un e-mail dès que la restauration sera terminée. Celle-ci peut prendre un certain temps, selon l'espace disque utilisé.
-
-> [!alert]
->
-> Notez que les Backups automatisés n'incluent pas vos éventuels disques additionnels.
->
-
-
-
-### Monter et accéder à une image de sauvegarde
-
-Cette option permet d'accéder aux données de sauvegarde au cas où vous ne souhaitez pas remplacer complètement votre service existant par la restauration.
-
-> [!warning]
->
-> OVHcloud met à votre disposition des services dont la configuration, la gestion et la responsabilité vous incombent. Il vous revient de ce fait d'en assurer le bon fonctionnement.
->
-> Nous mettons à votre disposition ce guide afin de vous accompagner au mieux sur des tâches courantes. Néanmoins, nous vous recommandons de faire appel à un [prestataire spécialisé](/links/partner) et/ou de contacter l'éditeur du service si vous éprouvez des difficultés. En effet, nous ne serons pas en mesure de vous fournir une assistance. Plus d'informations dans la section [Aller plus loin](#go-further) de ce guide.
->
-
-Sélectionnez votre VPS puis cliquez sur l'onglet `Backup automatisé`{.action} dans le menu horizontal.
-Cliquez sur `...`{.action} à droite de la sauvegarde souhaitée et sélectionnez `Montage`{.action}.
-
-{.thumbnail}
-
-Lorsque vous utilisez cette option, une copie de la sauvegarde accessible en lecture et écriture est créée et montée. La sauvegarde d'origine reste disponible telle quelle pour les restaurations futures.
-
-Une fois le processus terminé, vous recevrez un e-mail. Vous pourrez alors vous connecter à votre VPS et ajouter la partition où se trouve votre sauvegarde.
-
-
-
-#### Sous Linux
-
-Connectez-vous à votre VPS en SSH.
-
-Vous pouvez utiliser la commande suivante pour vérifier le nom du nouveau périphérique connecté :
-
-```bash
-lsblk
-```
-
-Voici un exemple de résultat de cette commande :
-
-```console
-NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
-sda 8:0 0 25G 0 disk
-├─sda1 8:1 0 24.9G 0 part /
-├─sda14 8:14 0 4M 0 part
-└─sda15 8:15 0 106M 0 part
-sdb 8:16 0 25G 0 disk
-├─sdb1 8:17 0 24.9G 0 part
-├─sdb14 8:30 0 4M 0 part
-└─sdb15 8:31 0 106M 0 part /boot/efi
-```
-
-Dans cet exemple, la partition contenant votre sauvegarde de système de fichiers est nommée « sdb1 ».
-Créez à présent un répertoire pour cette partition et définissez-le comme point de montage :
-
-```bash
-sudo mkdir -p /mnt/restore
-sudo mount /dev/sdb1 /mnt/restore
-```
-
-Vous pouvez maintenant basculer vers ce dossier et accéder à votre sauvegarde de données.
-
-Pensez à bien démonter le Backup automatisé une fois son utilisation terminée. Cliquez sur le bouton `Démonter le backup`{.action} dans l'onglet `Backup automatisé`{.action}, puis validez dans la fenêtre qui s'affiche.
-
-{.thumbnail}
-
-
-
-#### Sous Windows
-
-Établissez une connexion RDP (Remote Desktop) avec votre VPS.
-
-Une fois connecté, faites un clic droit sur le bouton `Démarrer`{.action} et ouvrez la `Gestion des disques`{.action}.
-
-{.thumbnail}
-
-Votre sauvegarde montée apparaîtra comme un disque de base avec le même espace de stockage que votre disque principal.
-
-{.thumbnail}
-
-Le disque apparaîtra dans l'état `hors ligne`, faites un clic droit sur le disque et sélectionnez `En ligne`{.action}.
-
-{.thumbnail}
-
-Par la suite, votre sauvegarde montée sera accessible dans l'`Explorateur de fichiers`.
-
-{.thumbnail}
-
-Pensez à bien démonter le Backup automatisé une fois son utilisation terminée. Cliquez sur le bouton `Démonter le backup`{.action} dans l'onglet `Backup automatisé`{.action}, puis validez dans la fenêtre qui s'affiche.
-
-{.thumbnail}
-
-> [!warning]
->
-> Un redémarrage du serveur se produira lors du démontage de la sauvegarde.
->
-
-
-
-### Bonnes pratiques pour l'utilisation du Backup automatisé
-
-La fonctionnalité de Backup automatisé est basée sur les snapshots VPS. Nous vous recommandons de suivre les étapes ci-dessous pour éviter toute anomalie avant d'utiliser cette option.
-
-
-
-#### Configuration de l'agent QEMU sur un VPS
-
-Les snapshots sont des images instantanées de votre système en cours d'exécution (« live snapshots »). Pour garantir la disponibilité de votre système lors de la création du snapshot, l'agent QEMU est utilisé pour préparer le système de fichiers au processus.
-
-L'agent « **qemu-guest-agent** » n'est pas installé par défaut sur la plupart des distributions. En outre, les restrictions de licence peuvent empêcher OVHcloud de l'inclure dans les images d'OS disponibles. Par conséquent, il est recommandé de vérifier et d'installer cet agent au cas où il ne serait pas activé sur votre VPS. Connectez-vous à votre VPS en SSH et suivez les instructions ci-dessous, selon votre système d'exploitation.
-
-
-
-##### **Distributions Debian (Debian, Ubuntu)**
-
-Utilisez la commande suivante pour vérifier si le système est correctement configuré pour les snapshots :
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-```
-
-Le résultat attendu est le suivant :
-
-```console
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-Si le résultat est différent, comme par exemple « No such file or directory », installez la dernière version du paquet :
-
-```bash
-sudo apt-get update
-sudo apt-get install qemu-guest-agent
-```
-
-Redémarrez le VPS :
-
-```bash
-sudo reboot
-```
-
-Démarrez le service pour vous assurer qu'il est en cours d'exécution :
-
-```bash
-sudo service qemu-guest-agent start
-```
-
-
-
-##### **Distributions Redhat (CentOS, Fedora)**
-
-Utilisez la commande suivante pour vérifier si le système est correctement configuré pour les snapshots :
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-```
-
-Le résultat attendu est le suivant :
-
-```console
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-Si le résultat est différent, comme par exemple « No such file or directory », installez et activez l'agent :
-
-```bash
-sudo yum install qemu-guest-agent
-sudo chkconfig qemu-guest-agent on
-```
-
-Redémarrez le VPS:
-
-```bash
-sudo reboot
-```
-
-Démarrez l'agent et vérifiez qu'il est en cours d'exécution :
-
-```bash
-sudo service qemu-guest-agent start
-sudo service qemu-guest-agent status
-```
-
-
-
-##### **Windows**
-
-Vous pouvez installer l'agent via un fichier MSI, disponible sur le site du projet Fedora : .
-
-Vérifiez que le service est en cours d'exécution à l'aide de la commande powershell suivante :
-
-```console
-PS C:\Users\Administrator> Get-Service QEMU-GA
-Status Name DisplayName
------- ---- -----------
-Running QEMU-GA QEMU Guest Agent
-```
-
-
-
-## Aller plus loin
-
-[Utiliser les snapshots sur un VPS](/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps)
-
-Échangez avec notre [communauté d'utilisateurs](/links/community).
\ No newline at end of file
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.fr-fr.md b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.fr-fr.md
index e3a73232d4e..83fe4c395d4 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.fr-fr.md
@@ -1,7 +1,7 @@
---
title: "Comment utiliser les sauvegardes automatisées sur un VPS"
excerpt: "Découvrez comment utiliser l'option Backup automatisé depuis l'espace client OVHcloud pour sécuriser vos données"
-updated: 2025-08-07
+updated: 2025-09-11
---
## Objectif
@@ -22,6 +22,10 @@ L'option Backup Automatisé pour les VPS offre un moyen pratique de disposer de
- Posséder un [VPS OVHcloud](/links/bare-metal/vps) déjà configuré.
- Disposer d'un accès administrateur (sudo) en SSH à votre VPS (facultatif).
+> [!warning]
+> Cette fonctionnalité est actuellement indisponible pour les serveurs privés virtuels dans les [Local Zones](/links/bare-metal/vps-lz).
+>
+
## En pratique
### Présentation du contenu
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.it-it.md b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.it-it.md
index e6d8aad066d..ca935219c2d 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.it-it.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.it-it.md
@@ -1,7 +1,7 @@
---
title: "Come utilizzare i backup automatizzati su un VPS"
excerpt: "Come utilizzare l’opzione di Backup automatico nello Spazio Cliente OVHcloud per proteggere i dati"
-updated: 2025-08-07
+updated: 2025-09-11
---
## Obiettivo
@@ -21,6 +21,10 @@ Prima di applicare le opzioni di backup, consigliamo di fare riferimento alle pa
- Disporre di un [VPS OVHcloud](/links/bare-metal/vps) già configurato.
- Avere accesso in SSH al tuo VPS (facoltativo) in SSH.
+> [!warning]
+> Questa funzionalità non è attualmente disponibile per i server privati virtuali nelle [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Procedura
### Panoramica del contenuto
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.pl-pl.md b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.pl-pl.md
index 9b350a029ad..4caa0ee4681 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.pl-pl.md
@@ -1,7 +1,7 @@
---
title: "Jak korzystać z automatycznych kopii zapasowych na serwerze VPS"
excerpt: "Dowiedz się, jak korzystać z opcji zautomatyzowany backup zapasowych z poziomu Panelu klienta OVHcloud do zabezpieczania danych"
-updated: 2025-08-07
+updated: 2025-09-11
---
## Wprowadzenie
@@ -20,6 +20,10 @@ Opcja zautomatyzowany backup zapasowych dla serwerów VPS pozwala na udostępnie
- Serwer [Prywatne serwery wirtualne](/links/bare-metal/vps) z poziomu Twojego konta OVHcloud.
- Dostęp administracyjny (uprawnienia użytkownika root) do prywatnego serwera wirtualnego za pośrednictwem protokołu SSH.
+> [!warning]
+> Funkcja ta nie jest aktualnie dostępna dla prywatnych serwerów wirtualnych w [Local Zones](/links/bare-metal/vps-lz).
+>
+
## W praktyce
### Omówienie zawartości
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.pt-pt.md b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.pt-pt.md
index d1c88a125d7..ed7278b8137 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps/guide.pt-pt.md
@@ -1,7 +1,7 @@
---
title: "Como utilizar os backups automatizados num VPS"
excerpt: "Descubra como utilizar a opção Backup automatizado a partir da Área de Cliente OVHcloud para proteger os seus dados"
-updated: 2025-08-07
+updated: 2025-09-11
---
## Objetivo
@@ -20,6 +20,10 @@ A opção de Backup automatizado para VPS oferece uma forma prática de ter back
- Ter um [VPS OVHcloud](/links/bare-metal/vps) já configurado.
- Ter acesso de administrador (sudo) por SSH ao VPS (opcional).
+> [!warning]
+> Esta funcionalidade está atualmente indisponível para os servidores privados virtuais nas [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instruções
### Apresentação do conteúdo
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.de-de.md b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.de-de.md
index 60e57f15070..6818e633b25 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.de-de.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.de-de.md
@@ -1,13 +1,9 @@
---
title: "Snapshots auf einem VPS verwenden"
excerpt: "Erfahren Sie hier, wie Sie im OVHcloud Kundencenter die Snapshot-Option aktivieren und verwenden"
-updated: 2024-09-18
+updated: 2025-09-11
---
-> [!primary]
-> Diese Übersetzung wurde durch unseren Partner SYSTRAN automatisch erstellt. In manchen Fällen können ungenaue Formulierungen verwendet worden sein, z.B. bei der Beschriftung von Schaltflächen oder technischen Details. Bitte ziehen Sie im Zweifelsfall die englische oder französische Fassung der Anleitung zu Rate. Möchten Sie mithelfen, diese Übersetzung zu verbessern? Dann nutzen Sie dazu bitte den Button "Beitragen" auf dieser Seite.
->
-
## Ziel
Mithilfe eines Snapshots haben Sie die Möglichkeit, schnell und einfach ein laufendes System zu sichern, etwa bevor Änderungen vorgenommen werden, die unerwünschte oder unvorhergesehene Folgen haben können (z.B. Testen einer neuen Konfiguration oder Software). Es handelt sich jedoch nicht um eine vollständige Backup-Strategie.
@@ -24,6 +20,10 @@ Bevor Sie Backup-Optionen anwenden, empfehlen wir, die [Produktseiten und FAQ](/
- Sie haben Zugriff auf Ihr [OVHcloud Kundencenter](/links/manager).
- Sie haben einen [VPS](/links/bare-metal/vps) in Ihrem Kunden-Account.
+> [!warning]
+> Diese Funktion ist derzeit nicht verfügbar für VPS in [Local Zones](/links/bare-metal/vps-lz).
+>
+
## In der praktischen Anwendung
Loggen Sie sich in Ihr [OVHcloud Kundencenter](/links/manager) ein, gehen Sie in den Bereich `Bare Metal Cloud`{.action} und wählen Sie unter `Virtual Private Server`{.action} Ihren Server aus.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-asia.md b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-asia.md
deleted file mode 100644
index 50a161ddf57..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-asia.md
+++ /dev/null
@@ -1,192 +0,0 @@
----
-title: "How to use snapshots on a VPS"
-excerpt: "Find out how to enable and use the Snapshot option in the OVHcloud Control Panel"
-updated: 2024-09-18
----
-
-## Objective
-
-Creating a snapshot is a fast and simple way to secure a functioning system before making changes that might have undesired or unforeseen consequences, for example testing a new configuration or software. It does not, however, constitute a complete system backup strategy.
-
-**This guide explains the usage of snapshots for your OVHcloud VPS.**
-
-> [!primary]
->
-Before applying backup options, we recommend to consult the [product pages and FAQ](/links/bare-metal/vps-options) for pricing comparisons and further details.
->
-
-## Requirements
-
-- Access to the [OVHcloud Control Panel](/links/manager)
-- An OVHcloud [VPS service](/links/bare-metal/vps) already set up
-
-## Instructions
-
-Log in to your [OVHcloud Control Panel](/links/manager), open the `Bare Metal Cloud`{.action} section, and select your server under `Virtual Private Servers`{.action}.
-
-### Step 1: Subscribing to the snapshot option
-
-From the `Home`{.action} tab, scroll down to the box labelled **Summary of options**.
-If "Snapshot" is already set to "Enabled", go directly to step 2. If "Snapshot" is not yet enabled, click on `...`{.action} next to the option "Snapshot" and in the context menu click on `Order`{.action}.
-
-{.thumbnail}
-
-In the next step, please take note of the pricing information, then click on `Order`{.action}. You will be guided through the order process and receive a confirmation email.
-
-To cancel the service option, click on the button `...`{.action} next to the option "Snapshot" and choose `Close`{.action} from the context menu.
-
-{.thumbnail}
-
-### Step 2: Taking a snapshot
-
-Once the option is enabled, click on `...`{.action} next to the option "Snapshot" and in the context menu click `Take a snapshot`{.action}. You can write a description that will be attached to your snapshot. The time it takes to create the snapshot depends on the storage space in use. Afterwards, refresh your page to see the timestamp of the creation in the **Summary of options** box.
-
-### Step 3: Deleting or restoring a snapshot
-
-Since you can only have one snapshot activated at a time, the existing snapshot has to be deleted before creating a new one. Simply choose `Delete the snapshot`{.action} from the context menu.
-
-{.thumbnail}
-
-If you are sure that you would like to reset your VPS to the status of the snapshot, click `Restore the snapshot`{.action} and confirm the restoration task in the popup window.
-
-> [!alert]
->
-> Please note that when you restore a VPS from a snapshot, the snapshot will be deleted. If you wish to keep the same snapshot, you should take a new one before making changes to the restored system.
->
-> If the snapshot function is too limited for your project, consider switching to the option [Automated Backups](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps).
-
-### Downloading a snapshot
-
-The current snapshot can be retrieved via download link. Click on `...`{.action} next to the option "Snapshot" and choose `Download the snapshot`{.action} from the context menu.
-
-{.thumbnail}
-
-> [!primary]
->
-> If your VPS is of an older product range, you might receive an error message because the option is not available for a legacy VPS. These older services have the following naming scheme: *vpsXXXX.ovh.net* (in which *X* stands for a number). You can verify this server reference on the `Home`{.action} tab in your [OVHcloud Control Panel](/links/manager).
->
-
-In the popup window, click on `Generate download link`{.action}.
-
-{.thumbnail}
-
-After a few seconds, a success message appears. Below it, you can copy the complete download command with one click.
-
-{.thumbnail}
-
-The size of the snapshot and the expiration date of the link will also be displayed.
-
-Note that the download link will expire after **24 hours**.
-
-The download command uses `curl`, in the following format:
-
-```bash
-curl "https://storage.sbg.cloud.ovh.net/v1/AUTH_f5fgh4674dd706f15f6ffgf4z667d3f4g5f05/glance/5ceg3f93-8b49-436b-aefe-4185f9fc3f78?
-temp_url_sig=f508cacda60256d5f211ddddf3f81130e935f0e4&temp_url_expires=1678247579" --output vps-x11x11xyy.vps.ovh.net --fail
-```
-
-It should work from any command line terminal.
-
-When using Windows *PowerShell* however, you will need to adjust the command as follows:
-
-```powershell
-curl -Uri "https://storage.sbg.cloud.ovh.net/v1/AUTH_f5fgh4674dd706f15f6ffgf4z667d3f4g5f05/glance/5ceg3f93-8b49-436b-aefe-4185f9fc3f78?
-temp_url_sig=f508cacda60256d5f211ddddf3f81130e935f0e4&temp_url_expires=1678247579" -OutFile vps-x11x11xyy.vps.ovh.net
-```
-
-{.thumbnail}
-
-> [!primary]
->
-> We recommend not to download snapshots directly to the VPS, to avoid using up the storage space.
->
-> The downloaded file can be imported into your Public Cloud Project as an image (QCOW2) via [OpenStack](products/public-cloud-compute-instance-management). (Find an example of use in [this guide](/pages/public_cloud/compute/upload_own_image).)
->
-
-### Best practice for using snapshots
-
-#### Configuring the QEMU agent on a VPS
-
-Snapshots are instantaneous images of your running system ("live snapshot"). To ensure the availability of your system when the snapshot is created, the QEMU agent is used to prepare the filesystem for the process.
-
-The required *qemu-guest-agent* is not installed by default on most distributions. Moreover, licensing restrictions may prevent OVHcloud from including it in the available OS images. Therefore, it is best practice to verify and install the agent in case it is not activated on your VPS. Connect to your VPS via SSH and follow the instructions below, according to your operating system.
-
-##### **Debian-based distributions (Debian, Ubuntu)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different ("No such file or directory"), install the latest package:
-
-```bash
-sudo apt-get update
-sudo apt-get install qemu-guest-agent
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Check the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent status
-```
-
-##### **Redhat-based distributions (Centos, Fedora)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different ("No such file or directory"), install and enable the agent:
-
-```bash
-sudo yum install qemu-guest-agent
-sudo chkconfig qemu-guest-agent on
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Check the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent status
-```
-
-##### **Kernel issues on cPanel**
-
-Consult our [cPanel auto backup](/pages/bare_metal_cloud/virtual_private_servers/cpanel_snapshot) guide to find out how to fix issues with cPanel servers getting stuck during an OVHcloud automated backup.
-
-##### **Windows**
-
-You can install the agent via MSI file, available from the Fedora project website: .
-
-Verify that the service is running by using this *PowerShell* command:
-
-```powershell
-PS C:\Users\Administrator> Get-Service QEMU-GA
-
-Status Name DisplayName
------- ---- -----------
-Running QEMU-GA QEMU Guest Agent
-```
-
-## Go further
-
-[Using automated backups on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps)
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-au.md b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-au.md
deleted file mode 100644
index c3af9bf2e2a..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-au.md
+++ /dev/null
@@ -1,192 +0,0 @@
----
-title: "How to use snapshots on a VPS"
-excerpt: "Find out how to enable and use the Snapshot option in the OVHcloud Control Panel"
-updated: 2024-09-18
----
-
-## Objective
-
-Creating a snapshot is a fast and simple way to secure a functioning system before making changes that might have undesired or unforeseen consequences, for example testing a new configuration or software. It does not, however, constitute a complete system backup strategy.
-
-**This guide explains the usage of snapshots for your OVHcloud VPS.**
-
-> [!primary]
->
-Before applying backup options, we recommend to consult the [product pages and FAQ](/links/bare-metal/vps-options) for pricing comparisons and further details.
->
-
-## Requirements
-
-- Access to the [OVHcloud Control Panel](/links/manager)
-- An OVHcloud [VPS service](/links/bare-metal/vps) already set up
-
-## Instructions
-
-Log in to your [OVHcloud Control Panel](/links/manager), open the "Bare Metal Cloud" section, and select your server under `Virtual Private Servers`{.action}.
-
-### Step 1: Subscribing to the snapshot option
-
-From the `Home`{.action} tab, scroll down to the box labelled **Summary of options**.
-If "Snapshot" is already set to "Enabled", go directly to step 2. If "Snapshot" is not yet enabled, click on `...`{.action} next to the option "Snapshot" and in the context menu click on `Order`{.action}.
-
-{.thumbnail}
-
-In the next step, please take note of the pricing information, then click on `Order`{.action}. You will be guided through the order process and receive a confirmation email.
-
-To cancel the service option, click on the button `...`{.action} next to the option "Snapshot" and choose `Close`{.action} from the context menu.
-
-{.thumbnail}
-
-### Step 2: Taking a snapshot
-
-Once the option is enabled, click on `...`{.action} next to the option "Snapshot" and in the context menu click `Take a snapshot`{.action}. You can write a description that will be attached to your snapshot. The time it takes to create the snapshot depends on the storage space in use. Afterwards, refresh your page to see the timestamp of the creation in the **Summary of options** box.
-
-### Step 3: Deleting or restoring a snapshot
-
-Since you can only have one snapshot activated at a time, the existing snapshot has to be deleted before creating a new one. Simply choose `Delete the snapshot`{.action} from the context menu.
-
-{.thumbnail}
-
-If you are sure that you would like to reset your VPS to the status of the snapshot, click `Restore the snapshot`{.action} and confirm the restoration task in the popup window.
-
-> [!alert]
->
-> Please note that when you restore a VPS from a snapshot, the snapshot will be deleted. If you wish to keep the same snapshot, you should take a new one before making changes to the restored system.
->
-> If the snapshot function is too limited for your project, consider switching to the option [Automated Backups](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps).
-
-### Downloading a snapshot
-
-The current snapshot can be retrieved via download link. Click on `...`{.action} next to the option "Snapshot" and choose `Download the snapshot`{.action} from the context menu.
-
-{.thumbnail}
-
-> [!primary]
->
-> If your VPS is of an older product range, you might receive an error message because the option is not available for a legacy VPS. These older services have the following naming scheme: *vpsXXXX.ovh.net* (in which *X* stands for a number). You can verify this server reference on the `Home`{.action} tab in your [OVHcloud Control Panel](/links/manager).
->
-
-In the popup window, click on `Generate download link`{.action}.
-
-{.thumbnail}
-
-After a few seconds, a success message appears. Below it, you can copy the complete download command with one click.
-
-{.thumbnail}
-
-The size of the snapshot and the expiration date of the link will also be displayed.
-
-Note that the download link will expire after **24 hours**.
-
-The download command uses `curl`, in the following format:
-
-```bash
-curl "https://storage.sbg.cloud.ovh.net/v1/AUTH_f5fgh4674dd706f15f6ffgf4z667d3f4g5f05/glance/5ceg3f93-8b49-436b-aefe-4185f9fc3f78?
-temp_url_sig=f508cacda60256d5f211ddddf3f81130e935f0e4&temp_url_expires=1678247579" --output vps-x11x11xyy.vps.ovh.net --fail
-```
-
-It should work from any command line terminal.
-
-When using Windows *PowerShell* however, you will need to adjust the command as follows:
-
-```powershell
-curl -Uri "https://storage.sbg.cloud.ovh.net/v1/AUTH_f5fgh4674dd706f15f6ffgf4z667d3f4g5f05/glance/5ceg3f93-8b49-436b-aefe-4185f9fc3f78?
-temp_url_sig=f508cacda60256d5f211ddddf3f81130e935f0e4&temp_url_expires=1678247579" -OutFile vps-x11x11xyy.vps.ovh.net
-```
-
-{.thumbnail}
-
-> [!primary]
->
-> We recommend not to download snapshots directly to the VPS, to avoid using up the storage space.
->
-> The downloaded file can be imported into your Public Cloud Project as an image (QCOW2) via [OpenStack](products/public-cloud-compute-instance-management). (Find an example of use in [this guide](/pages/public_cloud/compute/upload_own_image).)
->
-
-### Best practice for using snapshots
-
-#### Configuring the QEMU agent on a VPS
-
-Snapshots are instantaneous images of your running system ("live snapshot"). To ensure the availability of your system when the snapshot is created, the QEMU agent is used to prepare the filesystem for the process.
-
-The required *qemu-guest-agent* is not installed by default on most distributions. Moreover, licensing restrictions may prevent OVHcloud from including it in the available OS images. Therefore, it is best practice to verify and install the agent in case it is not activated on your VPS. Connect to your VPS via SSH and follow the instructions below, according to your operating system.
-
-##### **Debian-based distributions (Debian, Ubuntu)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different ("No such file or directory"), install the latest package:
-
-```bash
-sudo apt-get update
-sudo apt-get install qemu-guest-agent
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Check the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent status
-```
-
-##### **Redhat-based distributions (Centos, Fedora)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different ("No such file or directory"), install and enable the agent:
-
-```bash
-sudo yum install qemu-guest-agent
-sudo chkconfig qemu-guest-agent on
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Check the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent status
-```
-
-##### **Kernel issues on cPanel**
-
-Consult our [cPanel auto backup](/pages/bare_metal_cloud/virtual_private_servers/cpanel_snapshot) guide to find out how to fix issues with cPanel servers getting stuck during an OVHcloud automated backup.
-
-##### **Windows**
-
-You can install the agent via MSI file, available from the Fedora project website: .
-
-Verify that the service is running by using this *PowerShell* command:
-
-```powershell
-PS C:\Users\Administrator> Get-Service QEMU-GA
-
-Status Name DisplayName
------- ---- -----------
-Running QEMU-GA QEMU Guest Agent
-```
-
-## Go further
-
-[Using automated backups on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps)
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-ca.md b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-ca.md
deleted file mode 100644
index 50a161ddf57..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-ca.md
+++ /dev/null
@@ -1,192 +0,0 @@
----
-title: "How to use snapshots on a VPS"
-excerpt: "Find out how to enable and use the Snapshot option in the OVHcloud Control Panel"
-updated: 2024-09-18
----
-
-## Objective
-
-Creating a snapshot is a fast and simple way to secure a functioning system before making changes that might have undesired or unforeseen consequences, for example testing a new configuration or software. It does not, however, constitute a complete system backup strategy.
-
-**This guide explains the usage of snapshots for your OVHcloud VPS.**
-
-> [!primary]
->
-Before applying backup options, we recommend to consult the [product pages and FAQ](/links/bare-metal/vps-options) for pricing comparisons and further details.
->
-
-## Requirements
-
-- Access to the [OVHcloud Control Panel](/links/manager)
-- An OVHcloud [VPS service](/links/bare-metal/vps) already set up
-
-## Instructions
-
-Log in to your [OVHcloud Control Panel](/links/manager), open the `Bare Metal Cloud`{.action} section, and select your server under `Virtual Private Servers`{.action}.
-
-### Step 1: Subscribing to the snapshot option
-
-From the `Home`{.action} tab, scroll down to the box labelled **Summary of options**.
-If "Snapshot" is already set to "Enabled", go directly to step 2. If "Snapshot" is not yet enabled, click on `...`{.action} next to the option "Snapshot" and in the context menu click on `Order`{.action}.
-
-{.thumbnail}
-
-In the next step, please take note of the pricing information, then click on `Order`{.action}. You will be guided through the order process and receive a confirmation email.
-
-To cancel the service option, click on the button `...`{.action} next to the option "Snapshot" and choose `Close`{.action} from the context menu.
-
-{.thumbnail}
-
-### Step 2: Taking a snapshot
-
-Once the option is enabled, click on `...`{.action} next to the option "Snapshot" and in the context menu click `Take a snapshot`{.action}. You can write a description that will be attached to your snapshot. The time it takes to create the snapshot depends on the storage space in use. Afterwards, refresh your page to see the timestamp of the creation in the **Summary of options** box.
-
-### Step 3: Deleting or restoring a snapshot
-
-Since you can only have one snapshot activated at a time, the existing snapshot has to be deleted before creating a new one. Simply choose `Delete the snapshot`{.action} from the context menu.
-
-{.thumbnail}
-
-If you are sure that you would like to reset your VPS to the status of the snapshot, click `Restore the snapshot`{.action} and confirm the restoration task in the popup window.
-
-> [!alert]
->
-> Please note that when you restore a VPS from a snapshot, the snapshot will be deleted. If you wish to keep the same snapshot, you should take a new one before making changes to the restored system.
->
-> If the snapshot function is too limited for your project, consider switching to the option [Automated Backups](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps).
-
-### Downloading a snapshot
-
-The current snapshot can be retrieved via download link. Click on `...`{.action} next to the option "Snapshot" and choose `Download the snapshot`{.action} from the context menu.
-
-{.thumbnail}
-
-> [!primary]
->
-> If your VPS is of an older product range, you might receive an error message because the option is not available for a legacy VPS. These older services have the following naming scheme: *vpsXXXX.ovh.net* (in which *X* stands for a number). You can verify this server reference on the `Home`{.action} tab in your [OVHcloud Control Panel](/links/manager).
->
-
-In the popup window, click on `Generate download link`{.action}.
-
-{.thumbnail}
-
-After a few seconds, a success message appears. Below it, you can copy the complete download command with one click.
-
-{.thumbnail}
-
-The size of the snapshot and the expiration date of the link will also be displayed.
-
-Note that the download link will expire after **24 hours**.
-
-The download command uses `curl`, in the following format:
-
-```bash
-curl "https://storage.sbg.cloud.ovh.net/v1/AUTH_f5fgh4674dd706f15f6ffgf4z667d3f4g5f05/glance/5ceg3f93-8b49-436b-aefe-4185f9fc3f78?
-temp_url_sig=f508cacda60256d5f211ddddf3f81130e935f0e4&temp_url_expires=1678247579" --output vps-x11x11xyy.vps.ovh.net --fail
-```
-
-It should work from any command line terminal.
-
-When using Windows *PowerShell* however, you will need to adjust the command as follows:
-
-```powershell
-curl -Uri "https://storage.sbg.cloud.ovh.net/v1/AUTH_f5fgh4674dd706f15f6ffgf4z667d3f4g5f05/glance/5ceg3f93-8b49-436b-aefe-4185f9fc3f78?
-temp_url_sig=f508cacda60256d5f211ddddf3f81130e935f0e4&temp_url_expires=1678247579" -OutFile vps-x11x11xyy.vps.ovh.net
-```
-
-{.thumbnail}
-
-> [!primary]
->
-> We recommend not to download snapshots directly to the VPS, to avoid using up the storage space.
->
-> The downloaded file can be imported into your Public Cloud Project as an image (QCOW2) via [OpenStack](products/public-cloud-compute-instance-management). (Find an example of use in [this guide](/pages/public_cloud/compute/upload_own_image).)
->
-
-### Best practice for using snapshots
-
-#### Configuring the QEMU agent on a VPS
-
-Snapshots are instantaneous images of your running system ("live snapshot"). To ensure the availability of your system when the snapshot is created, the QEMU agent is used to prepare the filesystem for the process.
-
-The required *qemu-guest-agent* is not installed by default on most distributions. Moreover, licensing restrictions may prevent OVHcloud from including it in the available OS images. Therefore, it is best practice to verify and install the agent in case it is not activated on your VPS. Connect to your VPS via SSH and follow the instructions below, according to your operating system.
-
-##### **Debian-based distributions (Debian, Ubuntu)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different ("No such file or directory"), install the latest package:
-
-```bash
-sudo apt-get update
-sudo apt-get install qemu-guest-agent
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Check the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent status
-```
-
-##### **Redhat-based distributions (Centos, Fedora)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different ("No such file or directory"), install and enable the agent:
-
-```bash
-sudo yum install qemu-guest-agent
-sudo chkconfig qemu-guest-agent on
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Check the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent status
-```
-
-##### **Kernel issues on cPanel**
-
-Consult our [cPanel auto backup](/pages/bare_metal_cloud/virtual_private_servers/cpanel_snapshot) guide to find out how to fix issues with cPanel servers getting stuck during an OVHcloud automated backup.
-
-##### **Windows**
-
-You can install the agent via MSI file, available from the Fedora project website: .
-
-Verify that the service is running by using this *PowerShell* command:
-
-```powershell
-PS C:\Users\Administrator> Get-Service QEMU-GA
-
-Status Name DisplayName
------- ---- -----------
-Running QEMU-GA QEMU Guest Agent
-```
-
-## Go further
-
-[Using automated backups on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps)
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-gb.md b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-gb.md
index 9227dd201d2..32abe26852b 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-gb.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-gb.md
@@ -1,7 +1,7 @@
---
title: "How to use snapshots on a VPS"
excerpt: "Find out how to enable and use the Snapshot option in the OVHcloud Control Panel"
-updated: 2024-09-18
+updated: 2025-09-11
---
## Objective
@@ -18,7 +18,11 @@ Before applying backup options, we recommend to consult the [product pages and F
## Requirements
- Access to the [OVHcloud Control Panel](/links/manager)
-- An OVHcloud [VPS service](/links/bare-metal/vps) already set up
+- An active [Virtual Private Server](/links/bare-metal/vps) in your OVHcloud account
+
+> [!warning]
+> This feature is currently unavailable for Virtual Private Servers in [Local Zones](/links/bare-metal/vps-lz).
+>
## Instructions
@@ -187,6 +191,6 @@ Running QEMU-GA QEMU Guest Agent
## Go further
-[Using automated backups on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps)
+[How to use automated backups on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps)
Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-ie.md b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-ie.md
deleted file mode 100644
index 6b393a16c83..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-ie.md
+++ /dev/null
@@ -1,192 +0,0 @@
----
-title: "How to use snapshots on a VPS"
-excerpt: "Find out how to enable and use the Snapshot option in the OVHcloud Control Panel"
-updated: 2024-09-18
----
-
-## Objective
-
-Creating a snapshot is a fast and simple way to secure a functioning system before making changes that might have undesired or unforeseen consequences, for example testing a new configuration or software. It does not, however, constitute a complete system backup strategy.
-
-**This guide explains the usage of snapshots for your OVHcloud VPS.**
-
-> [!primary]
->
-Before applying backup options, we recommend to consult the [product pages and FAQ](/links/bare-metal/vps-options) for pricing comparisons and further details.
->
-
-## Requirements
-
-- Access to the [OVHcloud Control Panel](/links/manager)
-- An OVHcloud [VPS service](/links/bare-metal/vps) already set up
-
-## Instructions
-
-Log in to your [OVHcloud Control Panel](/links/manager), open the `Bare Metal Cloud`{.action} section, and select your server under `Virtual Private Servers`{.action}.
-
-### Step 1: Subscribing to the snapshot option
-
-From the `Home`{.action} tab, scroll down to the box labelled **Summary of options**.
-If "Snapshot" is already set to "Enabled", go directly to step 2. If "Snapshot" is not yet enabled, click on `...`{.action} next to the option "Snapshot" and in the context menu click on `Order`{.action}.
-
-{.thumbnail}
-
-In the next step, please take note of the pricing information, then click on `Order`{.action}. You will be guided through the order process and receive a confirmation email.
-
-To cancel the service option, click on the button `...`{.action} next to the option "Snapshot" and choose `Close`{.action} from the context menu.
-
-{.thumbnail}
-
-### Step 2: Taking a snapshot
-
-Once the option is enabled, click on `...`{.action} next to the option "Snapshot" and in the context menu click `Take a snapshot`{.action}. You can write a description that will be attached to your snapshot. The time it takes to create the snapshot depends on the storage space in use. Afterwards, refresh your page to see the timestamp of the creation in the **Summary of options** box.
-
-### Step 3: Deleting or restoring a snapshot
-
-Since you can only have one snapshot activated at a time, the existing snapshot has to be deleted before creating a new one. Simply choose `Delete the snapshot`{.action} from the context menu.
-
-{.thumbnail}
-
-If you are sure that you would like to reset your VPS to the status of the snapshot, click `Restore the snapshot`{.action} and confirm the restoration task in the popup window.
-
-> [!alert]
->
-> Please note that when you restore a VPS from a snapshot, the snapshot will be deleted. If you wish to keep the same snapshot, you should take a new one before making changes to the restored system.
->
-> If the snapshot function is too limited for your project, consider switching to the option [Automated Backups](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps).
-
-### Downloading a snapshot
-
-The current snapshot can be retrieved via download link. Click on `...`{.action} next to the option "Snapshot" and choose `Download the snapshot`{.action} from the context menu.
-
-{.thumbnail}
-
-> [!primary]
->
-> If your VPS is of an older product range, you might receive an error message because the option is not available for a legacy VPS. These older services have the following naming scheme: *vpsXXXX.ovh.net* (in which *X* stands for a number). You can verify this server reference on the `Home`{.action} tab in your [OVHcloud Control Panel](/links/manager).
->
-
-In the popup window, click on `Generate download link`{.action}.
-
-{.thumbnail}
-
-After a few seconds, a success message appears. Below it, you can copy the complete download command with one click.
-
-{.thumbnail}
-
-The size of the snapshot and the expiration date of the link will also be displayed.
-
-Note that the download link will expire after **24 hours**.
-
-The download command uses `curl`, in the following format:
-
-```bash
-curl "https://storage.sbg.cloud.ovh.net/v1/AUTH_f5fgh4674dd706f15f6ffgf4z667d3f4g5f05/glance/5ceg3f93-8b49-436b-aefe-4185f9fc3f78?
-temp_url_sig=f508cacda60256d5f211ddddf3f81130e935f0e4&temp_url_expires=1678247579" --output vps-x11x11xyy.vps.ovh.net --fail
-```
-
-It should work from any command line terminal.
-
-When using Windows *PowerShell* however, you will need to adjust the command as follows:
-
-```powershell
-curl -Uri "https://storage.sbg.cloud.ovh.net/v1/AUTH_f5fgh4674dd706f15f6ffgf4z667d3f4g5f05/glance/5ceg3f93-8b49-436b-aefe-4185f9fc3f78?
-temp_url_sig=f508cacda60256d5f211ddddf3f81130e935f0e4&temp_url_expires=1678247579" -OutFile vps-x11x11xyy.vps.ovh.net
-```
-
-{.thumbnail}
-
-> [!primary]
->
-> We recommend not to download snapshots directly to the VPS, to avoid using up the storage space.
->
-> The downloaded file can be imported into your Public Cloud Project as an image (QCOW2) via [OpenStack](products/public-cloud-compute-instance-management). (Find an example of use in [this guide](/pages/public_cloud/compute/upload_own_image).)
->
-
-### Best practice for using snapshots
-
-#### Configuring the QEMU agent on a VPS
-
-Snapshots are instantaneous images of your running system ("live snapshot"). To ensure the availability of your system when the snapshot is created, the QEMU agent is used to prepare the filesystem for the process.
-
-The required *qemu-guest-agent* is not installed by default on most distributions. Moreover, licensing restrictions may prevent OVHcloud from including it in the available OS images. Therefore, it is best practice to verify and install the agent in case it is not activated on your VPS. Connect to your VPS via SSH and follow the instructions below, according to your operating system.
-
-##### **Debian-based distributions (Debian, Ubuntu)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different ("No such file or directory"), install the latest package:
-
-```bash
-sudo apt-get update
-sudo apt-get install qemu-guest-agent
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Check the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent status
-```
-
-##### **Redhat-based distributions (Centos, Fedora)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different ("No such file or directory"), install and enable the agent:
-
-```bash
-sudo yum install qemu-guest-agent
-sudo chkconfig qemu-guest-agent on
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Check the agent and verify that it is running:
-
-```bash
-sudo service qemu-guest-agent status
-```
-
-##### **Kernel issues on cPanel**
-
-Consult our [cPanel auto backup](/pages/bare_metal_cloud/virtual_private_servers/cpanel_snapshot) guide to find out how to fix issues with cPanel servers getting stuck during an OVHcloud automated backup.
-
-##### **Windows**
-
-You can install the agent via MSI file, available from the Fedora project website: .
-
-Verify that the service is running by using this *PowerShell* command:
-
-```powershell
-PS C:\Users\Administrator> Get-Service QEMU-GA
-
-Status Name DisplayName
------- ---- -----------
-Running QEMU-GA QEMU Guest Agent
-```
-
-## Go further
-
-[Using automated backups on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps)
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-sg.md b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-sg.md
deleted file mode 100644
index 4047b346c35..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-sg.md
+++ /dev/null
@@ -1,193 +0,0 @@
----
-title: "How to use snapshots on a VPS"
-excerpt: "Find out how to enable and use the Snapshot option in the OVHcloud Control Panel"
-updated: 2024-09-18
----
-
-## Objective
-
-Creating a snapshot is a fast and simple way to secure a functioning system before making changes that might have undesired or unforeseen consequences, for example testing a new configuration or software. It does not, however, constitute a complete system backup strategy.
-
-**This guide explains the usage of snapshots for your OVHcloud VPS.**
-
-> [!primary]
->
-Before applying backup options, we recommend to consult the [product pages and FAQ](/links/bare-metal/vps-options) for pricing comparisons and further details.
->
-
-
-## Requirements
-
-- Access to the [OVHcloud Control Panel](/links/manager)
-- An OVHcloud [VPS service](/links/bare-metal/vps) already set up
-
-## Instructions
-
-Log in to your [OVHcloud Control Panel](/links/manager), open the `Bare Metal Cloud`{.action} section, and select your server under `Virtual Private Servers`{.action}.
-
-### Step 1: Subscribing to the snapshot option
-
-From the `Home`{.action} tab, scroll down to the box labelled **Summary of options**.
-If "Snapshot" is already set to "Enabled", go directly to step 2. If "Snapshot" is not yet enabled, click on `...`{.action} next to the option "Snapshot" and in the context menu click on `Order`{.action}.
-
-{.thumbnail}
-
-In the next step, please take note of the pricing information, then click on `Order`{.action}. You will be guided through the order process and receive a confirmation email.
-
-To cancel the service option, click on the button `...`{.action} next to the option "Snapshot" and choose `Close`{.action} from the context menu.
-
-{.thumbnail}
-
-### Step 2: Taking a snapshot
-
-Once the option is enabled, click on `...`{.action} next to the option "Snapshot" and in the context menu click `Take a snapshot`{.action}. You can write a description that will be attached to your snapshot. The time it takes to create the snapshot depends on the storage space in use. Afterwards, refresh your page to see the timestamp of the creation in the **Summary of options** box.
-
-### Step 3: Deleting or restoring a snapshot
-
-Since you can only have one snapshot activated at a time, the existing snapshot has to be deleted before creating a new one. Simply choose `Delete the snapshot`{.action} from the context menu.
-
-{.thumbnail}
-
-If you are sure that you would like to reset your VPS to the status of the snapshot, click `Restore the snapshot`{.action} and confirm the restoration task in the popup window.
-
-> [!alert]
->
-> Please note that when you restore a VPS from a snapshot, the snapshot will be deleted. If you wish to keep the same snapshot, you should take a new one before making changes to the restored system.
->
-> If the snapshot function is too limited for your project, consider switching to the option [Automated Backups](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps).
-
-### Downloading a snapshot
-
-The current snapshot can be retrieved via download link. Click on `...`{.action} next to the option "Snapshot" and choose `Download the snapshot`{.action} from the context menu.
-
-{.thumbnail}
-
-> [!primary]
->
-> If your VPS is of an older product range, you might receive an error message because the option is not available for a legacy VPS. These older services have the following naming scheme: *vpsXXXX.ovh.net* (in which *X* stands for a number). You can verify this server reference on the `Home`{.action} tab in your [OVHcloud Control Panel](/links/manager).
->
-
-In the popup window, click on `Generate download link`{.action}.
-
-{.thumbnail}
-
-After a few seconds, a success message appears. Below it, you can copy the complete download command with one click.
-
-{.thumbnail}
-
-The size of the snapshot and the expiration date of the link will also be displayed.
-
-Note that the download link will expire after **24 hours**.
-
-The download command uses `curl`, in the following format:
-
-```bash
-curl "https://storage.sbg.cloud.ovh.net/v1/AUTH_f5fgh4674dd706f15f6ffgf4z667d3f4g5f05/glance/5ceg3f93-8b49-436b-aefe-4185f9fc3f78?
-temp_url_sig=f508cacda60256d5f211ddddf3f81130e935f0e4&temp_url_expires=1678247579" --output vps-x11x11xyy.vps.ovh.net --fail
-```
-
-It should work from any command line terminal.
-
-When using Windows *PowerShell* however, you will need to adjust the command as follows:
-
-```powershell
-curl -Uri "https://storage.sbg.cloud.ovh.net/v1/AUTH_f5fgh4674dd706f15f6ffgf4z667d3f4g5f05/glance/5ceg3f93-8b49-436b-aefe-4185f9fc3f78?
-temp_url_sig=f508cacda60256d5f211ddddf3f81130e935f0e4&temp_url_expires=1678247579" -OutFile vps-x11x11xyy.vps.ovh.net
-```
-
-{.thumbnail}
-
-> [!primary]
->
-> We recommend not to download snapshots directly to the VPS, to avoid using up the storage space.
->
-> The downloaded file can be imported into your Public Cloud Project as an image (QCOW2) via [OpenStack](products/public-cloud-compute-instance-management). (Find an example of use in [this guide](/pages/public_cloud/compute/upload_own_image).)
->
-
-### Best practice for using snapshots
-
-#### Configuring the QEMU agent on a VPS
-
-Snapshots are instantaneous images of your running system ("live snapshot"). To ensure the availability of your system when the snapshot is created, the QEMU agent is used to prepare the filesystem for the process.
-
-The required *qemu-guest-agent* is not installed by default on most distributions. Moreover, licensing restrictions may prevent OVHcloud from including it in the available OS images. Therefore, it is best practice to verify and install the agent in case it is not activated on your VPS. Connect to your VPS via SSH and follow the instructions below, according to your operating system.
-
-##### **Debian-based distributions (Debian, Ubuntu)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different ("No such file or directory"), install the latest package:
-
-```bash
-sudo apt-get update
-sudo apt-get install qemu-guest-agent
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Check the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent status
-```
-
-##### **Redhat-based distributions (Centos, Fedora)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different ("No such file or directory"), install and enable the agent:
-
-```bash
-sudo yum install qemu-guest-agent
-sudo chkconfig qemu-guest-agent on
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Check the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent status
-```
-
-##### **Kernel issues on cPanel**
-
-Consult our [cPanel auto backup](/pages/bare_metal_cloud/virtual_private_servers/cpanel_snapshot) guide to find out how to fix issues with cPanel servers getting stuck during an OVHcloud automated backup.
-
-##### **Windows**
-
-You can install the agent via MSI file, available from the Fedora project website: .
-
-Verify that the service is running by using this *PowerShell* command:
-
-```powershell
-PS C:\Users\Administrator> Get-Service QEMU-GA
-
-Status Name DisplayName
------- ---- -----------
-Running QEMU-GA QEMU Guest Agent
-```
-
-## Go further
-
-[Using automated backups on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps)
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-us.md b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-us.md
deleted file mode 100644
index c3af9bf2e2a..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.en-us.md
+++ /dev/null
@@ -1,192 +0,0 @@
----
-title: "How to use snapshots on a VPS"
-excerpt: "Find out how to enable and use the Snapshot option in the OVHcloud Control Panel"
-updated: 2024-09-18
----
-
-## Objective
-
-Creating a snapshot is a fast and simple way to secure a functioning system before making changes that might have undesired or unforeseen consequences, for example testing a new configuration or software. It does not, however, constitute a complete system backup strategy.
-
-**This guide explains the usage of snapshots for your OVHcloud VPS.**
-
-> [!primary]
->
-Before applying backup options, we recommend to consult the [product pages and FAQ](/links/bare-metal/vps-options) for pricing comparisons and further details.
->
-
-## Requirements
-
-- Access to the [OVHcloud Control Panel](/links/manager)
-- An OVHcloud [VPS service](/links/bare-metal/vps) already set up
-
-## Instructions
-
-Log in to your [OVHcloud Control Panel](/links/manager), open the "Bare Metal Cloud" section, and select your server under `Virtual Private Servers`{.action}.
-
-### Step 1: Subscribing to the snapshot option
-
-From the `Home`{.action} tab, scroll down to the box labelled **Summary of options**.
-If "Snapshot" is already set to "Enabled", go directly to step 2. If "Snapshot" is not yet enabled, click on `...`{.action} next to the option "Snapshot" and in the context menu click on `Order`{.action}.
-
-{.thumbnail}
-
-In the next step, please take note of the pricing information, then click on `Order`{.action}. You will be guided through the order process and receive a confirmation email.
-
-To cancel the service option, click on the button `...`{.action} next to the option "Snapshot" and choose `Close`{.action} from the context menu.
-
-{.thumbnail}
-
-### Step 2: Taking a snapshot
-
-Once the option is enabled, click on `...`{.action} next to the option "Snapshot" and in the context menu click `Take a snapshot`{.action}. You can write a description that will be attached to your snapshot. The time it takes to create the snapshot depends on the storage space in use. Afterwards, refresh your page to see the timestamp of the creation in the **Summary of options** box.
-
-### Step 3: Deleting or restoring a snapshot
-
-Since you can only have one snapshot activated at a time, the existing snapshot has to be deleted before creating a new one. Simply choose `Delete the snapshot`{.action} from the context menu.
-
-{.thumbnail}
-
-If you are sure that you would like to reset your VPS to the status of the snapshot, click `Restore the snapshot`{.action} and confirm the restoration task in the popup window.
-
-> [!alert]
->
-> Please note that when you restore a VPS from a snapshot, the snapshot will be deleted. If you wish to keep the same snapshot, you should take a new one before making changes to the restored system.
->
-> If the snapshot function is too limited for your project, consider switching to the option [Automated Backups](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps).
-
-### Downloading a snapshot
-
-The current snapshot can be retrieved via download link. Click on `...`{.action} next to the option "Snapshot" and choose `Download the snapshot`{.action} from the context menu.
-
-{.thumbnail}
-
-> [!primary]
->
-> If your VPS is of an older product range, you might receive an error message because the option is not available for a legacy VPS. These older services have the following naming scheme: *vpsXXXX.ovh.net* (in which *X* stands for a number). You can verify this server reference on the `Home`{.action} tab in your [OVHcloud Control Panel](/links/manager).
->
-
-In the popup window, click on `Generate download link`{.action}.
-
-{.thumbnail}
-
-After a few seconds, a success message appears. Below it, you can copy the complete download command with one click.
-
-{.thumbnail}
-
-The size of the snapshot and the expiration date of the link will also be displayed.
-
-Note that the download link will expire after **24 hours**.
-
-The download command uses `curl`, in the following format:
-
-```bash
-curl "https://storage.sbg.cloud.ovh.net/v1/AUTH_f5fgh4674dd706f15f6ffgf4z667d3f4g5f05/glance/5ceg3f93-8b49-436b-aefe-4185f9fc3f78?
-temp_url_sig=f508cacda60256d5f211ddddf3f81130e935f0e4&temp_url_expires=1678247579" --output vps-x11x11xyy.vps.ovh.net --fail
-```
-
-It should work from any command line terminal.
-
-When using Windows *PowerShell* however, you will need to adjust the command as follows:
-
-```powershell
-curl -Uri "https://storage.sbg.cloud.ovh.net/v1/AUTH_f5fgh4674dd706f15f6ffgf4z667d3f4g5f05/glance/5ceg3f93-8b49-436b-aefe-4185f9fc3f78?
-temp_url_sig=f508cacda60256d5f211ddddf3f81130e935f0e4&temp_url_expires=1678247579" -OutFile vps-x11x11xyy.vps.ovh.net
-```
-
-{.thumbnail}
-
-> [!primary]
->
-> We recommend not to download snapshots directly to the VPS, to avoid using up the storage space.
->
-> The downloaded file can be imported into your Public Cloud Project as an image (QCOW2) via [OpenStack](products/public-cloud-compute-instance-management). (Find an example of use in [this guide](/pages/public_cloud/compute/upload_own_image).)
->
-
-### Best practice for using snapshots
-
-#### Configuring the QEMU agent on a VPS
-
-Snapshots are instantaneous images of your running system ("live snapshot"). To ensure the availability of your system when the snapshot is created, the QEMU agent is used to prepare the filesystem for the process.
-
-The required *qemu-guest-agent* is not installed by default on most distributions. Moreover, licensing restrictions may prevent OVHcloud from including it in the available OS images. Therefore, it is best practice to verify and install the agent in case it is not activated on your VPS. Connect to your VPS via SSH and follow the instructions below, according to your operating system.
-
-##### **Debian-based distributions (Debian, Ubuntu)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different ("No such file or directory"), install the latest package:
-
-```bash
-sudo apt-get update
-sudo apt-get install qemu-guest-agent
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Check the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent status
-```
-
-##### **Redhat-based distributions (Centos, Fedora)**
-
-Use the following command to check whether the system is properly set up for snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-If the output is different ("No such file or directory"), install and enable the agent:
-
-```bash
-sudo yum install qemu-guest-agent
-sudo chkconfig qemu-guest-agent on
-```
-
-Reboot the VPS:
-
-```bash
-sudo reboot
-```
-
-Check the service to ensure it is running:
-
-```bash
-sudo service qemu-guest-agent status
-```
-
-##### **Kernel issues on cPanel**
-
-Consult our [cPanel auto backup](/pages/bare_metal_cloud/virtual_private_servers/cpanel_snapshot) guide to find out how to fix issues with cPanel servers getting stuck during an OVHcloud automated backup.
-
-##### **Windows**
-
-You can install the agent via MSI file, available from the Fedora project website: .
-
-Verify that the service is running by using this *PowerShell* command:
-
-```powershell
-PS C:\Users\Administrator> Get-Service QEMU-GA
-
-Status Name DisplayName
------- ---- -----------
-Running QEMU-GA QEMU Guest Agent
-```
-
-## Go further
-
-[Using automated backups on a VPS](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps)
-
-Join our [community of users](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.es-es.md b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.es-es.md
index ec6eae612b1..adf8569f40a 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.es-es.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.es-es.md
@@ -1,13 +1,9 @@
---
title: "Uso de instantáneas Snapshots en un servidor virtual privado (VPS)"
excerpt: "Cómo activar y usar la opción Instantáneas en el panel de control de OVHcloud"
-updated: 2024-09-18
+updated: 2025-09-11
---
-> [!primary]
-> Esta traducción ha sido generada de forma automática por nuestro partner SYSTRAN. En algunos casos puede contener términos imprecisos, como en las etiquetas de los botones o los detalles técnicos. En caso de duda, le recomendamos que consulte la versión inglesa o francesa de la guía. Si quiere ayudarnos a mejorar esta traducción, por favor, utilice el botón «Contribuir» de esta página.
->
-
## Objetivo
Crear una instantánea (snapshot) es una forma simple y rápida de proteger un sistema en funciones antes de realizar cambios (p. ej., probar una nueva configuración o software) que puedan tener consecuencias indeseadas o imprevistas. Sin embargo, no constituye una estrategia completa de copia de seguridad del sistema.
@@ -24,6 +20,10 @@ Antes de aplicar las opciones de copia de seguridad, le recomendamos que consult
- Tener acceso al [panel de control de OVHcloud](/links/manager).
- Tener un [servicio de servidor virtual privado (VPS)](/links/bare-metal/vps) de OVHcloud configurado.
+> [!warning]
+> Esta funcionalidad no está disponible actualmente para los servidores virtuales en las [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Procedimiento
Conéctese al [Panel de configuración de OVHcloud](/links/manager), acceda a la sección `Bare Metal Cloud`{.action} y seleccione el servidor en la sección `Servidores Privados Virtuales`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.es-us.md b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.es-us.md
deleted file mode 100644
index 45a5da43969..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.es-us.md
+++ /dev/null
@@ -1,191 +0,0 @@
----
-title: "Uso de instantáneas Snapshots en un servidor virtual privado (VPS)"
-excerpt: "Cómo activar y usar la opción Instantáneas en el panel de control de OVHcloud"
-updated: 2024-09-18
----
-
-> [!primary]
-> Esta traducción ha sido generada de forma automática por nuestro partner SYSTRAN. En algunos casos puede contener términos imprecisos, como en las etiquetas de los botones o los detalles técnicos. En caso de duda, le recomendamos que consulte la versión inglesa o francesa de la guía. Si quiere ayudarnos a mejorar esta traducción, por favor, utilice el botón «Contribuir» de esta página.
->
-
-## Objetivo
-
-Crear una instantánea (snapshot) es una forma simple y rápida de proteger un sistema en funciones antes de realizar cambios (p. ej., probar una nueva configuración o software) que puedan tener consecuencias indeseadas o imprevistas. Sin embargo, no constituye una estrategia completa de copia de seguridad del sistema.
-
-**En esta guía, se explica cómo usar las instantáneas en su servidor virtual privado (VPS) de OVHcloud.**
-
-> [!primary]
->
-Antes de aplicar las opciones de copia de seguridad, le recomendamos que consulte las [preguntas frecuentes y demás páginas del producto](/links/bare-metal/vps-options) para acceder a una comparativa de los precios y otras informaciones.
->
-
-## Requisitos
-
-- Tener acceso al [panel de control de OVHcloud](/links/manager).
-- Tener un [servicio de servidor virtual privado (VPS)](/links/bare-metal/vps) de OVHcloud configurado.
-
-## Procedimiento
-
-Conéctese al [Panel de configuración de OVHcloud](/links/manager), acceda a la sección `Bare Metal Cloud`{.action} y seleccione el servidor en la sección `Servidores Privados Virtuales`{.action}.
-
-### Paso 1: Suscribirse a la opción «Instantáneas»
-
-Acceda a la pestaña `Inicio`{.action} y desplácese hacia abajo hasta el cuadro **Resumen de opciones**
-. Si el estado de "Snapshot" ya es "Activado", vaya directamente al paso 2. Si "Snapshot" todavía no está activado, haga clic en `...`{.action} junto a la opción "Snapshot" y, seguidamente, en `Contratar`{.action} (en el menú contextual).
-
-{.thumbnail}
-
-En el siguiente paso, preste atención a la información sobre los precios y, a continuación, haga clic en `Contratar`{.action}. Se le guiará por el proceso de contratación y recibirá un mensaje de correo electrónico de confirmación.
-
-Para dar de baja la opción de servicio, haga clic en el botón `...`{.action} situado junto a "Snapshot" y seleccione `Dar de baja`{.action} en el menú contextual.
-
-{.thumbnail}
-
-### Paso 2: Tomar una instantánea
-
-Una vez activada la opción, haga clic en `...`{.action} junto a la opción «Instantáneas» y, seguidamente, en «Tomar una instantánea» (en el menú contextual). Puede escribir una descripción que se asociará al snapshot. El tiempo de creación del snapshot depende del espacio de almacenamiento utilizado. Después, aparecerá la fecha y hora de su creación en el cuadro «Resumen de opciones».
-
-### Paso 3: Eliminar o restaurar una instantánea
-
-Puesto que las instantáneas solo se pueden activar de una en una, se debe eliminar la instantánea existente antes de crear una nueva. En el menú contextual, seleccione `Eliminar la instantánea`{.action}.
-
-{.thumbnail}
-
-Si está seguro de que desea restablecer su servidor virtual privado (VPS) al estado de la instantánea, haga clic en `Restaurar la instantánea`{.action} y confirme la acción de restauración en la ventana emergente.
-
-> [!alert]
->
-> Tenga en cuenta que, al restaurar un VPS a partir de un snapshot, el snapshot se eliminará. Si desea conservar la misma instantánea, debe tomar una nueva antes de realizar cambios en el sistema restaurado.
->
-> Si la función snapshot es demasiado limitada para su proyecto, la opción [Backup automatizado](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps) es una alternativa.
->
-
-### Descargar un snapshot
-
-El snapshot actual puede recuperarse mediante un enlace de descarga. Haga clic en el botón `...`{.action} situado junto a la opción `Snapshot` y seleccione `Descargar el snapshot`{.action} en el menú contextual.
-
-{.thumbnail}
-
-> [!primary]
->
-> Si su VPS proviene de una antigua gama, es posible que reciba un mensaje de error, ya que la opción no está disponible en los antiguos VPS. Su VPS procede de una antigua gama si su modelo de denominación es similar a: *vpsXXXX.ovh.net* (donde *X* representa un número). Puede consultar esta referencia del servidor en la pestaña `Inicio`{.action} del [área de cliente de OVHcloud](/links/manager).
->
-
-En la nueva ventana, haga clic en `Generar el enlace de descarga`{.action}.
-
-{.thumbnail}
-
-Al cabo de unos segundos, se mostrará un mensaje de éxito. Abajo, puede copiar el comando completo de descarga en un clic.
-
-{.thumbnail}
-
-También se mostrarán el tamaño del snapshot y la fecha de expiración del enlace.
-
-Tenga en cuenta que el enlace de descarga expirará después de **24 horas**.
-
-La orden de descarga utiliza un `curl` en el siguiente formato:
-
-```bash
-curl "https://storage.sbg.cloud.ovh.net/v1/AUTH_f5fgh4674dd706f15f6ffgf4z667d3f4g5f05/glance/5ceg3f93-8b49-436b-aefe-4185f9fc3f78?
-temp_url_sig=f508cacda60256d5f211ddddf3f81130e935f0e4&temp_url_expires=1678247579" --output vps-x11x11xyy.vps.ovh.net --fail
-```
-
-Este comando debe funcionar desde cualquier terminal de línea de comandos. No obstante, cuando utilice Windows *PowerShell*, deberá ajustar el comando de la siguiente forma:
-
-```powershell
-curl -Uri "https://storage.sbg.cloud.ovh.net/v1/AUTH_f5fgh4674dd706f15f6ffgf4z667d3f4g5f05/glance/5ceg3f93-8b49-436b-aefe-4185f9fc3f78?
-temp_url_sig=f508cacda60256d5f211ddddf3f81130e935f0e4&temp_url_expires=1678247579" -OutFile vps-x11x11xyy.vps.ovh.net
-```
-
-{.thumbnail}
-
-> [!primary]
->
-> No obstante, para no consumir demasiado espacio de almacenamiento, le recomendamos que no descargue los snapshots directamente en el VPS.
->
-> El archivo cargado puede importarse en un proyecto de Public Cloud como imagen (QCOW2) mediante [OpenStack](products/public-cloud-compute-instance-management). (Consulte un ejemplo de uso en [esta guía](/pages/public_cloud/compute/upload_own_image).)
->
-
-### Buenas prácticas para la creación de un snapshot
-
-#### Configuración del software QEMU en un VPS
-
-Los snapshots son imágenes instantáneas de su sistema en ejecución (« live snapshots »). Para garantizar la disponibilidad de su sistema durante la creación del snapshot, el software QEMO permite preparar el sistema de archivos para este proceso.
-
-El *qemu-guest-agent* necesario no está instalado por defecto en la mayoría de distribuciones. Además, las restricciones de licencia pueden impedir que OVHcloud lo incluya en las imágenes de los SO disponibles. Por lo tanto, le recomendamos que compruebe si este agente está activado en su VPS y, en caso negativo, que lo instale. Para ello, conéctese a su VPS por SSH y siga las instrucciones que se indican en función de su sistema operativo.
-
-##### **Distribuciones Debian (Debian, Ubuntu)**
-
-Utilice el siguiente comando para comprobar si el sistema está configurado correctamente para los snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-Si el resultado es diferente (« No such file or directory »), instale la última versión del paquete:
-
-```bash
-sudo apt-get update
-sudo apt-get install qemu-guest-agent
-```
-
-Reiniciar el VPS:
-
-```bash
-sudo reboot
-```
-
-Verifique el servicio para garantizar que está en ejecución:
-
-```bash
-sudo service qemu-guest-agent status
-```
-
-##### **Distribuciones Red Hat (CentOS, Fedora)**
-
-Utilice el siguiente comando para comprobar si el sistema está configurado correctamente para los snapshots:
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-Si el resultado es diferente (« No such file or directory »), instale y active el software:
-
-```bash
-sudo yum install qemu-guest-agent
-sudo chkconfig qemu-guest-agent on
-```
-
-Reiniciar el VPS:
-
-```bash
-sudo reboot
-```
-
-Verifique el software y compruebe que está en ejecución:
-
-```bash
-sudo service qemu-guest-agent status
-```
-
-##### **Windows**
-
-Puede instalar el software mediante un archivo MSI disponible en el sitio web del proyecto Fedora:
-
-Compruebe que el servicio está en ejecución con el siguiente comando *PowerShell*:
-
-```powershell
-PS C:\Users\Administrator> Get-Service QEMU-GA
-
-Status Name DisplayName
------- ---- -----------
-Running QEMU-GA QEMU Guest Agent
-```
-
-## Más información
-
-[Usar copias de seguridad automatizadas en un servidor virtual privado (VPS)](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps)
-
-Interactúe con nuestra comunidad de usuarios en .
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.fr-ca.md b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.fr-ca.md
deleted file mode 100644
index 8508c468270..00000000000
--- a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.fr-ca.md
+++ /dev/null
@@ -1,193 +0,0 @@
----
-title: "Utiliser le snapshot"
-excerpt: "Découvrez comment activer et utiliser l’option snapshot depuis l’espace client OVHcloud"
-updated: 2024-09-18
----
-
-## Objectif
-
-La création d'un snapshot (instantané) est un moyen simple et rapide de sauvegarder un système fonctionnel avant d'y apporter des modifications pouvant avoir des conséquences non souhaitées ou imprévues. Par exemple, tester une nouvelle configuration ou un nouveau logiciel.
-Un snapshot ne constitue pas pour autant une sauvegarde complète du système.
-
-**Découvrez comment activer et utiliser l’option snapshot depuis l’espace client OVHcloud.**
-
-
-
-> [!primary]
-> Avant d'appliquer une option de sauvegarde, nous vous recommandons de consulter les [options VPS](/links/bare-metal/vps-options) afin de comparer les détails et tarifs de chaque option.
->
-
-## Prérequis
-
-- Avoir accès à votre [espace client OVHcloud](/links/manager).
-- Un [VPS OVHcloud](/links/bare-metal/vps) déjà configuré.
-
-## En pratique
-
-Connectez-vous à votre [espace client OVHcloud](/links/manager), rendez-vous dans la section `Bare Metal Cloud`{.action} et sélectionnez votre serveur sous la partie `Serveur privés virtuels`{.action}.
-
-### Étape 1 : souscrire l'option snapshot
-
-Depuis l'onglet `Accueil`{.action}, descendez jusqu'au menu « Résumé des options ».
-Si « Snapshot » est déjà sur l'état « Activé », passez directement à l'étape 2. Si « Snapshot » n'est pas encore activé, cliquez sur `...`{.action} à droite de l'option « Snapshot » puis cliquez sur `Commander`{.action} dans le menu qui s'affiche.
-
-{.thumbnail}
-
-Veuillez prendre connaissance des informations de tarification de cette option, puis cliquez sur `Commander`{.action}. Vous serez orienté dans le processus de commande et recevrez un e-mail de confirmation.
-
-Pour résilier l'option de service, cliquez sur le bouton `...`{.action} à côté de « Snapshot » et choisissez `Résilier`{.action} dans le menu contextuel.
-
-{.thumbnail}
-
-### Étape 2 : prendre un snapshot
-
-Une fois l'option activée, cliquez sur `...`{.action} à droite de l'option « Snapshot » puis cliquez sur `Prendre un Snapshot`{.action} dans le menu qui apparaît. Vous pouvez tapez une description qui sera attachée à votre snapshot. La durée de création du snapshot dépend de l'espace de stockage utilisé. Par la suite, l'horodatage de la création s'affiche dans le menu « Résumé des options ».
-
-### Étape 3 : supprimer/restaurer un snapshot
-
-Étant donné que vous ne pouvez activer qu'un seul snapshot à la fois, vous devez supprimer le snapshot existant avant d'en créer un nouveau. Choisissez simplement `Supprimer le snapshot`{.action} dans le menu contextuel.
-
-{.thumbnail}
-
-Si vous êtes sûr de vouloir restaurer votre VPS à l'état du snapshot, cliquez sur `Restaurer le snapshot`{.action} et confirmez la restauration dans la fenêtre qui s'affiche alors.
-
-> [!alert]
->
-> Lorsque vous restaurez un VPS à partir d’un snapshot, ce dernier sera supprimé. Si vous souhaitez conserver le même snapshot, vous devez en créer un nouveau avant d'apporter des modifications au système restauré.
->
-> Si la fonction snapshot est trop limitée pour votre projet, l'option [Sauvegardes automatisées](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps) est une alternative.
->
-
-### Télécharger un snapshot
-
-Le snapshot en cours peut être récupéré via un lien de téléchargement. Cliquez sur le bouton `...`{.action} à côté de l'option `Snapshot` et choisissez `Télécharger le Snapshot`{.action} dans le menu contextuel.
-
-{.thumbnail}
-
-> [!primary]
->
-> Si votre VPS est issu d'une ancienne gamme, il est possible que vous receviez un message d'erreur car l'option n'est pas disponible sur les anciens VPS. Votre VPS est issu d'une ancienne gamme si le nom du modèle est nommé de cette façon : *vpsXXXX.ovh.net* (les *X* représentent le numéro de votre modèle). Vous pouvez vérifier cette référence de serveur dans l'onglet `Accueil`{.action} de votre [espace client OVHcloud](/links/manager).
->
-
-Dans la fenêtre qui s'affiche, cliquez sur `Générer le lien de téléchargement`{.action}.
-
-{.thumbnail}
-
-Patientez un instant, un message de succès s'affiche. En dessous, vous pouvez copier la commande complète de téléchargement en un clic.
-
-{.thumbnail}
-
-La taille du snapshot et la date d'expiration du lien seront également affichées.
-
-Notez que le lien de téléchargement expirera après **24 heures**.
-
-La commande de téléchargemment utilise un `curl` au format suivant :
-
-```bash
-curl "https://storage.sbg.cloud.ovh.net/v1/AUTH_f5fgh4674dd706f15f6ffgf4z667d3f4g5f05/glance/5ceg3f93-8b49-436b-aefe-4185f9fc3f78?
-temp_url_sig=f508cacda60256d5f211ddddf3f81130e935f0e4&temp_url_expires=1678247579" --output vps-x11x11xyy.vps.ovh.net --fail
-```
-
-Cette commande doit fonctionner depuis n'importe quel terminal de ligne de commande. Cependant, lorsque vous utilisez Windows *PowerShell*, vous devrez ajuster la commande ainsi :
-
-```powershell
-curl -Uri "https://storage.sbg.cloud.ovh.net/v1/AUTH_f5fgh4674dd706f15f6ffgf4z667d3f4g5f05/glance/5ceg3f93-8b49-436b-aefe-4185f9fc3f78?
-temp_url_sig=f508cacda60256d5f211ddddf3f81130e935f0e4&temp_url_expires=1678247579" -OutFile vps-x11x11xyy.vps.ovh.net
-```
-
-{.thumbnail}
-
-> [!primary]
->
-> Pour éviter de consommer trop d'espace de stockage, nous vous déconseillons de télécharger les snapshots directement sur le VPS.
->
-> Le fichier téléchargé peut être importé dans un Projet Public Cloud en tant qu'image (QCOW2) via [OpenStack](products/public-cloud-compute-instance-management). (Retrouvez un exemple d'utilisation dans [ce guide](/pages/public_cloud/compute/upload_own_image).)
->
-
-### Bonnes pratiques pour la création d'un snapshot
-
-#### Configuration de l'agent QEMU sur un VPS
-
-Les snapshots sont des images instantanées de votre système en cours d'exécution (« live snapshots »). Pour garantir la disponibilité de votre système lors de la création du snapshot, l'agent QEMU est utilisé pour préparer le système de fichiers au processus.
-
-Le *qemu-guest-agent* requis n'est pas installé par défaut sur la plupart des distributions. En outre, les restrictions de licence peuvent empêcher OVHcloud de l'inclure dans les images d'OS disponibles. Par conséquent, il est recommandé de vérifier et d'installer l'agent au cas où il ne serait pas activé sur votre VPS. Connectez-vous à votre VPS en SSH et suivez les instructions ci-dessous, selon votre système d'exploitation.
-
-##### **Distributions Debian (Debian, Ubuntu)**
-
-Utilisez la commande suivante pour vérifier si le système est correctement configuré pour les snapshots :
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-Si le résultat est différent (« No such file or directory »), installez le dernier package :
-
-```bash
-sudo apt-get update
-sudo apt-get install qemu-guest-agent
-```
-
-Redémarrez le VPS:
-
-```bash
-sudo reboot
-```
-
-Vérifier le service pour vous assurer qu'il est en cours d'exécution :
-
-```bash
-sudo service qemu-guest-agent status
-```
-
-##### **Distributions Redhat (CentOS, Fedora)**
-
-Utilisez la commande suivante pour vérifier si le système est correctement configuré pour les snapshots :
-
-```bash
-file /dev/virtio-ports/org.qemu.guest_agent.0
-/dev/virtio-ports/org.qemu.guest_agent.0: symbolic link to ../vport2p1
-```
-
-Si le résultat est différent (« No such file or directory »), installez et activez l'agent :
-
-```bash
-sudo yum install qemu-guest-agent
-sudo chkconfig qemu-guest-agent on
-```
-
-Redémarrez le VPS:
-
-```bash
-sudo reboot
-```
-
-Vérifier l'agent et vérifiez qu'il est en cours d'exécution :
-
-```bash
-sudo service qemu-guest-agent status
-```
-
-##### **Problèmes Kernel sur cPanel**
-
-Consultez notre guide [Sauvegarde automatique - Kernel panic (cPanel)](/pages/bare_metal_cloud/virtual_private_servers/cpanel_snapshot) pour savoir comment résoudre les problèmes de blocage des serveurs cPanel lors de la sauvegarde automatique OVHcloud.
-
-##### **Windows**
-
-Vous pouvez installer l'agent via un fichier MSI, disponible sur le site du projet Fedora:
-
-Vérifiez que le service est en cours d'exécution à l'aide de la commande *PowerShell* suivante :
-
-```powershell
-PS C:\Users\Administrator> Get-Service QEMU-GA
-
-Status Name DisplayName
------- ---- -----------
-Running QEMU-GA QEMU Guest Agent
-```
-
-## Aller plus loin
-
-[Utiliser la sauvegarde automatique sur un VPS](/pages/bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps)
-
-Échangez avec notre [communauté d'utilisateurs](/links/community).
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.fr-fr.md b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.fr-fr.md
index 754ed4deb7e..a04bab7dd5f 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.fr-fr.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.fr-fr.md
@@ -1,7 +1,7 @@
---
title: "Utiliser le snapshot"
excerpt: "Découvrez comment activer et utiliser l’option snapshot depuis l’espace client OVHcloud"
-updated: 2024-09-18
+updated: 2025-09-11
---
## Objectif
@@ -22,6 +22,10 @@ Un snapshot ne constitue pas pour autant une sauvegarde complète du système.
- Avoir accès à votre [espace client OVHcloud](/links/manager).
- Un [VPS OVHcloud](/links/bare-metal/vps) déjà configuré.
+> [!warning]
+> Cette fonctionnalité est actuellement indisponible pour les serveurs privés virtuels dans les [Local Zones](/links/bare-metal/vps-lz).
+>
+
## En pratique
Connectez-vous à votre [espace client OVHcloud](/links/manager), rendez-vous dans la section `Bare Metal Cloud`{.action} et sélectionnez votre serveur sous la partie `Serveur privés virtuels`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.it-it.md b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.it-it.md
index f68b68b7154..15e29ee4c2a 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.it-it.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.it-it.md
@@ -1,13 +1,9 @@
---
title: "Usare snapshot su un VPS"
excerpt: "Scopri come abilitare e utilizzare l’opzione Snapshot nello Spazio Cliente OVHcloud"
-updated: 2024-09-18
+updated: 2025-09-11
---
-> [!primary]
-> Questa traduzione è stata generata automaticamente dal nostro partner SYSTRAN. I contenuti potrebbero presentare imprecisioni, ad esempio la nomenclatura dei pulsanti o alcuni dettagli tecnici. In caso di dubbi consigliamo di fare riferimento alla versione inglese o francese della guida. Per aiutarci a migliorare questa traduzione, utilizza il pulsante "Contribuisci" di questa pagina.
->
-
## Obiettivo
Creare uno snapshot è un modo semplice e rapido per mettere al sicuro un sistema che funziona prima di effettuare modifiche che potrebbero avere conseguenze indesiderate o impreviste, ad esempio per testare una nuova configurazione o un nuovo software. Ciò non costituisce comunque una strategia completa di backup del sistema.
@@ -24,6 +20,10 @@ Prima di applicare opzioni di backup, consigliamo di fare riferimento alle pagin
- avere accesso allo [Spazio Cliente OVHcloud](/links/manager)
- un servizio [VPS OVHcloud](/links/bare-metal/vps) già impostato
+> [!warning]
+> Questa funzionalità non è attualmente disponibile per i server privati virtuali nelle [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Procedura
Accedi allo [Spazio Cliente OVHcloud](/links/manager), clicca su `Bare Metal Cloud`{.action} e seleziona il tuo server nella sezione `Server Privati Virtuali`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.pl-pl.md b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.pl-pl.md
index af311739c0a..6dceed4f717 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.pl-pl.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.pl-pl.md
@@ -1,13 +1,9 @@
---
title: "Korzystanie z migawek na prywatnym serwerze wirtualnym"
excerpt: "Dowiedz się, jak włączyć opcję migawki w Panelu klienta OVHcloud i korzystać z niej"
-updated: 2024-09-18
+updated: 2025-09-11
---
-> [!primary]
-> Tłumaczenie zostało wygenerowane automatycznie przez system naszego partnera SYSTRAN. W niektórych przypadkach mogą wystąpić nieprecyzyjne sformułowania, na przykład w tłumaczeniu nazw przycisków lub szczegółów technicznych. W przypadku jakichkolwiek wątpliwości zalecamy zapoznanie się z angielską/francuską wersją przewodnika. Jeśli chcesz przyczynić się do ulepszenia tłumaczenia, kliknij przycisk "Zgłóś propozycję modyfikacji" na tej stronie.
->
-
## Wprowadzenie
Utworzenie migawki jest szybkim i prostym sposobem na zabezpieczenie działania systemu przed wprowadzeniem zmian, które mogą mieć niepożądane lub nieprzewidziane konsekwencje, na przykład podczas testowania nowej konfiguracji albo oprogramowania. Nie stanowi to jednak pełnej strategii tworzenia kopii zapasowych systemu.
@@ -24,6 +20,10 @@ Przed zastosowaniem opcji tworzenia kopii zapasowych zalecamy przejrzenie [stron
- dostęp do [Panelu klienta OVHcloud](/links/manager)
- skonfigurowana [usługa VPS](/links/bare-metal/vps) OVHcloud
+> [!warning]
+> Funkcja ta nie jest aktualnie dostępna dla prywatnych serwerów wirtualnych w [Local Zones](/links/bare-metal/vps-lz).
+>
+
## W praktyce
Zaloguj się do [Panelu client OVHcloud](/links/manager), przejdź do sekcji `Bare Metal Cloud`{.action} i wybierz Twój serwer w części `Prywatny serwer wirtualny`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.pt-pt.md b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.pt-pt.md
index 8d3e20fd152..65ae931c97f 100644
--- a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.pt-pt.md
+++ b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/guide.pt-pt.md
@@ -1,13 +1,9 @@
---
title: "Utilizar snapshots num alojamento VPS"
excerpt: "Saiba como ativar e utilizar a opção Snapshot na Área de Cliente OVHcloud"
-updated: 2024-09-18
+updated: 2025-09-11
---
-> [!primary]
-> Esta tradução foi automaticamente gerada pelo nosso parceiro SYSTRAN. Em certos casos, poderão ocorrer formulações imprecisas, como por exemplo nomes de botões ou detalhes técnicos. Recomendamos que consulte a versão inglesa ou francesa do manual, caso tenha alguma dúvida. Se nos quiser ajudar a melhorar esta tradução, clique em "Contribuir" nesta página.
->
-
## Sumário
Criar um snapshot é uma forma simples e rápida de garantir o funcionamento de um sistema antes de proceder a alterações que podem ter consequências indesejadas e imprevisíveis como, por exemplo, testar uma nova configuração ou software. Não constitui, no entanto, uma estratégia completa de backup do sistema.
@@ -24,6 +20,10 @@ Antes de aplicar as opções de backup, recomendamos que consulte as [páginas e
- acesso à [Área de Cliente OVHcloud](/links/manager)
- um [serviço VPS](/links/bare-metal/vps) OVHcloud já instalado
+> [!warning]
+> Esta funcionalidade está atualmente indisponível para os servidores privados virtuais nas [Local Zones](/links/bare-metal/vps-lz).
+>
+
## Instruções
Ligue-se à sua [Área de Cliente OVHcloud](/links/manager), vá à secção `Bare Metal Cloud`{.action} e selecione o seu servidor na secção `Servidor privado virtual`{.action}.
diff --git a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/meta.yaml b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/meta.yaml
index 42a3be4fadd..83c4439e5d7 100755
--- a/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/meta.yaml
+++ b/pages/bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps/meta.yaml
@@ -1,2 +1,3 @@
id: 4951634d-c137-4639-ac51-0aaa182bf86e
-full_slug: vps-using-snapshots
\ No newline at end of file
+full_slug: vps-using-snapshots
+translation_banner: true
\ No newline at end of file
diff --git a/pages/index.md b/pages/index.md
index 9f134628194..62d9f48ebf5 100644
--- a/pages/index.md
+++ b/pages/index.md
@@ -270,14 +270,14 @@
+ [Managing a legacy VPS](bare_metal_cloud/virtual_private_servers/vps_legacy_control_panel)
+ [End of Plesk and cPanel support for VPS - Ensure continuity of your services](bare_metal_cloud/virtual_private_servers/eos-cpanel-plesk)
+ [Backup options](bare-metal-cloud-virtual-private-servers-backups)
- + [Using snapshots on a VPS](bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps)
+ + [How to use snapshots on a VPS](bare_metal_cloud/virtual_private_servers/using-snapshots-on-a-vps)
+ [How to use automated backups on a VPS](bare_metal_cloud/virtual_private_servers/using-automated-backups-on-a-vps)
+ [How to configure an additional disk](bare_metal_cloud/virtual_private_servers/config_additional_disk)
+ [How to increase the size of an additional disk](bare_metal_cloud/virtual_private_servers/increase_additional_disk)
+ [Network and IP management](bare-metal-cloud-virtual-private-servers-network-and-ip-management)
+ [How to configure IPv6 on a VPS](bare_metal_cloud/virtual_private_servers/configure-ipv6)
+ [How to configure reverse DNS for your server (PTR record)](bare_metal_cloud/virtual_private_servers/configuring-reverse-dns)
- + [Configuring IP aliasing](bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing)
+ + [How to configure IP aliasing](bare_metal_cloud/virtual_private_servers/configuring-ip-aliasing)
+ [Configuring OVHcloud Secondary DNS on a VPS](bare_metal_cloud/virtual_private_servers/adding-secondary-dns-on-vps)
+ [Troubleshooting](bare-metal-cloud-virtual-private-servers-troubleshooting)
+ [Checking the file system on a VPS](bare_metal_cloud/virtual_private_servers/check-filesystem)
diff --git a/pages/public_cloud/compute/public-cloud-first-steps/guide.fr-ca.md b/pages/public_cloud/compute/public-cloud-first-steps/guide.fr-ca.md
index 3d287098d72..f9572ccf48f 100644
--- a/pages/public_cloud/compute/public-cloud-first-steps/guide.fr-ca.md
+++ b/pages/public_cloud/compute/public-cloud-first-steps/guide.fr-ca.md
@@ -151,7 +151,7 @@ Pour plus d'informations, veuillez consulter nos guides dans la section [Public
Le mode privé local ne s'applique que si vous créez une instance dans une **Local Zone**. Les instances peuvent être exposées à Internet directement via IPv4/IPv6. Seules les instances d'une même Local Zone peuvent être connectées via des réseaux privés. Les Local Zones ne sont pas compatibles avec le [vRack](/links/network/vrack). Dans ce mode, DHCP fournit automatiquement des adresses IP à vos instances.
-Pour en savoir plus, consultez la [page Web des Local Zones](/links/public-cloud/local-zones).
+Pour en savoir plus, consultez la [page web des Local Zones](/links/public-cloud/local-zones).
///
@@ -217,7 +217,7 @@ Une **région** est définie comme un emplacement dans le monde composé d'un ou
**Local Zones**
-Les Local Zones sont une extension des **régions** qui rapprochent les services OVHcloud de sites spécifiques, offrant une latence réduite et des performances améliorées pour les applications. Vous pouvez trouver plus d'informations sur la [page Web des Local Zones](/links/public-cloud/local-zones) et dans la [documentation des capacités des Local Zones](/pages/public_cloud/compute/local-zones-capabilities-limitations).
+Les Local Zones sont une extension des **régions** qui rapprochent les services OVHcloud de sites spécifiques, offrant une latence réduite et des performances améliorées pour les applications. Vous pouvez trouver plus d'informations sur la [page web des Local Zones](/links/public-cloud/local-zones) et dans la [documentation des capacités des Local Zones](/pages/public_cloud/compute/local-zones-capabilities-limitations).
///
@@ -227,7 +227,7 @@ Les Local Zones sont une extension des **régions** qui rapprochent les services
Sélectionnez une [région](/links/public-cloud/regions-pci) la plus proche de vos utilisateurs ou clients. Cette option peut être limitée, selon le choix du modèle à l'**étape 4.1**. Notez que si vous sélectionnez une **Local Zone** à cette étape, des limitations de réseau s'appliqueront à l'instance (voir [Étape 3](#networking-modes)).
-Reportez-vous également aux informations de la [page Web des Local Zones](/links/public-cloud/local-zones) et de la [documentation des capacités des Local Zones](/pages/public_cloud/compute/local-zones-capabilities-limitations).
+Reportez-vous également aux informations de la [page web des Local Zones](/links/public-cloud/local-zones) et de la [documentation des capacités des Local Zones](/pages/public_cloud/compute/local-zones-capabilities-limitations).
{.thumbnail}
diff --git a/pages/public_cloud/compute/public-cloud-first-steps/guide.fr-fr.md b/pages/public_cloud/compute/public-cloud-first-steps/guide.fr-fr.md
index 93badd79cfe..f8cf8d8a6fc 100644
--- a/pages/public_cloud/compute/public-cloud-first-steps/guide.fr-fr.md
+++ b/pages/public_cloud/compute/public-cloud-first-steps/guide.fr-fr.md
@@ -151,7 +151,7 @@ Pour plus d'informations, veuillez consulter nos guides dans la section [Public
Le mode privé local ne s'applique que si vous créez une instance dans une **Local Zone**. Les instances peuvent être exposées à Internet directement via IPv4/IPv6. Seules les instances d'une même Local Zone peuvent être connectées via des réseaux privés. Les Local Zones ne sont pas compatibles avec le [vRack](/links/network/vrack). Dans ce mode, DHCP fournit automatiquement des adresses IP à vos instances.
-Pour en savoir plus, consultez la [page Web des Local Zones](/links/public-cloud/local-zones).
+Pour en savoir plus, consultez la [page web des Local Zones](/links/public-cloud/local-zones).
///
@@ -217,7 +217,7 @@ Une **région** est définie comme un emplacement dans le monde composé d'un ou
**Local Zones**
-Les Local Zones sont une extension des **régions** qui rapprochent les services OVHcloud de sites spécifiques, offrant une latence réduite et des performances améliorées pour les applications. Vous pouvez trouver plus d'informations sur la [page Web des Local Zones](/links/public-cloud/local-zones) et dans la [documentation des capacités des Local Zones](/pages/public_cloud/compute/local-zones-capabilities-limitations).
+Les Local Zones sont une extension des **régions** qui rapprochent les services OVHcloud de sites spécifiques, offrant une latence réduite et des performances améliorées pour les applications. Vous pouvez trouver plus d'informations sur la [page web des Local Zones](/links/public-cloud/local-zones) et dans la [documentation des capacités des Local Zones](/pages/public_cloud/compute/local-zones-capabilities-limitations).
///
@@ -227,7 +227,7 @@ Les Local Zones sont une extension des **régions** qui rapprochent les services
Sélectionnez une [région](/links/public-cloud/regions-pci) la plus proche de vos utilisateurs ou clients. Cette option peut être limitée, selon le choix du modèle à l'**étape 4.1**. Notez que si vous sélectionnez une **Local Zone** à cette étape, des limitations de réseau s'appliqueront à l'instance (voir [Étape 3](#networking-modes)).
-Reportez-vous également aux informations de la [page Web des Local Zones](/links/public-cloud/local-zones) et de la [documentation des capacités des Local Zones](/pages/public_cloud/compute/local-zones-capabilities-limitations).
+Reportez-vous également aux informations de la [page web des Local Zones](/links/public-cloud/local-zones) et de la [documentation des capacités des Local Zones](/pages/public_cloud/compute/local-zones-capabilities-limitations).
{.thumbnail}