Mapping an existing Veeam Agent backup chain to a Veeam Backup & Replication repository

KB ID: 2321
Product: Veeam Backup & Replication;Veeam Agent for Linux;Veeam Agent for Microsoft Windows
Version: VAW 2.0, VBR 9.5U2, VAL 1.x, 2.x
Published:
Last Modified: 2018-07-18

Challenge

You need to map an existing Veeam Agent backup chain to a Veeam Backup & Replication repository.

Cause

There are no features in Veeam Agent that would allow mapping existing backups to Veeam Backup & Replication, however it is possible to copy a local backup chain to a Veeam Backup & Replication repository and continue using it.

Solution

Here is the list of steps for mapping a local backup chain to a Veeam Backup & Replication repository.

1. Create a backup with Veeam Agent at any temporary backup destination of your choice.

If a Veeam Backup & Replication repository was used,

  • remove the existing Veeam Agent backup job from jobs (right lick > Delete)
  • remove the backup files from configuration: right click Disk (backups) > Endpoint Backups > Remove from configuration

2. Place the backup chain into the required folder.

2.1 Example for a non-cloud repository

Backup files reside in C:\VeeamBackup\Backup Job 1 and need to be moved to a Veeam Backup & Replication repository into the following folder: C:\Backup.

Under C:\Backup you will need to create a folder named after the account that is used to access the repository. In this example, the account is DOMAIN1\user1, so the folder name would be DOMAIN1_user1.

The complete path to the backup files would be C:\Backup\DOMAIN1_user1\Backup Job 1

2.2 Example for a cloud repository

The backup files reside in C:\VeeamBackup\Backup Job 1 and need to be moved to a cloud Veeam repository into following folder: C:\Backup.

Under C:\Backup you will need to create a folder named after the tenant account that is used to access the repository. If the account name is Tenant2, the complete path to the backup files would be C:\Backup\Tenant2\Backup Job 1

If a subtenant is used with the account name Subtenant3, the path will be C:\Backup\Tenant2\users\Subtenant3\Backup Job 1

3. Rescan the Veeam Backup & Replication repository. Here is a brief guide on repository rescan. 
Note: For backups that you are mapping to cloud, rescan the repository hosting the tenant backups on the provider side.

4. The Veeam Agent backup should appear under Disk > Imported.
Note: When a backup chain is mapped to cloud, it will not be displayed under Disk > Imported.

5. Point the Veeam Agent job to the required Veeam Backup & Replication repository. Do not run it immediately, just close the wizard after making the changes.

6. On the Veeam Backup & Replication machine, the backup should be moved from the Imported section to Backup > Disk. Make sure that backups are located in Backups > Disks (not Disk (imported)).

7. Run the Veeam Agent backup job. It should continue the imported backup chain.

Note: The described solution works for Veeam Backup & Replication repository and Veeam Cloud Connect repository.

More Information

NOTES: 1. If local backup encryption was enabled during the initial job configuration, additional steps may be needed to complete the mapping.

For non-cloud repositories
Importing a backup chain to a Veeam Backup and Replication server puts the imported chain in the Disk (encrypted) tab. Before the backup chain can be continued, you will need to right click on the encrypted backup chain and enter the password.

For cloud repositories
In some cases it may be necessary to enter the password in order to continue the backup chain. If entering the password is required, you will be prompted to do so when the job starts.

2. If Backup & Replication repository’s encryption is enabled at the repository, you should decrypt it using password specification (Right click > Specify password) to finish the import procedure.

3. Unfortunately, it is not possible to seed a local Veeam Agent backup to a Cloud Scale-Out repository. You can either use a simple Cloud repository to seed the backup instead or use a SOBR repository without an initial seeding.

If you have any questions, open a case with Veeam Support.

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.

OK

Rate the quality of this KB article: 
4.8 out of 5 based on 18 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Request new content