Exchange Disk Space Monitoring

Health Set: MailboxSpace

Exchange administrators may occasionally encounter Unhealthy states while monitoring Exchange servers. These health states can be reviewed using either Exchange Management Shell or Event Viewer.

To identify unhealthy components from the Exchange Management Shell, run the following command:

Get-ServerHealthCheck -Server <ServerName> | Where-Object {$_.AlertValue -eq "Unhealthy"}

Cmdlet’s output

Since multiple unhealthy components may be returned, this article focuses specifically on the MailboxSpace Health Set.

Additional details about unhealthy states can be obtained from Event Viewer under: Applications and Services Logs > Microsoft > Exchange > ManagedAvailability > Monitoring

Event ID: 6

Relevant events are typically logged with Event ID 6. As this Event ID is used for multiple Health Set alerts, detailed information should be reviewed from the Details tab of the event.

For further information about the MailboxSpace Health Set, use the following command:

Get-MonitoringItemHelp -Server <ServerName> -Identity <HealthSetName\Name\TargetResource>

For MailboxSpace monitoring, the identity format is: MailboxSpace\StorageLogicalDriveSpaceMonitor\EXCHDB01

Fixxing the Issue

In this scenario, Exchange generates an alert because the database volume does not meet the required free disk space threshold.

The default threshold values can be modified using Monitoring Overrides, which can be configured either globally or on a per-server basis:

• Add-GlobalMonitoringOverride
• Add-ServerMonitoringOverride

Overrides can be applied using either the Duration or ApplyVersion parameters. The ApplyVersion parameter ensures that the override persists for the specified Exchange version.

Note: The Duration and ApplyVersion parameters are case-sensitive and must be specified correctly.

The following example applies a Global Override to modify the MailboxSpace monitoring threshold across the entire Exchange organization:

Add-GlobalMonitoringOverride -Item Monitor -Identity MailboxSpace\StorageLogicalDriveSpaceMonitor -Property MonitoringThreshold -PropertyValue 40

In our environment, a third-party archiving solution controls Exchange database growth. Therefore, maintaining a minimum of 40 GB of free space on database volumes is considered sufficient.

Note: Threshold values should always be determined according to your organization’s operational and capacity planning requirements.

• Server-specific overrides are stored in the local server registry, while global overrides are stored in the Configuration partition of Active Directory.
• After applying a Global Override, allow sufficient time for Active Directory replication or trigger replication manually if immediate consistency is required.
• The Microsoft Exchange Health Manager service (MSExchangeHM) refreshes monitoring configuration approximately every 10 minutes. To apply the changes immediately, restart the service on all Exchange servers:

$servers = Get-ExchangeServer
Foreach($server in $servers){
  Invoke-Command -ComputerName $server -ScriptBlock {Restart-Service -Name MSExchangeHM}
}

• If an override for the same threshold already exists, remove the existing configuration before creating a new one by using either Remove-GlobalMonitoringOverride or Remove-ServerMonitoringOverride.

After applying the GlobalOverride, the health status was re-validated using Get-ServerHealthCheck, and MailboxSpace\StorageLogicalDriveSpaceMonitor components were observed to return to a Healthy state. Additionally, corresponding events in Event Viewer confirmed that the alerts were no longer being generated.

Exchange continuously monitors critical resources such as database disk space and generates health alerts when thresholds are exceeded. Properly tuning these thresholds can help reduce unnecessary alerts; however, administrators should ensure that capacity planning is performed carefully and that modified thresholds do not introduce operational risks.

Thanks for reading.