Step 8. Configure Repository Settings

The Repositories step of the wizard, a list of all standard and archive repositories already configured on the selected backup appliance will be displayed. After you complete the wizard, Veeam Backup & Replication will automatically add these repositories to the backup infrastructure.

You can specify the following configuration settings for each repository whose restore points you want to use to recover backed-up data:

Note

The following procedure applies only to standard repositories. For archive repositories, there is no possibility to specify any configuration settings.

  1. In the Repositories list, select the necessary standard repository and click Edit.
  2. In the Repository Settings window:
  1. From the Credentials drop-down list, select credentials of a Microsoft Azure storage account where the target blob container resides. Veeam Backup & Replication will use these credentials to access the repository. For more information on supported types of storage accounts, see the Veeam Backup & Replication User Guide, section Microsoft Azure Storage Accounts.

For credentials to be displayed in the list of available credentials, they must be added to the Cloud Credentials Manager.

If you have not added the credentials to the Cloud Credentials Manager beforehand, you can do it without closing the wizard. To do that, click either the Manage cloud accounts link or the Add button. Then, in the Credentials window, specify the storage account name and the access key generated for the account.

Note

If you do not specify credentials of the Microsoft Azure storage account for a standard repository, you will only be able to use the Veeam Backup & Replication console to perform entire VM restore and SQL database restore from backups stored in this repository. Moreover, encrypted backups will be displayed as non-encrypted ones, and information on the repository displayed in the Backup Infrastructure view under the External Repositories node will not include statistics on the amount of storage space that is currently consumed by restore points created by Veeam Backup for Microsoft Azure.

  1. From the Use the following gateway server for the Internet access drop-down list, select a gateway server that will be used to provide access to the repository.

For a gateway server to be displayed in the Use the following gateway server for the Internet access drop-down list, it must be added to the backup infrastructure. For more information on gateway servers, see Gateway Servers.

  1. If encryption is enabled for the repository, the following scenarios may apply:

For a password to be displayed in the Use the following password for encrypted backups drop-down list, it must be added to the backup infrastructure as described in the Veeam Backup & Replication User Guide, section Creating Passwords.

If you have not added the necessary password beforehand, you can do it without closing the Repository Settings window. To add the password, click either the Manage cloud accounts link or the Add button and specify a hint and the password in the Password window.

Note

If you do not specify a password for a standard repository with encryption enabled, you will have to decrypt data stored in this repository manually as described in section Managing Backed-Up Data Using Console.

  • If data in the standard repository is encrypted with an Azure Key Vault cryptographic key, Veeam Backup & Replication will show the used key in the Perform Azure encryption with the following key drop-down list, but will not allow you change it.

After you finish working with the wizard, all the added repositories will be displayed in the Backup Infrastructure view under the External Repositories node.

Note

If some of the repositories are already added to the backup infrastructure of another backup server, you will be prompted to claim the ownership of these repositories. To learn how to claim the ownership, see the Veeam Backup & Replication User Guide, section Ownership.

Connect appliance - Repositories

Related Topics

Managing Backed-Up Data Using Console