Skip to main content
Question

Do you have any storage policy with no Dedupe/compression?

  • June 2, 2026
  • 2 replies
  • 22 views

Forum|alt.badge.img+10

I have a interesting issue.  My AUX copy streams are capping out at 180 GB/h despite having multiple 10 GB WAN links.  I see this issue on a Storage Policy that has dedupe and compression disabled.(due to large unique data being backed up).   Does anyone by chance have a storage policy with no dedupe or compression?   I am really curious to know what speeds you are seeing on your AUX copy streams.   I feel like these should be able to go faster, but having a hard time convincing support that there is something in CV that is restricting it.

We have set the nNumPipelineBuffers set to 900 already.  
Our Dedupe AUX copies run amazing since there are so many streams for it to work with.

 

2 replies

Forum|alt.badge.img+10
  • Vaulter
  • June 3, 2026

Hi ​@Farmer92,

When deduplication and compression are disabled on a Storage Policy, auxiliary copy (AUX copy) jobs transfer the full, unoptimized data set. This means:

Every byte of data is sent over the network (no dedupe/compression savings).

To identify the bottleneck in your AUX copy scenario, review the MediaAgent's CVPerfMgr.log. 

Look for sections labeled:
Reader: Measures disk read speed from the source.
Network Transfer: Measures data transfer speed between MediaAgents.
Writer: Measures disk write speed to the destination.

Regards,

Wasim


Forum|alt.badge.img+10
  • Author
  • Explorer
  • June 3, 2026

Wasim,

   Thank you. I’ve been reviewing the CVPerfMgr.log and CvPerfLogAnalyze.log alongside support and our network team.

   At this point, I’m hoping to get feedback from another real-world customer regarding the transfer speeds they’re seeing—similar to what’s shown in my screenshot above. However, the comparison would need to exclude AUX copies of deduplicated data, since those speeds are synthetic and reflect “effective” throughput rather than actual transfer rates.  

Thank you again