The Disk Utilization Report provides a summary view of disk capacity, disk allocation, and usage of disk space in the System Center Data Protection Manager (DPM) storage pool. The data is collected per protected computer and aggregated for all protected computers or per protection group and aggregated for all protection groups.
The first page of the report, the summary page, shows disk utilization statistics for all protected computers or protection groups at a protected computer or protection group level, as specified in the report parameters. Subsequent pages, the detail pages, show disk utilization details for each protected computer or protection group at a volume level.
Frequently asked questions
While you are reviewing the data in the Disk Utilization Report, you might have questions about how to use the data or interpret the report.
How do I determine whether the DPM server is running out of disk space?
There are several data points that you might want to consider:
- If “Disk Used” size is within 70 to 80 percent of “Total Disk
Capacity,” you might soon run out of disk space. To avoid
interruption of data protection activities, you should add disks to
the storage pool.
- If “Disk Used” size is very close to the “Disk Allocated” size,
the replica and recovery point volumes are nearly full. If the
amount of protected data is expanding, you should consider
increasing the disk space allocated for replicas. For more
information, see How to Modify Disk
- If “Disk Allocated” size is close to “Total Disk Capacity” and
you plan to protect a new volume, you might need to add disks to
the storage pool or stop protecting other volumes so that you can
protect the new volume. For more information, see How to Remove Protection
Why are disk utilization statistics reported for inactive protection groups?
If you delete a protection group but retain its associated replicas and recovery points, the replicas and recovery points continue to use disk space. As long as the replicas and recovery points are retained, the Disk Utilization Report will continue to display disk usage statistics for the deleted protection group, both on the summary page and on the detail pages. Disk utilization statistics for deleted protection groups are displayed under the “(Inactive Replicas)” heading. For information about deleting protection groups, replicas, and recovery points, see Working with Protection Groups.
What does a negative change for Disk Usage Growth Rate mean?
A negative number indicates that the size of data in the storage pool is decreasing over time. A positive number indicates that the size of data in the storage pool is increasing over time.
Does the Storage Pool Details table include disk usage for protected computers?
No, the table specifies only the disk space allocated and used for replicas and recovery points in the storage pool on the DPM server.
Why is disk utilization for inactive replicas not reported correctly in the Disk Utilization Report?
For existing protection groups or protected computers, the Disk Utilization Report does not display the current information for replicas that were removed, added, or removed from protection on the day that the report is generated. Disk utilization for these replicas will be correct in reports generated at least a day after the change is made.
How do I determine whether the change journal on the protected computer is running out of disk space?
The disk utilization data for the change journal is displayed in the last column of the Storage Pool Details table. DPM sets the default for change journal space at 300 MB. For more information, see How to Modify Disk Allocation.To determine whether a change journal is running out of disk space
In DPM Administrator console, click Protection on the navigation bar.
Select the protection group associated with the change journal.
In the Actions pane, click Modify disk allocation.
Click the Protected computer tab to display the current disk allocation for the change journal.
Compare the allocated disk space with the data in your report to determine whether the change journal is running out of disk space.