veeam backup retention policy best practices

On the Home tab, click Backup Copy and select VMware or Hyper-V.After that, the backup copy job is put on hold until a new backup copy interval begins and a new point appears on the source backup repository. At the beginning of every backup copy interval, Veeam Backup & Replication checks the source backup repository: if a new restore point has been added to the primary backup chain, Veeam Backup & Replication automatically copies it to the target backup repository. By default, a new backup copy cycle begins every day however, you can specify any time interval needed. The backup copy job runs continuously, in cycles. The backup copy job supports the GFS retention scheme, allowing you to design a long-term archiving plan. When you create a backup copy job, you define what backup file you want to copy, the target repository for storing the copy, retention policy and other settings for the copying process. The backup chain produced on the target backup repository is forever-incremental: the first file in the chain is a full backup while all subsequent restore points are incremental. Instead, Veeam Backup & Replication retrieves data blocks necessary to create a restore point as of the latest point in time and copies this data to the cloud repository. Copied backup files have the same format as those created by backup jobs, and you can use any data recovery option for them.ĭuring the backup copying process, Veeam Backup & Replication does not simply copy a backup file from one backup repository to another. For example, you can configure a backup job to create a VM backup on the local backup repository, and use the backup copy job to copy the created VM backup from the local backup repository to the cloud repository. Backup copy jobs allow you to create several instances of the same backup file in different locations, onsite or offsite.

To follow the 3-2-1 backup best practice, you can configure a backup copy job and target it at the cloud repository.

Veeam backup retention policy best practices