c) Snapshot the VM, skip (or do inline replacement of) the changed dirty blocks during transport.
So, material impact from this feature can only be seen during full backups.
Gostev wrote:they are mutually exclusive
And that's why those blocks won't be included into incremental backup with BitLooker enabled. If you disable BitLooker then CBT will pick up dirty blocks even if the files were deleted. In next run those blocks, unless you change them again, won't be copied since they are already present in previous backup. With both options enabled you will get all your changed blocks in your incremental except for those that do not belong to existing files (based on MFT data)The final MFT will have no entry for the churned blocks from the short-lived file
NTmatter wrote:Apologies for the nitpicking - I'm still a bit fuzzy on this.
Users browsing this forum: Bing [Bot], Google [Bot], Google Feedfetcher and 1 guest