Hi all,
I would like to enable client-side deduplication on a Windows VSA proxy so that only unique data is sent directly from the VSA to the MediaAgent DDB/backup library, instead of sending all read data from the VSA and deduplicating only on the MediaAgent side.
We are looking to this approach because the VSA proxy will be a VM inside an AVS environment, while the MediaAgent will be outside of AVS (as Azure VM).
Could you please help with:
- Required packages on Windows VSA proxy: What Commvault packages are needed on the Windows server acting as VSA proxy to support client-side deduplication (e.g., Virtual Server, File System Core, File System, or any additional components)?
- How to enable client-side deduplication for VSA backups: What are the step-by-step configuration steps (storage policy, subclient properties, etc.) to enable source-side/client dedup specifically for VSA workloads?
- How to verify client-side dedup is working: What are the step-by-step checks (job details fields, reports, DDB verification, etc.) to confirm dedupe is processing on the VSA proxy and reduced data is sent to the MediaAgent?
Thanks in advance!
Best regards,
Nikos

