Manually moving backup files between Scale-Out Backup Repository extents

• An extent is filled up because of the “Data locality” SOBR placement policy.
• An extent is filled up because of the other extent “Evacuation”.
• A new extent was added to SOBR and a part of the backup needs to be migrated there.

Local SOBR:

1. Disable the job that needs to be migrated.
2. Migrate the whole backup chain including .vbm file to another extent.

Example:
Repository name is SOBR, there are 2 extents, backups need to be migrated from “SOBR Extent 1” to “SOBR Extent 2”.

Original folder: E:\VeeamBackup\Backup_Job_1\Backup_Job_1.vbm
New folder: C:\Backups\Backup_Job_1\Backup_Job_1.vbm

3. Navigate to Veeam Console -> Backup infrastructure-> Scale-out Repositories -> Right-click on the affected SOBR -> Rescan.

4. Enable/run the job.

Cloud Connect SOBR:

1. Disable the tenant or the job that needs to be migrated.
2. Migrate the whole backup chain including .vbm file to another extent.
    Backups need to be placed in the same folder starting from repository root.

3. Navigate to Veeam Cloud Connect Server -> Veeam Backup and Replication Console -> Backup infrastructure-> Scale-out Repositories -> Right-click on the affected SOBR -> Rescan.
4. Enable the tenant/job.

For Cloud Connect environments, note that there is a PowerShell commandlet available which can be used to simplify the migration: 
https://helpcenter.veeam.com/docs/backup/powershell/start-vbrcloudtenantbackupevacuation.html