#1 Global Leader in Data Resilience

Manually Moving Backup Files To or From a Scale-Out Backup Repository

KB ID: 2236
Product: Veeam Backup & Replication | 12 | 12.1 | 12.2 | 12.3
Published: 2017-02-09
Last Modified: 2024-12-18
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Veeam Cloud Service Provider Specific

Starting with Veeam Backup & Replication 12, migrating a tenant's backup files to or from a scale-out backup repository can be performed without the requirement to involve Veeam Technical Support (as was needed in previous versions).

Please carefully review: Moving Tenant Backups to Another Cloud Repository.

Purpose

This article provides information about migrating restore points between basic Backup Repositories and Scale-Out Backup Repositories (SOBR).

Solution

Modern Built-In Backup Migration

Starting with Veeam Backup & Replication 12, the ability to move backup files to or from a scale-out backup repository is now a built-in feature. For more information, review the following:

All customers using Veeam Backup & Replication 12 or newer are strongly encouraged to use the native Backup Move feature to move restore points between repositories (simple, scale-out, and object storage).

Legacy Manual Backup Migration Methods

Customers utilizing Veeam Backup & Replication version 12 or later are encouraged to utilize the integrated Backup Move feature for transferring restore points between repositories. This native functionality, in contrast to the processes outlined in this article, maintains ReFS Fast Clone capabilities and is capable of data migration from traditional storage to object storage.

The methods described below remain in this article as they are technically still viable and may be helpful for highly niche situations where the built-in capabilities might not be able to be used.

Legacy Migration Methods - Limitations and Consideration
  • Please review Limitations for Scale-Out Backup Repositories.
  • To let Veeam Backup & Replication automatically import backups during rescan of a scale-out backup repository, names of VBM files and paths to VBM files (starting from the backup repository root to VBM files, not including the root itself) must contain only allowed characters:
    • Alphanumeric characters: a-zA-Z0-9
    • Special characters: _-.+=@^
    The name of the VBM file and path to VBM files must not contain spaces.

    If a name of a VBM file or a path to a VBM file contains prohibited characters, Veeam Backup & Replication will fail to import such backup during rescan of the scale-out backup repository. To import such backup, you can replace prohibited characters with the underscore character, for example: [C:\My Repository\Backup Job\Backup Job.vbm] >> [C:\My Repository\Backup_Job\Backup_Job.vbm].
    Note: Do not rename the actual backup files (.vbk, .vib).
  • Moving backup files from one or multiple SOBR extents is viable as well. There are a few points to note:
    • Make sure to copy files from the backup chain from all extents.
    • SOBR backup chains are typically Per-Machine backup files. Simple repositories are typically per-job backup files. The chain will retain this method until an active full is run on the job to enforce the change.
    • The VBM file will exist in all extents. All VBMs for a particular backup job within a single SOBR should be identical. As a result, the target simple backup repository needs only contain one VBM.
Legacy Migration Method Scenario Examples
Move From Simple Repository to New Scale-Out Backup Repository
  1. Create simple repositories, and at least one of them should be a path where backup files to be imported are stored (e.g., if backup files are in D:\Backups\Backup_Job_1\, then create a repository referencing the path D:\Backups).
  2. Re-scan the simple repository(s) and ensure all backups are imported.
  3. Create the SOBR and add the relevant repositories as extents.
  4. During the creation process, Veeam will inform via confirmation prompt that “Jobs and backups using this extent will be automatically updated to point to the scale-out backup repository.” 
    User-added image
  5. If any jobs are not mapped to the backup files now within the SOBR, please map them according to the standard process.
Move From Simple Repository to Existing Scale-Out Backup Repository
  1. Place the backup files to be imported in a temporary path. (e.g., if backup files are in D:\Backups, either copy or move them to D:\Backups-temp. A move is usually much faster.)
  2. Create a new simple backup repository that references this path (in our example, D:\Backups-temp).
  3. Re-scan the repository, and ensure all backups are imported.
  4. You can map the pre-existing job to the backup files’ new location now, or at the end.
  5. Edit your existing SOBR and add the new temporary repository to its list of extents.
  6. Place the new temporary repository extent in Maintenance Mode.
  7. Evacuate the extent. Veeam will redistribute the backup files to other extents in the SOBR.
  8. If you did not map the original job in step 4, do so now.

If redistribution of files is not desired or necessary, you can simply copy the folder containing VBM and backup files to an existing extent. Rename both path and VBM to ensure import, and re-scan.

Move From Scale-Out Backup Repository to Simple Repository
  1. If you haven't done so yet, create a new simple backup repository.
  2. In the root folder of the new simple backup repository, create a folder with the name of the job folder on SOBR.
  3. (Optional) To avoid automatic rescans of SOBR finding the files during the move again, place the extents with the job files in Maintenance Mode.
  4. Remove the backups on the SOBR from the Backups > Disk section using the option Remove from configuration.
    (Do not click Delete from disk)
  5. Check the job folders on each Extent and move any VRB/VBK/VIB files you find to the newly created folder on the simple backup repository.
  6. Move one of the VBM files from any of the job's job folders on SOBR extents to the newly created job folder on the simple backup repository.
  7. Remove the leftover folders with the job name and VBM files from all extents of SOBR.
  8. Rescan the simple backup repository. It will import the backup into the configuration.
  9. Map the job which you want to use for this backup to the newly imported Backup.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
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
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.