Good morning,After moving some clients (vmware) to another policy, my msdp size growed up by 8 TO....I don't understand what is "global dedup"...Does anyone can explain that? Best regards
Good morning,
If a job failed, the first attempt state is "done" then a new job is submitted, if it failed too, it's going to state "incomplete", then retry.
Why not at the first job?
Best regards.
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.
Hello,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...Best regards.
Another idea, i'm using a backup proxy with client dedup enabled, so the backup was not made by the medi server directly.So, new policy, new fingerprint...
Hello,I have 2 5230 appliances, and 2 msdp on windows servers.I have backed up on the same stu, the only change is the vmware policy name, and the accelerator unchecked.Best regards.