Veeam Home | Support | Downloads
Best Practices for Veeam Backup & Replication 7.0 for VMware

Veeam Management Pack Help Center  > Best Practices for Deployment & Configuration >  Understanding Veeam Backup & Replication Options > How It Works: Backup Copy

How It Works: Backup Copy

Previous page Next page Print this Topic

Table of contents

Backup copy job allows you to duplicate local backups to a secondary location (onsite or offsite).

It is important to notice that the job does not copy backup files as a whole. Instead, it creates required restore points in target location from VM data in source backup repositories. Every backup copy job creates its own folder on the target backup repository and stores to it all copied restore points. The folder has the same name as the backup copy job.

Once created, Backup Copy job will immediately start processing the latest existing restore point for all VMs included in the job.

The backup on target can be called "forever incremental": the first restore point in the chain is always a full backup. All other restore points in the chain are incremental backups.

By default, Veeam Backup & Replication keeps 7 restore points on the target backup repository in case of simple retention policy (see Simple Retention Policy section of the User Guide for details). If you plan to use GFS retention, refer to GFS Retention Policy for details.

Even if a Backup Copy job processes several VMs, it creates one backup file on the target backup repository and stores to it data for all VMs processed by the job.

Backup copy jobs do not support parallel processing. Multiple VMs in the job are copied one by one, subsequently. Data for VM disks are also copied subsequently, not in parallel.

Limitations of backup copy jobs are described in Veeam Backup & Replication User Guide (http://helpcenter.veeam.com/backup/70/vsphere/index.html?backup_copy_select_point.html).

By default, during the Backup Copy job Veeam Backup & Replication transports VM data directly from the source backup repository to the target backup repository. This type of transport is recommended if you plan to copy backup files to onsite location, or offsite over fast connections:

hiw_bu_copy_direct_zoom80

However, if you plan to transport backup data over the WAN or slow connections, it is recommended to configure a pair of WAN accelerators in your backup infrastructure and copy VM backups via these WAN accelerators:

hiw_bu_copy_wan_zoom75

The goal of WAN acceleration is to send less data over the network. To reduce the amount of data going over the WAN, Veeam Backup & Replication uses the global data deduplication mechanism. The process goes as follows:

1.When you first run the Backup Copy job, Veeam Backup & Replication analyzes data blocks going over WAN.

2.With every synchronization interval of the Backup Copy job, Veeam Backup & Replication uses the data redundancy algorithm to find duplicate data blocks in the copied backup file. Veeam Backup & Replication analyzes data blocks in the backup file on the source side and compares them with those that have been previously transferred over the WAN. If an identical data block is found, Veeam Backup & Replication deduplicates it.

As a result, only unique data blocks go over the WAN. Data blocks that have already been sent are not sent with new job sessions. This way, Veeam eliminates transfer of redundant data over the WAN.

For details of VM restore point data communication and transform, please refer to Backup Copying Process section of the User Guide.

noteNote

Source WAN accelerator can process only one task at a time.

Table of contents