Synch job, transfer last not working as expected

silvered.dragon

Renowned Member
Nov 4, 2015
125
5
83
Dear all I have 2 pbs in the same lan, one is for synching backups from the other one. So I'm using the remote synch job and I have set the option transfer last 7, but every day I see the number of backups incrementing instead of stay to seven, but is not transfering the same number of the backups that I have in the remote dataset that is huge, so somehow is limiting the number of backups. To fix this I'm using prune set to latest 7 and gc jobs, but Perhaps I am interpreting the meaning of this function incorrectly?

Just a point, since the title of transfer last says "The maximum amount of snapshots to be transferred (per group)" I tried to made 2 groups one type ct and one type vm to include everything but this didn't changed anything.
 
Hi,
Dear all I have 2 pbs in the same lan, one is for synching backups from the other one. So I'm using the remote synch job and I have set the option transfer last 7, but every day I see the number of backups incrementing instead of stay to seven, but is not transfering the same number of the backups that I have in the remote dataset that is huge, so somehow is limiting the number of backups. To fix this I'm using prune set to latest 7 and gc jobs, but Perhaps I am interpreting the meaning of this function incorrectly?

Just a point, since the title of transfer last says "The maximum amount of snapshots to be transferred (per group)" I tried to made 2 groups one type ct and one type vm to include everything but this didn't changed anything.
AFAIK the "maximum" refers to a single run of the sync job. Something that's already been transferred by a previous sync is not going to be deleted by a subsequent sync (except if you set remove-vanished and the snapshot was already removed on the local side). Your sync job will transfer up to the 7 newest backups per group.
 
so the correct approach to retain latest 7 snapshots on the second pbs(considering that the first pbs has a lot more), is to transfer latest 7 through the synch job and after that run a purge job that will retain again latest 7, because without the purging job, the synch job will add everyday 7 more. is this right?
 
so the correct approach to retain latest 7 snapshots on the second pbs(considering that the first pbs has a lot more), is to transfer latest 7 through the synch job and after that run a purge job that will retain again latest 7, because without the purging job, the synch job will add everyday 7 more. is this right?
Yes, I think that approach is fine. Note, you'll only get 7 more if you actually have 7 new ones on the source side, otherwise it might be less. But that detail is not relevant for the purge setting.