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.
May I ask you if the results were the same without BitLooker enabled?
Should bitlooker work with Windows2012 deduplication and forever reverse incremental jobs, or do I need to continue using 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.BitLooker
detects if the file has been deleted and includes it into vrb.Deduplication
in Windows 2012 actually marks deduplicated data location as free thus BitLooker places that data into .vrb as well.
In other words - BitLooker does work with dedupe and reverse incremental chain in a strict accordance with all the rules I've descirbed. If you still feel that something is not working properly you can open a support case so our support team can take a closer look at your setup. Should you decide to open a case please post your case ID.