I have successful B2 Dedupe folder Building A then duplicate job to Dedupe folder Building B across the WAN, then duplicate job to tape in Building B. That is nirvan for me. All jobs are setup on Building B MMS where the tape drive is. If I use media server dedupe on the first part where the dedupe folder and the server are in the same buidling the 100 MB WAN gets full and the job rate is about 350 MB.
If I switch to Client side dedupe on that first job backing the local server now there is virtually no WAN traffic, the file server nic is hardly touched, but the processors that is uses are jammed and I get a full 1000MB per minute speed. I'm thinking that with the media dedupe it is comparing it to Building B's dedupe folder not Building A's where the job is running.
Also while the docs say it only uses 1 processor I see several bouncing back and forth and the BE agent is only using 4% of the cpu.
All of this gets very confusing so I hope you can follow this.
