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=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IzMTU4IiwiaGFzaCI6IjQ3Nzg5ZWE4LTE4ZTEtNDUxNi1iOTc4LWFjZDIzZjIzYWQwMyJ9
1-800-691-1991 | 9am - 8pm ET
EN

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

Challenge

You need to place a Veeam Agent backup chain on the Veeam Cloud Connect repository in such a way that the Veeam Agent backup job continues the existing backup chain.

Cause

A Veeam Agent backup job also starts a new backup chain when you change a target location in the backup job settings. If you do not want the backup job to start a new backup chain, you can map a backup job to the previously made backups.

The scenarios below may be required in case you want to back up a large amount of data to the cloud repository using a slow network connection. In this case, the Veeam Agent backup job may fail to transfer a full backup to a remote location in a limited time period of 168 hours. To resolve this, you need to create a full backup on a local storage, move the backup file to the cloud repository with external tools, and use the backup file as a "seed" for a new backup chain.

This article describes scenarios for Veeam Agent for Microsoft Windows operating in the standalone (unmanaged by Veeam Backup & Replication) mode where you need to move a backup file that were stored locally to a Veeam Cloud Connect repository. The article covers the following scenarios:

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

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

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

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

 

Solutions

Scenario 1

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 whose name is Subtenant1.

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

  1. Make sure 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 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 place in Step 2. During rescan, the rescan statistics window will display information about added tenant backups in the Tenant backups line.
    Note: Plan the rescan in non-working hours not to overload the repository with excessive tasks.in the rescan statistics window.
  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, 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.
    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.

Scenario 2

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 whose name is Subtenant1.
Scale-Out Backup Repoistory File\Folder Naming Standards

Note that the backup job name, the backup folder, the VBM file and the path to it must conform to naming standards for SOBR:

  • Allowed alphanumeric characters: a-z, A-Z, 0-9
  • Allowed special characters: _ - . + = @ ^
  • The path and VBM file must not contain spaces. If the path or the VBM file contain spaces, replace them with underscores.

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

  1. Make sure 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 Tenent 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 on the preferred extent in the newly created BackupJob1 folder.
    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 place in Step 2. During rescan, the rescan statistics window will display information about added tenant backups in the Tenant backups line.
    Note: Plan the rescan in non-working hours not to overload the repository with excessive tasks.in the rescan statistics window.
  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\subtenent 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.
    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\subtenent 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.

Scenario 3

Move a Veeam Agent backup which 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 whose name is Subtenant1.

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

  1. Make sure 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 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 place in Step 2. During rescan, the rescan statistics window will display information about added tenant backups in the Tenant backups line.
    Note: Plan the rescan in non-working hours not to overload the repository with excessive tasks.in the rescan statistics window.
  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.

Scenario 4

Move a Veeam Agent backup which 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 whose name is Subtenant1.
Scale-Out Backup Repoistory File\Folder Naming Standards

Note that the backup job name, the backup folder, the VBM file and the path to it must conform to naming standards for SOBR:

  • Allowed alphanumeric characters: a-z, A-Z, 0-9
  • Allowed special characters: _ - . + = @ ^
  • The path and VBM file must not contain spaces. If the path or the VBM file contain spaces, replace them with underscores.

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

  1. Make sure 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 Tenent 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 on the preferred extent in the newly created BackupJob1 folder.
    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 place in Step 2. During rescan, the rescan statistics window will display information about added tenant backups in the Tenant backups line.
    Note: Plan the rescan in non-working hours not to overload the repository with excessive tasks.in the rescan statistics window.
  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.

More information

See the following scenarios in other KB articles:

  1. How to migrate a backup chain to Scale-Out Backup Repository (SOBR) — KB2236.
  2. How to migrate a backup chain created by Veeam Agent operating in the standalone mode to the Veeam backup repository — KB2321.
  3. How to migrate a backup chain created by Veeam Agent operating in the managed mode to the new Veeam backup repository or Cloud Connect repository — KB2849.
  4. How to migrate a backup chain created by Veeam Backup & Replication to the new Veeam backup repository — KB1729.
KB ID:
3158
Product:
Veeam Agent for Microsoft Windows, Veeam Backup & Replication, Veeam Cloud Connect
Version:
Any
Published:
2020-04-27
Last Modified:
2020-10-07
Please rate how helpful this article was to you:
5 out of 5 based on 1 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.