I keep getting alerts from SCOM 2012 SP1 telling me that the database copy is low on log volume space.
The database volume is 600 GB and has 29% free space (180 GB). Confusingly, the alert itself seems to be telling me that it has only 4% disk space free, although perhaps I am misunderstanding it (it says Value: 4, but sample value: 29). Is there some distinction between "log volume space" and normal free space on the volume that the logs are stored on? In this case, log files and databases are stored in the same location, drive E:
Should I really have 50% free disk space on the volume hosting a DAG? That seems overkill to my naive view. If it is an excessively cautious figure, what is a good figure to use? Or should I just rely on the overall disk space warning messages that SCOM handles?
Also: I thought I had set up an override to generate a warning at 25% disk free and critical error at 10%, but they don't seem to be working the way I expected. Perhaps because of the "Value: 4" that I am seeing in the alert?
Here's the alert:
Alert: The database copy is low on log volume space. The volume has reached error levels.
Source: Database Copy (log) Logical Disk Space (E:) - MBX1 (Mailbox) - SITE1
Path: MBX1.domain.local;MBX1(Mailbox) - SITE1 Last modified by: NT AUTHORITY\SYSTEM Last modified time: 7/22/2013 9:11:05 AM Alert description: TimeSampled: 2013-07-21T03:15:19.0000000-04:00
ObjectName: LogicalDisk
CounterName: % Free Space
InstanceName: E:
Value: 4
SampleValue: 29.4853801727295