Today Microsoft announced support for Deduplication in System Center Data Protection Manager (DPM). To use Deduplication together with System Center Data Protection Manager you have to meet the following criteria:
- The Server running System Center Data Protection Manager must be virtualized.
- DPM Server has to use Windows Sevrer 2012 R2
- The Hyper-V Sever where the DPM VM is running on has to be Windows Server 2012 R2
- System Center Data Protection Manager must be version 2012 R2 with Update Rollup 4 (UR4) or higher.
- The Data Storage of the DPM Server must be VHDX Files attached to the DPM VM.
- DPM VHDX files need to be 1TB of size.
- The VHDX files of the DPM Server must be stored on a Scale-Out File Server Cluster using SMB 3.0
- All the Windows File Server nodes on which DPM virtual hard disks reside and on which deduplication will be enabled must be running Windows Server 2012 R2 with Update Rollup November 2014.
- Deduplication is enabled on the CSV of the Scale-Out File Server
- It is recommended to use Storage Spaces but it is not required
- Use Parity Storage Spaces with enclosure-awareness for resiliency and increased disk utilization.
- Format NTFS with 64 KB allocation units and large file record segments to work better with dedup use of sparse files.
- In the hardware configuration above the recommended volume size is 7.2TB volumes.
- Plan and set up DPM and deduplication scheduling
- Tune the File Server Cluster for DPM Storage
The combination of deduplication and DPM provides substantial space savings. This allows higher retention rates, more frequent backups, and better TCO for the DPM deployment. The guidance and recommendations in this document should provide you with the tools and knowledge to configure deduplication for DPM storage and see the benefits for yourself in your own deployment.
To get more information checkout the following TechNet Article: Deduplicating DPM storage