This article provides a method to change the repository where backup files are stored.
For documentation on changing the backup location of Veeam Agent jobs not directly controlled by Veeam Backup & Replication, but targeting a Veeam Backup & Replication server's repository, refer to vee.am/kb2321
If you have attempted to manually import the backup, prior to performing the steps outline in this article, you must first "Remove from configuration" any backups that were manually imported. These will be identifiable in the Backups > Disk (Imported) section. They will be listed with the suffix _imported and will have no repository listed in the Repository column.
There are two primary situations and respective methods that this KB article documents.
Below is a summary of both methods.
You have physically moved the backup files to new storage and want to map the old jobs to the backup chain in the new location.
You are seeding a job or mapping a job to a backup chain in a new location. This method does not require that the job doing the mapping be the same as the job that initially created the restore points.
If the steps in "Method A" continue to lead to "Move all backups files to the new backup repository first" error, and you have made sure absolutely all the backup files from the initial repository are in the new repository. You may need to use the method explained in "Method B" below to forcefully map the job.
If "Method B" also does not allow you to map correctly, please contact Veeam Support.
To map the existing backup files to a new or different job, follow these steps:
If you are attempting to seed failover cluster Veeam Agent for Microsoft Windows job’s restore points please follow the actions below (it has a bit different workflow due to the product design):