How Backup Copy Works
Veeam Backup & Replication performs backup copy in the following way:
- [For VM backup copy jobs only] Veeam Backup & Replication connects to vCenter Servers and ESXi hosts to gather information about VMs whose restore points you want to copy.
- For backup copying process, Veeam Backup & Replication starts two Veeam Data Movers — source Veeam Data Mover and target Veeam Data Mover. Veeam Data Movers location depends on the backup repository type and data transport path. For more information, see Backup Copy Architecture.
- The first backup copy run always produces a full backup file. Veeam Backup & Replication copies data blocks that are necessary to build a full backup of a machine as of the most recent state.
Veeam Backup & Replication can copy data blocks from one or more backup files in the backup chain in the source backup repository.
- If the backup chain is created in the reverse incremental backup method, Veeam Backup & Replication copies data blocks of the latest full backup.
- If the backup chain is created in the forward or forever forward incremental backup method, Veeam Backup & Replication copies data blocks from the first full backup and a set of incremental backups.
To minimize the amount of traffic going over the network, Veeam Backup & Replication uses WAN accelerator, the data compression and deduplication technologies.
- Veeam Backup & Replication transfers copied data to the target backup repository and writes all copied data blocks to the full backup file.
- New backup copy jobs will always work in per-machine mode. In per-machine mode, data of every machine in the job is stored to separate backup files in the target backup repository.
- If you have backup copy jobs created in previous versions of Veeam Backup & Replication, they will continue to work in the same mode. In this case, if Use per-machine backup files option was disabled, Veeam Backup & Replication will create one backup file in the target backup repository and will store to it data for all machines processed by the job.
- During every next backup copy run, when a new restore point appears in the source backup repository, Veeam Backup & Replication copies incremental changes from this most recent restore point and transfers them to the target backup repository. Veeam Backup & Replication writes the copied data blocks to the incremental backup file in the target backup repository, that is, Veeam Backup & Replication creates a new restore point in the forever forward incremental backup chain.
To retain the desired number of restore points, Veeam Backup & Replication uses a retention policy. For more information, see Short-Term Retention Policy.
If you want to store some restore points for longer periods (for weeks, months or years) and enable long-term retention policy (GFS retention policy), Veeam Backup & Replication creates a forward incremental backup chain. For more information on GFS retention policy, see Long-Term Retention Policy (GFS).
In some cases, the source backup job and backup copy job may overlap. This situation can occur if the source backup job needs to transform the source backup chain.
If a specific task in the backup copy job locks the source backup chain to read data from it, and the source backup job that needs to write data to this backup chain starts at this moment (for example, for reverse incremental backup), the task in the backup copy job is put on hold. The backup copy job can continue processing other tasks that use other sources (for example, backup files created by other backup jobs). After the source backup job releases the backup chain, the backup copy job resumes processing machines in this backup chain.