Operational Defect Database

BugZero found this defect 4090 days ago.

Veeam | kb1729

How to Move Veeam Backup & Replication Backup Files

Last update date:


Affected products:

Veeam Backup & Replication

Affected releases:


Fixed releases:

No fixed releases provided.



This article documents two methods for changing 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


Limitations and Considerations Customers are strongly encouraged to use the built-in Move Backup function. The legacy method documented in this KB article has the following limitations, which are not present with the built-in Move Backup function (explained in italics for each entry below). Backup files manually moved to a Fast Clone capable repository (ReFS or XFS) will not be able to utilize Fast Clone until a new Active Full is created.The built-in Backup Move function, on the other hand, has technology that is able to migrate backup files allowing Fast Clone to function with migrated backup files. If synthetic fulls that were created using Fast Clone are moved using the method documented in this article, they will be inflated to their full size on the destination storage when they are manually moved.Conversely, the integrated Backup Move function is able to preserve the space savings of fast clone created synthetic fulls when used to move backup files between Fast Clone compatible repositories. The manual method documented in this article should not be used to move backup files to or from an Immutable Hardened Linux Repository.Whereas, the built-in Backup Move function is capable of handling the intricacies of managing the immutable state of the files on the source or destination Immutable Linux Repository, allow it to be used to migrate to or from an Immutable Hardened Linux Repository.

Method A: Same Job, New Backup location

Methodology Note This method uses a feature built-in to Veeam Backup & Replication that seamlessly switches between repositories when old and new repositories contain the same backup files for the job (VBM, VBK, VIB, VRB). When the new repository is selected within the job, Veeam Backup & Replication will check if the backup files in the selected repository match the existing repository. If matching files are found in the new repository, the job will auto-map to backup files in the new repository.

Method B: New Job, New Backup location

To map the existing backup files to a new or different job, follow these steps: Under Backups > Disk, right click the job you are changing repository for, and select Remove from Configuration.   If you are mapping the backup set from one job to another, but the backup location will stay the same, skip this step. If you are moving the backup files to a new location create a new repository for the new location where backup files are located. Rescan the repository where the backup files are located.   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 Information This is also relevant for encrypted Veeam Agent backups. Edit the Backup\Backup Copy Job. Go to the Storage\Target tab, and from the drop-down menu, select the repository where the backup files you wish to map are located.   Click Map Backup and select the existing backup chain

More Information

If you are attempting to manually seed a backup copy job, please see the following KB: https://www.veeam.com/kb1856

Additional Resources / Links


BugZero® Risk Score

What's this?

Coming soon




Do you know how much operational outages are costing you?

Understand the cost to your business and how BugZero can help you reduce those costs.

Have you ever...

had your data corrupted from a