1-800-691-1991 | 9am - 8pm ET
EN

How to Move Veeam Backup & Replication Backup Files

KB ID: 1729
Product: Veeam Backup & Replication 11, Veeam Backup & Replication 10, Veeam Backup & Replication 9.5, Veeam Backup & Replication 9.0, Veeam Backup & Replication 8.0
Published: 2013-02-08
Last Modified: 2021-07-01
Languages: DE | IT | ES

Purpose

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

 

Solution

Manually Importing

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.

User-added image

There are two primary situations and respective methods that this KB article documents.
Below is a summary of both methods.

Method A:
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.

Method B:
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.

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.
  1. Disable the backup job/jobs which are going to be moved. This will prevent additional restore points being created during the repository transition. Disabling the job/jobs will also stop any SQL Transaction Log backups as those running during the transition will cause the final step to fail.
  2. In [Backup Infrastructure] > [Backup Repositories], 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).

    Note:

    • It is recommended to move all backup files, but you can omit incremental files if needed. If you decide to not 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. Also keep in mind that 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.

    User-added image

  5. 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.
  6. Edit the Backup\Backup Copy Job. Go to the Storage\Target tab, and from the drop-down menu, select the new repository.

    User-added image

  7. Press Finish to finalize the setting. If you 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.



Persistent "Move all backups files to the new backup repository first" Error

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.

Method B: New Job, New Backup location

To map the existing backup files to a new or different job, follow these steps:

  1. Under Backups > Disk, right click the job you are changing repository for, and select Remove from Configuration.

    User-added image

  2. 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.
  3. Rescan the repository where the backup files are located.

    User-added image

  4. 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.
  5. 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.

    User-added image

  6. Click Map Backup and select the existing backup chain

    User-added image

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):

  1. Clone the source cluster job
  2. Remove the source job (it will also remove from configuration its points; not from the disk but from Veeam config only)
  3. Move the source backup folder to a new backup folder;
  4. Rescan the new repository to import the moved files
  5. Change the cloned backup job to the new repository and map the imported points there

More information

If you are attempting to manually seed a backup copy job, please see the following KB: https://www.veeam.com/kb1856
 
KB ID: 1729
Product: Veeam Backup & Replication 11, Veeam Backup & Replication 10, Veeam Backup & Replication 9.5, Veeam Backup & Replication 9.0, Veeam Backup & Replication 8.0
Published: 2013-02-08
Last Modified: 2021-07-01
Languages: DE | IT | ES

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please try again later.