(I've had Veeam for many years and have done dozens-to-hundreds of disk expansion activities.)
I recently upgraded V12 to V13 (Windows). 13.0.1.2067
I have a concern that something changed with V13 replication jobs calculating digests. I need to understand if this is going to happen every time I expand a disk? The first time I expand a disk after the V13 upgrade? Never again because this is just some strange aberration?
I expanded a 5.8Tb disk to 6.4Tb. Backup read the entire disk (as expected) and found 42.5Gb of changes.
Replication job uses the backup repository as source and was up-to-date before the disk expansion.
The replication job "found" that 5.8Tb of data had changed on the expanded disk. There is just no way that's possible. I would have been better off just deleting the disk so it wouldn't have to calculate digests. (Note that the replication job still hasn't completed and seems to be incorrectly finding changed data on the non-expanded disks where no data was changed.)
I think this is correct:
1) Expand production disk
2) CBT reset by backup job
3) Backup job reads entire disk (calculating digests)
4) Backup compares repository data to production data (digest comparison)
5) Changed data is backed up
6) Replication job deletes snapshots
7) Replication disk expanded
CBT reset (I think, or maybe this doesn’t matter with replication jobs)9) Digests calculated
10) Replica digests compared with backup repository digests
11) Matching data skipped
12) Changed data transferred
The backup correctly found 42.5Gb of changed data. But on the replication job (steps 10-12 above), it appears that none of the data matched on the resized disk (except for or excluding the 600Gb of expanded emptiness), so all data is being incorrectly seen as changed and thus being transferred.
