Forum Discussion
When duplicating from one dedupe folder to another dedupe folder, and using CASO to manage it all, all the data should be in deduped form and NOT re-hydrated. If you had duplicated from dedupe folder to just a B2D, it would.
You may also want to try and turn on compression in the PD.CONF file within each media server. Turn the compression=0 value to 1
You may also want to try sending more concurrent jobs at the same time, if you have the available bandwidth?
Lastly, latency is the biggest killer for duplication/replication of data. A T1 can do 8.5GB of transfer in theory, but real world with dropped packets, latency of around 40ms, can only do around 6GB of data in 24 hours. And of course your duplication window is probably even less than that. So perhaps the expectations you have may not be realistic? (Note you didn't state your window duration or link type/quality, so this is just conjecture on my part ;-) )