verify after sync/replication ?

RolandK

Famous Member
Mar 5, 2019
1,087
269
128
52
hi, as it seems syncing a datastore to another pbs will "inherit" the verify state of the source snapshot(s)

is there a way to unset that verified flag on/after transfer so verify can be run AFTER transfer/sync, so we can verify freshly transferred snapshots and and can use re-verify-after-30d as normal ?

and wouldn't it make sense that some verify is being included in every sucessful sync of a chunk/snapshot, i.e. it's getting either verified "in flight" or "after write" when it's not verified on the source before transfer
 
Last edited:
ah, thanks for the pointer, i searched bugzilla but did miss this ticket.

but for my curiousity - when newly pulled data chunks are already verified - why do they appear unverified at the sync target when they had not been verified at the source before ? shouldn't set pbs them as verified then ?
 
ah, thanks for the pointer, i searched bugzilla but did miss this ticket.

but for my curiousity - when newly pulled data chunks are already verified - why do they appear unverified at the sync target when they had not been verified at the source before ? shouldn't set pbs them as verified then ?
That is because during sync, already known chunks (since 4.1 limited to the same group, see [0]) can be skipped. These might however not be good anymore locally, needing a re-verification.

[0] https://git.proxmox.com/?p=proxmox-backup.git;a=commit;h=fb06e6812e75e536b8cc5f7c84a2d86c64d613ca
 
  • Like
Reactions: RolandK