Unusual size of first File-based incremental backup after VAW v6 upgrade

[eider]

== Case ID: #05888070 ==

After upgrading B&R to v12 and VAW to v6, subsequent first (and only first) File-based backup job will generate unusually large (about 50% to 80% of full backup size) incremental backup.

While doing so, Agent claims that only actually-changed size was read

Code: Select all

20.02.2023 03:32:33 :: kirie (F:) (408,0 GB) 771,6 MB read at 147 KB/s

However it also claims that restore point size is 225 GB (which matches the size of new .vib file on B&R repository).



What is even more interesting, is that SOBR offload job that ran for the newly created huge incremental has copied only fraction (in the case of this job it was about 3 GB, which is both more than actual changed size and less than .vib size) of the size before declaring that job is done.



Running subsequent jobs after that one yields expected results, with only changed data being transferred (+/- block size difference).

Code: Select all

21.02.2023 00:02:19 :: kirie (F:) (408,0 GB) 24,3 MB read at 677 KB/s [CBT]

Is this documented behavior after upgrade (possibly due to file-based jobs now using CBT)?

[HannesK]

Hello,
that sounds wrong. Let's see what support finds out.

Best regards,
Hannes