Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
A Veeam Agent backup job 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 create 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 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 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 backed by a simple backup repository on the provider side.
Scenario #2
Move a standalone Veeam Agent backup to a cloud repository backed by a Scale-Out Backup Repository (SOBR) on the provider side.
Scenario #3
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.
Scenario #4
Move a Veeam Agent backup that is managed by Veeam Service Provider Console to a Scale-Out Backup Repository (SOBR) on the provider side.
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:
To move backup file(s) that are stored locally to the Veeam Cloud Connect repository, do the following:
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:
Note that the backup job name, the backup folder name, the VBM filename, and the path to the VBM must conform to naming standards for SOBR:
To move the backup file(s) that are stored locally to the Veeam Cloud Connect repository backed by SOBR, do the following:
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:
To move the backup file(s) that are stored locally to the Veeam Cloud Connect repository, do the following:
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:
Note that the backup job name, the backup folder name, the VBM filename, and the path to the VBM must conform to naming standards for SOBR:
To move the backup file(s) that are stored locally to the Veeam Cloud Connect repository backed by SOBR, do the following:
See the following scenarios in other KB articles:
Your feedback has been received and will be reviewed.
Please try again later.
Please try select less.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Your feedback has been received and will be reviewed.