How to Migrate Veeam Agent Backup Files to Cloud Connect Repository

Move a Veeam Agent backup that is managed by the Veeam Service Provider Console to a Scale-Out Backup Repository (SOBR) on the provider side.
 

This example is based on the following scenario information; please adjust accordingly for your situation:

• The initial Veeam Agent backup job name was created using VSPC.
• The initial Veeam Agent backup job is named: BackupJob1
• The initial Veeam Agent backup job created restore points on local storage in the folder: C:\VeeamBackup\BackupJob1\
• The Veeam Cloud Connect repository stores backup files in the folder: D:\TenantBackups\
• Cloud resources are exposed to a tenant named: Tenant1
• (Optional) Tenant1 provided access to the cloud repository to a subtenant named: Subtenant1

Note: This example uses Windows file paths. However, the method described is fully compatible with all supported repository path types (e.g., Linux [/backups/tenantbackups/], NFS [x.x.x.x:/backups/tenantbackups/], or SMB [\\nas\backups\tenantbackups\].

To move the backup file(s) that are stored locally to the Veeam Cloud Connect repository backed by SOBR, do the following:

Tenant Actions

1. Make sure the Veeam Agent job is not running.
2. Move the VBK, VIB, and VBM files from local storage to the Cloud Provider site using a reliable drive or NAS.
   Ask the provider if they have a preferred method.
    

Service Provider Actions

3. On the Service Provider side, create a folder for the job on each performance extent of the SOBR.
   • If the files are being seeded for a Tenant, the folder structure will be:
     D:\TenantBackups\Tenant1\BackupJob1
   • If the files are being seeded for a Subtenant, the folder structure will be:
     D:\TenantBackups\Tenant1\Users\Subtenant1\BackupJob1
4. Into each job folder created in Step 3, place a copy of the VBM file
5. Next, place the VBK and VIB files accordingly:
   • If the SOBR was created with the Data Locality placement policy, place the VBK and VIB files in the newly created BackupJob1 folder on the preferred extent.
   • If the SOBR was created with the Performance Mode placement policy, place the VBK file(s) on the designated extent(s) (if applicable) and place the VIB file(s) on the designated extent(s) (if applicable) in the BackupJob1 folder.
6. In the Service Provider's Veeam Backup & Replication console, rescan the Scale-Out Backup Repository where the files were placed in Step# 2.
   During rescan, the rescan statistics window will display information about added tenant backups in the Tenant backups line.
   
   Note: Perform the rescan during non-working hours to avoid overloading the repository with excessive tasks.
    

Tenant Action

7. Update the Veeam Agent backup job
   1. Edit the initial Veeam Agent backup job through the Veeam Service Provider Console.
   2. Go to the Destination step of the wizard, and change the destination to Veeam Cloud Connect Repository.
   3. On the Credentials step of the wizard, use the tenant or subtenant credentials that match the folder where the seed was placed in Step 3.
8. Run the job.