Skip to content

Commit 9910d9d

Browse files
Y0CossY0Coss
authored
Merge pull request #7778 from ovh/YC-Fixes-20250423
Veeam encrypt backup jobs - Format fix
2 parents fa6b134 + d65b819 commit 9910d9d

File tree

15 files changed

+285
-285
lines changed

15 files changed

+285
-285
lines changed

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

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -26,28 +26,28 @@ You can create your access certificate in OKMS using either the [OVHcloud API](
2626

2727
1. Generate the private key using the API (no CSR):
2828

29-
> [!api]
30-
>
31-
> @api {v1} /okms POST / /okms/resource/{okmsId}/credential
29+
> [!api]
30+
>
31+
> @api {v1} /okms POST / /okms/resource/{okmsId}/credential
3232
3333
2. Retrieve the certificate using a GET request:
3434

35-
> [!api]
36-
>
37-
> @api {v1} /okms GET /okms/resource/{okmsId}/credential
35+
> [!api]
36+
>
37+
> @api {v1} /okms GET /okms/resource/{okmsId}/credential
3838
39-
> [!primary]
40-
> This method is equivalent to selecting `I don't have a private key`{.action} in the [OVHcloud Control Panel](/links/manager) interface.
41-
> You may also submit a CSR if you already have your own private key.
39+
> [!primary]
40+
> This method is equivalent to selecting `I don't have a private key`{.action} in the [OVHcloud Control Panel](/links/manager) interface.
41+
> You may also submit a CSR if you already have your own private key.
4242
4343
3. Download the private key.
4444

4545
4. Download the certificate.
4646

47-
> [!primary]
48-
> The downloaded private key is used to generate the `.pfx` file in the next step.
49-
> You don't need to import it manually into Veeam, but it is required to convert the certificate into a compatible format.
50-
> Make sure to store it securely.
47+
> [!primary]
48+
> The downloaded private key is used to generate the `.pfx` file in the next step.
49+
> You don't need to import it manually into Veeam, but it is required to convert the certificate into a compatible format.
50+
> Make sure to store it securely.
5151
5252
#### Option 2: Using the [OVHcloud Control Panel](/links/manager)
5353

@@ -69,17 +69,17 @@ You can create your access certificate in OKMS using either the [OVHcloud API](
6969

7070
![Generate Access Certificate - No Private Key](images/veeam_okms_2.png){.thumbnail}
7171

72-
> [!primary]
73-
> This is the same as generating a certificate without a CSR, like with the API.
74-
> You can also choose `I already have a private key` to generate a certificate using your own CSR.
72+
> [!primary]
73+
> This is the same as generating a certificate without a CSR, like with the API.
74+
> You can also choose `I already have a private key` to generate a certificate using your own CSR.
7575
7676
6. Add user IDs to the certificate:
7777
- Click `Add user IDs`{.action}
7878
- Select the authorized users
7979
- Confirm to associate the certificate
8080

81-
> [!primary]
82-
> This step is required for the certificate to work with Veeam.
81+
> [!primary]
82+
> This step is required for the certificate to work with Veeam.
8383
8484
7. Download the private key and the certificate.
8585

@@ -148,4 +148,4 @@ If you need training or technical assistance to implement our solutions, contact
148148

149149
Ask questions, share feedback, and interact directly with the Hosted Private Cloud team on our [Discord](https://discord.gg/ovhcloud) channel.
150150

151-
Join our [community of users](/links/community).
151+
Join our [community of users](/links/community).

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

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -26,28 +26,28 @@ You can create your access certificate in OKMS using either the [OVHcloud API](
2626

2727
1. Generate the private key using the API (no CSR):
2828

29-
> [!api]
30-
>
31-
> @api {v1} /okms POST / /okms/resource/{okmsId}/credential
29+
> [!api]
30+
>
31+
> @api {v1} /okms POST / /okms/resource/{okmsId}/credential
3232
3333
2. Retrieve the certificate using a GET request:
3434

35-
> [!api]
36-
>
37-
> @api {v1} /okms GET /okms/resource/{okmsId}/credential
35+
> [!api]
36+
>
37+
> @api {v1} /okms GET /okms/resource/{okmsId}/credential
3838
39-
> [!primary]
40-
> This method is equivalent to selecting `I don't have a private key`{.action} in the [OVHcloud Control Panel](/links/manager) interface.
41-
> You may also submit a CSR if you already have your own private key.
39+
> [!primary]
40+
> This method is equivalent to selecting `I don't have a private key`{.action} in the [OVHcloud Control Panel](/links/manager) interface.
41+
> You may also submit a CSR if you already have your own private key.
4242
4343
3. Download the private key.
4444

4545
4. Download the certificate.
4646

47-
> [!primary]
48-
> The downloaded private key is used to generate the `.pfx` file in the next step.
49-
> You don't need to import it manually into Veeam, but it is required to convert the certificate into a compatible format.
50-
> Make sure to store it securely.
47+
> [!primary]
48+
> The downloaded private key is used to generate the `.pfx` file in the next step.
49+
> You don't need to import it manually into Veeam, but it is required to convert the certificate into a compatible format.
50+
> Make sure to store it securely.
5151
5252
#### Option 2: Using the [OVHcloud Control Panel](/links/manager)
5353

@@ -69,17 +69,17 @@ You can create your access certificate in OKMS using either the [OVHcloud API](
6969

7070
![Generate Access Certificate - No Private Key](images/veeam_okms_2.png){.thumbnail}
7171

72-
> [!primary]
73-
> This is the same as generating a certificate without a CSR, like with the API.
74-
> You can also choose `I already have a private key` to generate a certificate using your own CSR.
72+
> [!primary]
73+
> This is the same as generating a certificate without a CSR, like with the API.
74+
> You can also choose `I already have a private key` to generate a certificate using your own CSR.
7575
7676
6. Add user IDs to the certificate:
7777
- Click `Add user IDs`{.action}
7878
- Select the authorized users
7979
- Confirm to associate the certificate
8080

81-
> [!primary]
82-
> This step is required for the certificate to work with Veeam.
81+
> [!primary]
82+
> This step is required for the certificate to work with Veeam.
8383
8484
7. Download the private key and the certificate.
8585

@@ -148,4 +148,4 @@ If you need training or technical assistance to implement our solutions, contact
148148

149149
Ask questions, share feedback, and interact directly with the Hosted Private Cloud team on our [Discord](https://discord.gg/ovhcloud) channel.
150150

151-
Join our [community of users](/links/community).
151+
Join our [community of users](/links/community).

‎pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/veeam_encrypt_backup_job_with_okms/guide.en-au.md

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -26,28 +26,28 @@ You can create your access certificate in OKMS using either the [OVHcloud API](
2626

2727
1. Generate the private key using the API (no CSR):
2828

29-
> [!api]
30-
>
31-
> @api {v1} /okms POST / /okms/resource/{okmsId}/credential
29+
> [!api]
30+
>
31+
> @api {v1} /okms POST / /okms/resource/{okmsId}/credential
3232
3333
2. Retrieve the certificate using a GET request:
3434

35-
> [!api]
36-
>
37-
> @api {v1} /okms GET /okms/resource/{okmsId}/credential
35+
> [!api]
36+
>
37+
> @api {v1} /okms GET /okms/resource/{okmsId}/credential
3838
39-
> [!primary]
40-
> This method is equivalent to selecting `I don't have a private key`{.action} in the [OVHcloud Control Panel](/links/manager) interface.
41-
> You may also submit a CSR if you already have your own private key.
39+
> [!primary]
40+
> This method is equivalent to selecting `I don't have a private key`{.action} in the [OVHcloud Control Panel](/links/manager) interface.
41+
> You may also submit a CSR if you already have your own private key.
4242
4343
3. Download the private key.
4444

4545
4. Download the certificate.
4646

47-
> [!primary]
48-
> The downloaded private key is used to generate the `.pfx` file in the next step.
49-
> You don't need to import it manually into Veeam, but it is required to convert the certificate into a compatible format.
50-
> Make sure to store it securely.
47+
> [!primary]
48+
> The downloaded private key is used to generate the `.pfx` file in the next step.
49+
> You don't need to import it manually into Veeam, but it is required to convert the certificate into a compatible format.
50+
> Make sure to store it securely.
5151
5252
#### Option 2: Using the [OVHcloud Control Panel](/links/manager)
5353

@@ -69,17 +69,17 @@ You can create your access certificate in OKMS using either the [OVHcloud API](
6969

7070
![Generate Access Certificate - No Private Key](images/veeam_okms_2.png){.thumbnail}
7171

72-
> [!primary]
73-
> This is the same as generating a certificate without a CSR, like with the API.
74-
> You can also choose `I already have a private key` to generate a certificate using your own CSR.
72+
> [!primary]
73+
> This is the same as generating a certificate without a CSR, like with the API.
74+
> You can also choose `I already have a private key` to generate a certificate using your own CSR.
7575
7676
6. Add user IDs to the certificate:
7777
- Click `Add user IDs`{.action}
7878
- Select the authorized users
7979
- Confirm to associate the certificate
8080

81-
> [!primary]
82-
> This step is required for the certificate to work with Veeam.
81+
> [!primary]
82+
> This step is required for the certificate to work with Veeam.
8383
8484
7. Download the private key and the certificate.
8585

@@ -148,4 +148,4 @@ If you need training or technical assistance to implement our solutions, contact
148148

149149
Ask questions, share feedback, and interact directly with the Hosted Private Cloud team on our [Discord](https://discord.gg/ovhcloud) channel.
150150

151-
Join our [community of users](/links/community).
151+
Join our [community of users](/links/community).

‎pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/veeam_encrypt_backup_job_with_okms/guide.en-ca.md

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -26,28 +26,28 @@ You can create your access certificate in OKMS using either the [OVHcloud API](
2626

2727
1. Generate the private key using the API (no CSR):
2828

29-
> [!api]
30-
>
31-
> @api {v1} /okms POST / /okms/resource/{okmsId}/credential
29+
> [!api]
30+
>
31+
> @api {v1} /okms POST / /okms/resource/{okmsId}/credential
3232
3333
2. Retrieve the certificate using a GET request:
3434

35-
> [!api]
36-
>
37-
> @api {v1} /okms GET /okms/resource/{okmsId}/credential
35+
> [!api]
36+
>
37+
> @api {v1} /okms GET /okms/resource/{okmsId}/credential
3838
39-
> [!primary]
40-
> This method is equivalent to selecting `I don't have a private key`{.action} in the [OVHcloud Control Panel](/links/manager) interface.
41-
> You may also submit a CSR if you already have your own private key.
39+
> [!primary]
40+
> This method is equivalent to selecting `I don't have a private key`{.action} in the [OVHcloud Control Panel](/links/manager) interface.
41+
> You may also submit a CSR if you already have your own private key.
4242
4343
3. Download the private key.
4444

4545
4. Download the certificate.
4646

47-
> [!primary]
48-
> The downloaded private key is used to generate the `.pfx` file in the next step.
49-
> You don't need to import it manually into Veeam, but it is required to convert the certificate into a compatible format.
50-
> Make sure to store it securely.
47+
> [!primary]
48+
> The downloaded private key is used to generate the `.pfx` file in the next step.
49+
> You don't need to import it manually into Veeam, but it is required to convert the certificate into a compatible format.
50+
> Make sure to store it securely.
5151
5252
#### Option 2: Using the [OVHcloud Control Panel](/links/manager)
5353

@@ -69,17 +69,17 @@ You can create your access certificate in OKMS using either the [OVHcloud API](
6969

7070
![Generate Access Certificate - No Private Key](images/veeam_okms_2.png){.thumbnail}
7171

72-
> [!primary]
73-
> This is the same as generating a certificate without a CSR, like with the API.
74-
> You can also choose `I already have a private key` to generate a certificate using your own CSR.
72+
> [!primary]
73+
> This is the same as generating a certificate without a CSR, like with the API.
74+
> You can also choose `I already have a private key` to generate a certificate using your own CSR.
7575
7676
6. Add user IDs to the certificate:
7777
- Click `Add user IDs`{.action}
7878
- Select the authorized users
7979
- Confirm to associate the certificate
8080

81-
> [!primary]
82-
> This step is required for the certificate to work with Veeam.
81+
> [!primary]
82+
> This step is required for the certificate to work with Veeam.
8383
8484
7. Download the private key and the certificate.
8585

@@ -148,4 +148,4 @@ If you need training or technical assistance to implement our solutions, contact
148148

149149
Ask questions, share feedback, and interact directly with the Hosted Private Cloud team on our [Discord](https://discord.gg/ovhcloud) channel.
150150

151-
Join our [community of users](/links/community).
151+
Join our [community of users](/links/community).

‎pages/hosted_private_cloud/hosted_private_cloud_powered_by_vmware/veeam_encrypt_backup_job_with_okms/guide.en-gb.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -26,28 +26,28 @@ You can create your access certificate in OKMS using either the [OVHcloud API](
2626

2727
1. Generate the private key using the API (no CSR):
2828

29-
> [!api]
30-
>
31-
> @api {v1} /okms POST / /okms/resource/{okmsId}/credential
29+
> [!api]
30+
>
31+
> @api {v1} /okms POST / /okms/resource/{okmsId}/credential
3232
3333
2. Retrieve the certificate using a GET request:
3434

35-
> [!api]
36-
>
37-
> @api {v1} /okms GET /okms/resource/{okmsId}/credential
35+
> [!api]
36+
>
37+
> @api {v1} /okms GET /okms/resource/{okmsId}/credential
3838
39-
> [!primary]
40-
> This method is equivalent to selecting `I don't have a private key`{.action} in the [OVHcloud Control Panel](/links/manager) interface.
41-
> You may also submit a CSR if you already have your own private key.
39+
> [!primary]
40+
> This method is equivalent to selecting `I don't have a private key`{.action} in the [OVHcloud Control Panel](/links/manager) interface.
41+
> You may also submit a CSR if you already have your own private key.
4242
4343
3. Download the private key.
4444

4545
4. Download the certificate.
4646

47-
> [!primary]
48-
> The downloaded private key is used to generate the `.pfx` file in the next step.
49-
> You don't need to import it manually into Veeam, but it is required to convert the certificate into a compatible format.
50-
> Make sure to store it securely.
47+
> [!primary]
48+
> The downloaded private key is used to generate the `.pfx` file in the next step.
49+
> You don't need to import it manually into Veeam, but it is required to convert the certificate into a compatible format.
50+
> Make sure to store it securely.
5151
5252
#### Option 2: Using the [OVHcloud Control Panel](/links/manager)
5353

@@ -69,17 +69,17 @@ You can create your access certificate in OKMS using either the [OVHcloud API](
6969

7070
![Generate Access Certificate - No Private Key](images/veeam_okms_2.png){.thumbnail}
7171

72-
> [!primary]
73-
> This is the same as generating a certificate without a CSR, like with the API.
74-
> You can also choose `I already have a private key` to generate a certificate using your own CSR.
72+
> [!primary]
73+
> This is the same as generating a certificate without a CSR, like with the API.
74+
> You can also choose `I already have a private key` to generate a certificate using your own CSR.
7575
7676
6. Add user IDs to the certificate:
7777
- Click `Add user IDs`{.action}
7878
- Select the authorized users
7979
- Confirm to associate the certificate
8080

81-
> [!primary]
82-
> This step is required for the certificate to work with Veeam.
81+
> [!primary]
82+
> This step is required for the certificate to work with Veeam.
8383
8484
7. Download the private key and the certificate.
8585

0 commit comments

Comments
 (0)