I discussed your issue with the dev team and they confirmed digests recalculation shouldn't be triggered by replication job fail.
Also, the replication job should use CBT similar to the backup job behavior.
Cannot find dirty block information in the previous restore point, CBT will not be used
mcz wrote:Nobody was able to tell me exactly, why the chain has to be calculated again.
mcz wrote:But why is whole chain being calculated and not only the last restore point?
mcz wrote:And then why gets metadata corrupted (veeam tells you that on the next retry) when only the repository on which the metadata is stored wasn't available since the job started (that cannot be because only if the files are not available, they cannot get corrupted, right)?
Users browsing this forum: Bing [Bot], Majestic-12 [Bot] and 30 guests