It will consume more bandwidth, as this is copying all the necessary blocks instead of just the incremental data. The only way to avoid the merge in the backup copy job is to enable weekly archived copied, and select the “Read the entire restore point from the source backup instead of synthesizing it from increments.” This will send the data necessary to build the full backup file from the primary repository to the secondary repository on a weekly basis. If you’re running your job daily, and chose to keep 30 restore points, the first merge will take place on day 31. The merge will take place every run of the job, after the required number of restore points have been created. Merge is the process of taking the oldest incremental backup file and updating the full backup file with it. I’ll have the following restore points available to recover from: I have configured my GFS setting like this: It is designed to allow you to keep a gradually declining granularity of backups as independent restore points.Įxamples: It’s August 2 nd 2017, and I’ve been creating a single daily restore point running this job since September 8 th 2014. It uses the idea of GFS (Grandfather, Father, Son) to creates a separate, independent restore points, weekly, monthly, quarterly or annually.

How does the Backup Copy Job handle archives? This can be the same frequency as the primary backup job, or less frequent. The copy interval is how often you want to create a restore point in the second repository. It grabs blocks of data out of backup files in the primary repository and creates new backup files with these blocks in a secondary repository. It is a secondary job in Veeam Backup and Replication which helps to make additional copies, in either a local or offsite location, making it possible and easy to follow the 3-2-1 rule. It uses the backup files in an existing Veeam Backup Repository as a source to create a new set of backup files in a secondary repository.

Restore point simulator veeam