Setting up disk space monitoring can be difficult if you have many servers with different logical drive structures, and the recommendations from the previous chapter also apply to disk space monitoring to some degree.
Package Optimization
In order to minimize the number of diskspace-enabled system health packages we recommended that you organize the disk/logical drive partitions based on a common schema on all of your servers whenever possible. The table below shows an example:
Drive Letter(s) |
Purpose |
Comments (if any) |
C |
Operating System |
|
D |
Paging File |
This drive will always have low disk space since the space is allocated to the page file |
E - G |
Database Storage |
This drive might be low on disk space if database space is pre-allocated |
K - P |
Critical Files |
Stores regular files (office documents, etc.) |
Q - R |
Non-Critical Files |
Stores non-critical files that can be deleted and disk space alerts are not needed |
If you have a uniform policy such as the one listed above then it is easy to organize your health packages, and it will also help with your server administration. For the above policy, you could create the following disk space packages:
1.Disk Space - Operating System
2.Disk Server - Database Storage
3.Disk Server - Critical Files
4. Disk Server - General
Each of these packages can then have their own threshold limits and can be applied to computers and groups according to their role(s). The 4th package (General) could have settings for all other drives that cannot be categorized.
