Dell PowerVault DP600 - Manual (Page 57)

57
For example, while most backup software records data changes at the file level, DPM records
changes at the byte level. Depending on the type of data that you want to protect, this can
translate to a data change rate that is lower than the incremental backup might suggest.
The following table lists the data source limits that a DPM server that meets the minimum
hardware requirements can protect and the recommended disk space required per DPM server.
Platform Data Source Limit Recommended Disk Space
32-bit computers 150 data sources.
We recommend
approximately 30 to 40
servers fanning into a single
DPM server.
10 TB
Note
There is a Volume
Shadow Copy Service
(VSS) non-paged pool
limitation on x86 32-bit
operating systems. If you
are protecting data using
a secondary DPM server,
the recommended disk
space is only 6 TB.
64-bit computers 300 data sources
Data sources are typically
spread across 50 to 75
physical servers.
40 TB
Snapshot Limit
A DPM server can store up to 9,000 disk-based snapshots, including those retained when you
stop protection of a data source.The snapshot limit applies to express full backups and file
recovery points, but not to incremental synchronizations.
The snapshot limit applies per DPM server, regardless of storage pool size. When you configure
protection groups, the DPM server is provisioned for the number of snapshots to accommodate
the protection group configuration. You can use the following cmdlet in DPM Management Shell
to identify the number of snapshots the server is provisioned for:
$server=Connect-DPMServer –
DPMServerName Name $server.CurrentShadowCopyProvision
When planning your DPM deployment, you need to consider the snapshot limit as part of the
DPM server capacity. The following table lists examples of the number of snapshots that result
from different protection policies.