Operational Defect Database

BugZero found this defect 2628 days ago.

Veeam | kb2236

Manually moving backup files to or from a Scale-Out Backup Repository

Last update date:

6/21/2023

Affected products:

Veeam Backup & Replication

Affected releases:

10

Fixed releases:

No fixed releases provided.

Description:

Purpose

You have backup files on a standard repository that you wish to move to a Scale-Out Backup Repository (SOBR).

Cause

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.

Solution

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. Create the SOBR and add the relevant repositories as extents. 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.”  If any jobs are not mapped to the backup files now within the SOBR, map them per the standard process.

More Information

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.

Additional Resources / Links

Share:

BugZero® Risk Score

What's this?

Coming soon

Status

Solved

cost-cta-background

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

VMware

bug?

Search:

...