Validating Backup Repositories
This section explains how to check if the parameters you want to use to add a backup repository satisfy Veeam Backup for Microsoft Azure validation criteria.
Request
POST https://<hostname>/api/v1/repositories/settings/validate |
Request Headers
The request header must contain an authorization token of the current session.
Request Parameters
None.
Request Body
Property | Type | Description |
name | string | Checks the name of the backup repository. |
description | string | Checks the description of the backup repository. |
enableEncryption | string | Checks is it is possible to /disables encryption. |
password | string | Checks the password to be used to encrypt data. |
hint | string | Checks the password hint. |
azureStorageAccountId | string | Checks the identification number of the Azure store account. |
azureStorageFolder | string | Checks the folder to be used to keep backups. |
azureStorageContainer | string | Checks the Azure container. |
azureConnectionId | string | Checks the connection identification number. |
Request Example
Request: POST https://<hostname>/api/v1/repositories/settings/validate
Request Header: Authorization: Bearer <Access-Token>
Request Body: { "name":"Backup Repository 2", "description":"", "enableEncryption":true, "password":"!@#!@#!@#", "hint":"Hint", "azureStorageAccountId":"6s9rdnmvdsnmebudp49abg8gg44k3t4huhka9anrca1smd9u8wwo", "azureStorageFolder":"OSRv3", "azureStorageContainer":"container3", "azureConnectionId":9 } |
Response
The server returns the following response to the client.
Response Codes
A successfully completed operation returns a response code 200 (OK).
Response Headers
The response to this request contains the following headers. The response may also include additional standard HTTPS headers.
Header | Description |
Content-length | The length of the response body. |
Content-type | The media type and syntax of the response body message: application/json; charset=utf-8 |
Response Examples
Response: 200 OK
Response Body: { "success": true, "message": "" } |