System Center Data Protection Manager (DPM) 2010 requires a disk that is dedicated to the storage pool and a disk that is dedicated to the following:

You can install DPM on the same volume that the operating system is installed on, or you can install DPM on a different volume that does not include the operating system. However, you cannot install DPM on the disk that is dedicated to the storage pool, which is a set of disks on which the DPM server stores the replicas and recovery points for the protected data.

DPM owns and manages the disks in the storage pool, which must be dynamic. For purposes of DPM, disk is defined as any disk device manifested as a disk in Disk Management. For more information about the types of disks that the storage pool supports and how to plan your disk configuration, see Planning the Storage Pool [pg].

If you want to manage your own additional disk space, DPM enables you to attach or associate custom volumes to data sources that you are protecting in a protection group. Custom volumes can be on basic or dynamic disks. Any volume that is attached to the DPM server can be selected as a custom volume; however, DPM cannot manage the space in custom volumes. Note that DPM will not delete any existing volumes on the disk attached to the storage pool to make the entire disk space available.

If you have critical data that you want to store, you can use a high-performance logical unit number (LUN) on a storage area network rather than the DPM-managed storage pool.

The following table lists the minimum and recommended hardware requirements for the DPM server. For more information about planning DPM server configurations, see Planning a DPM 2010 Deployment.

Component Minimum Requirement Recommended Requirement


  • 1 gigahertz (GHz) or faster

  • 2.33 GHz quad-core CPUs


  • 512 MB

    For more information about how DPM manages memory, see DPM and Memory.

  • 4 GB RAM


  • 0.2 percent of the combined size of all recovery point volumes, in addition to the recommended size (generally, 1.5 times the amount of RAM on the computer).

    For more information about configuring the DPM pagefile size, in the DPM Operations Guide, see Managing Performance.


Disk space for DPM installation

  • DPM Installation location: 1.260 GB

  • Database files drive: 900 MB

  • System drive: 1 GB

The system drive disk space requirement is necessary if you chose to install the dedicated instance of SQL Server from DPM. If you are using an existing instance of SQL Server, this disk space requirement is considerably less.
DPM requires a minimum of 300 MB of free space on each protected volume for the change journal. Additionally, before archiving data to tape, DPM copies the file catalog to a DPM temporary installation location; therefore, we recommend that the volume on which DPM is installed contains 2–3 GB of free space.

Disk space for storage pool

The storage pool does not support Universal Serial Bus (USB)/1394 disks.
  • 1.5 times the size of the protected data

    For more information about calculating capacity requirements and planning the configuration of the disks, in Planning a DPM 2010 Deployment, see Planning the Storage Pool.

  • 2–3 times the size of the protected data

Logical unit number (LUN)


  • Maximum of 17 TB for GUID partition table (GPT) dynamic disks

  • 2 TB for master boot record (MBR) disks

These requirements are based on the maximum size of the disk as it appears to the Windows Server operating system.

The following table lists the data source limits that a DPM server can protect (if it meets the minimum hardware requirements) and the recommended disk space required for the DPM server.

Platform Data source limit Recommended disk space

64-bit computers

300 data sources

Data sources are typically spread across approximately 75 servers and 150 client computers.

45 TB

See Also