https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IzMTAwIiwiaGFzaCI6ImVkZjlmZjBhLTU4MjMtNGEzMy1iNDI1LWQzZWZhYmU5NGNmMyJ9
1-800-691-1991 | 9am - 8pm ET
EN

Manually moving backup files between Scale-Out Backup Repository extents

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.
Example:
Repository name is SOBR, there are 2 extents, backups need to be migrated from “SOBR Extent 1” to “SOBR Extent 2”.
User-added image
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.
User-added image
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.
Example:
Original folder: E:\VeeamBackup\Tenant1\Backup_Job_1\Backup_Job_1.vbm
New folder: C:\Backups\Tenant1\Backup_Job_1\Backup_Job_1.vbm
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.

 
KB ID:
3100
Product:
Veeam Backup & Replication, Veeam Cloud Connect
Version:
9.5.4.2866
Published:
2020-02-11
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
3.5 out of 5 based on 3 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.