Reporting Storage Size in Microsoft Exchange
In a great blog entry by Michael B. Smith, he has outlined a scripted method of obtaining the Mailbox and Public Folder store sizes on all Exchange servers in your organization.
As Michael explains, it is a common request is to find out how much disk space Exchange is using in all of the various EDB and STM files spread out everywhere. By running Michael’s fine script, you will get an output similar to this (I’ve used Michael’s own report, as I do not have a test environment with more than one server right now):
Exchange Organization Name: We Do Email best Default SMTP address for organization: e12beta.com All Exchange Servers in forest DC=e12beta,DC=com Server Name: VOLCANO Server Name: E12BETA Server name: VOLCANO Storage group: First Storage Group Store: Public Folder Store (VOLCANO) EDB file: C:\Program Files\Exchsrvr\mdbdata\pub1.edb Size: 11 megabytes SLV file: C:\Program Files\Exchsrvr\mdbdata\pub1.stm Size: 4 megabytes Store Size Total: 15 megabytes Store: Mailbox Store (VOLCANO) EDB file: C:\Program Files\Exchsrvr\mdbdata\priv1.edb Size: 6 megabytes SLV file: C:\Program Files\Exchsrvr\mdbdata\priv1.stm Size: 8 megabytes Store Size Total: 14 megabytes Storage Group total: 29 megabytes Server total: 29 megabytes Server name: E12BETA Storage group: First Storage Group Store: Public Folder Store (E12BETA) EDB file: D:\Exchsrvr\MDBDATA\pub1.edb Size: 897 megabytes SLV file: D:\Exchsrvr\MDBDATA\pub1.stm Size: 212 megabytes Store Size Total: 1,109 megabytes Store: 7-Day-DIR EDB file: D:\Exchsrvr\MDBDATA\7-Day-DIR.edb Size: 22,189 megabytes SLV file: D:\Exchsrvr\MDBDATA\7-Day-DIR.stm Size: 15,296 megabytes Store Size Total: 37,485 megabytes Store: DBI Archive Store EDB file: D:\Exchsrvr\MDBDATA\DBI Archive Store.edb Size: 4,752 megabytes SLV file: D:\Exchsrvr\MDBDATA\DBI Archive Store.stm Size: 4,288 megabytes Store Size Total: 9,040 megabytes Store: Mailbox Store (E12BETA) EDB file: D:\Exchsrvr\MDBDATA\priv1.edb Size: 92,861 megabytes SLV file: D:\Exchsrvr\MDBDATA\priv1.stm Size: 46,632 megabytes Store Size Total: 139,493 megabytes Store: Mailbox Store 2 EDB file: D:\Exchsrvr\MDBDATA\Mailbox Store 2.edb Size: 4,047 megabytes SLV file: D:\Exchsrvr\MDBDATA\Mailbox Store 2.stm Size: 18 megabytes Store Size Total: 4,065 megabytes Storage Group total: 191,192 megabytes Storage group: Second Storage Group Store: Mailbox Store 3 EDB file: D:\Exchsrvr\SecondStorageGroup\Mailbox Store 3.edb Size: 5,180 megabytes SLV file: D:\Exchsrvr\SecondStorageGroup\Mailbox Store 3.stm Size: 1,508 megabytes Store Size Total: 6,688 megabytes Storage Group total: 6,688 megabytes Server total: 197,909 megabytes Organization total: 197,938 megabytes
As you see, this text report (which can easily be piped into a file) gives you some nice information about your servers, store locations, and store sizes. For each storage group a subtotal is generated, for each server a subtotal is generated, and for the entire organization a total is generated. This presents a nice little hierarchical view of your storage usage.
The script should work on Exchange 2000, 2003, and 2007, but in order to use it you also need to create some more script files that can be found in another of Michael’s posts. However some readers asked me if I could help them in understanding what these scripts do and how to use them. I will not go into technical details on how these scripts work, the author does a much better job than me, but I can help by creating the scripts for you, placing them into a zipped file, and adding a simple installing batch.
Say Goodbye to Traditional PC Lifecycle Management
Traditional IT tools, including Microsoft SCCM, Ghost Solution Suite, and KACE, often require considerable custom configurations by T3 technicians (an expensive and often elusive IT resource) to enable management of a hybrid onsite + remote workforce. In many cases, even with the best resources, organizations are finding that these on-premise tools simply cannot support remote endpoints consistently and reliably due to infrastructure limitations.
When done, go to the %Systemdrive%\Scripts folder and run the following command: