Disk Utilization Report
Published : April 8, 2005 | Updated : August 17, 2005
The Disk Utilization Report provides a summary view of disk capacity, disk allocation, and usage of disk space in the DPM storage pool. The data is collected per file server and aggregated for all file servers 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 file servers or protection groups at a file server or protection group level, as specified in the report parameters. Subsequent pages, the detailed pages, show disk utilization details for each file server or protection group at a volume level.
Frequently asked questions
While you are reviewing the data in the Disk Utilization Report, you may have questions about how to use the data or interpret the report.
How do I determine if the DPM server is running out of disk space?
There are several data points that you may want to consider:
If “Disk Used” size is within 70 to 80 percent of “Total Disk Capacity,” you may soon run out of disk space. To avoid interruption of data protection activities, you should add disks to the storage pool. For more information, see How to add a disk to the storage pool.
If “Disk Used” size is very close to the “Disk Allocated” size, the replica and shadow copy 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 allocation.
If “Disk Allocated” size is close to “Total Disk Capacity” and you plan to protect a new volume, you may 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 members.
Why are disk utilization statistics reported for inactive protection groups?
If you delete a protection group but retain its associated replicas and shadow copies, the replicas and shadow copies continue to use disk space. As long as the replicas and shadow copies 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 shadow copies, 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 file servers?
No, the table only specifies the disk space allocated and used for replicas and shadow copies in the storage pool on the DPM server.
How do I determine if a synchronization log on the file server is running out of disk space?
The disk utilization data for synchronization logs is displayed in the last column of the Storage Pool Details table. The average synchronization log usage is based on the amount of replication data transferred by successfully completed synchronization jobs divided by the number of such jobs. As a general rule, an average log usage should be within 75 percent of the allocated space for the log. If the average synchronization log usage consistently exceeds 75 percent, you should minimize the risk of synchronization failure by increasing the disk space allocated for the log. For more information, see How to modify disk allocation.
To determine if a synchronization log is running out of disk space
In the DPM Administrator console, click Protection on the navigation bar.
Select the protection group associated with the synchronization log.
In the Actions pane, click Modify disk allocation.
In the Recommended disk allocations table, click Change.
The Space to allocate for synchronization log box displays the current disk allocation for the synchronization log.
Compare the allocated disk space with the log usage data in your report to determine if the synchronization log is running out of disk space.