Absolutely correct.hyvokar wrote:My guess is that dedup full optimization shuffles data around and rearrange it. That causes blocks to change and veeam to back them up.
It is better to perform dedupe prior to backup. Otherwise the same blocks will be backed up twice: before deduplication and after deduplication due to CBT.hyvokar wrote:So can someone confirm, should bitlooker work with windows dedupe...
Please take a look at this post regarding bitlooker behaviour with reverse incremental mode.hyvokar wrote:...and forever reverse incremental backups ?
PTide wrote:It is better to perform dedupe prior to backup. Otherwise the same blocks will be backed up twice: before deduplication and after deduplication due to CBT.
PTide wrote:Please take a look at this post regarding bitlooker behaviour with reverse incremental mode.
May I ask you if the results were the same without BitLooker enabled?This is exactly what is happening. First windows dedup, then backup. I'm just wondering, why doesnt the bitlooker zeroing seem to have desider effects.
Sdelete creates a huge file filled with zeroes and deletes it afterwards thus cleaning up space on your drive (including the deduped space). With reverse incremental that will cause backup job to place previous versions of all blocks that have been zeroed into .vrb.Should bitlooker work with Windows2012 deduplication and forever reverse incremental jobs, or do I need to continue using sdelete?
VladV wrote:And they will be picked up by the incremental or full backup when Bitlooker is disabled.
mkaec wrote:They'll get picked up even if BitLooker is enabled. The only way for them to not get picked up is if the files are created and deleted before the next backup runs. If you're doing daily backups, that's not likely to happen. When a garbage collection routine runs, it is working on blocks that have been around for more than a day.
mkaec wrote:When a file is deleted, its contents may be in a container that is shared with blocks from other files that haven't been deleted. Garbage collection goes through and repackages the blocks of the non-deleted files. This creates new/changed blocks that Veeam needs to back up.
Users browsing this forum: Google [Bot], nighteyes307 and 68 guests