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 > Retention


Previous page Next page Print this Topic

Table of contents

Veeam Backup & Replication fully automates the backup copying process and lets you specify retention policy settings to maintain the desired number of restore points for copied backups. This feature can be used to implement the most common backup scenario: local Backup job with short retention period and remote Backup Copy job that copies data offsite for long-term archival purposes.

Simple Retention

To use simple retention scheme, on the Target step of Backup Copy job wizard you just specify the number of restore points you want to keep in the target repository. Default is 7 restore points, minimal is 2. If using this scheme, you need to understand, however, the relation between the main backup job that creates restore points locally, and the Backup Copy job that creates the duplicates of restore points in a target repository.

For example, if your backup job keeps 14 restore points, and the newest restore point was created last night, say, at 11:00 PM, then after your Backup Copy job will start a new synchronization interval at 12:00 AM, it will sync that last night restore point. So, if you define 14 restore points for the main job, and 21 for the Backup Copy job, then at least 13 (or even 14) of them will be shared.

GFS Retention

The GFS retention scheme allows your backup files to comply with archiving policies and to stay independent on each other (i.e. full backups). Otherwise, all your backup files would be vulnerable to potential corruption issue: assuming that some kind of failure happened during first week and you did not figure it out, it would be then copied to the whole yearly chain, leaving you without any reliable restore point. Classic GFS retention scheme is as follows:

“Daily cycle” with 7 days retention

“Weekly cycle” with 4 weeks retention period (it will hold last full backup of each week for a month)

“Monthly cycle” 12 months retention (it will hold last full backup of month for a year).

However, you can adjust the classic schema according to your requirements or policies.

Table of contents