Update:
This appears to be a result of changing the hashing algorithm to BLAKE3 in v13. But existing backup chains continue to use the former hashing algorithm. Thus, when a replication job that uses an existing backup chain as the source needs to recalculate digests (for example, when expanding a disk), nothing will match because the source backup chain uses a different hashing algorithm than the replication job.
This appears to be a result of changing the hashing algorithm to BLAKE3 in v13. But existing backup chains continue to use the former hashing algorithm. Thus, when a replication job that uses an existing backup chain as the source needs to recalculate digests (for example, when expanding a disk), nothing will match because the source backup chain uses a different hashing algorithm than the replication job.
Statistics: Posted by averylarry — May 20, 2026 4:14 pm
