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).
You have backup files on a standard repository that you wish to move to a Scale-Out Backup Repository (SOBR).
Scale-Out Backup Repositories have special considerations for how backup files and metadata are distributed. Thus, simply copying files to one extent may be insufficient for a rescan of the repository to detect them properly and import them.
If you have not yet created a SOBR:
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).
Re-scan the simple repository or repositories, and ensure all backups are imported.
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.
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
Your feedback has been received and will be reviewed.