To migrate Veeam Backup Files from one storage to another, you need to switch between repositories when old and new repositories contain the same backup files for the job (VBM, VBK, VIB, VRB). This article shows how to migrate Veeam Backup Files from one storage to another.
- Disable the backup job(s) planned to be moved.
2. Create a new repository for the new location where backup files will be located.
3. Manually move the backup files to the new repository path. You must include the metadata file (.vbm), full backup files (.vbk), and any needed incremental files (.vib or .vrb). In our case, we use robocopy to copy all backup files to the new storage. You can map both drives and then copy/past.
Note:
It is recommended to move all backup files, but you may omit incremental files if needed. However, if you decide not to move/copy all backup files to the new storage, you will need to use the “Forget Missing Restore Points” function to clear any references to backup files that were not moved/copied after the final step.
There will be folders created inside the directory/path for job names. If your repository path is set as E:\Backups, Job A will go to E:\Backups\Job A.
4. Rescan the new repository.
- If the backup files are not encrypted, skip this step.
If the backup files are encrypted, the encrypted backup will appear under the Backups > Disk (encrypted) node in the inventory pane. In the working area, select the imported backup and click Specify Password on the ribbon or right-click the backup and select Specify password. More InformationThis is also relevant for encrypted Veeam Agent backups. - Observe that after the Rescan has been completed, there will be duplicate entries for the backup files. One is associated with the old Repository under Backups > Disk, and the other is associated with the new repository under Backups > Disk (Imported).
7. Remove old repository from the configuration by going to Backup>Disk. Right click on the old repository and click on Remove from configuration.
8. Edit the Backup or Backup Copy Job, and go to the Storage or Target tab, and from the drop-down menu, select the new repository.
9. Map to the new repository
10. Press Next through the rest of the pages of the wizard to finalize the setting. If no error occurs, and the job now lists the new repository in its Repository column, the mapping has been completed.
Note: If you encounter the following error: “Move all backup files to the new backup repository first”, some restore points the software was expecting to find were not found in the new repository. Cancel out of the job configuration and check both the old repository location and the new location to verify that all restore points have been moved. Then return to step 3 again.
9. Verify migration by checking under Backups > Disk to see that the Job’s backup files listed there are now associated with the new repository.
Please view this step by step video:
