External Repositories

An external repository is a read-only repository storing backups created by Veeam Backup for AWS, Veeam Backup for Google Cloud and Veeam Backup for Microsoft Azure. Once you connect to an external repository, you can use Veeam Backup & Replication to copy, import and restore backups of cloud VMs from external repositories to the cloud or on-premises repositories. This way, you can migrate workloads between cloud, on-premises and virtual infrastructures.

Veeam Backup & Replication supports the following types of external repositories:

Amazon S3 (with Standard storage class assigned)
Azure Blob (Hot and Cool access tier)
Google Cloud (with Standard storage class assigned)
Veeam Data Cloud Vault for AWS
Veeam Data Cloud Vault for Azure

Deployment

To start working with backups created by Veeam Backup for AWS, Veeam Backup for Google Cloud and Veeam Backup for Microsoft Azure, you must connect to a repository that contains backups of Amazon EC2 instances, Azure VMs or Google Cloud VMs and add it to the Veeam Backup & Replication infrastructure as an external repository. For more information, see Connecting to External Repositories.

Note

This section is about connecting to an existing external repository. To create a new external repository to be used as a primary backup target for Veeam Backup for AWS, Veeam Backup for Google Cloud and Veeam Backup for Microsoft Azure, you must use a different wizard. For more information, see the Managing Backup Repositories section for Amazon Web Services, Google Cloud and Microsoft Azure workloads.

Usage Scenarios

You can perform the following operations:

Note

Consider the following:

During the process of copying backups, or restore to Amazon EC2 or Microsoft Azure, data of EC2 instances and Azure VMs may migrate from one geographic location to another. In this case, Veeam Backup & Replication displays a warning and stores a record about data migration to job or task session details. For more information, see Locations.
You cannot use an external repository as a target for backup or backup copy jobs.
If your Azure Blob repository is encrypted using an Azure Key Vault key, the gateway server associated with this repository must have a direct connection to the following resources: management.azure.com, login.windows.net, and login.microsoftonline.com. HTTP/HTTPS proxies are not supported.

In This Section