How to place Veeam Agent for Microsoft Windows backup chain on Veeam Cloud Connect repository, so that backup job continues backup chain

Move a standalone Veeam Agent backup to a cloud repository that is backed by a simple backup repository on the provider side.

In this scenario, assume the following:

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

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

1. Make sure the Veeam Agent job is not running.
2. Move VBK, VIB, and VBM files from the local storage to the cloud repository using a reliable drive or NAS
3. (ask the provider if they have a preferred method)
   • If you are moving the backup file(s) for a tenant:
     move files from C:\VeeamBackup\BackupJob1 to D:\TenantBackups\Tenant1\BackupJob1
   • If you are moving the backup files(s) for a subtenant:
     move files from C:\VeeamBackup\BackupJob1 to D:\TenantBackups\Tenant1\Users\Subtenant1\BackupJob1
4. In the Service Provider's Veeam Backup & Replication console open the [Backup Infrastructure] -> [Backup Repositories] section and rescan the 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 so as not to overload the repository with excessive tasks.
5. On the Veeam Agent computer
   1. If the initial job will be reused:
      1. Edit the initial backup job.
      2. Go to the Destination step of the wizard, change the destination to Veeam Cloud Connect Repository.
      3. On the Credentials step of the wizard, use the tenant\subtenant credentials that match the folder where the seed was placed in Step 2.
      4. If you use Veeam Backup & Replication 10 / Veeam Agent for Microsoft Windows 4.0, on the Backup Resources step of the wizard, click the Map backup link and select the backup file. If you use earlier versions of Veeam software, just proceed to the next step.
   2. If a new Agent job is being created:
      1. Name the job to match the folder where the seed was placed in Step 2. (Example: BackupJob1)
      2. On the Destination step of the wizard, specify Veeam Cloud Connect Repository.
      3. On the Credentials step of the wizard, use the tenant\subtenant credentials that match the folder where the seed was placed in Step 2.
      4. If you use Veeam Backup & Replication 10 / Veeam Agent for Microsoft Windows 4.0, at the Backup Resources step of the wizard, click the Map backup link and select the backup file. If you use earlier versions of Veeam software, just proceed to the next step.
      5. If the original backup job was set to encrypt backup files, enable encryption in the new job and use the same password as the original job.
6. Run the job.

Move a standalone Veeam Agent backup to a cloud repository that is backed by a Scale-Out Backup Repository (SOBR) on the provider side.

In this scenario, assume the following:

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

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

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).
3. On the Service Provider side, create a folder for the job on each extent of the SOBR
   1. If the files are being seeded for a Tenant, the folder structure will be:
      D:\TenantBackups\Tenant1\BackupJob1
   2. 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 2, place a copy of the VBM file
5. Next, place the VBK and VIB files accordingly:
   1. If the SOBR was created with the Data Locality placement policy, place VBK and VIB files in the newly created BackupJob1 folder on the preferred extent.
   2. If the SOBR was created with the Performance Mode placement policy, place VBK files on their designated extents (if applicable) and place the VIB(s) on their designated extent(s) (if applicable) in the BackupJob1 folder.
6. In the Service Provider's Veeam Backup & Replication console open the [Backup Infrastructure] -> [Backup Repositories] section and rescan the 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 so as not to overload the repository with excessive tasks.
7. On the Veeam Agent computer
   1. If the initial job will be reused:
      1. Edit the initial backup job.
      2. Go to the Destination step of the wizard, change the destination to Veeam Cloud Connect Repository.
      3. On the Credentials step of the wizard, use the tenant\subtenant credentials that match the folder where the seed was placed in Step 3.
      4. If you use Veeam Backup & Replication 10 / Veeam Agent for Microsoft Windows 4.0, on the Backup Resources step of the wizard, click the Map backup link and select the backup file. If you use earlier versions of Veeam software, just proceed to the next step.
   2. If a new Agent job is being created:
      1. Name the job to match the folder where the seed was placed in Step 3. (Example: BackupJob1)
      2. On the Destination step of the wizard, specify Veeam Cloud Connect Repository.
      3. On the Credentials step of the wizard, use the tenant\subtenant credentials that match the folder where the seed was placed in Step 3.
      4. If you use Veeam Backup & Replication 10 / Veeam Agent for Microsoft Windows 4.0, at the Backup Resources step of the wizard, click the Map backup link and select the backup file. If you use earlier versions of Veeam software, just proceed to the next step.
      5. If the original backup job was set to encrypt backup files, enable encryption in the new job and use the same password as the original job.
8. Run the job.

Move a Veeam Agent backup that is managed by Veeam Service Provider Console to a cloud repository that is backed by a simple backup repository on the provider side.

In this scenario, assume the following:

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

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

1. Make sure the Veeam Agent job is not running.
2. Move VBK, VIB, and VBM files from the local storage to the cloud repository using a reliable drive or NAS
   (ask the provider if they have a preferred method)
   • If you are moving the backup file(s) for the tenant:
     move files from C:\VeeamBackup\BackupJob1 to D:\TenantBackups\Tenant1\BackupJob1
   • If you are moving the backup files(s) for the subtenant:
     move files from C:\VeeamBackup\BackupJob1 to D:\TenantBackups\Tenant1\Users\Subtenant1\BackupJob1
3. In the Service Provider's Veeam Backup & Replication console open the [Backup Infrastructure>Backup Repositories] section and rescan the 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 so as not to overload the repository with excessive tasks.
4. Edit the initial Veeam Agent backup job through Veeam Service Provider Console
   
   1. Go to the Destination step of the wizard, change the destination to Veeam Cloud Connect Repository.
   2. On the Credentials step of the wizard, use the tenant\subtenant credentials that match the folder where the seed was placed in Step 2.
5. Run the job.

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

In this scenario, assume the following:

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

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

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).
3. On the Service Provider side, create a folder for the job on each extent of the SOBR
   1. If the files are being seeded for a Tenant, the folder structure will be:
      D:\TenantBackups\Tenant1\BackupJob1
   2. 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 2, place a copy of the VBM file
5. Next, place the VBK and VIB files accordingly:
   1. If the SOBR was created with the Data Locality placement policy, place VBK and VIB files in the newly created BackupJob1 folder on the preferred extent.
   2. If the SOBR was created with the Performance Mode placement policy, place VBK files on their designated extents (if applicable) and place the VIB(s) on their designated extent(s) (if applicable) in the BackupJob1 folder.
6. In the Service Provider's Veeam Backup & Replication console open the [Backup Infrastructure] -> [Backup Repositories] section and rescan the 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 so as not to overload the repository with excessive tasks.
7. Edit the initial Veeam Agent backup job through Veeam Service Provider Console
   
   1. Go to the Destination step of the wizard, change the destination to Veeam Cloud Connect Repository.
   2. On the Credentials step of the wizard, use the tenant\subtenant credentials that match the folder where the seed was placed in Step 3.
8. Run the job.