MSDP are islands of dedupe. Thus, the 52xx and 53xx range of NetBackup Appliances are each islands of dedupe. But they are "global" in the sense that any backup sent to an MSDP storage unit is a candidate for dedupe by that island of MSDP no matter what the source.
The term global dedupe is sometimes misused these days. There used to be a range of appliances, the 50x0 NetBackup Deduplication Appliance range which could be configured for global dedupe, but these have been discontinued. These 50x0 Appliances were also sometimes referred to as PDDO Appliances.
It sounds to me as if you have caused a change in target - and so perhaps you have multiple MSDP storage units, and you have now caused the backups to be written to another different MSDP storage unit.
Those of us with multiple MSDP storage units will usually be quite careful in our configuration of storage unit groups - so that backups always go to a specific MSDP storage unit, but so that we can also quickly cause multiple backups to go to a different storage unit, if the need should arise, without having to change multiple backup policies or multiple schedule or even multiple SLPs - but we are always mindful of perhaps your experience and do our best to minimise what has hapenned in your case.
I assume your have only NetBackup Appliances? Or do you have other vendor deduplication devices instead, or as well as?
What model are your Symantec/Veritas applliances? 50xx or 52xx or 53xx ?
How many MSDP storage units do you have?
It seems more than just policy was changed.
Without knowing what was in Backup Selection before and after the change, there is no way of telling why more data is getting backed up by the new policy.
Maybe browse backup of 3 Nov?
And then compare with browsing of 5 Nov backup?
AFAIK, fingerprint is based on the actual content of the backup data blocks, not on policy name, nor schedule name, nor SLP name, nor client name, nor VM name, nor file name, no folder name, nor volume name.
After a support call:
It's working as inteded, when you move a client to another policy, you create a new image on the msdp.
The dedup is not global.
So for exemple the same client in 10 policy make 10 times the data on msdp...
After some test on my side:
1 client and dedicated msdp, mutiple policy for this client, source and target dedup,with and without accelerator,
full and inc schedule.
I was not able to reproduce the problem....
I'll reopen the case.