Backup Copy question(s)

[FireExit]

Hi,

We have backup jobs doing daily incremental and weekly synthetic fulls, never active fulls.
They have backup copy jobs which have been disabled for a couple of months.
Enabling them, Veeam is copying incrementals but there are aren't incrementals going back two months anymore. Not enough to go back to the last time the copy job ran.

I think it's going to copy incrementals forever, "reporting success" every time, and never make a valid backup chain. There's no active full on the Backup jobs, and no option to do weekly Active Full on the copy jobs to bring it back in sync. I can't tell what the synthetic full does to copy jobs.

Is this normal? What to do?

[Brad.Barker]

Hello! The behavior you are seeing sounds expected. Backup copy jobs that run in the periodic mode are not one to one copies of the source backup chain. Instead they intelligently capture just the data blocks that are different between what the copy job has and what the source backup job has. You can look at it from the perspective of a backup job that runs multiple times a day, and a backup copy that runs once a day. The backup copy job that would run in this situation runs once, and creates a single backup file that is an aggregate of the unique data blocks in source backup files created earlier. The end result of the copy job is to have just the blocks to be consistent with the source backup chain's latest incremental backup's state.

What you should see happen in your situation is that copy job will finish and it will result in a much larger incremental than normal, then subsequent runs will be smaller and more inline with what you'd expect. The copy job will read across the source jobs full backup and incremental just grab the data blocks it's missing. This should help as well: https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13