Aurock wrote:I assumed maybe it was because some of the blocks (in sizes veeam looks at them) might contain data other than just swap
Aurock wrote:but in one particular case, I know that the swap file is on a separate VHD, with nothing else on it. The "Swap File blocks skipped" for that VM says 1.4GB, when the actual swap file size is 32GB. Why wouldn't veeam be skipping the entire 32gb of data, effectively the entire 2nd vhd file?
foggy wrote:Correct, as Veeam B&R operates by 1MB blocks, some of them could contain also other data due to disk fragmentation and should still be fully transferred to target (hence, those are not excluded and are not accounted in the displayed amount of skipped swap file blocks).
foggy wrote:Other factor that should be considered is whether the particular job run is full or incremental. During incremental job run, swap file blocks to be skipped are excluded from the blocks that have changed since the last backup and obviously not the whole swap file is typically changed between job runs.
Besides, blocks that belong to swap file but are already marked to be skipped during previous data processing stages (zero blocks, for example) are also not accounted in the displayed amount of skipped swap file blocks (though they are accounted in the actual swap file size inside the guest OS).
Hope this makes sense.
Aurock wrote:Okay, I expected as much. Though in our case, I have the backup job set for WAN target, so that would still apply, but in 256KB blocks instead of 1MB, correct?
Users browsing this forum: No registered users and 2 guests