Step 8. Map Backup File

If the target backup repository already stores a backup of workloads that you want to copy, you can map the backup copy job to this backup. The backup can be created by a backup job or another backup copy job.

The backup copy job will use the backup as a seed. As a result, Veeam Backup & Replication will transfer less data over network. For more information, see Mapping Backup Copy Jobs.

To map the backup copy job to a backup:

  1. At the Target step of the wizard, click the Map backup link.
  2. In the Select Backup window, select a backup that contains restore points of workloads that you want to copy.

Limitations for Mapping

When mapping a backup copy job, mind the following limitations:

  • If a backup that you plan to use as a seed is encrypted, you must enable encryption for the backup copy job. The password that you use for the backup copy job can differ from the password used for the initial job.
  • The following limitations apply to a backup that can be used as a seed:
  • If you map the backup copy job to a backup created by another backup copy job, the backup must be created with the same copy mode.
  • [For the immediate copy mode] You can map the backup copy job only to a backup created by another backup copy job.
  • [For the periodic copy mode] If you map the backup copy job to a backup created by a backup job. The backup must be created with the incremental backup method only, that is, forever forward or forward incremental.

Mapping Backup Copy Jobs Note:

To overcome the listed limitations, you can use a workaround scenario. For more information, see Creating Seed for Backup Copy Job.

  • [For the periodic copy mode] You can map a Veeam Agent backup copy job only to a backup created by the following types of jobs:
  • Backup copy job that processes backups created by Veeam Agent operating in the standalone mode.
  • Backup job created in Veeam Agent operating in the standalone mode.

Mapping Backup Copy Jobs 

I want to report a typo

There is a misspelling right here:

 

I want to let the Veeam Documentation Team know about that.