I verified that his site collection was not 5554 MB as stated in Storage Metrics by:
- Looking at the Site Collection Quota page in CA, the site collection quota is set to 5120 MB and the Current storage used is 4002 MB – quite different than what is reported via storman.aspx
- The Site Collection Web Analytics report for the site collection (https://<sitecollection/_layouts/WebAnalytics/Report.aspx?t=StorageTrendsReport&l=sc) shows 4001.95 MB storage used.
- The following PowerShell cmds calculate 4002 MB of storage used:
$site = Get-SPSite https://<sitecollection>
$site.Usage.Storage / 1mb;
I stopped/started the Storage Metrics Processing timer job, ran PowerShell script to recalculate storage used, both to no avail:
$URL = "https://<sitecollection>"I then performed a backup / restore of the site collection and then an export/import... and voila! The import function recalculates the StorageMetrics table and *temporarily* resolves this issue. However, this issue will continue to reappear (see explanation below) until the solution is deployed. So... what's the actual problem and solution?
$Site = Get-SPSite -identity $URL
It appears that when a user checks out a document in a document library SharePoint is updating TotalSize field in StorageMetrics table to add the document size from the existing value when a document is checked- out and you would think they would deduct the file size from the TotalSize field in the StorageMetrics Table, once it is checked back in. Now either SharePoint is not deducting the document size upon check-in, or there is no function to account for documents which never get checked back in. Regardless, if you delete all content from a folder within a library with check-in/out enabled, then run the Storage Metrics Processing Job, check /_layouts/Storman.aspx you will see that the folders still hold a value of the former content, although that content is deleted.
The problem with exporting/importing sites is that you loose some functionaility such as workflow associations, etc. However, this discovery did lead me to the solution, which is found in the August 2012 CU. See the following article: http://support.microsoft.com/kb/2687339