Challenge
One of the extents is filling up faster than the others and you want to balance them, but only certain backups/tenants need to be moved to another extent.
This article applies to Backup, Backup copy, Agent backups, Agent backups with subtenant accounts.
NOTE: This article must not be applied for backup migration from a simple repository or for backup migration between extents of different Scale-out backup repositories. For such cases, refer to this article: https://www.veeam.com/kb2236
Before you proceed, check REFS Fast Clone limitations. For more information, see this article:
https://helpcenter.veeam.com/docs/backup/vsphere/backup_repository_block_cloning.html?ver=95u4
Cause
- 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.
Solution
Local SOBR:
1. Disable 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.
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.
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.
Original folder: E:\VeeamBackup\Tenant1\Backup_Job_1\Backup_Job_1.vbm
New folder: C:\Backups\Tenant1\Backup_Job_1\Backup_Job_1.vbm
4. Enable the tenant/job.